Almost every established business has one: a spreadsheet that started as a convenience and now runs something important. Job scheduling, stock, quotes, compliance records, commission calculations.
It works. That is why nobody replaces it. Here is how to tell when working is no longer good enough.
The signs it has outgrown itself
More than one person needs it at once
Shared spreadsheets handle concurrent editing badly, and the workarounds are worse: a copy each, merged later; a rule that only one person edits before noon; a file named with a date and initials.
If your team has invented etiquette to avoid overwriting each other, that is the signal.
A mistake in it would cost real money
Spreadsheet errors are famously hard to see. A formula that stopped covering the last twenty rows when somebody inserted them looks entirely normal, and produces a wrong number every day until someone notices.
There is no validation, no warning and no audit trail. If a wrong figure would go out to a customer or into accounts, the risk is larger than it feels.
Its history matters
Who changed this price? When did this job move to complete? Who approved it?
Spreadsheets do not answer these questions. For anything with a compliance or dispute dimension, that is a genuine problem, covered in why audit logging matters.
Somebody maintains it rather than uses it
When a person spends four hours a week copying between tabs, reformatting exports and fixing broken references, you are paying a salary to sustain a file.
Only one person understands it
The nested formulas, the hidden columns, the macro that must be run on Fridays. When that person is on leave, work stops. When they leave permanently, it becomes an archaeology project.
The dangerous spreadsheet is not the one that breaks. It is the one that quietly produces a plausible wrong number and has done for months.
What it costs while nobody acts
Four costs, and only the first is visible.
Time. Hours a week on maintenance and reconciliation.
Errors. Not the ones you caught — the ones you did not.
Constraint. Things you do not attempt because the spreadsheet could not cope. That is invisible and often the largest.
Key person risk. A concentration of operational knowledge in one head.
What replaces it
Not necessarily a custom build. Work through the options in order:
A better-structured spreadsheet. Sometimes the real problem is that one file is doing four jobs. Splitting it, adding validation and locking formula cells solves more cases than people expect, at no cost.
An off-the-shelf product. If your spreadsheet is a job scheduler, buy a job scheduler. See build versus buy before commissioning anything.
A database tool. Products designed for structured records with a spreadsheet-like interface handle multi-user editing, permissions and history without a development project.
A custom application. Right when the process is genuinely yours and the alternatives would force costly workarounds.
How to replace one without disruption
Understand what it actually does
Sit with whoever runs it for a morning. Every spreadsheet contains rules nobody documented — the column that is left blank on purpose, the manual adjustment applied to one customer, the tab used once a quarter.
Those undocumented rules are the requirements. Skipping this step is why replacements get rejected by the people who have to use them.
Replace one job at a time
If the spreadsheet does scheduling, invoicing and reporting, take scheduling first. A narrow replacement that works completely beats a broad one that half works.
Run in parallel
Keep the spreadsheet alongside the new system for a few weeks and compare. Where the figures differ, one of them is wrong, and finding out which is valuable in itself.
Parallel running is also what gives people permission to stop keeping a private copy, which they will otherwise do indefinitely.
Migrate the history deliberately
Years of records in that file usually matter. Decide what comes across and in what form before launch, not after — the pattern is the same as any other migration, covered in migrating without losing history.
Make the new thing faster than the old one
People revert to the spreadsheet when the replacement is slower for the daily task. If entering a job took thirty seconds and now takes two minutes because of a longer form, the system will be abandoned quietly.
Keeping spreadsheets where they belong
None of this is an argument against spreadsheets. They are excellent for one-off analysis, modelling, quick calculations and anything exploratory.
The failure mode is specific: a spreadsheet that became an operational system by accident, without anyone deciding it should. Those are worth addressing before something goes wrong rather than afterwards.
Our automation team replaces business-critical spreadsheets for UK companies, and frequently recommends restructuring rather than rebuilding. Show us the spreadsheet and we will tell you which it needs.
