Spreadsheets are a fine prototype
Many good businesses start with a temporary sheet: a quote model, a live job list, a what we promised the customer grid. The problem is not the tool. It is when no one will say: this file is the system — the same load-bearing shortcut you see when the stack is heavier than the work and the official app is not where the room puts its trust on a Tuesday.
Signs the sheet is the real brain:
- The naming, macros, and logic sit in one person’s head. A week of leave is a recovery project, not a rest.
- You juggle v2, v2_FINAL, and reconciliation Friday to get the number the board asked for — two versions of the truth ran in parallel.
- You cannot show a defensible who changed what trail to a customer or a regulator, because the version the P&L relies on is a story in chat, not a record the next hire can run.
A spreadsheet is a fast prototype. A system has a source of truth, a next step a new person can follow, and ownership of the result — even when the UI is a tab. Map the process before the next software purchase if you want the next tool to stick.
Book a free systems review — we work in Teesside and the North East and remotely when the fit is right. What we offer is here: process audit, a build that does one job honestly, and system care in production. For the business case, we use the same ROI levers as elsewhere: time, rework, and speed to cash in bands you can defend, not a fantasy in the next workbook over.
What we look for in a systems review
We are not here to sneer at Excel. We are asking: if the person who truly runs the master is away, do margin and schedule still make sense without heroics?
- Source of truth or a named split: is there a master for a job or a line, or a written rule for which system wins in a dispute? The sheet cannot be the ledger in the room while another system is the ledger in procurement, unless everyone knows which counts.
- Parallel work without overwriting: can two roles update what they own in one place — or is it time for a proper hub, even a minimum viable CRM to start with?
- Handover: is there a one-pager a new person can run — tabs, import steps, and the one number the board trusts? If the whole picture lives in one person’s head, read handover when one person holds the truth before a bigger hire is the only plan.
The upgrade path, not a rip-and-replace
The next move is not always a bigger licence. Sometimes it is a smaller, honest build that does one job the sheet was pretending to be — after the process is written down and the room agrees what is true. Sometimes the right move is tighter discipline around the same file: a named owner, a single master location everyone uses, and a weekly habit so v3 stops multiplying in silence.
When the bet is build or buy, use the same hour in the room as bespoke vs off the shelf: twelve questions, and is custom software worth it? to keep the numbers honest.
We are not wedded to code; we are wedded to you being in control of what is true in the business. Book a systems review, read how we work, and see case studies for what good looks like when the noise goes down.