Why spreadsheets win in the first place
It is worth being fair to the spreadsheet, because most articles on this subject are not. It is the best piece of business software ever made. It costs nothing you are not already paying, everyone can use one, it takes any shape you need on a Tuesday afternoon, and it never requires a meeting with a supplier.
That flexibility is exactly why businesses run on them far past the point of sense. There is never a day when the spreadsheet stops working. There is only a slow accumulation of small workarounds, each one individually reasonable, until the workarounds are the system.
Outgrowing one is not a failure of planning. It is what success looks like from the inside: more customers, more staff, more moving parts than a grid of cells can hold honestly.
The seven signs
Any one of these on its own is survivable. Three or more together is a business paying a tax it has stopped noticing.
1. The same fact is typed in more than once. A customer’s order arrives by email, gets typed into a sheet, then into an invoice, then onto a delivery note. You are paying for that work three times and buying three chances to disagree with yourself.
2. There is a master copy, and people hesitate over which one it is. If the answer involves a date in a filename, a folder called Final, or the phrase “the one on my desktop”, the single source of truth has already gone.
3. It needs a person to interpret it. When a colleague cannot answer a question from the sheet without asking whoever built it what a column means, the knowledge is in a head, not a system. That head takes holidays and eventually another job.
4. Access is all or nothing. You want a subcontractor to see their job without seeing your margins, or an employee to see their rota without seeing payroll. A spreadsheet cannot really do that, so the workaround is a second, hand-cut copy — which is sign one wearing a disguise.
5. Two people editing it is a known hazard. Everyone has learned a small ritual: ask before you open it, keep it open for as short a time as possible, copy it first. Any process with folklore attached is a process under strain.
6. The formulas are load-bearing and one person understands them. There is a tab nobody touches, with a lookup nobody can explain, that quietly decides the numbers everyone quotes. This is the risk that turns into a crisis on exactly the wrong week.
7. Answering “how did we do” is an assembly job. Exporting from three places and reconciling them by hand every month is not reporting. It is manufacturing a report, by hand, repeatedly, from parts.
The one that matters most
If you only act on one, make it the second: more than one version of the truth.
Everything else on the list costs time. This one costs decisions. When two copies of a number exist, some of your decisions are being made against the wrong one, and you will not find out which until a customer or an accountant tells you. The cost is not the reconciliation work. It is the quote that was wrong, the stock you did not order, the month you thought was better than it was.
A useful question at any management meeting: if two people in this room looked up the same figure right now, in the way they normally would, would they get the same answer? If you cannot say yes confidently, that is the problem to solve first — before dashboards, before automation, before anything.
What replacing it properly looks like
The wrong answer is a bigger spreadsheet, and the second wrong answer is a large platform that does everything except the one thing your business does differently.
What actually works for a small business is smaller than people expect. In practice it is a simple, secure web application with four properties:
- One record per real thing. One row per job, customer, order — existing once, with a history attached. Not a row per row.
- Entered once, used everywhere. The quote becomes the job becomes the invoice, carrying its own data forward rather than being re-typed into the next stage.
- Roles, not copies. Each person signs in and sees their part — the engineer their route, the client their own jobs, the owner everything. Restriction by permission, not by maintaining separate files.
- It cannot be edited into an invalid state. A job cannot be marked complete without the thing that makes it complete. Rules the spreadsheet could only ask nicely for are enforced.
That is the shape of the web apps in our services section — and it is deliberately a thin layer, not a replacement for your accounting package or your email. We set out where that line falls in custom software or off-the-shelf.
What to keep the spreadsheet for
Do not throw them out. After a build, the businesses we work with still use spreadsheets constantly, and should — just for different work.
Spreadsheets are excellent for thinking: modelling a price change, sketching next year’s numbers, working out whether a second van pays. Anything one person does once, to answer a question, and then throws away.
They are poor at being the permanent record that several people depend on at the same time. The line is roughly that: a spreadsheet is a calculator, not a filing cabinet. Trouble starts when a calculation quietly becomes the place the business keeps its facts.
Moving without a big bang
The fear here is reasonable: everyone has heard of the migration that took a year and left the business worse off. The way to avoid it is not a better plan, it is a smaller first step.
- Move one noun, not the whole business. Jobs, or customers, or stock — whichever causes the most re-typing. One thing, done properly, beats four things half-done.
- Run both for a fortnight. Keep the spreadsheet updated alongside. It is duplicate work for two weeks and it is the cheapest insurance available.
- Import the history, do not re-key it. If the old data cannot be brought across cleanly, that tells you something important about its quality — better to learn it now.
- Agree what “done” means before starting. In writing, with a date. Our second phase exists entirely because of this.
Once one thing lives in one place, the next steps get much cheaper — the reporting stops being an assembly job (see what a business dashboard should actually show) and the re-keying becomes automatable (see what to automate first). Both of those depend on this one being done.
The ten-minute check
Open the spreadsheet your business most depends on. Ask three questions. Is there another copy of this anywhere? Could a new starter read it without a translator? If the person who built it left tomorrow, what would break?
If those answers are uncomfortable, you already know. The only question left is whether you fix it now, while it is a project, or later, when it is an incident.