Stuart Totterdell
Technical Director
Every few years, someone in your business raises the topic. The ERP is old. The ERP is slow. The ERP cannot do what we need it to do. And so begins the cycle: the discovery workshops, the vendor demos, the six-figure proposals, the eighteen-month implementation timelines, the promises that this time it will be different.
It will not be different.
ERP replacement projects in the mid-market fail at an astonishing rate. Not because the technology is bad - the platforms are often perfectly capable - but because the fundamental model is broken. You are being asked to rip out the nervous system of your business, replace it with something entirely new, and keep operating while you do it. That is not transformation. That is surgery without anaesthetic.
And yet the industry keeps selling it. Because ERP replacement is enormously profitable - for the vendor, the implementation partner, and the consulting firm running the programme. It is less profitable for you, the business that is about to spend half a million pounds and two years of management attention on a project that has a coin-flip chance of delivering what was promised.
Why ERP projects fail
Let us be honest about what actually goes wrong. It is not usually the software. It is the gap between what the business thinks it needs and what it is actually ready for.
Most mid-market companies do not have clean data. They do not have documented processes. They do not have internal capability to manage a complex technology programme. And the implementation partner's job is not to fix those things - it is to configure software. So you get a shiny new system sitting on top of the same messy foundations, and within six months the workarounds start multiplying, the spreadsheets reappear, and you are back where you started, except now you also have a large invoice and a demoralised team.
The dirty secret of ERP is that the system was never the problem. The problem is what sits around it: the manual processes, the disconnected data, the tribal knowledge, the shadow systems that actually run the business. Replacing the ERP does not fix any of that. It just moves the mess to a new address.
The alternative nobody is selling you
What if you did not replace the system? What if, instead, you made it work? This is not a radical idea. It is, in fact, how most of the world's largest companies operate. They do not rip and replace. They build integration layers. They create orchestration platforms that sit on top of existing systems and connect them. They normalise the data, automate the workflows, and add intelligence where it matters - without touching the core system at all.
This approach is faster, cheaper, lower risk, and more reversible than replacement. It does not require a two-year programme. It does not require a full data migration. It does not require retraining every user in the business. And critically, it delivers value in weeks, not years.
The reason you have not been offered this is simple: there is less money in it for the people selling to you. An overlay platform does not generate a six-figure licence deal. A phased integration programme does not require a team of twelve consultants for eighteen months. It is a better outcome for the business, but a worse outcome for the supply chain — and that is why you keep hearing about replacement instead.
Your ERP is not the bottleneck. Your operations are.
If you stripped away every frustration you have with your current system and traced it back to the root cause, you would find the same things every time: data that is not connected, processes that depend on specific people, reporting that requires manual extraction, and decisions that are made on gut feel because the information is not available in time.
None of those problems require a new ERP. Every single one of them can be solved by structuring what you already have.
Connect the systems. Normalise the data. Automate the handoffs. Build a reporting layer that gives leadership real-time visibility. Add AI where it is safe and useful - summarising, categorising, flagging exceptions, recommending actions. Do all of this on top of what you already run, without the risk and cost of replacement.
The honest conversation
If someone is telling you that you need to replace your ERP, ask them three questions:
First: what specifically will the new system do that we cannot achieve by integrating what we already have? If the answer is vague, that is your answer.
Second: what is the total cost of ownership over five years, including implementation, change management, lost productivity during transition, and ongoing support? If they hesitate, that is your answer.
Third: what happens if it goes wrong? If there is no credible rollback plan, that is your answer.
Your ERP is not great. I know that. But it works, your team knows it, and your business runs on it. The smart move is not to blow it up. The smart move is to build around it - quickly, cheaply, and with measurable results from month one.
Stop listening to people who profit from your dissatisfaction with the status quo. Start building systems that make the status quo work harder.
