When the spreadsheet stops keeping up
A spreadsheet is a great tool until the day three people need to work in it at once. A few signs that the process already calls for a system, and what to do before hiring someone to build one.
Systems. October 22, 2026. 6 min read.
Almost every system we build started out as a spreadsheet. That speaks well of the spreadsheet. It's quick to set up, everyone knows how to use it, and it accepts information in any format. For a new process that still changes every week, it's hard to find anything better.
The trouble shows up later, when the process grows and the spreadsheet stays the same.
The signs
None of them alone means it's time to switch. When three or four show up together, it's worth stopping to think.
One person has become the owner of the spreadsheet. Only they know what the yellow column means, why the "June (2)" tab exists and which formula must never be deleted. When that person goes on vacation, the process stops or runs wrong.
The same information gets typed in more than one place. The order comes in over WhatsApp, goes into the spreadsheet, then into the invoicing system and then into another spreadsheet for commissions. Every hand-off is a chance for error, and nobody knows which copy is right.
Nobody trusts the end-of-month number. Before any meeting, someone spends an afternoon checking the spreadsheet line by line. That work is invisible because it doesn't show up anywhere, except in how tired the person doing it is.
The people who need to know find out late. A customer asks about an order, the team opens the spreadsheet, calls the warehouse and answers an hour later. The information existed. It just wasn't where the person needed it.
Two people edit at the same time and one wipes out the other's work. Online spreadsheets have gotten much better at this, but row-level permissions, a history of who changed what, and rules like "only the manager approves discounts above 10%" are still hard to set up.
What changes with a system
A system built for the company's process deals with these signs in a very practical way. Each piece of information is typed once and shows up everywhere it's needed. The rules live in the code, so a discount above the limit simply asks for approval. Each person sees what they need to see. And the history records who did what, and when.
There's a cost, and it's worth being upfront about it. A system takes weeks to build, and changing a rule is no longer a matter of editing a cell. That's why the switch only pays off once the process is reasonably stable. If it still changes every week, the spreadsheet is still the right tool.
Before you hire anyone
Three things help a lot, whether you work with us or with any other company:
- Map the path of a real order. Take a case from last week and write down every person it went through, in which tool, and how long it sat still. That map is worth more than a list of features.
- Separate rules from habits. "Finance checks before invoicing" may be an important rule or a habit that started because something went wrong one day. The system should carry the rules. The habits deserve to be questioned.
- Pick the first piece. A system doesn't need to replace the whole spreadsheet on day one. Starting with the part that hurts most, say, entering orders, already removes most of the rework and shows quickly whether the approach is a good one.
If you'd like, send us that map on WhatsApp. We'll tell you what we think, even if the answer is to stay with the spreadsheet a while longer.
