Odoo built around how your team actually works.

The problem

ERP implementations go wrong when the consultant optimises for the demo rather than for the Tuesday afternoon. The configuration matches the sales process that was described in a workshop, not the one with the exception everybody actually uses. Six months later there is a parallel spreadsheet, because the system cannot represent something the business does every week, and nobody wants to raise it.

What you get

• Odoo implementation configured against observed process, not described process
• Customisations and modules where standard Odoo genuinely does not fit
• Data migration with a parallel-running period and a reconciliation you sign off
• Third-party integrations — payments, shipping, e-commerce, accounting
• Training built around the roles that use it daily
• Documentation of what was customised and why, so the next person is not guessing

How it works

We watch the process before configuring it. That means sitting with the people who run month-end and order intake, and finding the exceptions they have stopped mentioning because they are normal. Configuration favours standard Odoo wherever it can — every customisation is a cost you carry at every upgrade, and we will argue against the ones that are not worth it. Migration runs in parallel until finance has closed a full period in the new system and agreed the numbers match. The cutover date is theirs, not ours.

Technical detail

What's not included

• Odoo hosting and infrastructure management as an ongoing service. We will set it up and hand it over, or work alongside your provider.
• Accounting advice. We build what your accountant specifies; we do not specify it.
• Rescuing an implementation without changing anything. If a failed rollout is failing on process rather than on configuration, more software will not fix it and we will say so.

Where we hand off, we tell you before the invoice arrives — not after.

Related services