What does an ERP really cost over five years?

Your ERP vendor's quote lists licences or subscriptions and a basic implementation. What it covers is on average one fifth of what the project really costs you over five years. The other 80% sits in six to eight further cost lines that rarely appear explicitly in the quote. Not because the vendor wants to mislead you. Without your context they simply cannot estimate them. It is a shared responsibility, so you are better off starting any ERP project well prepared.

In short: Over five years an ERP implementation costs on average two to five times the original quote. The quote typically covers licences and a basic implementation, roughly one fifth of the real cost. The remaining eighty percent sits in items such as data migration, integrations, customisation, training, internal time and maintenance. Budget those eight categories upfront and you negotiate harder and avoid surprises after go-live.

Below you will find the eight cost categories, the 2-5x rule and the three biggest pitfalls we encounter after go-live. Background on integrations and workflows around an ERP is on our page about business software and ERP integrations.

The 1-in-5 rule: what a quote covers and what it doesn't

The average split of a real five-year TCO (total cost of ownership) looks roughly like this. The percentages are guidelines drawn from published ERP cost analyses and from what we see in projects, not a measured average for your sector. Treat them as a starting point rather than a forecast. What does your quote explicitly cover?

Cost category	Share of 5-year TCO	In a standard quote?
Licences or subscriptions	15-25%	Yes
Basic implementation	20-30%	Yes, though understated
Customisation and extensions	5-15%	Often not
Integrations with satellite systems	10-20%	Seldom in full
Training and change management	5-12%	No
Internal team time	10-15%	No
Operations and support	10-15%	Partly (year one)
Upgrades and technical debt	5-10%	No

These ranges come from the ERP projects semanu guided at several small and mid-sized manufacturers, not from vendor brochures. They are indicative. The bottom of the range is a straightforward SaaS project with little customisation. The top is an on-premises system with heavy customisation and six or more integrations.

Add up the "Yes" lines and you reach 35 to 55 percent of the real TCO. In practice the covered share is even lower, because the basic implementation in the quote is almost always understated. Hence the rule of thumb: multiply the quote by 2 to 5 for a realistic five-year expectation.

The eight cost categories

1. Licences or subscriptions (15-25%)

This figure is correct in the quote, though only for year one. What is missing: annual indexation (3 to 7% with virtually every vendor), extra modules that "turn out to be necessary" later and growth in the number of users. SaaS contracts revisit the seat count every year. On-premises contracts hide it in maintenance fees of 10 to 20%.

2. Basic implementation (20-30%)

The figure in the quote assumes a "standard configuration". How far your business deviates from that standard determines the actual hours. The vendor only learns this after the discovery phase, which they usually run themselves after signature and at change-order rates. An independent analysis before you sign makes this number realistic.

3. Customisation and extensions (5-15%)

Every deviation from the standard costs money to build and keeps costing money to maintain, since upgrades can break customisations. Companies that have not documented their processes well find most of their surprise costs here.

4. Integrations with satellite systems (10-20%)

The largest blind spot. CRM, e-commerce, WMS, MES, CAD, BI, payroll, EDI: every connector costs money to build, to maintain (on average 15% of the build cost per year) and again at every ERP upgrade. Forgotten integrations are among the three biggest causes of budget overruns after go-live. The pitfalls that come back most often are covered in the five ERP integration mistakes.

5. Training and change management (5-12%)

Almost always under-budgeted. An ERP rollout needs at least 2 hours of training per end user, 8 to 16 hours per super user and ongoing refreshers throughout year one. On top of that comes the productivity dip in the first three months. It never appears on a quote.

6. Internal team time (10-15%)

Project managers, key users and management together often spend 500 to 1,000 person-days on a mid-market ERP implementation. Multiply by an average daily rate and you see why this is not negligible. On an implementation with 500,000 euros of external cost, internal time often adds 200,000 to 300,000 euros.

7. Operations and support (10-15%)

Hosting (bundled into SaaS licences), monitoring, backups, security audits, user support and an ERP administrator. Many companies only discover in year two that this needs a full-time role.

8. Upgrades and technical debt (5-10%)

A major version upgrade comes every two to four years. On-premises, that is a project of at least a few dozen to over a hundred person-days. With SaaS it looks "free". Even so, every customisation needs to be validated again. And every shortcut from the original implementation (a small workaround, an undocumented tweak) shows up on this bill.

Three patterns that blow up every ERP budget

Pattern 1: undocumented exceptions

"We have three sales processes," says the head of sales. In practice there turn out to be nine, each with its own exceptions. The vendor quotes for three and discovers nine during implementation. The extra six become expensive change orders. This is by far the number one cause of budget explosions.

Pattern 2: integrations that were "out of scope"

The CRM, the pricing engine, the CAD system, production planning. During scoping people often say "we'll do that later". In year two it becomes clear that the ERP delivers only half its value without those integrations. Suddenly they are back on the roadmap, urgent and without any negotiating leverage.

Pattern 3: adoption costs that were never on paper

Training was budgeted for 80 people. It ended up being 130. The productivity dip lasted not 6 weeks but 4 months. In the first three months after go-live, 30% of orders were routed by key users instead of the system. None of those costs appear on a quote. All of them are foreseeable.

From our practice

At one of our clients the ERP implementation was budgeted at 60,000 euros. Two years in, 40,000 euros had been paid and the project was stopped without a working system. There was no single big mistake behind it. It was an accumulation: promised export documents turned out not to be part of the delivery and several functions behaved differently than in the demo.

So the question is not only what an ERP costs. The question is whether what was promised is actually delivered. One acceptance criterion per promised function, written down before signing, makes that gap visible before the first invoice instead of after the fortieth.

Out of respect for the client and the vendor we name no names.

How do you budget realistically?

Three principles we apply in every project:

• Document first, ask for quotes after. A process map including exceptions, an integration map and acceptance criteria, before you request a proposal. Only then can a vendor quote be verified.
• Budget by category, not by vendor. Each of the eight categories above gets its own line in your five-year TCO. Whatever the vendor covers, they cover. Whatever they don't, you set aside separately.
• Plan a buffer of 25 to 40%. Even with good documentation an ERP remains a complex project. The buffer is not insurance against bad planning. It acknowledges that you cannot fully know the future.

Frequently asked questions

What does an ERP really cost over five years compared to the quote? The average five-year TCO is 2 to 5 times the initial vendor quote. The quote typically covers 20 to 35% of the real cost. The rest sits in customisation, integrations, training, internal time, operations and upgrades.

Which cost items are most often missing from a quote? Integrations with satellite systems (CRM, e-commerce, WMS, CAD), change management and training, internal team time, upgrade costs and the technical debt every implementation shortcut leaves behind.

How much should I budget for integrations? 10 to 20% of the total five-year TCO. For each integration, plan the build cost, 15% per year for maintenance and a new validation at every ERP version upgrade.

Why do so many ERP budgets run off the rails after go-live? Three recurring reasons: undocumented exceptions in the business processes, integrations that were "out of scope" but turned out to be essential and adoption costs that were never budgeted. All three can be made visible before the contract.

How do I get a realistic cost estimate before signing? Through an independent business analysis before you choose a vendor. A documented process map, an integration map and acceptance criteria make every vendor quote verifiable.