The five components of ERP cost
Every ERP quotation, whatever its format, resolves into five components. Quotations become comparable once you force each vendor to separate them.
Where ERP money goes
| Component | What it covers | Typical share of five-year cost |
|---|---|---|
| Licensing or subscription | Per-user or per-module fees, recurring annually | Significant, but rarely the largest |
| Implementation | Configuration, process design, testing, go-live support | Frequently the largest single line in year one |
| Data migration | Extracting, cleansing, mapping and loading existing data | Consistently the most underestimated |
| Customisation | Development beyond configuration, plus its ongoing maintenance | Highly variable — and the line that compounds |
| Support and change | Annual support, upgrade re-testing, post-go-live change requests | Accumulates quietly across years two to five |
The licence-price illusion
Buyers routinely shortlist on per-user licence cost because it is the only number available early. It is also the number least correlated with what you will actually spend. Odoo publishes low per-user pricing and has a free Community edition; a Kuwaiti implementation with substantial customisation can still cost more over five years than a higher-licence platform implemented close to standard.
The useful comparison is total five-year cost including implementation, migration, customisation, support and a realistic allowance for post-go-live change. Ask every vendor to model it. The quality of their answer is itself informative.
What genuinely moves the number
- Number of legal entities — each one adds configuration, consolidated reporting and its own go-live coordination
- Number of branches and warehouses — rollout logistics and site-specific process variation scale with these
- Functional scope — manufacturing and service modules add disproportionately more design and testing effort than finance or sales
- Integration count — each integration carries specification, testing and a permanent maintenance obligation
- Data migration depth — source data quality drives this far more than data volume does
- Customisation volume — this is the only driver that increases cost every year rather than once
- Training scope — role count, not headcount, determines training effort
- Internal project capacity — where it is thin, consultants absorb the gap and bill for it
Costs that appear after signature
- Data cleansing, when source quality turns out to be worse than assumed
- Additional user licences, as departments outside the original scope request access
- Report development, when the reports the business actually needs were never specified
- Integration rework, when a third-party system changes its interface
- Backfill for internal staff seconded to the project
- A second training round, when adoption after go-live proves weaker than expected
Getting quotations you can compare
Four requirements to put in your RFP
- 1
Separate the five components
Require licensing, implementation, migration, customisation and support to be priced as distinct lines.
- 2
Fix the assumptions
State user count, entity count, module scope and integration list yourself, so every vendor prices the same thing.
- 3
Require a change-control process
Ask how out-of-scope requests are priced and approved. A vendor without a written process will invoice you for one anyway.
- 4
Ask for a five-year total
Including annual support, licence escalation and an allowance for upgrade re-testing of any custom work.
Our ERP cost calculator classifies your project and identifies which drivers will dominate your quotation.
Compare ERP systemsControlling cost without damaging the outcome
The most effective cost control in an ERP project is not negotiating the licence rate. It is deciding, deliberately and in writing, which of your processes will adapt to the system and which the system must adapt to. Every item in the second list has a price, and the price recurs.
Cost discipline that works
- Adopt standard process wherever the difference is preference rather than competitive advantage
- Migrate opening balances rather than full history unless there is a specific legal or operational need
- Phase the rollout so that later phases are priced with real knowledge from earlier ones
- Keep a written register of every customisation and the reason for it
- Budget explicitly for upgrade re-testing from day one
- Commit real internal resource — every gap you leave is filled by a billable consultant