Why Every Mid-Market Company Is Running Three ERPs and Calling It One

NetSuite + Salesforce + Chargebee is not an ERP stack. It’s three systems that barely know the other exists, connected by middleware and manual effort. Here’s a plain-English accounting of what the average $20M company is actually running under the hood — and why the gap between what they believe and what’s true is costing them.

Ask a mid-market CFO what ERP they’re on and they’ll give you a clean answer. “We’re on NetSuite.” Maybe they add: “We use Salesforce for sales and Chargebee for billing.” What they’re describing, without realizing it, is three separate systems of record, each maintaining its own version of the financial truth, loosely synchronized by a combination of API connections, Zapier workflows, and a person whose entire job is making the numbers agree.

That’s not an ERP. That’s an ERP-shaped collection of software.

The distinction matters because ERP — Enterprise Resource Planning, in the original sense — was supposed to mean exactly the opposite. One system. One data model. Every business event touching the same record. The concept goes back to the early 1990s, when Gartner coined the term to describe the evolution beyond MRP (Manufacturing Resource Planning) into something that unified the whole enterprise, not just the factory floor.¹ The goal was a single ledger that knew about everything: sales, purchasing, inventory, finance, HR.

What happened instead is that the software industry fragmented. Best-of-breed won the argument. And by the time cloud SaaS made software cheap enough for mid-market companies to adopt, the category had already split into dozens of specialized tools — each excellent at its own thing, each maintaining its own database, each requiring somebody or something to keep them in sync.

What “integrated” actually means in practice

The word integration shows up in every ERP vendor’s marketing. What it almost always means is API connectivity — one system can read data from another, push records across, trigger workflows. This is genuinely useful. It is not the same as being one system.

When a sales rep closes a deal in Salesforce, a record gets created. That record, if the integration is working correctly, creates a corresponding account in NetSuite and kicks off a subscription in Chargebee. Three systems. Three records. Three potential points of divergence. If the integration job fails at 2 AM on a Thursday, the records drift. They drift quietly, invisibly, until someone notices — usually at month-end, usually when it’s expensive to care.

A 2023 survey by Gartner found that integration failures are among the top three causes of ERP project problems, even in companies that have already completed implementation.² The integration doesn’t break dramatically. It degrades. A field that doesn’t map. A sync that runs on a delay. A record that gets updated in one system but not the other because the webhook timed out.

The hidden employee

Every company running this kind of stack has what we’d call a hidden employee: the person whose informal job is keeping the systems honest. They’re usually in finance. They run the Monday morning reconciliation. They know which reports to trust and which to verify. They maintain a spreadsheet that bridges the gap between what Salesforce says about deferred revenue and what NetSuite has posted. They are, functionally, the integration layer.

This person’s salary doesn’t appear on the ERP bill. Neither does the time of the controller who reviews their work, or the auditor who spends two extra days untangling the transaction trail during year-end. But those costs are as real as the license fee.

Why the stack keeps growing

The irony is that each addition to the stack is individually defensible. Salesforce is genuinely good at CRM. Chargebee handles subscription billing with sophistication that a general-purpose ERP typically can’t match. DocuSign manages contract execution better than anything built into a finance system. The tools earn their place.

The problem is systemic. Every new tool that joins the stack is a new source of truth that needs to be reconciled against every other source of truth. The complexity compounds. A company that started with QuickBooks and Salesforce adds NetSuite when it outgrows QuickBooks, adds Chargebee when subscriptions get complicated, adds a contract tool when DocuSign integrations become necessary, adds a planning tool when the CFO can’t build what they need in NetSuite’s reporting. Each addition solved a real problem. Collectively, they created a new one.

By the time a $30M company has a mature stack, they’re typically running five to eight systems, connected by three to five integration layers, maintained by a combination of vendors and internal staff, and generating reconciliation work that occupies meaningful portions of their finance team’s time every month.³

What this actually costs

Nucleus Research estimates that ERP projects — including integration and customization — come in over budget 75% of the time, with the average overrun around 30%.⁴ But the budget overrun is a one-time problem. The ongoing cost of running a fragmented stack is permanent. It shows up as close process length, headcount in finance, audit prep hours, and — most damagingly — the quality of decisions being made on data that might be two systems out of sync.

The question isn’t whether your stack is technically integrated. It’s whether it’s architecturally unified. Those are different things, and the gap between them is what most companies are living in.

Next: The Dirty Secret of ERP “Integration”: Someone Always Reconciles Manually

Sources