Judging an ERP investment on licence price alone does not produce the right answer. Your company structure, user count, manufacturing processes, integrations, data migration and custom development needs together determine project scope. This article explains how to build a comparable total cost of ownership model.

Which lines make up the real total cost?

Depending on project structure these lines can arise. Ask for each as a separate line; a single total is not comparable.

  • Licence or subscription
  • Infrastructure / cloud
  • Analysis
  • Consulting
  • Configuration
  • Development
  • Integration
  • Data cleansing
  • Data migration
  • Testing
  • Training
  • Internal project team time
  • Go-live
  • Hypercare (intensive post go-live support)
  • Maintenance and support
  • Version upgrades
  • Third-party licences

If the cut-over method requires a parallel run, that is budgeted as its own line. A parallel run is not mandatory in every project; the method is chosen according to project risk.

Line weights differ between projects

A common generalisation says most of the budget is always labour. In practice the distribution varies:

To see which lines gain weight in your own scope, use the ERP investment and TCO pre-assessment tool. It produces no prices; it shows which lines your scope creates and their relative weight.

Read the licence line properly

Details in the licence line can break a comparison:

  • User types: the price and rights of full, limited and read-only users.
  • Concurrent or named: in a plant running shifts this difference moves the total noticeably.
  • Annual increase model: what index or rate maintenance and subscription increases follow.
  • API and data access: is access included, and are there volume or call limits?
  • Module boundaries: which function requires an additional module.

Measure migration cost before you sign

Migration cost is driven as much by data quality, the number of source systems, transformation rules, historical depth and validation requirements as by volume. These measurements turn the migration line from a guess into an estimate:

  • The share of duplicate account records (how often does the same tax number appear?)
  • The share of stock items with inconsistent unit of measure or product code
  • The share of accounts whose open balance does not match its source document
  • How many source systems the data comes from, and whether they share a common key

Split the data into three categories: master data, open transactions and historical transactions. For each, decide separately whether it is moved, archived, transformed or kept for reporting only.

Put internal effort in the budget

Most ERP budgets contain only what is paid externally. The hours key users spend in analysis workshops, data cleansing, testing and training are a real cost.

A simple method: key users per department × hours committed per week × internal hourly cost. Writing that line down also makes scope decisions easier, because the price of "let us add one more module" becomes visible.

Compare over five years

A single-year comparison hides the recurring lines. A five-year table should carry annual maintenance or subscription, infrastructure refresh, internal staff, additional user licences, version upgrades and the effort of carrying configurations through those upgrades.

The upgrade line depends on how the configurations were built: work done in the extensibility layers the platform supports is usually more predictable to carry forward, while approaches that modify standard objects can create extra work at upgrade time.

Measure the cost you avoid

Judging ERP only on the expense side is incomplete. Measurable items sit on the other side: accounting hours spent on reconciliations that will not close, stock count variance, delayed collection caused by late invoicing, and the time needed to prepare manual reports.

Measure these before the project and repeat the same measurement some time after go-live. Without measurement there can be no claim of improvement — which is why we quote no percentages in advance and instead state what becomes measurable.

Cost items to settle in the contract

  • The out-of-scope list (what is explicitly not included)
  • Acceptance criteria and who performs acceptance testing
  • Unit price and approval process for out-of-scope requests
  • Data ownership and the format in which data is handed back
  • Who is responsible for carrying configurations through version upgrades
  • Support SLA: response time and resolution time defined separately
  • The licence increase model and the price of adding users

The full selection framework is in how to choose an ERP, and assessing the implementation team in how to choose an ERP consultancy. To build this calculation on your own scope, you can talk to our ERP consulting team.

Frequently asked questions

Which budget line is missed most often?

Internal effort: the time key users spend on analysis, data cleansing, testing and training. Where the cut-over method requires a parallel run, duplicate data entry belongs in the budget the same way.

Fixed price or time and materials?

Fixed price works for scope that has been analysed and signed off. For areas where analysis is incomplete, fixed price produces either a high risk premium or a scope dispute. A common approach is to price the analysis separately and fix the development price afterwards.

How should cloud and on-premise costs be compared?

Compare over five years, including subscription increases, server refresh, backup, uninterruptible power, system administrator time and the disaster recovery scenario. A single-year comparison usually favours cloud; the five-year result depends on workload and infrastructure needs.

How is custom development cost kept under control?

By taking every development request back to the fit-gap table first: can this need be met by standard functionality, configuration or integration? If not, development goes ahead, but its method and upgrade impact are documented.