Odoo · ERP · Peru
What a professional Odoo implementation proposal should include
A proposal you can hold someone to has eleven things in it. Most of the proposals companies show us are missing four or five, and the gaps are always where the disputes happen later.
Last updated: September 2026
Progress by phase
Discovery100%
Functional design100%
Configuration78%
Migration45%
Testing20%
Training0%
Deliverables
1. Scope, stated positively
Which modules, which legal entities, which warehouses, which processes. Not a module list, but the cycles the system will run.
2. Exclusions, stated explicitly
What is not included. This is the single most useful section of any proposal, and the most frequently absent.
3. Deliverables per phase
What you receive at the end of each phase, in a form you can inspect: a scope document, a configured environment, signed reconciliations, a test log, training material.
4. Responsibilities
Who decides, who configures, who validates data, who approves reconciliations. Projects slip because this was never written down, not because the software failed.
5. Acceptance criteria
How each phase is declared finished. Without this, "done" is an opinion.
6. Data migration scope
Which entities, which periods, who cleanses and who validates. Migration is where the largest unplanned effort hides.
7. Integrations, itemised
Each one named, with what it does and what it does not. Electronic invoicing in particular should never be implied.
8. Training
Roles, hours, whether it uses the company’s own data, and what material remains afterwards.
9. Timeline with dependencies
Not just dates, but what each date depends on from the company. A calendar that assumes instant availability of key users is decorative.
10. Change control
What happens when scope changes: how it is documented, estimated and approved. Every project changes; only some projects handle it.
11. Post go-live support
What is covered, for how long, with what response expectations, and what happens at the first monthly close.
If a proposal has no exclusions section and no acceptance criteria, the price is not really a price.
Frequently asked questions
Should the proposal include a fixed price?
It can, if the scope is genuinely fixed and the data has been inspected. A fixed price on unseen data is either padded or about to become a change request.
How long should a proposal be?
Long enough to contain the eleven points. Precision matters more than length; a clear ten-page proposal beats a vague forty-page one.
Is a discovery phase worth paying for separately?
Often yes. A paid discovery that produces a real scope document is cheaper than a free estimate that turns out to be wrong.