Your spreadsheet is a database with no seatbelt

A spreadsheet that runs a business is not a failure. It’s a success that outgrew its container. It became the database because it was the only thing everyone could open, and it has been doing its best ever since.

The trouble starts when nobody has decided how to handle conflicting edits, bad values, permissions or customer updates. And when spreadsheets go wrong, they rarely crash. They quietly carry on with the wrong answer.

When spreadsheets go wrong, they go quietly

Two real cases, from people far better resourced than most small businesses:

• Gene names became dates. Excel turns a gene called SEPT2 into “2-Sep”. Researchers screened 3,597 published papers with gene lists in Excel and found errors like that in 704 of them: roughly one in five.
• A file ran out of rows. In 2020, England’s public health agency used an old Excel format that held only about 65,000 rows. The BBC reported that nearly 16,000 coronavirus cases went unreported as a result. Today’s format holds 1,048,576 rows. The limit that bites small businesses is usually a different one: the one person who knows how it all works.

Signs it has outgrown the job

• Several people edit it at once, and changes occasionally vanish.
• There’s a file called something like “Bookings FINAL v3 (Dana’s copy)”.
• The same details get copied from the sheet into emails, calendars and invoices, by hand.
• One person knows how it really works, and everyone panics when they’re on holiday.
• Customers ask where things stand, and someone has to go and check the sheet.

If two or three of those sound familiar, the sheet isn’t the problem. It’s telling you where the work is.

What can go wrong

Mostly small things, often. A number typed as text. A row sorted without its neighbours. A formula overwritten with a value. And a few bigger ones: no record of who changed what, customer details shared more widely than anyone intended, and a business that depends on one file nobody wants to touch.

The upgrade isn’t always custom software

There’s a sensible ladder here, and most businesses only need the first rung or two.

1. Put a form in front of the sheet. New information arrives through a form with the right fields and choices, so bad data never gets in.
2. Add guardrails. Dropdowns, validation and protected columns stop the most common mistakes.
3. Let a small tool do the copying. When a new row appears, send the confirmation, create the calendar event or update the invoice automatically.
4. Move to a real system. When many people and processes depend on the data, it deserves a proper database with permissions, history and a screen designed for the job. That’s where custom software earns its place.

Start with one real job

Follow a single job through the sheet, from the first call to the final invoice. Where does someone check, copy or correct the same information? That’s the useful place to start, and it’s usually smaller and cheaper to fix than people expect.

What I’d do first

1. Today: ask the one person who knows how the sheet works to write down how. Half a page is plenty.
2. This week: put a form in front of it, and add dropdowns to the columns people get wrong.
3. This month: follow one real job from first call to invoice, and circle every place someone copies by hand.

It’s exactly the kind of work we like. See how we approach systems and automation, or try the repair company example on our homepage, where one job scattered across five tools becomes a single shared record.