How to Know You've Outgrown Your ERP (Without Waiting for the Crisis)

The signs are subtle at first. A spreadsheet that gets emailed every Monday morning. A Slack channel that exists to coordinate between two systems. A close process that takes a little longer each quarter. None of these feel like system failures. They are. We describe the pattern — and the inflection point most companies recognize only in retrospect.

Companies rarely outgrow their ERP in a single dramatic moment. The deterioration is gradual. The system that worked well at $10M starts showing stress at $25M. By $40M, the workarounds have become infrastructure. By the time leadership acknowledges that the system needs to be replaced, the finance team has been compensating for its limitations for years.

Understanding the signs before they become a crisis is one of the most valuable things a CFO or operations leader can do for an organization’s momentum.

The workaround inventory

The most reliable diagnostic for ERP health is a workaround inventory: a list of every place where someone does something outside the system to compensate for what the system can’t do. These workarounds accumulate invisibly, because each one seems small and reasonable at the time.

A spreadsheet built to handle the multi-entity consolidation that the ERP doesn’t support natively. A manual process to generate the aging report in the format the board wants because the ERP’s built-in report doesn’t match. A recurring calendar reminder to manually update the revenue recognition schedule every month because the billing system doesn’t talk to the GL. A shared folder where the operations team drops their weekly status updates because the project management tool doesn’t connect to anything the finance team uses.

Each of these is a workaround. Collectively, they’re a measure of the gap between what the business needs and what the system provides. When the workaround count is high and growing, the system is being outgrown.

The close duration trend

Month-end close duration is one of the clearest metrics for ERP health. It’s not an absolute number — some businesses have legitimately complex closes — but it’s a trend that matters. If close was taking five days two years ago and now takes nine, something has changed. Usually what’s changed is business complexity: more entities, more transactions, more systems to reconcile. If the system were scaling with the business, the close wouldn’t be growing.

A growing close duration is a leading indicator. The crisis version of this metric is a close that misses its deadline — financials not available for the board meeting, a quarterly report delayed — which typically represents months of accumulated pressure finally breaking the surface.¹

The reporting request backlog

When leadership asks for reports the system can’t produce — or can produce only with significant manual effort — someone has to build something outside the system. Over time, the reporting backlog fills with requests that got answered “we’ll pull that manually” or “we’ll build a spreadsheet model for that.” When the manual reports become permanent fixtures and the spreadsheet models become operational infrastructure, the system is failing to keep up.

The specific reports that accumulate in the backlog are informative: customer-level profitability, department-level actuals vs. budget, real-time cash position by entity, revenue by segment. These aren’t exotic requests. They’re the standard views that a functioning ERP should be able to produce on demand. When they’re not available on demand, the system has a capability gap.

The new hire tell

When a company hires a new CFO, controller, or finance director who has worked at companies with more capable systems, the feedback comes quickly. “I can’t believe we’re doing this manually.” “Why isn’t this in the system?” “At my last company, this report took thirty seconds.” These observations are diagnostic. The new hire’s frame of reference reveals what the current system is missing, relative to what the same size company with a better system would be able to do.

What to do with the diagnosis

Identifying that a system is being outgrown is the first step. The second is determining whether the gap is the system or the configuration — whether a better-implemented version of the current system would close the gap, or whether the gap is architectural and requires a different platform.

This distinction is important because migration is expensive and disruptive regardless of how well it’s managed. If the current system is under-configured rather than under-capable, optimization is faster and cheaper. If the system is genuinely at its ceiling, continuing to invest in workarounds is borrowing against a migration that will eventually be necessary anyway.

Sources