When to Replace a Business-Critical Spreadsheet

Why your most important business process is running on a spreadsheet2026-04-09 — 6 min readNobody decided the business would run on a spreadsheet. It just kept working, until the day it didn’t. Here’s how to tell where yours is on that curve.Every established business has one. A workbook with a name like "MASTER_final_v4_USE_THIS.xlsx", understood in full by exactly one person, that the business can’t operate without.It got there honestly. Spreadsheets are the fastest way to model a process, and that flexibility is a real strength. The problem is that nothing ever signals when it’s time to graduate.Signals it has outgrown itself

More than one person needs it at once, and your process for that’s asking in Slack whether anyone has it open.

It contains data you would have to disclose if it leaked: personal information, payroll, customer records.

Someone re-keys its contents into another system. That’s a synchronisation job being done by a human.

There’s a recovery story that begins "we restore last week’s copy and redo the week."

Only one person fully understands the formulas, and the business has quietly become dependent on them not leaving.

Errors have reached customers. Once is bad luck; twice is a structural problem.

One of these is fine. Three or more and you’re carrying a risk you have not priced.What it’s costingSpreadsheet risk hides because it’s diffuse. Add up the hours spent re-keying, the time lost reconciling versions, the cost of errors that reached a customer, and the value of decisions delayed because nobody trusted the numbers. In most businesses we look at, the annual figure comfortably exceeds the cost of replacing it.Replace it without the risky rewriteThe instinct is a full custom system. Resist it. Big-bang replacements of processes nobody has fully documented fail at a high rate, because the spreadsheet encodes years of undocumented exceptions.A lower-risk sequence:

Document what it does, including the exceptions people handle manually. This alone is often revealing.

Move the data into a real database first, leaving the process alone. Concurrency, history and backup problems disappear immediately.

Replace the single highest-pain interaction with a proper interface. Usually data entry.

Add validation, so bad data can’t get in rather than being cleaned up later.

Only then automate the parts that are repetitive.

Each step is independently useful. If budget disappears after step two, you’re still better off than you started, which isn’t true of a rewrite abandoned halfway.When to leave it aloneNot every spreadsheet needs replacing. If one person uses it, the data isn’t sensitive, and an error would be an inconvenience rather than an incident, it’s doing its job. Flexibility is a genuine feature and software will take some of it away.The goal isn’t to eliminate spreadsheets. It’s to stop betting the business on one.More reading

What belongs in an MVP, and what founders keep putting in that shouldn’t

What a website costs in Calgary (and what drives the number)

Build or buy? A decision framework that survives contact with reality

Core Web Vitals, explained for people who don’t write code

Local SEO for Calgary businesses: what moves the needle