# Outgrown Spreadsheets? A Decision Framework for SMBs > A practical decision framework for SMBs weighing spreadsheets vs ERP: six concrete signals, a scorecard you can run in an hour, and when staying on Excel is right. URL: https://www.matthewswong.com/en/blog/spreadsheet-to-erp-decision-framework/ - Author: Matthews Wong (https://www.matthewswong.com/en/about/) - Published: 2026-05-07 - Updated: 2026-05-07 - Category: ERP Every Indonesian SMB I have consulted for runs on spreadsheets at some point — and most of them should. Excel and Google Sheets are genuinely excellent tools: zero training cost, infinite flexibility, and everyone already has them. The interesting question is never whether spreadsheets are bad. It is whether your business has crossed the specific lines where their strengths flip into liabilities. Most owners feel that moment as vague pain; this post turns it into a checklist. To be clear about scope: this is a decision framework, not a migration manual. The how of moving Excel data into an ERP is its own topic. What follows are the six signals I look for in the first hour of talking to a client, a scorecard you can run on your own business this week, and — just as important — the cases where my honest advice is to stay on spreadsheets longer. ## First, a Defense of the Spreadsheet I build ERPs for a living, and I will still say it: for a business under roughly ten people with one location, one person per function, and a few hundred transactions a month, a disciplined spreadsheet setup beats a badly chosen ERP. The spreadsheet does not need a server, never has a login outage, and bends instantly to whatever the business needs tomorrow. Flexibility is a real feature while the business is still discovering its own processes. The trap is that the same flexibility silently accumulates risk as the team grows. Nothing announces the transition. The file that worked perfectly at five users develops version conflicts at eight, formula breakage at twelve, and a full-blown trust crisis at twenty. The framework below exists because the right moment to move is visible in operations long before it is visible in the accounting. ## Six Signals You Have Crossed the Line These come from real engagements — each one is a pattern I have personally watched cost a business money. One signal is a conversation; three or more is a decision: ## 1. The reconciliation ritual Someone spends hours every week making two files agree — sales versus stock, bank versus ledger. That person is a human foreign key, and their vacation is your data outage. ## 2. Concurrent editing collisions Two people need the same file at the same time, so you have FINAL_v3_revB filenames or an always-locked shared workbook. Multi-user writes are precisely what databases do and files do not. ## 3. Questions take minutes, not seconds How much stock do we have right now, who owes us money beyond 60 days — if answers require opening three workbooks and running a mental join, decision speed is already throttled. ## 4. Anyone can change anything No roles, no approvals, no history of who edited which cell when. The first serious dispute — with an employee, a vendor, or the tax office — turns absence of an audit trail into a real liability. ## 5. Formula fear There is one workbook only one person dares to touch, because a broken VLOOKUP once silently corrupted a month of margins. Critical logic that nobody can review or test is unmanaged operational risk. ## 6. Volume is meeting the math Excel caps at 1,048,576 rows per sheet, but practical pain arrives far earlier — multi-megabyte files that take a minute to open, recalculate on every edit, and crash on save. If you are archiving by year just to keep files usable, the data outgrew the container. ## The One-Hour Scorecard Feelings argue; scores decide. Answer these five questions honestly, sum the points, and the band tells you where you stand: Question 0 points 1 point 2 points People entering data weekly 1-3 4-9 10 or more Hours per week spent reconciling files Under 1 1-5 More than 5 Decisions delayed waiting for a number Rarely Monthly Weekly or worse Errors found in customer-facing documents Almost never A few per quarter Monthly or more Processes needing approval before money moves None 1-2 3 or more Zero to three points: stay on spreadsheets, but add discipline — one master file per domain, protected sheets, a weekly backup. Four to six: you are in the transition zone; start scoping, budgeting, and cleaning your data now, because you will move within a year or two. Seven to ten: every month of delay is actively costing you money in labor, errors, and missed decisions — the move is overdue. Pro tip: run the scorecard with three people separately — the owner, the person who maintains the spreadsheets, and one person who only consumes the reports. The spread between their scores is itself diagnostic: owners consistently score two points lower than the operators who live in the files. ## When the Answer Is Genuinely Not Yet An honest framework needs a negative branch. I have told prospective clients not to hire me yet in each of these situations: Processes still changing monthly — if how you quote, buy, or fulfill is being reinvented as you grow, an ERP will freeze the wrong version of it. Stabilize the process on paper first; software hardens whatever it finds. No internal owner — an ERP needs one person inside the business who owns master data and user discipline. If nobody can give it four hours a week, the system will rot regardless of build quality. The pain is one report, not the operation — sometimes the fix is a shared database behind the existing sheets or a BI tool over exports, at a tenth of the cost. Buy the aspirin before the surgery. The worst possible timing is moving to an ERP during a cash crisis because leadership hopes software will impose control that management has not. An implementation consumes attention and money for months before it pays back. Microsoft's own ERP guidance frames adoption around growth limitations and visibility — it is an investment made from stability, not a rescue performed mid-fall. ## The Cost Conversation Owners Actually Need Spreadsheets feel free because their costs hide inside salaries: the admin spending Friday afternoons reconciling, the owner re-checking quotations because one went out 10 percent low, the stock bought twice because two sheets disagreed. When I help a client run this math, the recurring number that surprises them is labor — reconciliation hours alone often exceed what a modest system would cost monthly, before counting a single prevented error. Against that: an SMB-grade ERP path in Indonesia — whether a hosted open-source system like Odoo Community, a SaaS package, or a focused custom build like the AP/AR module I built on NestJS and PostgreSQL for ANCoraPRO — typically lands in the tens to low hundreds of millions of rupiah for year one, depending on scope. The point of the scorecard is to know whether the hidden spreadsheet costs already exceed that figure. Frequently they do, and nobody had ever added them up. ## If You Scored High: The First Four Moves The decision to move is not a purchase order for software. The right sequence starts before any vendor is contacted: Write down your top five processes as they actually run today — quote to cash, purchase to payment — one page each. Every gap you find on paper is ten times cheaper than the same gap found during implementation. Clean master data inside the spreadsheets you already have: deduplicate customers, standardize item names, fix phone-number-in-the-address-field entries. This work transfers entirely to whatever system you choose. Decide scope ruthlessly: the first phase should cover the one or two processes bleeding the most — usually inventory plus invoicing — not all eleven modules a brochure offers. Only then evaluate options — packaged versus custom, cloud versus on-premise — against your written processes, not against feature lists. ## The Takeaway Spreadsheets do not fail loudly; they fail one reconciliation hour at a time. Run the scorecard, count the hidden hours, and make the call on numbers instead of frustration. And if the score says stay — stay proudly, tighten the discipline, and re-run the test in six months. The businesses that time this transition well are the ones that treated it as a decision, not a destiny. ## Sources and further reading - Microsoft Support — Excel Specifications and Limits - Microsoft Dynamics 365 — What Is ERP and Why Businesses Adopt It > **Key takeaway:** Most Indonesian SMBs run on spreadsheets, and most of them should: zero training cost and near-infinite flexibility are real advantages. The move to an ERP is justified by specific failures, such as concurrent edits corrupting data or no audit trail, rather than by company size alone. ## Source links - https://support.microsoft.com/en-us/office/excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3 - https://www.microsoft.com/en-us/dynamics-365/topics/erp/what-is-erp ## FAQ ### How do I know when my business has actually outgrown spreadsheets? The post identifies six concrete signals: recurring reconciliation rituals between files, concurrent editing collisions, questions that take minutes rather than seconds to answer, no access controls or audit trail, formula fear where only one person dares to touch a critical workbook, and files too large to open reliably. One signal is a conversation starter; three or more signals together indicate a decision needs to be made. ### What does the one-hour scorecard measure and how should I interpret the result? The scorecard asks five questions covering the number of people entering data weekly, hours spent reconciling files, frequency of delayed decisions, errors in customer-facing documents, and processes requiring approval before money moves. Scores of 0–3 mean staying on spreadsheets with added discipline; 4–6 means you are in the transition zone and should start scoping within a year or two; 7–10 means the move is overdue and every month of delay is actively costing money. ### Are there situations where an ERP is the wrong choice even if the spreadsheets feel painful? Yes. The post outlines three cases where the honest advice is to wait: when core processes are still changing monthly (the ERP will freeze the wrong version), when no internal person can commit four hours a week to own the system, and when the pain is limited to one report rather than a broader operational problem. Moving to an ERP during a cash crisis is described as the worst possible timing. ### What are the hidden costs of staying on spreadsheets that owners usually miss? Spreadsheets feel free because their costs hide inside salaries — time spent by admins reconciling files, owners re-checking quotations because one went out incorrectly, and stock purchased twice because two sheets disagreed. The post notes that reconciliation hours alone often already exceed what a modest ERP system would cost monthly, before counting any prevented errors. ### What is the recommended first step once I decide to move to an ERP? The post recommends four steps before contacting any vendor: write down your top five processes as they actually run today (one page each), clean master data inside your existing spreadsheets by deduplicating customers and standardizing item names, decide scope ruthlessly to cover only the one or two most-painful processes first, and only then evaluate packaged versus custom or cloud versus on-premise options against your written processes rather than feature lists. --- - HTML version: https://www.matthewswong.com/en/blog/spreadsheet-to-erp-decision-framework/ - Bahasa Indonesia: https://www.matthewswong.com/id/blog/spreadsheet-to-erp-decision-framework/ - Site index for agents: https://www.matthewswong.com/llms.txt - Sitemap: https://www.matthewswong.com/sitemap.xml - API description (OpenAPI): https://www.matthewswong.com/openapi.json