Insights / Custom Software
When should spreadsheets become custom software?
Spreadsheets are the most successful business software ever made. Here is how to tell when yours has quietly become a system that needs to be built properly.
Nearly every custom system we design starts life as a spreadsheet. That is not a failure. Spreadsheets are flexible, familiar and fast to change, which is exactly why businesses use them to run processes nobody planned for.
The problem is that spreadsheets are very good at being a tool and very bad at being a system. The moment one crosses that line is rarely obvious, because it happens gradually: one more tab, one more person with edit access, one more macro.
Signs your spreadsheet has become a system
- Several people depend on it every day. If work stops when the file is locked, broken or missing, it is infrastructure.
- Errors are expensive. A wrong cell means a wrong invoice, a missed delivery or a compliance problem.
- You need history. People ask "who changed this, and when?" and nobody can answer.
- You need permissions. Some people should see or edit some rows but not others.
- Data is copied in and out. Someone exports from one system and pastes into the sheet, then back out again.
- One person understands it. The formulas, the macros and the unwritten rules live in one head.
What changes when you build it properly
Custom software gives the process a real data model, meaning records with relationships, validation and history. It gives each role a screen designed for what they do instead of one giant grid. And it lets the process connect directly to the systems around it, so data stops being re-typed.
It also forces clarity. Turning a spreadsheet into software means writing down the rules that were previously implicit. That exercise alone usually uncovers inconsistencies the business did not know it had.
What should not change
The best replacement keeps what people liked about the spreadsheet: speed, flexibility and the ability to see a lot of information at once. A system that is slower to use than the file it replaced will be quietly abandoned, and the spreadsheet will come back.
A practical way to decide
- List every spreadsheet that more than two people rely on.
- For each, note what goes wrong when it is wrong, and how often.
- Estimate the hours spent maintaining, copying and checking it.
- Pick the one where the cost of error and effort is highest, and start there.
You rarely need to replace everything at once. A focused first release that removes the most painful spreadsheet often pays for the thinking behind the next one.
Recognise this problem in your business?
Tell Us Your Problem
