A Monday-morning stock meeting at a growing Thai distributor usually goes the same way: sales says forty units are available, the warehouse says twenty-five, and finance is still working off Friday's export file. Nobody in the room is lying. Nobody has looked at the same number today.
ETDA's most recent Digital Maturity Index puts the average Thai SME at 2.45, up just 3.81% year-over-year, with most businesses still classified as "Digital Followers" — using digital tools, but not yet connecting them across core operations. Thailand counts more than 3.3 million SMEs, and the study suggests the large majority sit at roughly this same stage.
It sounds like a technology gap. It's actually an agreement gap: different departments trusting different versions of the same fact, with nobody clearly responsible for which version is real. Software doesn't create agreement on its own — it just makes disagreement expensive enough to finally notice.
ERP becomes useful when disconnected work costs more than connected change.
This piece walks through seven concrete signs that a Thai SME has outgrown Excel and LINE as its coordination layer, how to confirm the real cost of staying disconnected before you buy anything, and how to build a 90-day readiness plan that actually protects the investment.
Seven Signs Your Systems Have Stopped Agreeing
- The same data is entered repeatedly. Sales, warehouse, and finance each keep their own version of "the truth," and reconciling them has quietly become somebody's part-time job.
- Stock cannot be trusted. Staff call the warehouse before promising an order, because the number on screen has been wrong before.
- Approvals disappear into chat. Nobody can see who is waiting, what they're waiting for, or how long it's been sitting there.
- Month-end depends on manual reconciliation. Teams spend days comparing exports instead of closing the books.
- Growth requires more coordinators, not more output. Volume rises, and the number of people whose real job is "make sure everyone has the same information" rises faster.
- Management reports arrive too late to matter. Decisions get made on last month's almost-correct numbers, because this month's aren't ready yet.
- Branches operate differently for no good reason. Controls, pricing, and customer experience vary depending on who happens to be working that day.
If two or three of these sound familiar, it's worth measuring what they actually cost before assuming ERP is the fix — which is exactly what the next section walks through.
The Coordination Tax: What Disconnected Growth Actually Costs
Call it the Coordination Tax: the hidden, compounding cost of keeping people employed to manually reconcile numbers that software should already agree on. It shows up first in sign five — headcount growing faster than output — and it's the clearest evidence that a business has crossed from "needs better habits" into "needs a shared system of record."
The tax is easy to underestimate, because it's paid in small amounts, constantly: ten minutes here confirming stock by phone, an hour there rebuilding last week's numbers because two spreadsheets disagreed, half a day every month-end spent chasing the few thousand baht that won't reconcile. None of it looks large in isolation. All of it compounds as a business adds branches, staff, and sales channels — and it compounds across a very large population. Thailand had 967,210 active registered juristic persons at the end of 2025, out of just over two million ever registered, according to the Department of Business Development. The operational habits that work fine for a single-location SME rarely survive the jump past two or three locations unchanged.
Picture a hypothetical company called Ruamjai Hardware, a fictional three-branch construction-supplies distributor. At one branch, Ruamjai could get away with a shared spreadsheet and a group chat — one warehouse, one till, one person who simply remembered what was actually in stock. At three branches, that same setup means three people who each think they know what's available, a purchasing team ordering against a stock count that's a day old, and a manager who spends every Monday morning just figuring out which branch's numbers to believe. The Coordination Tax didn't appear when Ruamjai opened branch two — it appeared the moment nobody could say, with confidence, which system was the real one.
Confirm the Problem Before You Buy Anything
Before shortlisting software, measure what disconnection is actually costing: duplicate data entry, emergency stock adjustments, approval turnaround time, order errors, month-end closing time, and how long it takes to produce a management report anyone actually trusts. Map two flows end-to-end — quotation to cash, and purchase request to payment — and mark every handoff where the process depends on a person remembering to tell someone else.
Don't start with a feature checklist. Start with the single handoff that's currently the most expensive, and the business rule that should be governing it but currently isn't.
Know When ERP Isn't the Right Fix Yet
If the real problem is one broken spreadsheet, one missing sales process, or unclear ownership, fix that first — a focused inventory tool, a CRM, or a redesigned approval workflow may solve the actual bottleneck with far less disruption than a full ERP rollout. If you're not sure whether your gap is genuinely an ERP problem or something narrower, it's worth reading how ERP, CRM, and accounting software are each actually built to solve different problems before you shortlist a single vendor.
ERP is also premature if leadership can't assign process owners, staff can't free up real time to test the system, or nobody currently owns master data like customer and product records. Software cannot make a decision the business itself refuses to make — it can only enforce whichever decision you finally commit to.
Build a 90-Day Readiness Plan
Month one: map two core end-to-end processes and record baseline metrics for each — current duplicate entry, current approval time, current closing time. Month two: clean customer, supplier, and product data, and assign a named owner for each dataset. Month three: compare vendors through scripted demonstrations using your own real scenarios, deciding along the way whether a ready-made package or a custom build actually fits how your business runs.
Ask every vendor to demonstrate a partial delivery, a return, a price override, a duplicate supplier record, and a month-end reconciliation — not just the scenario that makes their software look best. Success before you sign anything means the business can already describe what will change, who owns it, and how the improvement will be measured.
The Coordination Tax Playbook
- Named Data Owner — every core record (customer, product, price) has one accountable person, not a department that quietly shares the blame.
- One Flow First — pilot a single end-to-end process before touching anything else, and only expand once it's proven under real volume.
- Measured Handoffs — every point where work crosses from one team to another gets a time and error measurement, not just a process diagram nobody re-checks.
- Cross-Industry Check — a spa chain running four branches faces the exact same Coordination Tax the moment its front desk, therapist schedule, and product stock stop agreeing with each other; the fix is the same discipline, not spa-specific software.
Agreement: What This Actually Comes Down To
If there's one word for when a Thai SME actually needs ERP, it's Agreement — not more software, not more headcount, just one version of "available stock" or "approved order" that every department already trusts before someone has to ask.
So here's a fair question to sit with: the next time two people in your business quote a different number for the same thing — same product, same customer, same day — how long does it take before anyone notices? If you don't already know the answer, that gap is where your next Coordination Tax bill is quietly accumulating.
FAQ
How many of the seven signs need to be true before ERP is worth considering?
There's no fixed threshold, but two or three consistently true signs — especially disappearing approvals and untrustworthy stock — are usually enough to justify measuring the real cost, even if the honest answer turns out to be "not yet."
Is ERP only for larger companies?
No. The signs above tend to appear around the second branch, the tenth employee, or the first time a business runs more than one sales channel at once — well within typical Thai SME scale, not just enterprise scale.
What's the biggest mistake SMEs make when they think they need ERP?
Starting from a feature checklist instead of the actual handoff that's costing money. A vendor demo can make almost any system look capable; only your own numbers show what's actually broken.
How long should a readiness phase realistically take?
Around 90 days for a focused SME: a month to map processes and baseline metrics, a month to clean master data and assign ownership, and a month to compare real vendor demonstrations against your own scenarios.
If you recognize two or more of these seven signs and want a clearer picture of what disconnection is actually costing you, request an ERP readiness assessment from NAWA and we'll help you measure it before you commit to anything.