What an Odoo implementation costs.
Three separate things get called "the cost of Odoo", and they are paid to different people. Understanding which is which is most of the work of comparing quotes.
Licences
Per user, per month, direct to Odoo. The number depends on how many people need a login and which edition you are on. We tell you the figure during scoping and never mark it up.
Usually the smallest of the three for a business under 20 users.
Implementation
One-off. Scoping, configuration, data migration, integrations, custom modules, training and go-live support. This is where quotes differ by a factor of five, and where the difference is usually scope rather than rate.
Ours starts at £12,000 and is fixed after scoping: see the pricing page.
Running it
Hosting, backups, annual version upgrades and support. Monthly, and the part most first-time buyers forget to budget for.
Skipping it is how businesses end up three versions behind on software nobody will touch.
What actually moves the number.
Not user count, which is what most people assume. These six, in roughly this order.
How many apps go live at once
Three or four is a normal first phase. Ten is a different project, and usually a worse one.
How much custom code you need
Budget for some. Odoo covers most of an operation out of the box; custom code fills the gaps where your process and the standard product part company, and most operations of any complexity have a few. A quote with no custom line has usually not looked hard enough — and if custom code is needed, the system cannot live on Odoo Online, which changes the hosting line too.
The state of your data
One clean system is quick. Four overlapping sources with no shared product codes is the expensive case.
Integrations
Each external system is its own small project: payments, couriers, marketplaces, EDI, bank feeds.
Whether one person can decide
Decision latency is a cost. Projects with a single empowered owner finish materially cheaper.
Number of users
Last, and only really affects the licence line. Training scales with roles, not headcount.
What a cheap quote usually leaves out.
A quote that is a third of the others is not generous, it is scoped differently. Before comparing, check that each one includes these — and treat a quote with no custom development line as a scoping gap rather than a saving.
Data migration and reconciliation
Not just a contact import. Balances that agree with the old system, signed off.
Training and handover
Role by role, with written documentation. A demo is not training.
Go-live support
Someone available in the first week, and present for the first month-end.
Upgrading the custom modules
The part charged for twice if the contract is silent. Ours is in the support agreement.
Who owns the custom code
A low build fee sometimes means a licence you pay indefinitely. Both routes are set out openly.
Hosting and backups
Where it lives, who restores it, and how often that restore is actually tested.
Questions about budget.
Can you give a figure before scoping?
A range, on the first call, based on apps and data sources. A fixed number needs scoping, which is banded by headcount from £1,500 and gives you the architecture and the timeline whether or not you build with us.
Is Odoo cheaper than what we have?
Often on subscriptions, once four or five tools collapse into one. Not on year one overall, because implementation is a one-off cost the current setup has already absorbed.
Can we phase the spend?
Yes, and most do. Go live on the core, add apps once the first set is habit. Each phase is quoted as its own fixed piece.
What if the estimate is wrong?
After scoping the price is fixed. If we misjudged the work, that is our problem — which is a strong incentive to scope properly.