Consulting hours and flat fees in Odoo implementation
3 min readEquipo de Nodu
Odoo implementation is usually sold in packs of hours. Odoo itself sells its Success Packs as bundles of 25, 50, 100 and 200 hours, and most partners bill in that same unit. The price a customer sees before signing is the price of an estimate.
An estimate in hours is a forecast about work that has not been done yet. When the forecast falls short, the project does not stop: the pack is extended. The customer pays for that extension, because the unit they bought was working time and not a result.
That is the decision worth understanding before comparing two quotes: not what the hour costs, but who absorbs the cost of needing more hours than were calculated.
What a customer buys in an hour pack
In an hour pack, the supplier is paid the same whether the estimate was right or wrong. If the scope is misunderstood, if source data turns up in a different format than expected, or if an integration takes two attempts, the cost of those attempts is added to the invoice.
The side effect arrives before the work starts. When every request draws down a balance, customers learn not to ask. Small improvements, such as a missing view, an automatic alert or a report that is still produced by hand, get postponed because opening a request costs hours and hours cost money. The system keeps whatever was asked for on the first day.
What a flat fee changes
With a fixed monthly fee, the unit being bought stops being time and becomes delivery. If a piece of work takes twice as long as expected, the cost to the customer is the same. The estimation risk stays with the supplier, which is the party holding the information needed to estimate.
What bounds the spend is not the price but the pace: one active request at a time, and one delivery every 48 hours from the moment that request starts. A large piece of work does not cost more; it is split across several deliveries and occupies the queue for as long as it occupies it.
Why a flat fee can be offered
A fixed price over variable work only holds if the marginal cost of an iteration is low. In a human-hours model it is not, because every additional attempt is someone's working day.
Today the building is done by agents, and human work concentrates on deciding what gets built, reviewing it and answering for it. That is the difference that makes the fee viable: not that there is less work, but that repeating an attempt stops costing a working day. The supplier's role moves from programming to designing the architecture, integrating the systems and approving what comes out.
Two conditions follow from that. Everything is built on a digital twin of the customer's installation, so a failed attempt does not touch their Odoo. And approving what gets sent, charged or modified stays with someone on their team.
What does not change
The Odoo licence is paid to Odoo and sits outside the fee, with or without one. Setting up an Odoo from scratch has its own one-off price. Version migration is inside the fee: it is done on the digital twin, in deliveries.
A flat fee also does not turn a long project into a short one. What it removes is the question of how much finishing it will cost.
To see which specific process in your company fits into a first delivery, half an hour is enough.
The Odoo hour packs cited above are those published on its pricing page. Confirmed on 17 September 2026.