Client story · Trade services · Gloucestershire
The office, not the engineers.
A diagnostic, 1 day onsite, and a director who now builds his own tools.
Mark, Director, blu-fish
1 day onsite. 11 weeks later he was building his own business tools, with no further paid help.
4 to 6 hours of office admin per large testing job, now targeted by a tablet platform he built himself.
A new quoting tool in about 30 hours of his own time: survey, price and send the quote before leaving the site.
His conclusion: the field team can grow without adding office staff.
Part 1: The question
The business ran mostly on manual systems: paper job tracking, invoices assembled by hand, a spreadsheet for gas safety renewals, and an office team absorbing the same details typed in at every stage of a job. Mark wanted to grow towards 20 staff and assumed what held him back was engineering capacity.
On the Diagnostic call I asked him one thing: if 200 new landlord properties arrived tomorrow, what breaks first? His answer was immediate. "Not the engineers. The admin."
The report named 5 processes worth changing, with invoicing and closing off jobs at the top. It also picked up that a member of his team had spent 18 months building an internal job management system, so the recommendations were written to work alongside it.
Part 2: The aim was capability, not a tool
Mark already knew the feeling:
"As a business owner, I have lots of ideas, but implementing them is often difficult."
So the install was built as a teaching day, not a software drop, with the goal of leaving him able to carry on alone. He wrote the business brief himself, about 1,100 words in his own voice, and Matthew Thistle structured it with the AIMED framework (Act, Instruction, Method, End-goal, Distil) so Claude would read it the way he meant it. His email, files and calendar were connected, under one rule: nothing reaches a customer unless he's read it first.
11 weeks later
"Absolutely, I've been, I feel like Claude's my third arm."
On his own, he filed an inbox 3,000 to 4,000 emails deep, then moved from chat to Claude Code, Anthropic's tool for building software, and built 2 working tools.
Quoting. For a new air conditioning line, he fed Claude a manufacturer's brochure page by page and turned it into a survey and pricing system: "I've probably spent 30 hours over a period of 10 days building a complete survey and pricing structure spreadsheet to enable me to walk around the property, survey it, and walk out in a position where I can press send to give the customer a quote."
Appliance testing. Large sites run to 1,500 to 1,800 items, recorded by hand. The sheets came back "as a scribbled mess on six, eight pieces of engineer paper that's been in the van with a coffee and a donut", and took 4 to 6 hours of office time to tidy. His tablet platform, he estimates, will "take away probably 80% of the onsite admin."
The line that answers the Diagnostic
"we could expand our field team by quite a few members without needing additional headcount in the office because we're just going to be able to create more capacity."
What hasn't landed yet
The email and calendar connections are barely used; he calls it "a habit thing". The largest opportunity from the Diagnostic, the gap between a finished job and an invoice going out, is next.
The takeaway
The first day's value wasn't the software. It was an owner putting his business into words and learning to direct the tool himself. Everything he built afterwards, he built alone. That's the difference between installing AI and seeding the capability to use it.
"Thanks for getting me started on the journey. I wouldn't be into it without you."