Your ERP might be running perfectly. No outages, no support tickets, no complaints from the helpdesk. That’s exactly what makes this harder to spot than a system that’s obviously failing, a system can work fine and still have become the ceiling on what your business can do.
This isn’t about whether your provider is responsive or your support contract is fair value. It’s a narrower, more uncomfortable question: was the system built for the business you are now, or the business you were when you bought it? For a lot of mid-market companies, the ones that have grown from £50m to £250m, added entities, added geographies, maybe added an acquisition or two, the honest answer is the second one, and nobody’s stopped to notice.
Here are five signs worth checking against, none of which show up as a red light on a dashboard.
1. Closing the books takes days longer than it should
If your month-end close still involves pulling data out of the system and into spreadsheets before anyone can trust the numbers, that’s not a process problem your finance team can fix with more discipline. It’s a sign the system was never designed to give you a single, reliable version of the truth across the business you now run. The workaround becomes so normal that people stop describing it as a workaround at all, it’s just “how we close the books here.” A recent survey of over 1,700 finance leaders found 45% of finance teams now spend more than ten hours a month just reconciling data and fixing errors across systems, a full working day and a half, every month, before the actual close work even starts.
2. Board questions get “let me get back to you” as the answer
A board member asks how one entity or business unit is performing against another, right now, not as of last month’s report. If the honest answer requires someone to go away and manually reconcile numbers from two or three systems before a confident answer comes back, that’s a capability gap, not a communication gap. The system can’t give you a real-time consolidated view, so you’re presenting a snapshot that was already out of date by the time it reached the boardroom. It’s a more common gap than most finance leaders would admit out loud: the same 1,700-respondent survey found 63% of finance teams believe they have real-time access to their data, yet 77% say actually pulling an insight out of it takes over an hour, and a quarter say it takes longer than half a working day.
3. Every acquisition or new business line means another spreadsheet
Growth is supposed to get easier to manage as the business matures, not harder. If every new entity, product line, or geography you add creates another manual workaround, another spreadsheet, another shadow process running alongside the “real” system rather than inside it, the ERP isn’t scaling with you. It’s quietly capping how fast you can integrate anything new, and nobody put that limit in the growth plan. This is more widespread than it feels from inside one business: the same research found 63% of finance teams now rely on ten or more separate systems just to produce a unified set of financials, and over a third have had to reopen or restate a closed period because of errors that only surfaced afterwards.
4. The system can tell you what happened, not what’s coming
There’s a meaningful difference between a system that reports the past accurately and one that helps you model what’s next. If forecasting and scenario planning still happen almost entirely outside the ERP, built by hand, refreshed manually, owned by whoever has the most patience for it, you’re running a rear-view mirror, not a system your finance team can actually plan from. That gap tends to matter most exactly when you need it least to matter: during a downturn, a fundraise, or a fast-moving decision.
5. Headcount is quietly growing to compensate for the system, not the business
This is the one that’s easiest to miss because it looks like normal growth. Look honestly at the last few finance hires, were they brought in to do more valuable analysis, or to manually stitch together data the system should already be connecting? If the answer trends toward the latter, the team isn’t scaling with the business. It’s scaling to cover for a system that hasn’t kept up, and that’s a cost that never shows up as a line item labelled “legacy ERP.”
What the ceiling actually costs
None of these five signs, taken alone, looks urgent. That’s precisely why they tend to persist for years rather than months. The cost isn’t a single dramatic failure, it’s a steady tax on the things that matter most at this stage of a business: how quickly you can answer a board’s questions, how confidently you can move on an acquisition, how much of your best analytical talent is spent reconciling numbers instead of interpreting them. None of that shows up as a line item. It shows up as slower decisions, more caution around growth than the business actually needs, and a finance team that feels permanently behind despite working harder than ever.
None of these are about your provider
It’s worth saying plainly: none of this is a comment on whether your current ERP partner is good at their job. A capable, responsive provider can still be selling and supporting a system that was simply never designed for a business your size, with your complexity, doing what you’re doing now. The relationship can be excellent and the ceiling can still be real, they’re separate questions, and it’s worth not letting a good relationship with your provider stand in for an honest answer to the capability question.
The mid-market version of this problem
This particular flavour of the problem is distinctly a mid-market one. A small business doesn’t have enough entities or complexity to hit this ceiling yet. A large enterprise typically has the budget and internal team to patch around it indefinitely, however inefficiently. It’s the business in between, big enough to have real complexity, not yet big enough to have an internal army to manage it manually that feels this most acutely, and for the longest time, before anyone names it out loud.
None of these five signs demand an immediate decision. But they’re worth an honest look, ideally before the next board meeting, the next acquisition, or the next time someone asks a question your systems should be able to answer in seconds rather than days.
See where you stand: Get an ERP Health Check
Sources: Finance Software Consolidation Statistics 2026, Stripe CFO Insights Report, 1,700+ respondents
