What does an ERP system cost for an SME?
By Dennis Jacobs — twelve years of ERP experience in manufacturing
The question “what does an ERP system cost” has no honest single-number answer, and whoever gives you one is usually selling something. What we can do: show where the costs sit, which rules of thumb are common, and where projects quietly get more expensive than the quote.
The four cost blocks
Every ERP project consists of the same four blocks. Licences or subscriptions: what you pay the vendor, these days usually per user per month. Implementation: the partner that configures, migrates and delivers. Internal work: the hours of your own people — key users, project management, testing, training. And the years after: maintenance, changes, new integrations.
The quote you receive almost always covers only the first two blocks. You pay the other two just as surely — only to yourself — and they are underestimated most often.
The rule of thumb you should know
A common industry rule of thumb: budget one to two times the annual licence cost for the implementation, and more with heavy customisation or a difficult migration. It's a rule of thumb, not a guarantee — but when a quote deviates far from it, in either direction, that's worth a question.
There is no tidy formula for the internal work, but there is an honest warning: an implementation in which your own people get no serious time doesn't get cheaper. It gets longer.
Where projects quietly get more expensive
Change orders rarely come out of nowhere. The usual sources: a scope that only sharpens during the build, data migration that disappoints because nobody looked at the data beforehand, integrations that were supposed to “just come with it”, and licence tiers that end up higher after go-live than discussed during the demos.
All of these share one root: they grow where preparation was thin. Every euro you invest before the selection in sharpening processes and data comes back multiplied during the project.
Subscription or one-off?
Nearly the whole market has shifted to subscriptions (SaaS). That lowers the entry cost and makes maintenance more predictable, but it changes the arithmetic: over five to ten years, a subscription is not by definition cheaper. Always calculate a project over its expected lifetime, not over the first year.
How to force an honest price
Ask every vendor for the same breakdown: licences per user tier, implementation per phase, what happens on overrun, and what a change after go-live costs. A vendor unwilling to give that breakdown is telling you something too.
And the biggest cost decision happens before the quote: knowing what you need. A selection based on sharp requirements prevents both the overpriced system and the cheap one that almost fits.
