The five-year number, including the lines that never appear in a vendor proposal.
Total cost of ownership for an ERP covers licence or subscription, implementation, data migration, integration, infrastructure, training, support, upgrades and internal staff time, across a defined period — usually five years. The costs most often omitted are internal effort and upgrades, and they are rarely small.
Vendor proposals quote what the vendor sells. They do not include your people's time, the integration to systems the vendor does not supply, or the upgrade in year three. Comparing two options on proposal totals therefore compares two incomplete numbers, and the gap between them is not necessarily in the same place for both.
Licence and maintenance, or subscription. For per-user models, project user growth across the period.
Configuration, data migration, integration, testing and training. Normally the largest single line.
Servers, storage, backup, disaster recovery and the environments for test and development — or the hosting that replaces them.
Your project team, the business time in workshops and UAT, and data cleansing. Omitted from almost every comparison.
Support, enhancements, upgrades and the internal administration the system needs each year.
A hundred-user mid-market ERP decision, modelled over five years, has five cost lines and most comparisons include only the first two.
Licence or subscription is visible and negotiated hard. Implementation is quoted and scrutinised. Infrastructure is often omitted for on-premise and genuinely near zero for SaaS. Run cost — the administrator's time, the support contract, the internal super-users — is almost always omitted entirely, and over five years it is frequently comparable to the implementation cost. Upgrades are omitted on the assumption that they are included, which is true for SaaS and not for on-premise.
A model that includes all five, with the internal time costed at a realistic rate, usually produces a different ranking than the quoted-cost comparison. It also produces a more useful conversation, because the largest controllable line is often run cost, and that is affected by choices — how much customisation, how standard the processes, how well documented the system — made during implementation.
| Term | What it means |
|---|---|
| Licence or subscription | The cost of the software right, recurring or perpetual. |
| Implementation | Configuration, development, migration, testing and training. |
| Infrastructure | Servers, storage, network, database and their refresh cycle. |
| Run cost | Support, administration, and the internal time nobody budgets. |
| Upgrade cost | The periodic cost of staying current, which on-premise is a project. |
Data cleansing and UAT are client work. Excluding them understates every option, and unevenly.
A low entry cost with a high subscription inverts over five years. Model the whole period.
On-premise upgrades are projects with real cost. Cloud updates need regression testing each cycle.
Few ERPs stand alone. Interfaces to banking, eCommerce, payroll and carriers all cost to build and to maintain.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Cost per user per year, fully loaded | A comparable figure across options, once everything is included. | |
| Implementation as a multiple of licence | A high multiple signals heavy customisation and future maintenance. | |
| Internal effort hours | The cost treated as free, which over five years rarely is. | |
| Cost of change requests after go-live | Whether the system fits or is being continuously adjusted. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.