Five signs you've outgrown your spreadsheets

Let's be clear up front: spreadsheets are great. They're flexible, everyone knows them, and they cost almost nothing. Most businesses we work with started on spreadsheets, and they were the right call at the time.

The trouble starts when a spreadsheet stops being a tool and quietly becomes infrastructure — when the business doesn't just use the sheet, it runs on the sheet. That shift rarely announces itself. But there are signs, and they're remarkably consistent. Here are the five we see most often.

1. The filename has its own version history

Somewhere in a shared folder sits Q2-pricing_final_v3_REAL.xlsx. Next to it: final_v2, final_v3, and final_v3_REAL (copy). Last month, two people quoted customers from two different "finals."

Version suffixes are version control done by hand. They work right up until the moment someone picks the wrong file — and you usually find out from a customer, not from the spreadsheet.

2. One person owns the sheet, and nobody else dares touch it

Maria built the scheduling workbook four years ago. She knows why column Q is hidden, why you must never sort the data on tab three, and which cells are safe to type in. Everyone else has learned to ask Maria.

When Maria is on vacation, scheduling slows down. When Maria eventually leaves, you don't lose an employee — you lose the operating manual for part of your business. That's not a spreadsheet anymore. That's a single point of failure with a login.

3. Copy-paste between tools is part of someone's job

Every Friday before anyone goes home, someone exports the week's orders from the online store, pastes them into the master sheet, fixes the columns that never line up, then re-types the totals into the invoicing system. Two hours, every week, and it's been "temporary" for three years.

That person is acting as a human integration. It's tedious for them, expensive for you, and every paste is a chance for an error. Software can move data between systems automatically — that's precisely the kind of glue work it's good at.

4. Formulas break silently, and you find out weeks later

Someone inserts a row. A SUM range doesn't stretch to include it. The margin report is now quietly wrong — not blank, not flagged in red, just wrong — and it stays wrong for six weeks until your accountant asks why the numbers don't reconcile.

This is the spreadsheet failure mode that hurts most, because spreadsheets don't crash. They show you a confident, well-formatted wrong number, and you make decisions on it.

5. Permissions are managed by hope

The sheet that calculates payroll is shared with "anyone with the link can edit." Nobody has changed the formula in cell F14 — as far as you know. There's no record of who opened it, no review before changes go live, and the only thing standing between your payroll and an accidental keystroke is good intentions.

If that sentence made you slightly uncomfortable, it should. Hope is not a permissions model.

What graduating actually involves

Here's the part most owners get wrong: outgrowing spreadsheets doesn't mean buying an ERP. Big platforms solve a hundred problems you don't have and force your team to work the platform's way.

What usually fits is a small operational tool: a proper database, a few screens shaped around how the work actually flows, real user permissions, and integrations that retire the copy-paste job. One source of truth, no version suffixes, and numbers that either compute correctly or tell you loudly that something's off.

And the first step isn't writing code. It's mapping what the sheet really does — what feeds into it, who touches it, what decisions come out of it, and which of those hidden columns are load-bearing. That map is mostly built by asking questions, which happens to be our favorite part of the job.

So: how many of the five did you recognize? If it's two or more, your spreadsheet is probably infrastructure already — the only question is whether it's infrastructure you chose. Tell us about your sheet, or email hello@domandas.com.