Excel is not the enemy. Spreadsheets are genuinely brilliant tools, and most of the businesses I work with wouldn't have survived their early years without them. The problem isn't Excel — it's continuing to use Excel when a different kind of system would serve you better.
There's an inflection point in every growing business. Before it, spreadsheets are flexible, fast and cheap. After it, they quietly become the source of the most operational friction in the business — errors, version chaos, and an inability to answer basic questions about your own operation quickly.
The tricky part is that nothing announces the crossing of that line. The spreadsheet that worked fine at five clients is still open on someone's screen at fifty. It just costs a little more every month — in time, in mistakes, and in decisions made on numbers nobody fully trusts.
The warning signs
You have more than three spreadsheets that need to agree with each other. When data has to be manually copied between files, you have a synchronisation problem. Human beings are unreliable data transfer mechanisms. I worked with a utilities consultancy where the renewal pipeline lived in one workbook, the customer list in another, and site details in a third. Every quote required cross-referencing all three — and every month someone found a renewal that had been quoted against out-of-date site information.
The person who built the spreadsheet is the only person who can maintain it. Complex workbooks accrete logic over time — nested IFs, VLOOKUP chains, named ranges referencing other named ranges. When the person who built it leaves, goes on holiday, or simply can't remember why a formula works, the business is one bad edit away from a broken process. If this sounds familiar, your system isn't a spreadsheet — it's a single point of failure wearing a spreadsheet costume.
You're making decisions on data you don't fully trust. If your team regularly says 'the numbers should be roughly right' or 'I think this is up to date', you have a data quality problem. The cost isn't just checking time — it's the decision made on a figure that turned out to be wrong, discovered weeks later when it's expensive to reverse.
Adding a client means updating the same information in multiple places. Redundancy is a scaling failure. Each repeated entry is both a cost and an opportunity for the copies to diverge — after which nobody knows which version is true.
You can't answer operational questions quickly. 'How many clients are due for renewal this month?' 'What's our outstanding pipeline value?' 'Which sites haven't had a visit this quarter?' If these require opening several files, running calculations and hoping nothing changed in the meantime, your reporting infrastructure isn't fit for purpose.
What it actually costs
The direct cost is usually underestimated because it's diffuse — an hour here, an afternoon there. Across the businesses I assess, it's typically five to fifteen hours a week of skilled staff time spent on manual reconciliation, chasing versions and re-entering data. At a conservative £30 an hour fully loaded, that's £8,000–£23,000 a year, before you count the cost of errors or the revenue opportunities missed because nobody could see them.
The indirect costs are worse. Decisions get deferred because the numbers take too long to assemble. Growth gets constrained because onboarding another twenty clients would break the spreadsheet — and everyone quietly knows it.
When Excel is still the right answer
To be clear: if you're a team of two tracking a straightforward sales pipeline, a well-kept spreadsheet is probably the correct tool. The inflection point isn't about size — it's about the number of people who need the same data at once, the number of places the same fact is recorded, and the cost of being wrong. A small business with a complex process can outgrow Excel before a larger business with a simple one.
What replaces it
Not necessarily a bespoke system. The ladder looks roughly like this: first, disciplined spreadsheets — one source of truth per fact, protected sheets, no manual copying. Second, connected tools — your accounts, CRM and project tools actually talking to each other so data is entered once. Third, a structured system — a proper database with an interface built around your process, which is where bespoke starts to make sense.
The right question isn't 'should we stop using Excel?' It's 'which of our processes has outgrown it?' Usually it's one or two — and fixing those two is a much smaller project than people expect.