Where does an ERP really save money?
An ERP saves where you currently wait, enter things twice and fix them afterwards, not on the licence. The three items that really drive a budget appear on no invoice: waiting time between a requirement and its delivery, duplicated work caused by separate data states, and the cost of errors corrected after the fact. Negotiation still happens over what is visible, licences and day rates, because that is what appears in quotes. In more than 25 years of project work we keep seeing the same three.
Item one: the waiting
A requirement from sales sits in the queue for three months. The report controlling has been asking for has not arrived in a year. The new price list goes live two weeks late. Each of these waits costs business, it just never shows up in any project statement.
The test is simple: how long does it take in your company from "the business needs X" to "X is live"? If the honest answer is measured in quarters, the waiting is very likely your most expensive ERP item. The cause almost never lies in a single bottleneck, but in unclear processes, ambiguous data and the question of who is allowed to decide.
Item two: the duplicate work
If sales, finance and logistics each maintain their own view of the same customer, every change is entered three times and every report is reconciled three times. People use Excel to compensate for what the system does not hold unambiguously. This work is invisible because it is spread across many desks. Added up, it is often a full position, in larger companies several.
Item three: the error costs
A wrong delivery, a duplicate payment, a quote on an outdated price basis: individual cases look small, the sum does not. Errors arise where rules are contradictory and the system mirrors exactly what it was given. A new system changes nothing about that. It only makes the contradictions visible faster.
In the projects we have seen, the waiting was almost always more expensive than the project. It just had never been added up before.
Why the order of work decides the economics
All three items share the same root: processes and data foundation no longer support the business. That is why saving money in ERP does not start with the licence negotiation, it starts with the order of work: first clarify the processes and the competitive advantage, then clean up the data foundation, then adapt the system. Whoever reverses the order automates their problems and pays for them in operations afterwards, week after week.
McKinsey puts the share of large programmes that overrun budget or scheduleat 65 to 80 %. It is almost never the technology. It is exactly the patterns that also create the three quiet items: unclear responsibility, ambiguous data, postponed decisions.
The first step: make the items visible
Before you invest in licences, a project or AI, an honest look at where you standpays off: where is the business waiting for the system? Where is data entered twice? Where do errors arise from contradictory rules? These three questions can be answered in days, not months. Let us look in a conversation at where your three items sit, senior-led, with Business Central as home.
Frequently asked questions
Does an ERP change automatically save costs?
No. A change lowers none of the three quiet items if processes and data foundation stay unchanged. It only moves the costs into a more modern system.
How do I find out what the waiting costs us?
Messen Sie die Zeit von Anforderung bis produktiv für die letzten zehn Änderungen und legen Sie den Geschäftswert daneben. Das Ergebnis ist meist deutlicher als jede Budgetdiskussion.
Do licence costs not matter then?
They do, but they are the smallest and the best-negotiated item. The levers with substance sit in processes, data and decision paths.
