When is a spreadsheet still the right answer?
Most advice on this topic starts from a conclusion: spreadsheets are bad, buy software. That's not true, and any owner who has actually run a business on Excel knows it's not true. A spreadsheet is a genuinely good tool for a genuine job. The real question isn't whether spreadsheets are good or bad. It's which side of a handful of thresholds your business is currently sitting on. Cross one, and the spreadsheet doesn't get visibly worse. It gets dangerous, quietly, while still looking exactly the same as it did the week before.
If one person owns the file, nobody else needs the data in real time, and a mistake gets caught before it costs anything, keep the spreadsheet. Don't let anyone talk you out of it.
A finance manager reconciling last month's bank statement against the ledger, alone, once a month, is doing a spreadsheet job. So is comparing three vendor quotes before a purchase decision, or building a one-off pricing model for next year. Anywhere the "process" is really just one person thinking with a calculator, a spreadsheet is the fastest tool you own. Replacing it with a system at that point is solving a problem you don't have, and it slows that person down for nothing.
The trouble starts when a spreadsheet stops being a workspace for one person and gets asked to do a job it was never built for: coordinating other people.
What are the actual signs a spreadsheet has become the problem?
It becomes the problem the moment more than one person has to act on the same data at different times, a handoff happens inside the file, or you need to know who did something and when, not just what the final number says. Four situations account for most of what actually goes wrong in an SME.
More than one person edits it live, not just for review. A dispatch tracker that the warehouse team fills in, the driver checks against, and sales refers to before promising a delivery date isn't a spreadsheet any more. It's an uncoordinated multi-user database with no locking, no audit trail, and no way to know whose version is current. Excel technically allows shared editing. It was never designed to be a system of record for several people working in it at once, and most SMEs that have tried it have a story about two people overwriting each other's changes on the same Tuesday afternoon.
A task inside the sheet has to move from one person to another with a deadline attached. The moment a cell needs to mean "this is now Rekha's job, due Thursday, and someone needs to know if Thursday passes without it happening," you're asking a grid of cells to run escalation. Spreadsheets have no concept of an overdue item that alerts anyone. A red conditional-format cell nobody opens isn't an escalation. It's decoration.
You need proof something happened, not just a figure. Take a quality check on an assembly line: a component gets measured, and someone types "42 microns, pass" into a cell. That tells you nothing about who measured it, which gauge they used, or whether it was checked at all rather than copied down from yesterday's row. A spreadsheet records a value. It cannot record that the value is true.
The data has to be trusted across locations before anyone can act on it. A paints distributor running depots in Nashik, Aurangabad and Nagpur finds this out the day head office tries to build one consolidated stock view and discovers each depot's sheet has drifted: one renamed a column, one added a row for a new SKU category halfway through the year, one is still running last quarter's template. Every individual sheet looks fine to the person using it. Consolidation is where spreadsheets fail silently.
What about the row-limit and performance problems people talk about?
They're real, but they're rarely the reason SMEs actually get hurt. Excel's hard ceiling, fixed since the 2007 file format, is 1,048,576 rows by 16,384 columns per worksheet. Google Sheets allows up to 10 million cells, or 18,278 columns, per spreadsheet. Almost no 30–150 person business generates enough rows in one file to hit either ceiling.
What it does hit is a practical wall long before that: a file with formulas chained across tens of thousands of rows starts to lag, recalculating every time someone touches a cell, until opening it becomes a coffee-break rather than a task. That's an annoyance, not the reason a spreadsheet turns dangerous. The real damage comes from generating enough people, branches and handoffs to break the informal coordination the file was quietly relying on, and that happens at a far smaller size than any technical limit suggests.
What does crossing a threshold actually look like day to day?
It looks ordinary, which is why it goes unnoticed for months. A quality checklist that used to work fine as a shared sheet starts having gaps nobody flags until a customer complains about a batch. A shift handover note gets updated by the morning supervisor and never reaches the evening one, because nothing pushed it to them. An owner opens six branch sheets before a Monday review because there's no single version anyone actually trusts. None of it looks like a crisis. It looks like "someone should clean this file up," the sentence that precedes almost every operational failure that traces back to a spreadsheet carrying more than it was built for.
It's the same pattern that shows up when coordination runs on WhatsApp groups instead of a spreadsheet: the tool isn't wrong, but it has no owner, no status, and no proof built in, so nothing holds once more than one person depends on it.
What replaces the spreadsheet once you've actually crossed a threshold?
Not a bigger spreadsheet, and not "software" in the abstract. What you need is a place where a recurring task has a named owner, a deadline, a record of whether it happened, and an automatic escalation if it didn't — the four things a spreadsheet structurally cannot hold once more than one person is involved. That's a different category of tool, sometimes called a business operating system, and it's worth building once you've confirmed you've actually crossed a threshold, not because someone told you spreadsheets are outdated.
What to do this week
Pick the three spreadsheets in your business that more than one person touches as part of getting work done, not for reporting. For each one, ask a single question: if this file disappeared right now, would you know who was meant to do what today, and whether it happened? If the answer is no for any of them, that's the file to fix first, not by replacing it wholesale, but by writing down, on paper if you have to, who owns each recurring item in it, when it's due, and what "done" looks like. That exercise alone will tell you which of your spreadsheets are still fine, and which one has quietly become the weak point in how your business runs.