When spreadsheets stop being enough
Spreadsheets are excellent tools used past their limit. The question is not whether Excel can hold the data, but whether the process survives the people who maintain it leaving.
The four warning signs
Multiple people edit the same file and version conflicts are resolved by email. A formula exists that nobody can explain. Monthly reporting requires manual copy-paste between files. A single mistake in one cell changes a number that goes to a customer or a bank.
Two or more of these means the sheet is now a system without the safeguards of one.
The cheapest correct first step
Usually it is not an ERP. It is one small application for the single process causing the most rework, with a database behind it and an export that still feeds the spreadsheet.
Replacing one process at a time keeps the business running and gives you evidence about what the wider system needs.
What an ERP actually costs
Beyond licences, an ERP costs process redesign, data cleanup and training. Data cleanup is routinely underestimated: duplicate customers and inconsistent product codes surface the moment a system enforces uniqueness.
Common questions
- Can we keep using spreadsheets alongside a new system?
- Yes, for analysis and ad hoc reporting. The rule is that the system owns the data and the spreadsheet reads from it, never the reverse.
- How long does a first internal system take?
- A focused single-process application typically takes six to twelve weeks including data migration and training.
Next step
If this question is live in your business right now, describe the situation and you will get a written view on the options, including whether you should build at all.
Discuss your projectRelated notes
All insightsHow to justify an internal tool
A simple model for calculating whether an internal tool pays for itself, using hours recovered, error cost and the value of visibility.
ReadCustom softwareIntegrating systems without creating a spider web
How to connect CRM, ERP, payments and internal tools with clear ownership of data, retries and error handling.
ReadCustom softwareDatabase design mistakes that cost years
The modelling errors that are cheap to fix before launch and expensive afterwards: missing keys, storing derived data and treating status as free text.
Read