When the spreadsheet became a system: the hidden cost of internal tools
Every business runs on tools it never chose — the spreadsheet that quietly became critical, the app that half-fits. They work, until the day they don't. Here's how to tell when a custom tool has stopped being a convenience and started being a risk.
Walk into almost any operations meeting and you’ll find it: a spreadsheet that started life as one person’s shortcut and is now load-bearing. Nobody decided it would run the business. It just crept there, one clever formula at a time, until a process the company depends on lives inside a file that a single laptop crash could take with it.
This is the internal-tools trap, and it’s rarely a technology failure. It’s a success that outgrew its container.
Why the workaround wins, then loses
Workarounds win at first for a good reason: they’re fast, free, and shaped exactly to the problem by the person who has it. A spreadsheet, a shared inbox, a folder of templates — each one solves something real, today, with no procurement cycle and no IT ticket. That’s genuinely valuable, and we’d never tell a team to stop.
The trap is that the same qualities that make a workaround useful make it fragile at scale. There’s no audit trail, so you can’t prove who changed what. There’s no validation, so a fat-fingered entry propagates silently. There’s a single point of knowledge — the one person who understands the macros — and the day they leave, the process leaves with them. The tool didn’t get worse. The stakes got higher.
The signs it’s time
You don’t need a formal review to know. The signals are usually sitting in plain view:
- A business-critical process lives in a file only one or two people fully understand.
- Approvals happen over email, with no reliable record of who signed off, or when.
- The month-end, the reconciliation, or the report that leadership asks for eats days of manual effort every single cycle.
- You’ve stopped trusting the numbers, so people quietly keep their own version.
Any one of these means the workaround has crossed from convenience to liability. Two or more, and it’s costing you more than it saves — you just can’t see the bill, because it’s paid in risk and hours rather than a line item.
What “replacing it” actually means
The instinct is often to buy a big platform, but that’s usually the wrong move. A packaged product asks you to bend your process to fit it, and the reason the spreadsheet exists in the first place is that your process is specific. The right answer is usually smaller and sharper: a custom tool that encodes the rules you already follow, keeps a clean trail, and turns the recurring effort into a few clicks — while connecting to the systems you already run rather than replacing them.
Done well, it’s not a big-bang project. You retire one risky spreadsheet, ship it in weeks, and give your team something they own and understand. Then you do the next one. The goal isn’t to digitise everything at once; it’s to take the load-bearing workarounds off the critical path, one at a time, before one of them fails at the worst possible moment.
The honest test
Before building anything, we ask a blunt question: what happens if this tool disappears tomorrow? If the answer is “we lose a bit of convenience,” leave it alone — not everything needs to be engineered. But if the answer is “we can’t close the books,” or “we can’t dispatch,” or “we can’t prove compliance,” then it was never really a spreadsheet. It was a system all along. It just never got built like one.