When a spreadsheet becomes a liability.

Spreadsheets are one of the most useful tools a business can have. A blank grid with formulas is flexible enough to model a shopping list or a financial forecast, which is why so much of a small business's work tends to end up in them.

That flexibility is also why they become harder to work with over time. A spreadsheet built for one user and one process continues to be used long after both have changed.

When a spreadsheet is the right tool

• A single user maintains it.
• It represents a single, stable process.
• The dataset is small enough to scan by eye.
• The cost of a wrong cell is low.
• Nothing else depends on the output.

Under those conditions, a spreadsheet is a good fit, and replacing it with software is over-engineering.

When it stops being the right tool

The change is usually gradual. Most of the signals involve the spreadsheet quietly taking on responsibilities it wasn't designed for:

• More than one person edits it. Concurrent edits create version conflicts with no built-in way to resolve them.
• Other systems or processes depend on it. A formula in the sheet drives invoices, commissions, or reports. The spreadsheet is now infrastructure, without any of the reliability guarantees infrastructure usually has.
• Decisions are made from it. If the numbers are wrong, the business acts on incorrect information, and there's no record of who changed what when.
• It has grown past a few hundred rows. Performance and readability degrade, and errors become harder to spot.
• Critical data exists only in the file. Customer lists, pipelines, inventories. A lost or corrupted file is a material loss.
• Access isn't controlled at a useful level. Anyone with the link sees everything.

When more than one of these applies, the spreadsheet has taken on the roles of a database, an application, and a record of truth at the same time. It wasn't designed for any of those.

What replacing it involves

Replacing a spreadsheet isn't the same as moving the same structure into Airtable or a similar tool. Those products have their uses, but they tend to reproduce the same pattern with better styling. The underlying issue is that the process is being modelled as rows and columns at all.

The alternative is to model the process directly. State changes get recorded as they happen. Permissions become explicit. The audit trail exists because the software produces it, not because a user maintains one.

The spreadsheet doesn't always disappear afterwards. Some of what was in it really was spreadsheet-shaped. What changes is that it stops being the thing the business runs on.

The cost that's already being paid

Every process that runs on a spreadsheet has a recurring cost: the time someone spends keeping the spreadsheet accurate. That work is already in the business. Replacing the spreadsheet doesn't remove the work of running the process, but it removes most of the work of maintaining the tool that represents it.