Your ERP isn't the problem. The gaps around it are.

There’s a conversation we have often. A leadership team is frustrated with their ERP — it’s clunky, people avoid it, the real work happens in spreadsheets alongside it — and they’ve concluded they need to replace it. Sometimes that’s true. Far more often, the ERP is doing its job fine. What’s broken is the space around it: the handful of workflows the platform never fit, papered over with manual effort.

Replacing a system of record to fix a workflow gap is one of the most expensive mistakes in enterprise technology. It’s a multi-year, high-risk programme to solve a problem that a thin, sharp custom layer could handle in weeks.

Why the gaps exist

Big platforms are built for the average of thousands of companies. That’s their strength — you get decades of accumulated capability out of the box — and their limitation. Your business isn’t the average. The places where you compete are, by definition, the places where you do things differently. Those are exactly the workflows a general product handles worst, because handling them well would mean not being general.

So people fill the gap the only way they can: exporting to a spreadsheet, doing the specific thing by hand, re-keying the result back in. The ERP isn’t failing. It’s just silent on the parts of your business that are most your own.

The custom layer

The alternative to replacing the platform is to build around it. A custom layer sits alongside your ERP or CRM and does three things: it gives people a clean, purpose-fit interface for the workflow the platform makes painful; it enforces your specific rules and keeps an audit trail; and it exchanges data with the system of record through proper, documented integrations, so nothing has to be re-keyed and nothing drifts out of sync.

You keep everything the platform is good at — the accounting, the master data, the compliance backbone — and you stop paying the daily tax of the workflows it isn’t. It’s the difference between a two-week build with a fast payback and a two-year programme with a nervous board.

How to tell which case you’re in

A genuine “replace the platform” case looks like this: the system is unsupported or end-of-life, the vendor is gone, the data model can’t represent your business at all, or the licensing economics have simply broken. Those are real, and when they’re real we’ll say so plainly.

But if your complaints are “people work around it,” “the pipeline lives in a spreadsheet,” “quoting is slow and error-prone,” or “we can’t get the report we need” — those aren’t reasons to replace the platform. They’re reasons to build the layer the platform was never going to give you. Same outcome your team is asking for, a fraction of the cost and the risk.

The honest advice is usually the cheaper one: don’t buy a new engine because the dashboard is in the wrong place. Fix the dashboard.