The ERP ladder: when a lighter-touch system is the right answer

There’s a moment in every scaling brand’s life when someone says the sentence. We heard it verbatim from a founder recently, running a completely normal stack, entry-level inventory system, cloud accounting, Shopify on the front: “we’ve outgrown the thing.”

What happens next usually goes one of two ways, and both of them are wrong.

Way one: panic-buy enterprise. The brand decides that outgrowing the small system means it’s time for the big system, engages an implementation partner, and spends eighteen months and a serious six figures installing an ERP built for a business three times their size. The implementation eats the ops team’s year. Half the modules never get configured. The brand is now paying enterprise maintenance on entry-level usage.

Way two: denial. The brand decides the small system is fine actually, adds another app, another spreadsheet, another integration, and defers the decision until the month finance stops trusting the numbers, which is the most expensive possible moment to start a systems project.

We want to argue for the boring middle, and specifically to say something consultants aren’t supposed to say: the lighter-touch ERP is underrated, and the expensive mistake in this market is almost never buying too small. It’s buying enterprise for a business you haven’t built yet.

The evidence for the light system

Here’s a story from a recent conversation that should be told more often. A UK brand localising its US operation, the classic complexity jump, inventory in two territories for the first time. One operator, essentially working alone, ran the whole thing through a lighter-touch ERP that the industry habitually describes as a stepping stone. Full range, live operation, no enterprise anything. The brand is now growing strongly in the US on the back of it.

The lesson isn’t that small systems are secretly enterprise-grade. They’re not. The lesson is sequencing. This operator built the operation first, matched the system to its actual current shape, and planned to add complexity when volume demanded it rather than in anticipation. The brands that struggle run it backwards: they buy for the business plan instead of the business, and the system’s demands then compete with the growth it was supposed to enable.

A light ERP implemented well beats a heavy ERP implemented late, every time, and it usually beats a heavy ERP implemented on schedule too, because the schedule is fictional.

So when do you actually graduate?

This is the useful question, because “we’ve outgrown it” is a feeling, and feelings are how brands end up in way one. The graduation signals are more specific than a feeling, and most of them are visible a year before the crisis.

Multi-territory inventory is the big one. The moment stock lives in two places with different demand curves, entry-level tools start creaking, because they were built around one pool of stock and one version of the truth. If international localisation is genuinely on the eighteen-month horizon, the ERP conversation starts now, calmly, not later, urgently.

B2B and B2C on one back end is another. Wholesale brings return agreements, bulk credit notes, partner-specific pricing and paperwork the light tools handle grudgingly or not at all. If wholesale is heading past a quarter of revenue, you’re graduating.

The third signal is the finance one, and it’s the deadline rather than the warning: the month-end close starts requiring manual reconciliation between systems, and the FD stops trusting the numbers without checking them somewhere else. When finance builds a shadow spreadsheet, the system has already failed. Everything after that is overdue.

And a non-signal, worth naming because it triggers so many premature migrations: pain that’s actually data governance wearing a systems costume. A remarkable amount of “we’ve outgrown the ERP” turns out to be ungoverned fields, duplicate SKUs and integration gaps that would follow the brand into any system on earth. Fix the data first. You’ll often find the appetite for replatforming shrinks, and if it doesn’t, at least the migration won’t import the mess.

The ladder, not the leap

Think of it as a ladder with known rungs. Spreadsheets, then entry-level inventory plus cloud accounting, then the light ERP, then mid-market, then enterprise, and the skill isn’t picking the right rung so much as knowing your climbing speed. Each move costs a project, so you want to move when the signals fire, not when the vendor’s sales team does.

The brands that get this right are unglamorous about it. They’re on a smaller system than their revenue suggests, it’s configured properly, the data in it is clean, and they know exactly which signal will trigger the next move. The brands that get it wrong have the biggest system money can buy and a finance team running the business from Excel next to it, expensively.

If any of this rings true to where you are right now, get in touch, and we can talk it through.