When a spreadsheet stops being enough

Spreadsheets run more small businesses than any software vendor would like to admit, and for good reason. The question is not whether to leave them but when, and the answer is usually "later than you fear and sooner than you would like".

The five signs

1. Two people need it at once and someone keeps overwriting the other. Shared documents help; they do not solve concurrent editing of the same row.
2. You have a copy called final_v3_USE THIS. Version confusion means the data is no longer trustworthy, which means decisions are no longer trustworthy.
3. The same data lives in three places. Customer in the sheet, in the invoicing tool, in the inbox. They disagree, and reconciling them is now a weekly job.
4. Someone spends hours retyping. Copying order details into an invoice, into a delivery note, into the accounts. That is the clearest possible signal.
5. It holds personal data and lives on somebody's laptop. Under the GDPR that is a real exposure, not a theoretical one.

What to build — and what not to

The instinct is a full system. Usually the right answer is one small tool that removes one specific pain. A form that writes to a database instead of an email. A page that generates the invoice from the order. A shared list with a proper status field and an audit trail.

Automating the wrong thing is expensive; automating the retyping is almost always right.

Buy before you build

If a €30-a-month tool does 80% of it, use the tool. Build only where your process is genuinely unusual, or where the tools force a workflow that costs you more than the licence saves. Most businesses build too early and then maintain something they did not need.

A realistic first step

Write down the process exactly as it happens today, including the annoying parts. Nine times out of ten the bottleneck is one step, and that one step can be replaced in a week for a few thousand euros — far short of the system that was imagined at the start.