Total cost of ownership
The Hidden ERP Costs That Blow Up Your Budget
The headline number in an ERP business case, the licence, the implementation fee, the hardware, is the part everyone argues about. And it is rarely the number that blows the budget. The budget is blown by costs that sit below the headline, quietly growing in quarters nobody tracks, until one day the programme is 50 per cent over its total cost of ownership and no single line can explain where it went.
The obvious costs are not the problem
Licences, implementation fees, hardware and training appear in every budget, so they get scrutiny. The danger is that scrutiny ends there. The costs that sink projects are the ones that look small individually and only reveal their full weight in a proper total cost of ownership analysis. Below I walk through the categories that consistently surprise, and the budget lines that prevent the surprise. SelectHub's ERP cost research tracks the same hidden lines that trip budgets.
Integration and interfaces
Every ERP talks to something else, a CRM, an e-commerce platform, a payment gateway, a BI tool, a legacy system it must coexist with during transition. Organisations routinely budget a flat amount for "the interface" and discover there are dozens, each needing design, build, testing and ongoing maintenance. Integration is routinely one of the most underestimated lines in the whole project.
The discipline is to enumerate every interface before signing, not after. Count them, name the systems on each end, and budget for the integration architecture that keeps them in sync. This is where modernisation of the integration layer, rather than a point-to-point patch for each, pays for itself, because a decent middleware estate costs less to run than a tangle of custom links. The architectural view is covered in our piece on planning the migration step by step.
Data, the budget breaker
If there is one category that reliably breaks the budget, it is data. The extract, transform and load, the cleaning, the deduplication, the validation, the reconciliation, and the legions of business people pulled off their day jobs to make judgement calls. None of this appears in the tidy software quote, and all of it appears in the final invoice, one way or another.
I have seen data work account for a third of a project's real cost, and almost none of it counted at the start. The fix is to scope it honestly before you commit, with a real audit of what you hold, rather than a guess. For the practical method, see our field guide to cleaning master data before migration.
A client once signed a plan that set aside a single line for data migration, a few thousand pounds and a fortnight. Ten months in, the data workstream was the longest on the project and consuming more effort than the entire software build. The gap between the plan and reality was entirely a scoping problem, not a technical one.
The internal time you never price
The most invisible cost is your own people. Every ERP project pulls skilled employees away from their work for workshops, testing, training and data decisions, and their backfill cost, or the lost productivity, is rarely on the budget. It is real money, and for a mid-size organisation it can exceed the external consultant bill, because there are more of you than there are of us, and your time is not free.
Price this explicitly. Estimate the hours your key people will give, multiply by their loaded cost, and put it on the business case. It also forces honesty about capacity, because a department that "has no time" for the project was never going to adopt the system well anyway, a problem explored in why ERP projects fail.
Licence and subscription traps
The licence quote is rarely the licence you end up buying. User counts grow, modules get added mid-build, and support renewals climb. With cloud subscriptions, the trap is usage-based pricing, integration fees and the small print on user tiers. The very act of implementing a new system tends to increase demand on it, which increases the bill.
Model the licence and subscription as a curve, not a point, with realistic growth and renewal assumptions. Factor this into the cloud versus on-premise decision in legacy versus cloud ERP, because the two models hide different surprises. Whatever the platform, the lesson is identical: the number in the brochure and the number in year three are rarely the same.
Frequently asked questions
What are the hidden costs of an ERP system?
Integration, data migration and cleaning, internal staff time, training, ongoing support, licence growth and subscriptions, and the cost of change management. Together these often exceed the headline licence and implementation fee, so they must be priced up front.
How much does ERP implementation actually cost per user?
It varies widely with scope and vendor. A reasonable planning figure for mid-market ERP is several thousand pounds per user once licence, implementation, data, integration and support are counted, with enterprise projects in the millions overall.
How do you estimate total cost of ownership for ERP?
Add licence or subscription, implementation, hardware or cloud, integration, data, internal time, training, support renewals and change management, then model them over five to ten years with realistic growth. Most hidden costs fail to show up only because this full picture is skipped.
Why do ERP budgets blow up?
Mostly because data and integration work, and the cost of internal people, are under-scoped at the start, then scope creeps once the build is underway. Budgeting these honestly and controlling changes prevents most of the overrun.
Sources and further reading
The argument in this article draws on public research. Where you want to go deeper, these are the sources cited in the text and further reading.
