Skip to content
Andrew Herendeen
Go back

A spreadsheet is a database until it isn't

Edit page

Almost every business I’ve worked with runs something important on a spreadsheet. Not because anyone decided to — it just happened. A quick tracker became the source of truth, then three people depended on it, and now it’s load-bearing.

Spreadsheets are fantastic. They’re also a database in disguise, and disguises slip. Here’s how to tell when yours has crossed the line.

The warning signs

None of these mean the spreadsheet is bad. They mean it’s succeeding — it’s doing a real job — and the job has outgrown the tool.

What to do about it

You don’t have to leap to a custom application. The useful middle ground is to treat the data and the presentation as separate things.

  1. Get the data somewhere structured. Even a single well-formed table — one row per record, consistent columns, no merged cells — is most of the battle. That’s a database, conceptually, even if it still lives in a sheet.
  2. Keep formulas out of the data. Raw facts in one place, calculations in another. When inputs and logic are tangled, you can’t change either safely.
  3. Make the risky steps repeatable. The copy-paste ritual is exactly the thing worth automating first, because it’s where errors hide.

The honest take

I’m not anti-spreadsheet — I live in them. The point isn’t to abandon the grid; it’s to notice when it has quietly become your database and to give it the structure that a database would have demanded from day one. A spreadsheet that knows it’s a database is a much safer place to keep the numbers a business depends on.


Edit page
Share this post:

Previous Post
Why an accountant learned to code
Next Post
Reconciling faster with a small script