The Real Cost of a Failed ERP Project
How much does a failed ERP implementation actually cost? More than the software. Here are the real numbers from a real project — and how an upfront audit would have prevented it.
The Project Nobody Talks About
I worked with a business that had spent 18 months and over £150,000 on an ERP implementation. They had the software licences, the customisations, the integrations — and a system that nobody in the business could actually use.
The production team had reverted to spreadsheets within three weeks of go-live. The finance team were running parallel manual processes because they didn't trust the data. The MD was spending 15 hours a week in operational meetings that should have been handled by the system.
That £150,000 was written off. The system was eventually decommissioned and replaced. The total cost — software, implementation, internal time, lost productivity, and the replacement project — was closer to £250,000.
The frustrating part? A £10,000 operational audit before they selected the software would have identified every problem that later killed the project.
Why ERP implementation failure is so common in this sector
ERP implementation failure in the print and embroidery sector follows a predictable pattern. The same five mistakes appear across almost every failed or struggling implementation. Manufacturing ERP software is not inherently unreliable — but it is almost always implemented without the right brief, the right oversight, or the right internal ownership.
The Real Cost Breakdown
When an ERP project fails, the cost is rarely just the software licence. Here's what the full picture looks like:
Software Licences: £15,000–£50,000+
The licences are usually the smallest cost. But they're the most visible, which is why they get the most attention. Most businesses focus on negotiating the licence fee down, while the real costs are accumulating elsewhere.
Implementation: £20,000–£80,000
Implementation fees cover configuration, data migration, training, and go-live support. The problem is that these are estimated based on the vendor's standard template — not your actual business. When the template doesn't fit, the costs escalate.
Internal Time: £30,000–£100,000+
This is the cost that never gets measured. The project manager who spends 20 hours a week on the implementation instead of their day job. The production manager who attends requirement workshops. The finance team who have to run dual processes during transition. In the project I mentioned above, internal time accounted for roughly half the total cost.
Lost Productivity: £20,000–£60,000
During and after a failed implementation, productivity drops. Orders take longer to process. Errors increase. The team spend more time working around the system than working in it. This cost continues for months or years after the implementation is abandoned.
Cost of Replacing: £50,000–£150,000
If the implementation fails completely and you need to start over, you're looking at the entire cost again — plus the damage to team confidence and the reluctance to invest in a second system after the first one failed.
The five patterns behind every ERP implementation failure
The print, embroidery, and decoration sector is not like manufacturing or distribution. Every order can be different. Personalisation data has to flow from order to production. Artwork approval is part of the workflow. Stock might be blank goods, finished goods, or held for specific customers.
Generic ERP systems are not designed for this. And even sector-specific systems need to be implemented correctly.
The most common failure pattern I see:
- No independent vendor brief. The business talks to vendors first, sees demos, and makes a decision based on presentation quality rather than fit.
- Implementation scoped by the vendor. The vendor scopes what their software does, not what the business needs. Gaps are discovered after go-live.
- No one accountable for outcomes. The project has a project manager, but nobody whose job depends on the system actually working for the business.
- Employee buy-in assumed, not earned. The team who will use the system every day were not meaningfully involved in the selection or design.
- Data quality ignored. The implementation proceeds on the assumption that existing data can be migrated as-is. It can't.
What independent ERP oversight would have prevented
In the case I described at the start, an operational audit would have identified:
- The ERP didn't handle decoration methods the way the production team worked
- The eCommerce integration gap couldn't be bridged by the chosen platform
- The data migration would require months of preparation, not weeks
- The implementation timeline was unrealistic given the business's seasonal peaks
- The training approach assumed digital literacy that didn't exist on the production floor
Every single one of these was identified after go-live — when fixing them cost ten times what it would have cost to address them before selection.
The 3x Clarity Guarantee
The Clarity Audit costs between £2,500 and £12,000 depending on the size of your business. It comes with a guarantee: if the report doesn't identify at least three times the fee in recoverable cost or lost revenue, you get a full refund. No conditions. No questions.
Against a £150,000 ERP failure, that £10,000 audit isn't insurance. It's near-certain cost avoidance.
Thinking about a new ERP?
Before you talk to vendors, talk to someone who's seen this play out dozens of times. Our ERP implementation programme is built around exactly this — independent oversight, vendor accountability, and a clean exit if the project isn't tracking. Or start with why ERP projects fail in decorated goods businesses.
Plain English. No jargon. No vendor agenda.
A Clarity Audit maps your actual operations, identifies the changes that will make the biggest difference, and gives you a plan you can act on. No reports you'll never read. No recommendations you can't implement.
See ClarityMore in this topic
Cloud ERP for a Print Business: What Changes When You Move Online
Cloud ERP for small print businesses: what changes, what you need to check, and the hidden traps that on-premise systems don't have.
What Is ERP? And Does Your Decorated Goods Business Actually Need One?
A jargon-free explanation of what ERP actually does for a decorated goods business — and how to know whether you need one or are being sold something you don't.
ERP Selection for Decorated Goods: A Plain-English Buying Guide
How to choose an ERP for print, embroidery, and decoration businesses — with a process that puts your requirements first and the vendor demo second.