If we got a dollar for every time a small-business owner told us, in their first call, "I think we need an ERP" — we'd have an ERP.
Almost every time, that's a misdiagnosis. And the most valuable hour of the engagement is the one we spend correctly naming what's actually going on.
This isn't a critique of the founders saying it. The phrase "ERP" is the only word the small-business world has handed them for the feeling of "this is too big for spreadsheets and too small for software the way I keep being pitched it." So they reach for "ERP" because it's the only label available. The problem is that the label is almost always pointing at the wrong solution category — and a six-figure six-month ERP rollout for a 14-person operation is the kind of expensive mistake that takes a year to recover from.
What people mean when they say ERP
When a small-business owner says they need an ERP, what they almost always mean is one of three deeply un-ERP things:
1. "I want my numbers to agree with each other." Online sales, wholesale orders, inventory, accounting — they're each accurate, but they live in different places, and nobody connects them. Every discrepancy is a scavenger hunt.
2. "I want a single source of truth I can trust." Customer info lives in four places. Pricing lives in three. The "correct" version is whatever the most senior person says it is, in their head, on a Tuesday.
3. "I want a dashboard that tells me what's actually happening." The data exists somewhere. Pulling it together takes someone three hours. By the time the report exists, the question has changed.
None of these is an ERP. ERPs are answers to a different problem entirely — multi-entity accounting, complex financial consolidation, hundreds of employees with role-based workflows that span departments. For a 14-person operation with a Shopify store and an accounting tool, an ERP doesn't fit, doesn't earn its room, and creates a maintenance burden that compounds for years.
Why misdiagnosis is the expensive part
The reason "we need an ERP" is the dangerous opening line isn't the work involved. It's that what gets named, gets quoted.
If a founder calls a vendor with "we need an ERP," the vendor will quote an ERP. The quote will be six figures. The implementation will be six months. The change management — retraining the entire team, migrating data, integrating with everything else — will be a years-long process that the business doesn't actually need.
Meanwhile, the actual problem (numbers disagreeing, fragmented customer data, no real-time visibility) goes unfixed during the entire ERP rollout. The business pays twice: once for the ERP that didn't fit, and again in the slow-motion damage of the underlying problem never having been solved.
The most valuable thing a consultant can do, before a line of code gets written, is to correctly name the problem. That's the work. Everything downstream of a correctly-named problem is just craft. Everything downstream of a misnamed problem is, at best, expensive coping.
The three real problems, and why they're worth solving well
Reconciliation across systems
When the issue is "my numbers don't agree with each other," the answer is a quiet middleware layer that watches every relevant data source and continuously reconciles them into the source of truth that already exists (almost always: accounting). Anything that needs human attention gets surfaced in a morning digest.
The value isn't in the technical complexity. It's that you stop spending mental cycles on whether the numbers are right. The owner gets back the part of their week they were burning on the scavenger hunt. Errors that were silently costing margin get caught in week one. The team operates with more confidence because the back office stops being a question mark.
This is the kind of work that returns five-figure annual margin recoveries on its own — before you count the time saved.
Single source of truth migration
When the issue is "my data is everywhere and nothing agrees," the answer is an honest migration. Pick the home for whichever piece of data is fragmented. Move it cleanly. Put guardrails on so it stays clean. Document where it lives so the next hire doesn't have to inherit the institutional memory.
The value isn't in the migration itself. It's in everything downstream — every report that becomes trustworthy, every onboarding that takes hours instead of weeks, every decision that gets made on real numbers instead of "what someone remembered."
Internal dashboards
When the issue is "I can't see what's actually happening," the answer is a focused tool — internal portal, Slack bot, lightweight web app — that pulls from the systems that already run the business and surfaces the answers to the questions the team is asking every day.
The value here compounds. A dashboard that surfaces the right metric in the right place changes what gets attention. What gets attention changes what gets better. Most of the businesses we've built dashboards for talk about the culture shift that came from finally having visibility — not the dashboard itself.
Why "but we'll grow into the ERP" is the wrong frame
The most common pushback to "this isn't an ERP problem" is some version of: won't we eventually need one? Better to set it up now and grow into it.
Two things wrong with that.
The first is that ERPs you "grow into" usually aren't the ERP you would have picked at the size you eventually grow to. The system you'd want at 50 employees is different from the system you'd want at 200, and very different from the system you'd be implementing at 14. Buying for a future you might not have is the most expensive way to spend money on software.
The second is that the small-business equivalents of ERP problems are all unbundleable. You can solve reconciliation this quarter and the dashboard next quarter and the source-of-truth migration the quarter after. An ERP is a bundle — you buy it whole, implement it whole, live with it whole, and pay for the parts you don't need forever. Solving the actual problem you have, this quarter, doesn't preclude an ERP if you genuinely need one in five years. It does preclude the expensive ERP that was never going to fit.
The conversation we have
When a founder calls and says "I need an ERP," the first thing we ask is: what would the ERP let you do that you can't do now?
The answer is almost always one of the three flavors above. Sometimes it's a fourth — wholesale operational structure, dealer pricing tiers, multi-warehouse inventory with serial-number tracking. Those are real, and they're things we build well. Even those are usually a focused engagement, not an ERP rollout.
The honest, value-creating move — the part that's worth paying for — is naming the actual problem, scoping the work that fixes it, and being willing to walk away from the framing that would have produced a much bigger invoice. We do that on purpose. It's the part that earns the trust to do the next engagement, and the one after that.
If you're sitting on the "we need an ERP" feeling and considering a six-figure quote: ask the question above first. The answer is almost always not an ERP. Knowing which of the three real problems you actually have is worth more than the system you would have bought.