Somewhere in your company there is a spreadsheet that runs a critical process. It started as a quick tracker. Ten years later it has forty tabs, macros nobody dares open, and one person who understands it, and everyone quietly hopes they never win the lottery.
This is not a failure. It is what success looks like for a spreadsheet: it worked so well that the business grew around it. But there are signals that tell you it has crossed from asset to liability.
The five signals
1. More than three people edit it
Spreadsheets have no real concept of simultaneous editing with rules. Once several people write to the same file, you get silent overwrites, “final_v7_ACTUAL” filenames, and numbers that differ depending on who you ask.
2. It feeds decisions, but nobody can audit it
When a formula error can misprice a job or misstate inventory, “who changed this cell, when, and why” stops being a nice-to-have. Spreadsheets cannot answer it. Databases answer it natively.
3. The same data is typed twice
If someone re-keys rows from the spreadsheet into the accounting system, or from an email into the spreadsheet, you are paying a person to be an integration, and paying again for every typo.
4. It has become the training manual
New hires learn the process by learning the spreadsheet’s quirks: which cells never to touch, which tab is stale, which macro to run twice. That is business logic with no backup copy.
5. It is slow, and getting slower
A workbook that takes a minute to open and recalculates on every keystroke is telling you it has outgrown its container.
What replacing it actually looks like
The good news: replacing a mature spreadsheet is one of the most well-defined projects in custom software, because the spreadsheet is the requirements document. It already encodes your fields, your rules, your reports, and your edge cases. Our job is to read it carefully, including the formulas everyone forgot about, and rebuild it as a proper application: multi-user, permissioned, audited, connected to the systems around it, and usable from a phone.
Projects like this typically run weeks, not months, and the spreadsheet stays alive in parallel until the replacement has earned everyone’s trust.
What not to do
Do not announce the spreadsheet’s retirement before the replacement exists, and do not buy a generic platform first and try to bend the process into it. The spreadsheet survived a decade because it fits how your business actually works. Its replacement has to clear that same bar.
