Skip to main content

ERP Was Supposed to Fix Everything

Enterprise resource planning promised to unify your business. Three decades later, most organisations are still working around their ERP, not with it.
8 May 2023·7 min read
Mike Ridgway
Mike Ridgway
Technology Growth Advisory
I've spent the better part of twenty years building software that sits alongside ERP systems. At Flintfox, our entire business was built on the reality that ERP platforms, despite their promise of unified everything, consistently fail to handle pricing complexity. That gap was our opportunity. But it also taught me something about enterprise software: the promise and the reality almost never match.

What You Need to Know

  • ERP was sold as the single source of truth for your business. In practice, most organisations have between 3 and 15 systems sitting alongside or on top of their ERP to fill capability gaps
  • The total cost of ERP ownership is typically 4-7x the initial implementation cost over a ten-year period, once you account for customisations, integrations, and workarounds
  • ERP implementations fail at roughly the same rate they did twenty years ago, despite better tooling and methodology. The root cause isn't technical; it's organisational
  • The next wave of enterprise software won't replace ERP. It will route around it, handling the complexity that ERP was never designed to manage
  • Organisations should stop trying to make their ERP do everything and start investing in purpose-built tools for their genuine differentiators
75%
of ERP projects fail to meet their objectives, with the average implementation running 58% over budget
Source: Panorama Consulting Group, ERP Report, 2022

The Original Promise

The pitch was elegant. One system for your entire business. Finance, operations, supply chain, human resources, customer management, all unified. No more data silos. No more manual reconciliation. One version of the truth.
It made perfect sense on a whiteboard.
In practice, ERP systems are brilliant at structured, repeatable processes. General ledger transactions. Purchase orders. Inventory movements. The transactional backbone of a business. They do that well, and most organisations couldn't function without it.
But business isn't just transactions. It's decisions. Negotiations. Exceptions. Relationships. And ERP systems handle exceptions about as gracefully as a freight train handles a hairpin turn.

Where It Broke Down

At Flintfox, we built intelligent pricing and rebate management because ERP systems couldn't handle it. Not because ERP vendors were incompetent, but because pricing in complex supply chains involves thousands of variables, conditional logic, temporal rules, and relationship-specific agreements that don't fit neatly into a transaction processing framework.
Our customers would say, "We bought SAP to handle everything." Then they'd show us spreadsheets with 10,000 rows of pricing rules that someone was maintaining manually because the ERP couldn't manage the complexity.
This pattern repeats everywhere. CRM bolted onto ERP because the customer management module is too rigid. Planning tools bolted on because demand forecasting requires specialised algorithms. Analytics platforms bolted on because reporting in ERP is painful.
Each bolt-on adds integration complexity. Each integration adds maintenance cost. And gradually, the "single system" becomes a loosely connected collection of systems, with ERP at the centre doing less and less of the actual work.
The most expensive ERP projects I've seen weren't the ones that failed. They were the ones that succeeded at implementing the software but failed at changing the business. The system went live. The organisation worked around it.
Mike Ridgway
Technology Growth Advisory

The Customisation Death Spiral

Here's where it gets worse. Organisations realise their ERP doesn't handle their unique processes. So they customise it. Every customisation makes the system harder to upgrade. Harder upgrades mean longer cycles between versions. Longer cycles mean falling further behind on features and security patches.
I've seen organisations running ERP versions that are five, sometimes ten years out of date because the customisation layer is so deep that upgrading would effectively mean re-implementing.
That's not a technology platform. That's technical debt with an annual maintenance fee.
$413B
global ERP software market projected by 2026, despite persistent implementation failure rates
Source: Gartner, Enterprise Application Software Forecast, 2022

What Comes Next

I don't think ERP goes away. The transactional backbone it provides is genuinely valuable. But I think the era of pretending ERP can handle everything is ending.
The smartest organisations I work with have accepted that ERP is infrastructure, not a business platform. They use it for what it does well: financial transactions, order processing, inventory management. For everything else, they invest in purpose-built tools that handle specific domains with the depth those domains require.
There's early noise about AI transforming ERP. I'm sceptical, but watching closely. The pattern I've seen over three decades is that new technology doesn't replace ERP; it fills the gaps ERP creates. AI may do the same, handling the exceptions and decisions that ERP processes into rigid workflows.

The Practical Takeaway

If you're considering a major ERP investment, or living with the consequences of one, here's my advice after two decades of working in this space.
Stop trying to make your ERP do everything. It won't. Accept what it does well and invest in complementary tools for the rest.
Budget for the real cost. Whatever the vendor quoted for implementation, multiply by four for the ten-year total cost. That's closer to reality.
Protect your differentiators. The things that make your business unique, your pricing, your customer relationships, your operational expertise, deserve purpose-built systems. Don't flatten them into a generic ERP module because it's simpler to manage.
Plan for change. The ERP market is shifting. Cloud-native platforms, composable architectures, and yes, AI are creating alternatives that didn't exist five years ago. Your next ERP decision should be made with flexibility in mind, not just current requirements.
The organisations that thrive won't be the ones with the best ERP implementation. They'll be the ones that understood what ERP can't do and built around it intelligently.