Odoo licensing is the part everyone can price. It is also the part that usually matters least to the final number. The spread between two proposals for the same project almost always comes from everything around the licence.
The lines that move the total
- Scoping and process mapping — the work of understanding how the business runs before anything is configured.
- Data migration, which depends entirely on the state of the data you are migrating from.
- Customisation, where every requirement standard Odoo cannot meet becomes code that must be maintained through every future upgrade.
- Integrations — ZATCA, banks, payment gateways, and whatever else must exchange data.
- Training, in Arabic and English, for people who did not ask for a new system.
- Support after go-live, which is where an implementation either sticks or quietly fails.
Why cheap proposals get expensive
A low quote usually means scoping has been skipped. The requirements surface anyway — just later, as change requests, once the configuration is already built around assumptions that turned out to be wrong. The cheapest implementations are rarely the ones with the lowest quote; they are the ones where the scope was understood before the work started.
Ask what happens to the price when a requirement appears in month three. The answer tells you how carefully the scoping was done.
What to ask for in a proposal
Insist on seeing the assumptions written down: how many users, which modules, how many legacy records, which integrations, and who is responsible for cleaning the data. A proposal that states its assumptions can be compared against another. One that quotes a single number cannot.
