ERP or Spreadsheets? Knowing When You Have Outgrown Excel

Spreadsheets are not the enemy. They are the most successful business software ever written, and most companies should stay on them far longer than a software vendor would like to admit.

But there is a point where the spreadsheet stops holding the business together and starts quietly costing it money. The trick is recognising that point — rather than switching too early because someone sold you on it, or too late because the pain crept up gradually.

TL;DR

• Spreadsheets fail on concurrency, history and enforcement — not on size.
• The real cost is rarely the software. It is the double entry, the reconciliation, and the decisions made on stale numbers.
• Do not replace everything at once. Move the process that hurts most and prove it.
• If your business logic genuinely is unusual, off-the-shelf will fight you. That is when custom is the cheaper answer.

Where Spreadsheets Actually Break

Not at ten thousand rows. They break on four things:

Seven Signs You Have Outgrown the Spreadsheet

1. Somebody's whole morning is copying figures from one file into another.
2. Two departments quote different numbers for the same month, and both can defend theirs.
3. The file has a version suffix — final, final-2, final-USE-THIS.
4. Only one person understands the formulas, and the business stops when they take leave.
5. You cannot answer "what did we have in stock last Tuesday?" at all.
6. Month-end close takes days, and most of it is reconciliation rather than analysis.
7. A customer asks about their order history and someone has to search four files to answer.

One or two of these is normal. Four or more, consistently, means the spreadsheet has become the bottleneck.

Off-the-Shelf or Custom?

Start by assuming off-the-shelf. It is faster, cheaper and someone else maintains it. Standard accounting, standard payroll, standard inventory — buy it.

Custom becomes the right answer when your process genuinely is not standard, and when that difference is the business. A manufacturer with unusual costing rules, a distributor with a pricing model no package can express, an institution whose workflow is set by regulation — these are the cases where configuring a package into shape costs more than building the thing properly, and leaves you with something nobody can maintain.

The honest test: if you find yourself planning to "work around" a package in three or more places before you have even bought it, you are about to pay full price for a poor fit.

Move One Process, Not Everything

Big-bang ERP rollouts fail for the same reason every time — too much change, all at once, on a deadline, while everyone is still doing their day job.

A sequence that works:

1. Pick the process that hurts most and has the clearest boundary. Usually inventory or invoicing.
2. Map it as it actually runs, including the exceptions people handle informally. Those exceptions are the requirements.
3. Clean the data before you migrate it. Moving mess into a new system produces a more expensive mess.
4. Run in parallel for one cycle. Old and new together for one month, and reconcile. This is where you find what the map missed.
5. Switch, then choose the next process.

Keep the Spreadsheet for What It Is Good At

The goal is not to eliminate spreadsheets. It is to stop using them as a database.

Once the system of record is a real system, the spreadsheet goes back to being an excellent tool for one-off analysis, modelling and quick answers — with the important difference that it now pulls from a single source of truth instead of being one.

See how we build a connected foundation, or tell us which process hurts most.