It's everyone's first question, and rightly so. Here's the honest answer, the one you don't always get
Let's be frank: there's no clear-cut, definitive answer to this question. And anyone who quotes you a firm price before even understanding your business is either getting it wrong, or heavily overestimating their quote to cover themselves
An Odoo project is a 100% tailor-made project, from A to Z, for one specific company. Take three competitors in the same industry, and they'll end up with three different Odoo setups, because they don't have the same process, the same priorities or the same way of working. That's lived experience, not a marketing line
The cost of a project depends on a set of factors that can't be guessed in advance: the number of modules to deploy, the complexity of your process, the volume of data to migrate, the level of customization needed, and the pace your teams can keep up
On one side, there's the Odoo license, paid to the vendor: free for a single app, and around €35 excl. VAT per user per month for the full suite. On the other, my engagement, which is the implementation service itself. These are two separate lines
I chose a single day rate, known in advance, set within a well-defined engagement: a budget of days, an adjustable pace and a duration of 1 to 12 months. That's what keeps the project adaptable and able to evolve as it goes. And it fits the way I lead it: we ship a v1 that works, we go live fast, then we iterate based on real feedback from the field
This model protects you from the fixed price inflated to cover risk, and from the tunnel effect where you pay a lot for frozen specifications that will no longer match your real needs six months later. The invoice follows reality: if the project ends earlier, you only pay for the days used. And you always know where you stand
What I offer is an indicative estimate, built on previous projects of a similar scope to yours. It's an honest order of magnitude, not a figure set in stone. Depending on the need, especially for adjustments once live, it can vary, and I tell you so clearly rather than hiding it in a reassuring quote
This estimate sets the budget of days for the engagement, and therefore the day rate, which depends on the volume of the engagement. The handover to your teams is included from the scoping stage, not tacked on at the end
My reference day rate, the framework of an engagement, and a budget simulator
How I work, how a project unfolds, who it's for and under what conditions
See it all → New projectThe approach to launch your project and go live quickly
See the approach → TakeoverThe cost and the logic when we take over a database rather than starting from scratch
Learn more →A first conversation, free and with no commitment, to pin down your project and set an honest first order of magnitude