Start with the constraint, not the platform
Most selection exercises begin with a feature matrix and end in a tie. The useful starting question is narrower: what specifically breaks today? A nine-day month-end close, unreliable WIP visibility and manual GST assembly are constraints. "We need a modern ERP" is not.
When the constraint is written down and quantified, the platform question usually answers itself within two weeks rather than two quarters.
Where Odoo is the stronger choice
Odoo suits manufacturers whose commercial edge lives in a non-standard process — configure-to-order pricing, hybrid job and process costing, or service contracts attached to installed equipment.
- Process differentiation that a standard template would flatten
- Appetite to own configuration internally after go-live
- Multi-entity operations that do not carry heavy global statutory load
- A need to ship changes in weeks, not release cycles
Where SAP remains the right answer
SAP earns its cost where statutory complexity is genuinely global, where group consolidation and audit expectations are set by a parent company, or where the customer base contractually expects a tier-one system of record.
- Multi-country statutory reporting across many jurisdictions
- Parent-company mandates on the group system of record
- Deep industry-specific compliance already encoded in standard modules
The five-year cost picture
Across our implementations, licences account for a minority of five-year spend. Implementation, data migration, integration and post-go-live change dominate. A platform that internal teams can safely change is therefore cheaper over time even when its sticker price is comparable.
Model the cost of the twentieth change request, not the first. That is where the two options diverge.
How we run the decision
We run a four-week discovery that produces a validated process model, a data-quality audit and a costed comparison against both options. The output is a decision document the board can sign, not a vendor pitch.