Signs your business has outgrown its spreadsheets
Spreadsheets are excellent until they quietly become the thing your business depends on and nobody controls.
Nearly every custom system we build replaces a spreadsheet, and in almost every case the spreadsheet was the right answer once. The problem is that nothing tells you when it stopped being right, because it degrades slowly and everybody adapts around it.
Here are the specific signals, and what to do about each, including the times when the answer is not to build anything.
1. Somebody re-keys the same data twice
Information leaves one system, lives briefly in a spreadsheet, and gets typed into another. Every re-keying is a chance to introduce an error and an ongoing salary cost nobody has ever added up.
What to do: count the hours a week and multiply by a rate. That number is what you are already paying. Often the fix is not a new system at all but connecting the two you have.
2. The file has a person's name in it
pricing_v4_FINAL_dave.xlsx. When a business process depends on a particular person's copy of a particular file, that is key-person risk with a filename, and it is only invisible while Dave is at his desk.
What to do: whatever else you do, get it somewhere shared and versioned this week. That is free and it removes the worst outcome.
3. Nobody can answer a simple question quickly
"How many jobs did we run last month for that client, and what did they cost us?" If that takes an afternoon and three files, the data exists but the answers do not. Businesses in this state usually cannot see job-level margin until long after the fact, which is exactly what one logistics client dealt with before their platform existed.
What to do: write down the five questions you wish you could answer instantly. That list is a better brief than any feature list.
4. The process lives in WhatsApp
The spreadsheet holds the plan, and the actual coordination happens in messages, calls and someone's memory. It works right up until the day two people are working from different versions of the truth. We saw the pattern clearly in a cleaning operation whose rota lived in a spreadsheet and got re-sent on WhatsApp every time it changed.
What to do: this one rarely fixes itself with better spreadsheet discipline, because the problem is that several people need different views of the same live information at the same time. That is what software is for.
5. Every new client or product makes it worse
Healthy systems get cheaper per unit as you grow. If each new client means another tab, another manual step, or another thing to remember, your admin cost is growing at least as fast as your revenue.
What to do: work out the cost per client of the current arrangement, then again at double the clients. If it does not improve, the spreadsheet is now capping your growth rather than supporting it.
6. You are afraid to change it
Formulas nobody understands, written by somebody who left. Nobody dares touch it, so workarounds accumulate around it instead. A system everyone is frightened of is a system that has already failed, it just has not fallen over yet.
What to do: this is the point at which doing nothing is the expensive option.
When the answer is not to build
Two honest exceptions.
If the process is not agreed, software will not fix it. Encoding a confused process makes it expensive to change your mind later. Sort it on paper first, and you may find the spreadsheet works fine once everyone is doing the same thing.
If a product already does it. Accounting, payroll, scheduling for common trades and general CRM are solved problems. Build the part that is genuinely yours, buy the rest, and read bespoke or off the shelf before briefing anybody.
What replacing it usually looks like
Rarely one enormous system. More often the awkward middle bit, connected to the products you already use, so the data stops being re-keyed and the questions become answerable. Starting small also means starting cheaply, and simple projects start from around £1,500.
If a spreadsheet has become load-bearing in your business, tell us what you are trying to build and we will tell you honestly whether it needs software or better process.
Sounds like your situation?
A 20-minute conversation, in plain English. We’ll tell you honestly what it would take.