When spreadsheets stop working for your business

Almost every small business runs on a spreadsheet somewhere. That’s not a failure — spreadsheets are genuinely excellent. They’re free, everyone can use one, and you can build something useful in an afternoon without asking permission from anyone.

The trouble is that they’re so useful, they quietly get promoted. What started as a list becomes the quoting system. The quoting system grows a second tab for jobs. Someone adds a colour code that only they understand. Two years later, the business genuinely cannot operate if that file is corrupted, and nobody has ever said out loud that this is now critical infrastructure.

The line worth watching

The useful distinction isn’t size. We’ve seen perfectly healthy spreadsheets with thousands of rows, and disastrous ones with forty.

The line is this: a spreadsheet is fine while it’s a document, and becomes a problem when it becomes a system.

A document records something. A system is relied on by other people, feeds decisions, and has to be correct. Once a file crosses into the second category, all the things spreadsheets are bad at start to matter — permissions, history, validation, two people editing at once, and knowing which version is the real one.

The warning signs that actually matter

Most of the signs are about people rather than data.

Only one person really understands it. Not “wrote it” — understands it. If that person is on leave and something breaks, what happens? This is the single most common reason businesses call us, and it’s usually urgent by the time they do.

The same information gets typed twice. A customer’s details go into the spreadsheet, then into the invoice, then into the email. Every one of those is a chance to introduce a difference, and differences are what turn into arguments with customers later.

Something depends on someone remembering. A follow-up that happens because a person recalls it, not because the system raised it. That works right up until a busy week.

You’ve stopped trusting the totals. This one is telling. When people start checking the number by hand before they use it, the spreadsheet has already stopped doing its job — you’re now paying for the work twice.

What it’s actually costing

It’s rarely a dramatic failure. It’s usually a few hours a week spread across several people, in ten-minute pieces that nobody logs and nobody complains about, because it’s just how things are done.

That’s precisely why it goes unfixed for years. Nothing is on fire. It’s just slower and more fragile than it needs to be, and it gets a bit worse each quarter.

The important part: the fix is usually small

Here’s where a lot of advice goes wrong. The answer to “our spreadsheet has outgrown itself” is almost never “commission a custom system”.

In rough order of how often it’s the right call:

Configure something that already exists. Most businesses need a proper tool for one specific thing — jobs, quotes, bookings, stock — and there are good, cheap, proven options. Set up properly for how you actually work, that’s the answer far more often than anything custom.

Fix the joins instead of the tools. Frequently nothing is wrong with any individual tool; they just don’t talk to each other, so a person is acting as the integration. Connecting two things you already pay for can remove the retyping without changing how anyone works.

Move the data, keep the habits. Sometimes a spreadsheet is fine and the problem is that it lives on one laptop. Moving it somewhere shared, with proper access control and version history, solves the actual risk at almost no cost.

Build something. This is the right answer when the way you work is genuinely specific — when the reason nothing fits is that your process is a real competitive difference rather than an accident. It’s the least common case, and it’s the one worth being most careful about.

How to work out which one you need

Before looking at any software, write down what actually happens now. Not what’s supposed to happen — what happens. Who touches the information, in what order, and where does it get retyped.

That one page tends to answer the question on its own. It usually shows either an obvious gap that an off-the-shelf tool fills, or a process so specific that you can see immediately why nothing off the shelf has fitted.

If you’d rather not do that alone, that’s essentially what a business systems review is — a look at how the work moves, and an honest answer about whether you need to build anything at all. Quite often the answer is that you don’t.