Every business has one. The spreadsheet with the formulas nobody else is allowed to touch. The one that prices the quotes, or tracks the jobs, or works out the wages — and lives one accidental sort-by-column-B away from disaster. If it broke tomorrow, someone would lose a weekend rebuilding it from memory.
Here’s the reframe: that spreadsheet isn’t a mess. It’s a specification. Years of your actual pricing logic, your actual rules, your actual edge cases — written down in the only tool you had. Nobody could hand a developer a better brief if they tried.
The reason it never became real software is that it never made financial sense. Custom software meant a dev team, five figures, and months. So the workaround stayed — and quietly billed you in hours every single week. That math has changed, and this article is about what changed, with a real build as the walkthrough.
The dreaded-spreadsheet test
Not every spreadsheet should become software. Here’s the test we use — three questions:
- Does it have logic someone protects? Formulas that encode judgement — “add 15% if it’s a two-storey”, “these materials price differently past 40m²”. Protected logic means the spreadsheet is doing thinking, not just storage. Thinking is what software is for.
- Does it cost the same hours every week? A one-off spreadsheet is fine as a spreadsheet. One that eats every Sunday evening is a subscription you’re paying in life.
- Does money touch it? Quotes, payroll, margins, invoices. Spreadsheet errors here aren’t hypothetical — studies have put material error rates in the vast majority of real-world spreadsheets. One wrong cell reference in a quote template can underprice jobs for months before anyone notices.
Two or more yeses: you have a software brief wearing a spreadsheet costume.
A real build: plan in, quote out
Here’s one we built, end to end, for the trades — a quote generator. The before-state is universal: quoting from a floor plan took an evening. Measure off the plan, count the quantities, apply your rates, remember the exceptions, write it up so it looks professional. Three hours, on the couch, after a full day on the tools. And the quotes that never got done — because the evening ran out — were jobs that went to whoever did quote.
The tool collapses that into minutes:
Step 1 — the plan goes in. Upload the floor plan. The system reads it and measures the actual quantities — areas, lengths, counts — the same take-off work you’d do with a scale ruler, done in seconds and shown on screen so you can check and correct it. Nothing goes forward that you haven’t seen.
Step 2 — your pricing logic runs. This is the part that matters. Not generic industry rates — the tool encodes how this business prices: their material rates, their labour-hours model (how long each kind of work actually takes their crew), their margins, their “always add X for that scenario” rules. All of it extracted from — you guessed it — the spreadsheet and the owner’s head. The software prices the job the way the owner would on their best day, every time.
Step 3 — a draft quote comes out. Formatted, itemised, in the business’s own template and voice. The tradie reviews it, adjusts anything, sends it. The judgement stays human; the three hours of assembly don’t.
The evening of maths becomes minutes of review. The quotes that used to not-happen, happen. And the pricing logic — which used to live in one person’s head and one fragile spreadsheet — is now a durable asset of the business, versioned, backed up, and consistent no matter who runs it.
What changed in the math
Five years ago that build was a $30,000+ project with a specialist dev shop — a scoping phase, a build team, a project manager, months. For a small trades business the answer was obviously no.
AI-native development changed the equation the same way it changed how we build websites: one senior builder with AI tooling now does what took a team, in days instead of months. The expensive parts of software were never the ideas — they were the assembly, the boilerplate, the coordination. That’s the part that collapsed. What’s left, and what you’re actually paying for, is the judgement: understanding your business, extracting the real rules (including the ones you don’t know you apply), and shipping something your least-technical staff member will actually use.
Small tools start small — priced like a fix, not a transformation. And the brief-writing is our job, not yours: “quoting takes me three hours every Sunday” is a complete, professional-grade brief. So is “only Sharon understands the wages spreadsheet and Sharon is going on leave.”
Find yours
Ask your team one question this week: “which spreadsheet would hurt most if it vanished?” The answer — and the nervous laugh that comes with it — is your software brief. Then ask what those weekly hours are worth over a year, and compare that to what a small tool costs once. That’s the whole business case, and you can run it on the back of the envelope the spreadsheet should have been.
Got one? Describe the job you dread — that’s the brief. We’ll come back with what the fix looks like and a fixed quote.