When a Spreadsheet Becomes a System
The point at which a spreadsheet stops being a tool and starts being infrastructure — and the four signs it has already happened.
Nobody decides to run their business on a spreadsheet. It happens by accretion — one tab to track a thing, a second so two people can both see it, a third because the first two stopped agreeing.
The question is not whether spreadsheets are bad. They are the fastest way to model a process nobody fully understands yet, which is exactly what you need early on. The question is when yours stopped being a draft and became the system of record.
Four signs it already happened
1. Someone owns it
Not "uses" — owns. There is a person who knows why column M is hidden and what breaks if you sort by date. When that person is on holiday, decisions wait. That is not a spreadsheet any more; it is an application with a single maintainer and no documentation.
2. There are rules nobody wrote down
Rows highlighted yellow mean something. The bottom section is archived but not deleted because a formula elsewhere still points at it. Every one of those conventions is business logic living in someone's head, and it leaves when they do.
3. You reconcile it against something else
If part of a regular routine is checking the sheet against the ERP, the CRM, or another sheet, you already have two systems of record and a manual process holding them together. That reconciliation is the real cost, and it grows with volume.
4. You have stopped changing it
The clearest sign. When people work around the sheet rather than modify it — keeping side notes, using a code in a comment field, maintaining a personal copy — the structure no longer fits the process and everyone has quietly agreed not to mention it.
What to do about it
Not necessarily replace it. A spreadsheet that four people use twice a month is fine, and rebuilding it as software is a waste. What matters is whether the cost of it being fragile has passed the cost of making it solid.
Two questions get you most of the way there. What happens if it is wrong for a week before anyone notices? And what happens if the person who owns it leaves tomorrow? If either answer is genuinely serious, the spreadsheet is infrastructure and should be treated like it.
The usual mistake at that point is to rebuild everything the spreadsheet does. Most of what a mature spreadsheet contains is workarounds for earlier limitations of the spreadsheet. Model the process, not the file.
Recognise any of this?
Start with a conversation. We will help you scope the problem before anything gets built.
Start a Project