Engineering · 5 min read
The spreadsheet is the system. Treat it like one.
Most companies run a critical process on a spreadsheet nobody is allowed to close. Here is how we replace one without breaking the business that depends on it.

Arslan Javed
October 14, 2026
Almost every company we talk to has one. Fourteen tabs, three people who understand it, and a quiet rule that nobody closes it on a Friday afternoon. It started as a quick fix and became the thing invoices, schedules or stock levels actually depend on.
It is not a spreadsheet. It is a business system that was never given a budget, a test suite or a second owner.
Why it is harder to replace than it looks
The official process lives in the ERP or the CRM. The real process lives in the spreadsheet, and the gap between the two is filled by someone's evenings. That means the spreadsheet encodes decisions nobody wrote down anywhere else:
- The exceptions. The customer who is billed differently, the supplier whose prices are keyed in by hand, the column that is overwritten every quarter for reasons lost to history.
- The timing. Which tab is updated first, which numbers are stale on purpose, which totals are only trusted after a particular person has looked at them.
- The workarounds for other systems. Half the formulas exist because an export from somewhere else arrives in the wrong shape.
A replacement that ignores any of this will be rejected by the people who use it, and they will be right to reject it.
How we approach it
Read the spreadsheet before writing a line of code. We go through it tab by tab with the people who maintain it and write down what each part does, including the parts they are slightly embarrassed about. This usually takes two or three sessions and produces the real requirements document.
Build the boring version first. The first release does exactly what the spreadsheet does, with the same inputs and the same outputs, plus validation, history and more than one person who can run it. No new features. The goal is that the three people can stop being on call.
Run both side by side. For a few weeks the spreadsheet and the new system both run, and we compare the outputs every day. Every difference is either a bug in our system or a bug in the spreadsheet that nobody had noticed. There are always some of the second kind.
Then connect it. Once the numbers agree, the new system starts pulling from the ERP, the bank feed or the supplier portal directly, and the manual exports stop. This is where the time savings actually arrive.
What it costs and what it saves
A replacement for a load-bearing spreadsheet is rarely a large build. The logic is already worked out; it just lives in the wrong place. Most of the ones we have done were a few months of work for a small team.
What it saves is harder to see on a quote and easy to see a year later: the evenings, the errors that reached a customer, and the month when one of the three people went on holiday.
If you have one of these, we would genuinely like to see it. The eleventh tab is usually where the interesting part is.