Seven signs the spreadsheet running your business needs to become a system.
How to tell when a spreadsheet, shared inbox or paper process has reached its limit, what replacing it actually involves, and what to keep.
By the Wovekit team · · 6 min read
Every small business has one: the spreadsheet (or shared inbox, or WhatsApp group) that the whole operation quietly depends on. It started as a quick fix and became the system of record. Nothing is wrong with that. Spreadsheets are the most successful business software ever written, and the best time to replace one is later than most consultants will tell you.
But there is a point where the spreadsheet stops saving time and starts costing it. Here is how to recognise it.
1. Only one person really understands it
There are columns nobody dares delete, a tab called 'OLD do not use' and formulas that break when someone sorts. When that person is on holiday, the business slows down. That is not a spreadsheet problem; it is a single point of failure dressed as one.
2. The same information is typed in more than once
A customer's details go into the spreadsheet, then the invoice, then the calendar, then the email. Each copy drifts. Rekeying is the clearest sign that the data wants to live in one place with the other tools reading from it.
3. Reminders are a person, not a process
Deposits are chased when someone remembers. Appointments are confirmed by hand. Follow-ups happen if the inbox is quiet. A system does these on a schedule, every time, and tells you when it could not.
4. Customers ask for things they could do themselves
Can I move my booking? What is the status of my order? Can you resend the document? Every one of these is a phone call or an email that a portal would answer at two in the morning without anyone involved.
5. You cannot answer a simple question without a project
How many jobs did we complete last month, and how long did each take? If the answer involves exporting, filtering and a pivot table, the data is there but the system is not.
6. Mistakes have started to cost money
A double booking. A deposit never taken. A quote sent with last year's prices. Spreadsheets have no rules; they let you type anything into any cell. Systems have validation, roles and history, so the mistake is prevented or at least traceable.
7. You have tried two off-the-shelf tools and kept the spreadsheet
This is the decisive one. If generic software did not fit, it is usually because your process has exceptions the tool cannot express. That is exactly the case for building something around your rules rather than bending your rules around a product.
What replacing it actually involves
Less than people fear, provided it is done in the right order.
- 1.Map the process as it really runs, including the workarounds. The workarounds are the requirements.
- 2.Pick the one process that matters most. Not all of them. One.
- 3.Import the existing data; do not start from an empty system.
- 4.Release something usable within two weeks: usually intake and a status list. Let one team use it with real data.
- 5.Switch on automation one piece at a time (confirmations, reminders, reports), each with a number attached so you can see what it saved.
- 6.Keep the spreadsheet running alongside until nobody opens it. Then archive it.
What it tends to cost
A first process, built this way, usually sits in the £5k to £15k band and takes three to eight weeks. The payback is measured in hours: the ones no longer spent rekeying, chasing and apologising. If you want a sense of the shape before talking to anyone, our planner at /plan will turn a description of how things work today into a short brief.
Short answers.
Should we just buy an off-the-shelf tool instead?
Often yes, and we will say so. Buy when your process is standard and you are willing to change it to fit the tool. Build when the process is your edge, when you have tried two tools and still keep the spreadsheet, or when the exceptions are what make the work hard.
Will we lose the data in the spreadsheet?
No. Importing the existing data is part of the first release, and the spreadsheet usually keeps running alongside the new tool for a few weeks until everyone trusts it.
How long does the first version take?
For one process, three to eight weeks, released weekly. The first useful release, often just intake plus a status view, is usually live within a fortnight.