Spreadsheets got you here. Here is how to tell when they have started costing more than they save, and what to do about it.
Spreadsheets are the most successful business software ever made, and for good reason. They are flexible, free and everyone already knows them. Most growing businesses run on a handful of them long after the business has become too big for that to be safe. The trick is noticing when the crossover happens.
Five signs it already has
- There is a version problem. Someone asks "is this the latest one?" more than once a week. Files have names like schedule-FINAL-v3-updated. Two people made edits to two copies and one set of changes is gone.
- One person is the only one who understands it. The pricing sheet or the job tracker has grown formulas and tabs that only its creator can maintain. When they are on vacation, work waits. When they leave, the business inherits a black box.
- Data gets re-typed into it. Numbers are copied from the CRM, the bank, or the timesheets into the sheet by hand. That is a person acting as an integration, and every copy is a chance for a typo.
- It has become a database. Thousands of rows, lookups across tabs, colour-coding that means something. A spreadsheet is a calculator that people are using as a system of record, and it has no permissions, no history and no validation.
- Decisions wait on it. The owner cannot answer "how are we doing this month" without someone spending an afternoon assembling the numbers. By the time the answer arrives, the month is over.
Why the obvious fix disappoints
The reflex is to buy an off-the-shelf app. Sometimes that works. Often the business has a process that is genuinely its own, which is why the spreadsheet grew in the first place, and the app forces the process to bend around the software. Six months later, the spreadsheet is back, feeding the app.
The reframe
The spreadsheet is not the problem. It is a very detailed specification of how your business actually works, written by the people who do the work. That makes it the best possible starting point for something purpose-built.
What to do instead
- Name the one sheet that hurts most. Not all of them. The one that causes the version problem or blocks the decision.
- Write down what it really does. Who enters what, who reads it, what it feeds. This is usually shorter than people fear.
- Replace that one with a small custom application that keeps the process and adds what the spreadsheet cannot: one shared copy, permissions, history, validation, and connections to the tools that feed it.
- Leave the other sheets alone until the first replacement has paid for itself.
Right-sized custom software for a 20-person business is not an enterprise project. It ships in weeks, and it is built around your process, not the other way around. If you recognised three or more of the signs above, a workflow audit will tell you which sheet to start with.