Every job in your firm waits for you to read it. That is the real limit.

01You quietly became the operating system

It happened slowly. Early on you surveyed, priced, filed the grid application and rang the customer, because there was nobody else. The firm grew and the routing never left your head, because doing it beat writing it down. It is written nowhere. It lives in your attention.

Hiring another surveyor adds a salary, supervision, and 1 more person learning the unwritten rules you were the only keeper of. The bottleneck is not gone. It has a second head to depend on.

Write the routing down and a system can run it. Leave it in your head and only you ever will.

02For an installer, the service is the marketing

In an installation business the customer experience is the marketing. Not the website, not the van. The quote back the same day. The survey booked without 3 phone calls. The install that ran to the day you promised. The aftercare visit nobody had to chase. That is what gets you recommended.

A quote that took a week is a deposit a faster rival took. A finished install never invoiced is money you earned and left on the roof. When the operating system is 1 tired owner, the service frays where a homeowner notices.

So most installers run more ads into a firm whose delivery still runs through the owner. That makes slower quotes and stalled jobs, not profit. Fix capacity first, then win the work.

03The 9 steps, in 3 phases

Here is the whole map. Your firm already does all 9 of these jobs. The framework names them, then decides 1 at a time whether a person or a system does each.

4 of those happen before anybody builds anything. Skipping them is why most let us try some Ai projects quietly die.

04The 4 steps before you build anything

Step 1 is a leak audit. Put a number on the money already walking out. Not feelings, a count of losses. Enquiries gone cold because the quote took days, and whoever replies first takes the deposit. Jobs blocked for weeks by a late grid application. Finished installs never invoiced, always a bigger pile than the owner guesses.

Step 2 is to watch. Follow 1 live job from enquiry to handover and write down every decision. Not the manual version, the real one. You will find 100 unwritten rules living in your surveyor's head and the group chat. The roof you will not quote without a survey. The scaffold lead time you always add. The deposit that clears before you book.

Step 3 turns that into 1 written procedure, in the order it really happens. Dull, and it makes the rest possible, because an assistant can only work a procedure somebody wrote. Here the crown jewel gets written down. 3 checks decide whether a job goes live: the MCS certificate so the customer can claim what they are owed, the grid operator's approval so the connection is agreed, and the building control notification so the work is signed off as safe.

The gate is not advice. It is a wall.

Step 4 is 30 minutes that saves a year of arguments. Write today's numbers down and agree them. How long a quote takes. What share of jobs clear all 3 checks before the crew is booked. How much finished work sits unbilled. Memory rewrites history. The baseline is your receipt.

Skip these 4 and you buy the clever part first, and get a fast tool that does not know how your firm runs a job. More on that in most firms bought Ai and few changed how the work gets done.

05The 3 steps that build it

Step 5 is the place the owner looks. 1 screen with the whole firm in the order that costs money, instead of a job app, a spreadsheet, an inbox and the group chat. Build it on 1 spine, not 12 tools that do not talk, with the owner as the glue. I pay for plenty of tools, and none of them run a firm alone. I build this as an AiOS command center, so the next piece is nearly free.

In the middle is a job radar: every live install ranked by what blocks it or bills first. The job stuck on a missing certificate sits top in red, the one waiting on the grid operator in amber. Beside it the compliance gate in 3 separate states, because 1 tick hides the certificate that never came. Then the money on the floor: every install handed over and never invoiced. And the job pack wall, reading the storage you already have, no migration, so a certificate takes seconds. The owner sees it all, the crew only their own jobs.

Step 6 turns the procedure into the company brain. A document just sits there. As data, every rule and good answer is joined by meaning, so anybody asks in plain words and gets your answer with its source. Ask a general model twice and you get 2 answers that differ, and here a wrong answer means an unsafe job.

Step 7 is the part people picture when they hear Ai. An employee, not a chatbot. It wakes on a timer, reads the job board, files the work and flags what needs a person. A small crew of them, 1 job each, inside the Telegram bot the crew already has open. The first one owners fall for reads a photographed electricity bill, takes the yearly usage and drafts a system size, a price and a savings estimate. Beside it: a document controller filing certificates to the right job pack, a refusal fence that holds a job short of commissioning until all 3 checks read clear, an invoice filler, and a critic that grades the work first.

06The last 2 steps are the whole point

Step 8 hands it to the crew, and people stop drafting the work and start approving it. The system writes the quote, the update and the invoice, and a person says yes or sends it back. Same crew, far more jobs, and your qualified people keep the surveying, installing and sign off. What everyone feels first is the morning brief at 8: blocked installs and the check each waits on, handovers due with packs drafted, finished work waiting to be invoiced.

Removal is a frightening word, so say this out loud to your crew. It means removing the rekeying, the chasing and the frightened certificate hunts, nothing else. A crew that thinks it means them will quietly starve the system.

Step 9 is not training, it is removal. 1 test tells you if you got there: the owner takes a real week off and nothing leaks. Enquiries get a same day indicative quote. Jobs move through survey, grid application and install in order. No job goes live until its 3 checks pass, because the gate does not care who is watching. Finished work still gets invoiced.

Every Monday a proof report tells the owner, in the numbers agreed in step 4, what the system did. Bills turned into quotes in minutes instead of days. Zero jobs live before their checks cleared. Then the real question. What do you do with the attention you got back. The contracts with the real margin, the next crew, the next van.

The running cost is metered like a utility bill, not hidden in a flat fee. On a real firm's volume the Ai usage is a few pounds a day and the hosting a few tens a month, roughly £100 a month to run. Put that next to 2.5 hours a day lost to pricing by hand, chasing and rekeying, across 22 working days. That is 55 hours a month, and at even £50 an hour it is over £2,500 of attention.

07Questions, answered