Every few weeks, an owner asks us some version of the same question: at what revenue number do we need a real ERP? It's a reasonable question with a useless answer. We've seen tightly run companies thriving on QuickBooks at a scale that would surprise you, and we've seen much smaller businesses drowning because their accounting system stopped describing reality two years ago.
The threshold isn't revenue. It's where the truth lives. When the numbers your team actually acts on come out of spreadsheets rather than your system of record, you've already outgrown it — you just haven't paid the bill yet.
The Workaround Economy
Every accounting system develops a shadow layer. Someone builds a spreadsheet to handle a case the software doesn't cover. It works. Someone else builds another. Within a couple of years there's a quiet economy of files — inventory valuation, commission calculations, job costing, multi-entity rollups, revenue recognition — that no one planned and no one owns.
Individually, each one is harmless. Collectively, they become the operating system of the business, and they have none of the properties you'd want from one. No permissions. No audit trail. No validation. No version history beyond a filename ending in `_FINAL_v3_USE THIS`. And almost always, one person who understands how it all fits together.
That's the risk. Not inefficiency — fragility.
Signals That Actually Matter
Ignore headcount and revenue. Watch for these instead:
- Month-end close keeps getting longer even though the business hasn't gotten more complex. That's compounding manual work, not seasonality.
- Two people can produce two different answers to a basic question like margin by product line or open order value — and both can defend their math.
- Inventory, projects, or production live outside accounting entirely, so you reconcile them rather than operate from them.
- You can't grant someone access to what they need without also giving them access to things they shouldn't see.
- Decisions wait on a person, because only one teammate can assemble the report that answers the question.
If you're nodding at three or more, the conversation isn't "should we migrate someday." It's "what does the next twelve months cost us if we don't."
The Honest Case for Staying Put
Migration is not automatically the right call, and anyone who tells you otherwise is selling software.
If your workarounds are stable, documented, and owned by more than one person — and your core operations genuinely fit a straightforward accounting model — you may be better served by targeted integrations than a platform change. Connecting your CRM, your e-commerce storefront, or a purpose-built inventory tool to QuickBooks can eliminate most of the re-keying that creates spreadsheet sprawl in the first place.
The question to ask is structural: are the gaps about connection or about capability? Disconnected systems can be wired together. A system that fundamentally can't model your business — multi-entity consolidation, real manufacturing, complex project accounting, meaningful role-based permissions — can't be patched into one. Integration buys you years. It doesn't buy you a different category of software.
Sequencing Beats Scope
When the move is warranted, the failure mode is almost never the software. It's attempting to replace everything on one weekend.
A phased approach earns trust while reducing risk. Start with financials and the master data that everything else depends on: customers, vendors, items, chart of accounts. Get that clean and running in parallel long enough that your team believes the numbers. Then layer in the operational modules that eliminated your biggest spreadsheets — inventory, purchasing, project costing, whatever your specific pain is.
Each phase should retire something. If a go-live doesn't delete a spreadsheet, replace a manual handoff, or shorten a close, it hasn't delivered value yet — it's just added a login.
Two things will matter more than feature lists. First, decide upfront which data is coming over and which is staying behind in an archive you can query. Second, name the people who own each process in the new system before you configure it. Software doesn't create accountability; it enforces whatever accountability you already defined.
Start With an Inventory, Not a Demo
Before you sit through a single software demo, do this: list every spreadsheet your business depends on, who maintains it, and what decision it drives. Most teams are surprised by the length of the list and by how many entries have a single name next to them.
That document tells you more about whether you need an ERP — and which one — than any vendor comparison chart will.
If you'd like a second set of eyes on that list, we do this work every day. Infraxio pairs hands-on operator experience with modern tooling to figure out whether you need a migration, a few well-placed integrations, or just better discipline around what you already own. Reach out and we'll tell you straight.