Seven signs you have outgrown spreadsheets

Let us start by defending spreadsheets, because most advice on this topic is snobbery.

Spreadsheets are one of the great tools of business. They are flexible, universal, free-ish, and they fit your process exactly because you built them around it. For a huge range of jobs they are the right answer, and plenty of businesses reach for heavy software when a good spreadsheet would have served them better and cheaper. If a spreadsheet works, keep it. Do not let anyone shame you off a tool that is doing its job.

But spreadsheets fail in specific, predictable ways — always the same seven. When you see these, you have not failed at spreadsheets; you have simply reached the edge of what the tool can do. Here is how to recognise the wall.

1. Two people need to edit the same thing at once

The defining limit. A spreadsheet is fundamentally a single-person tool wearing a multi-person costume. The moment two people need to update it simultaneously — and reliably, without one overwriting the other or working off a stale copy — you are fighting the tool's nature.

You will recognise this as: "don't touch the file, I'm in it", versions named final-v3-USE-THIS, and the sinking discovery that someone has been editing last week's copy all morning. That is not misuse. That is the tool's ceiling.

2. Nobody is sure which version is real

Spreadsheets multiply. They get emailed, copied, saved locally, renamed. Soon there are several versions and genuine uncertainty about which is authoritative. When "let me check I have the latest" becomes a routine sentence, the spreadsheet has stopped being a single source of truth — which was the one job you needed it for.

3. You cannot answer a simple question quickly

"How much did we sell last month, by product, by channel?" If answering means an afternoon of copying, pasting and VLOOKUPs across several files, your data is trapped in a shape that resists questioning. The information exists; you just cannot get at it without manual labour every time. A business that cannot cheaply ask basic questions of its own data is flying with the instruments in a drawer.

4. The rules live in one person's head

The spreadsheet works because Ah Ling knows that column K only applies to the KL branch and the total ignores row 40 because of that one client. None of that is written down. It is in her head, and the spreadsheet is a fragile shell around her knowledge.

When Ah Ling is on leave, the process stops. When she leaves, it breaks. A business rule that exists only in a person's memory is a risk, not a system — and the spreadsheet is hiding how exposed you are.

5. Mistakes are silent and expensive

A spreadsheet will let you overwrite a formula, mistype a number, drag a cell wrong — silently, with no warning and no record of who did it or when. Errors hide until they cause a problem, and then you cannot trace them. There is no audit trail, no permission, no validation. For anything involving money, that silence is dangerous, and it gets more dangerous as the stakes grow.

6. You are copying data between spreadsheets

When one spreadsheet feeds another, and someone manually keeps them in sync, you have built a fragile machine out of a tool never meant for it. Every manual copy is a chance to introduce an error or fall behind, and the sync is only as reliable as the busy person doing it. This is usually the sign you have outgrown not just a spreadsheet but the spreadsheet approach — you are simulating a database with human glue.

7. Approvals happen outside the spreadsheet

The spreadsheet records the purchase, but the approval happened in WhatsApp, or verbally, or not at all. The spreadsheet cannot enforce that something is checked before it proceeds — it is a passive record, not an active process. When your actual workflow lives half in a spreadsheet and half in messages and memory, the spreadsheet has stopped being able to hold your process.

What the signs have in common

Look at the seven and notice the pattern: spreadsheets fail at collaboration, at scale, at process, and at trust. They are brilliant single-person calculators and passive record-keepers. They are poor at multiple people working together, at enforcing that steps happen, at keeping an honest history, and at answering questions across a lot of data.

Which tells you exactly what you need next — and, importantly, what you do not.

What you do not need

You do not need a giant ERP. That is the overcorrection, and it is how businesses go from a tool that is too light to one that is far too heavy, expensive and rigid — trading one bad fit for another. The gap between "outgrown spreadsheets" and "needs SAP" is enormous, and most businesses sit squarely in it. See why ERP failed small businesses for why that middle ground stayed unserved for thirty years.

What you need is something that keeps the flexibility you loved about spreadsheets — the fit to your actual process — while adding the things spreadsheets cannot do: real collaboration, a single source of truth, enforced process, permissions and an audit trail. That is a very different requirement from "enterprise ERP", and matching it is the whole point of describing what you need instead of configuring modules.

What to do about it

Do not rip out every spreadsheet in a panic — that is a project, and projects stall. Find the one spreadsheet that is causing the most pain from the list above — usually the shared one that people fight over, or the one holding rules only one person knows — and replace just that one. Feel the difference. Then find the next.

Most spreadsheets in your business are fine and should stay. It is the two or three load-bearing ones — the ones that have quietly become critical systems held together by convention and one person's memory — that have outgrown the tool. Replace those, keep the rest, and you have solved the actual problem without buying an ERP you did not need.

Common questions

How do I know when a spreadsheet has stopped being good enough?

Watch for the specific failures rather than general untidiness. Two people needing to edit the same thing at once. Nobody sure which version is real. A simple question — how much did we sell last month, by product, by channel — taking an afternoon. The rules living in one person's head. Mistakes that happen silently with no record of who made them. Data copied by hand between files. Approvals happening in WhatsApp instead of in the sheet.

Should I replace all my spreadsheets?

No, and doing it in a panic is a project, and projects stall. Most spreadsheets in your business are fine and should stay: they are flexible, cheap, and they fit your process exactly because you built them around it. It is the two or three load-bearing ones that have outgrown the tool — usually the shared file people fight over, or the one holding rules only one person knows. Replace those, feel the difference, keep the rest.

What is the risk of business rules living in one person's head?

The process stops when that person is on leave and breaks when they resign. A spreadsheet works because a colleague knows that one column only applies to one branch, and that the total ignores a particular row because of one client — none of which is written down. The file is a fragile shell around her knowledge. A business rule that exists only in a person's memory is a risk, not a system.

If I have outgrown spreadsheets, do I need an ERP?

Not a giant one. That is the overcorrection, and it trades a tool that is too light for one that is far too heavy, expensive and rigid. The gap between "outgrown spreadsheets" and "needs SAP" is enormous and most businesses sit squarely in it. What you need keeps the fit to your actual process that you liked about spreadsheets, while adding real collaboration, a single source of truth, enforced process, permissions and an audit trail.

If you want to work out what this would look like in your business, talk to us — including if the honest answer is that you are not ready yet.

Related: signs you have outgrown your accounting software and SmartB vs spreadsheets.

Also worth reading: do you even need an ERP.