v3_FINAL_really
You are not too small for software when the sheet is the brain — the when the spreadsheet becomes the business brain piece covers the signs. Growth does not wait for your tooling roadmap. It exposes load-bearing shortcuts until version chaos, hero dependency, and audit gaps become daily risk — and then something snaps, usually at the worst possible moment.
v3_FINAL_really starts as a joke. Multiple versions in circulation. Macros only one person understands. Board numbers rebuilt every Friday because nobody trusts a single export. Audit answers living in chat history. New hires learning "ask Sarah" instead of reading a system.
Warning signs before the snap
Customer or job references that exist only in a spreadsheet tab, not in finance. Permissions that mean everyone edits everything — or nobody can edit without Sarah. Integration attempts abandoned mid-build, leaving a manual export as permanent glue. Leadership asking for software while ops cannot spare a week to map the process — that gap predicts failure more reliably than anything else.
The snap is not always dramatic. Sometimes it is quiet margin erosion from errors nobody counts. Sometimes it is a compliance question you cannot answer cleanly. Sometimes Sarah gives notice.
Before the snap: one decision
Name the one fact you cannot get wrong this quarter — WIP, stock, AR, pipeline tied to cash. Decide whether to build, buy, or apply discipline, with honest maths behind the answer — the custom software worth it piece helps with that. Discipline means a named owner, a single version, and a fixed refresh time — sometimes that is enough to buy two quarters of time.
Do not copy enterprise RFP theatre while the sheet still runs the business. Map the process first, then think about phase one scope when you are ready to ship. The RFP without a real process piece explains why skipping the map is expensive.
After the snap: rescue without shame
If you are already in reconciliation hell or living through a failed go-live, rescue beats denial. Stabilise the truth for this week and design the next step for next quarter. The first 30 days habits apply to recovery just as much as to a fresh build.
Discipline buys time without denial
Not every snap needs a platform. Sometimes one version, a fixed refresh time, a named owner, and a rule against new tabs stabilise the spreadsheet for two quarters while you map properly. That is not romanticising Excel — it is honest phase one thinking applied to your current reality.
When you do buy or build, migrate with eyes open. The data migration checklist is honest about what "we will clean data at go-live" actually means. Growth waits for nobody, but your planning can still be blunt.
Board patience for map-before-buy is cheaper than board surprise when the sheet snaps mid-quarter. A systems review helps when leadership feels ready but ops is drowning.
Version control for spreadsheets is a discipline, not a joke: one live file, named owner, change log for structure edits. Until software ships, that discipline slows the snap.
Involve finance early when the sheet carries board numbers — they feel the snap first at month-end and will push for software or discipline. Align before the error becomes a crisis.
Book a review — Teesside and the North East. Audit when the map is missing, and care when the tool is live but the habit is rotting.