Every business starts on spreadsheets. There's nothing wrong with that. They're free, flexible, and every employee already knows how to open one. For the first few years of most small businesses, a well-maintained spreadsheet is genuinely the right tool.
But there's a moment (and most business owners recognise it only in retrospect) when the spreadsheet stops being a tool and starts being the problem. If you're searching for the signs your business has outgrown spreadsheets, there's a reasonable chance you're already past that point and just looking for someone to confirm it.
Here are seven of those signs.
Why we start on spreadsheets in the first place
Spreadsheets aren't the enemy. They're fast to build, infinitely flexible, and require no budget approval. When you're a 5-person business tracking 200 clients, a well-structured Excel file is the sensible choice. The problem isn't that you started there. It's when the business scales, and the spreadsheet doesn't.
Nobody designs a spreadsheet to handle 20,000 rows, three departments, and simultaneous edits from eight people. They design it to solve a problem this week. The accumulation of those weekly fixes is how you end up with the thing you've currently got.
Sign 1: Two people are editing the same file
You know the file. It lives in Dropbox, or SharePoint, or someone's OneDrive, and it has a name that tells you everything about its history: master-tracker_v7_FINAL_use-this-one.xlsx.
When two people open it simultaneously, one of them gets a copy. When they both save, one version gets overwritten. When you compare the two copies on Monday morning and realise they've been edited in conflicting ways over the weekend, someone has to spend an hour reconciling them by hand.
This is not a spreadsheet problem. This is a database problem wearing a spreadsheet costume. The fix is a shared system with a single source of truth, not more careful version naming.
Sign 2: You're copy-pasting between sheets to generate reports
One of the clearest tells in any operational audit is watching a team member open five spreadsheets and spend 45 minutes copy-pasting columns from one into another to generate a report that someone will look at for three minutes.
In one recent engagement, a compliance officer was replicating the same customer data into up to four different spreadsheet locations every time a record changed. Not because anyone asked her to design it that way, but because the system had grown by accretion, one spreadsheet at a time, over four years.
That 45-minute task almost certainly happens every week. It's roughly 40 hours a year of someone's time spent on work that a business automation script could do in seconds. The question isn't whether that's fixable. It obviously is. The question is how long you've been paying for it to happen manually.
Sign 3: The formula is broken and nobody dares fix it
There's a formula in the master tracker. It lives in column AJ. Nobody can quite remember who wrote it, and the person who probably did has been gone for two years. It sometimes produces a number that doesn't look right, and whenever it does, Dave adjusts it by hand and doesn't mention it.
This sign is slightly darker than the others, because it means your spreadsheet has crossed from "a tool" into "a system of record that we're afraid of." When the team treats a formula like unexploded ordnance, you no longer have a flexible tool. You have a liability.
The right fix depends on what the formula is actually doing. Sometimes a workflow audit reveals it's doing something that should be in proper software, sometimes it's doing something that doesn't need to exist at all. But ignoring it isn't a strategy.
Sign 4: There's no audit trail
"Who changed this number? And when?"
If nobody can answer that question, your spreadsheet isn't a record. It's a guess dressed up as a record. Spreadsheets don't track who edited what cell at what time. Google Sheets has a rudimentary version history; Excel's is worse. Neither is remotely sufficient for a business where accountability matters.
For businesses with any kind of compliance requirement (financial reporting, client data, contractual commitments) the absence of a proper audit trail is more than an operational inconvenience. It's a risk.
Proper software systems log everything. Who did what, when, and what it used to say before the change. If that accountability matters to your business (and it probably does), spreadsheets have already stopped being appropriate.
Sign 5: It's the bottleneck in every meeting
"I'll send you the latest sheet."
If that's the sentence that ends every meeting where someone asks about numbers, the spreadsheet is the bottleneck. Decisions get delayed because the right version isn't to hand. Meetings get called to align on what the data says rather than what to do with it.
This one compounds. The more decisions get routed through the spreadsheet, the more time gets spent maintaining it, which means it takes longer to get the latest version, which means more meetings, which means more time.
Business automation doesn't just save the time that goes into maintaining the spreadsheet. It saves the downstream time that gets consumed by everyone waiting on it.
Sign 6: You've got a "spreadsheet person"
Every business has one. They know how the master tracker works. They know which formula feeds which cell. They know that the colour-coded rows in column B mean something specific even though nobody documented what.
This person has become, without anyone deciding it should be this way, a single point of failure. If they're off sick, progress stalls. If they leave, you're suddenly six weeks into reverse-engineering something that should have been a documented system.
Having a "spreadsheet person" is a sign that your operations have been personalised to one individual instead of systematised. The business's knowledge is living in someone's head, and in a spreadsheet only they fully understand. That's not a people problem. That's a systems problem.
Sign 7: You're embarrassed by the data
Half-joking, half not: if you'd be uncomfortable showing your spreadsheet to your accountant, an auditor, or an inspector, that discomfort is information.
The usual reason is that the data isn't trustworthy. Not wrong exactly, but not reliable. There are gaps you can't explain, totals that don't reconcile cleanly, fields that mean different things depending on who entered them. The spreadsheet has become the thing you update for appearances rather than the thing you run the business on.
If you already know the data is shaky, you already know the spreadsheet has to go. The question is just what replaces it.
What to do about it, and what NOT to do
What not to do
Don't buy a generic SaaS platform first. The mistake most businesses make when they realise the spreadsheet is broken is to immediately sign up for the most well-marketed option they've heard of. Six months later, they've spent £600 in subscription fees, half the team hates the new system, and the other half are still using the spreadsheet because the SaaS doesn't quite do what they need.
Don't hire a consultant to "digitally transform" you. If the first meeting produces a roadmap and a deck but no actual work, you've hired the wrong people.
Don't ignore it. The spreadsheet problem doesn't get better on its own. The formula gets more fragile. The version history gets longer. The "spreadsheet person" becomes harder to replace. Technical debt in operations is exactly like technical debt in code: deferring it doesn't reduce it.
What to do
Start with a workflow audit. Before deciding what replaces the spreadsheet, you need to understand what the spreadsheet is actually doing. Sometimes a custom-built internal tool is the right answer: a proper database application that does the same thing, properly, with an audit trail and multi-user access. Sometimes the answer is a targeted automation that keeps the spreadsheet but removes the manual work around it. Sometimes the right answer is a better-structured spreadsheet with proper data validation and a Google Sheets formula that isn't terrifying.
The point is that the diagnosis comes first. Picking a solution before you've mapped the problem is how you end up back at square one in two years.
Most businesses that have outgrown their spreadsheets have also been burned by at least one previous attempt to fix it. The pattern is almost always the same: they bought something, it didn't quite fit, they adapted to it, they accumulated workarounds, and now they have the same problem in a different box.
The case study that comes up most often in this context: a specialist UK recruitment operation running eight disconnected systems (none of which talked to each other) with manual data entry bridging the gaps. The audit found exactly that pattern, consolidated the eight systems into a single HRIS, and rebuilt the onboarding workflow. The result was £24,520 per year in savings and fourteen hours a week per worker recovered. That wasn't found by buying new software. It was found by mapping what was actually there first.
If you're recognising your own business in two or more of these signs, it's worth a conversation. The 15-minute triage is free. You describe the bottleneck (the spreadsheet, the manual process, the formula nobody dares touch) and you'll get an honest answer on whether a fix is warranted and what shape it might take. No pitch. No deck. No commitment.