Your business already
runs on software.
Nobody designed it.
A spreadsheet, a folder tree, a group chat and a document someone copied from the last one. Each was the right answer to a smaller business. Together they became the system, and nobody chose it.
(CUSTOM SYSTEMS — LONDON & KENT)The stack you didn't choose.
(01 — TAP A TILE)One job, all the way down.
(02 — WHERE IT FALLS OUT)The enquiry
Comes in by phone, so it exists as a name on the back of an envelope until someone types it somewhere. Some never get typed.
The quote
Built by opening the last one and editing it. It goes out correct. Whether it was ever chased depends on whether anyone remembered.
The job number
Assigned from memory, or by looking at what the last folder was called. Two people doing that on the same afternoon is how you end up with two of the same number.
The work
Progress is real and completely invisible. Anyone who wants to know where it has got to has to interrupt the person doing it.
The invoice
Save-As from the previous job, because that is the only copy with the right letterhead on it. A copy starts life as a complete, valid, wrong document, and every edit subtracts from it. Miss one field and it goes out carrying the last customer's number.
Afterwards
The job is finished, so it stops being anybody's job. Nobody asks for the review, and nobody rings them a year later.
Not one of those is carelessness. Every one is a system doing exactly what it was built to do.
It fits because it was measured.
Every vendor's list of features is endless, and the length of the list has never been the point. The point is whether the thing on your screen uses your words, for your stages, in your order. Pick a trade and watch the same system change shape.
Same system underneath. The stages, the reference format, the words on the cards and the thing it nags you about are all yours, because they were taken from how you already work rather than picked off a menu.
Two of them, running.
(04 — BUILT AND IN USE)A practice running everything out of one spreadsheet
Jobs, fees and planning dates lived across a tracker, a folder tree and a set of Word templates. We read all three rather than replacing them with our own idea of an architecture practice — and found the schema was already written, in the folder names.
- Every job on one board, in the practice's own stage names
- Quotes, invoices and receipts generated with the right number from the right counter
- Planning clocks that count themselves down instead of being remembered
A contractor whose progress lived in a group chat
Work happens on sites with no signal, gets photographed on a phone, and has to be signed off by someone who is not there. Everything before this was a chat thread nobody could total up at the end of a week.
- Capture that works with no signal and syncs when the van gets back
- Supervisor sign-off attached to the plot rather than to a message
- One view across every site, without ringing round for it
(BOTH REAL, BOTH ANONYMOUS FOR NOW — NAMES GO UP WHEN THEY SAY SO, NOT BEFORE.)
What I still won't build.
(05 — HOVER OR TAP A LINE)What a custom dashboard actually is
A custom dashboard is not a reporting screen. It is the place the work happens — where a job is created, moved along, chased, documented and closed. The reporting falls out of it for free, because a system everybody actually uses is the only one whose numbers mean anything. That distinction matters more than any feature list. Plenty of small businesses have been sold a beautiful summary screen sitting on top of data that is still being maintained by hand somewhere else.
Most businesses we meet across London and Kent already have a system. It is simply made of parts that were never meant to be one: a spreadsheet doing the job of a database, a folder tree doing the job of a filing system, a group chat doing the job of an audit trail, and one long-serving person doing the job of the documentation. It works. It also quietly sets a ceiling on how big the business can get, because every one of those parts scales by asking more of the same person.
Off-the-shelf software is built for the average of ten thousand businesses
This is the honest reason so much bought software goes unused. A product sold to ten thousand firms has to describe all of them, so it ships with the union of everyone's requirements and the vocabulary of none of them. You end up with a stage called Opportunity when your team has always called it a quote, mandatory fields nobody fills in, and three modules you pay for and never open. Adoption fails, people drift back to the spreadsheet, and the business now runs two systems instead of one.
Fitting the software to the business rather than the business to the software is not a luxury. It is the difference between a tool people use and a subscription people resent.
The schema is already there — it is in your folder names
A business with no database still has a data model. It is written in the folder names, the tab names in the tracker, and the way people abbreviate things in the group chat. When a job folder is called something like 26-112 — Rear extension — DA1, that is a record with four fields in it: year, sequence, work type and area. Nobody designed it and everybody obeys it, which is the strongest possible evidence that those are the fields that matter.
So the first job is not building. It is reading — the tracker, the folders, the last twenty documents that went out — and writing down the system that is already being followed. Most of the design work for a custom system was usually done years ago, for free, by the people doing the work. It has simply never been written down anywhere a computer could act on it.
What we build
One place where every job lives, in your stage names and your order. Documents generated rather than copied, so a quote or an invoice cannot inherit the last one's numbers. Dates that count themselves down instead of relying on somebody remembering. A record of what happened that survives the person who was there. And nothing else — because every screen that exists has to be maintained, and a screen nobody opens is a liability rather than a feature.
It runs in a browser, on a laptop, a phone in a van or a tablet on a site. Where the work happens somewhere with no signal, it captures offline and syncs when there is a connection again — because a system that only works in the office is a system that gets filled in from memory on Friday afternoon.
Owning it instead of renting it
The usual model for business software is a monthly fee per person, forever, that grows as you hire. It buys convenience, and it also means that after five years you have paid continuously for something you own no part of — and that your own records sit on somebody else's server, subject to their export button.
What we build is yours: the code, the data, and the documentation to hand to anyone else. It works out cheaper over the life of the thing than renting the equivalent, though that is genuinely not the main argument. The main argument is that it fits, and that nobody can change the terms on you later. It is the same idea as an enquiry pipeline you own outright, applied to the inside of the business rather than the front of it.
Where to start
The same place everything else here starts: with an audit rather than a proposal. A week spent looking at how work actually moves through your business, and an honest answer at the end of it — including "your admin is fine, the problem is your follow-up", if that is what it turns out to be. It is a slower way to sell something and a much better way to build the right thing.
If the leak you recognise is on the front of the business rather than the inside of it, start with what a website actually fixes or the four usual suspects instead. If it is the six hours a week that disappear into admin, this is the page for it.
Reasonable questions.
(06 — FAQ)Isn't this just a spreadsheet with extra steps?
A spreadsheet stores what you type. A system knows what the rows mean, so it can act on them — move a job to the next stage, notice one that has gone quiet, produce the document that stage needs with the right number on it. The difference isn't the storage. It's that the rules stop living in someone's head.
What happens to the spreadsheet we already use?
We read it first. It's the most accurate description of how your business works that exists anywhere, because it was written by the people doing the work rather than by a software company. The column headings usually become the fields, and the tabs usually become the stages.
How long does it take to build?
Weeks rather than months for a first working version that holds real jobs. We'd rather put something narrow in front of you early and widen it than disappear for a quarter and come back with the wrong thing.
What if we need it to do something else in six months?
That's the normal case, not the exception. It's built to be changed, and because it's yours there's nobody to ask for permission and no feature request to file behind ten thousand other businesses.
Do we own it?
Yes. The code and the data are yours outright. No per-seat licence that grows as you hire, and nothing that holds your own records hostage if you stop paying someone.
What if you disappear?
You keep the code, the data and the documentation, and any competent developer can pick it up. Building something only its author can maintain would be the same trap in a new coat.