I build custom AI systems that do it — drafting the replies, reading a week of feedback, deciding when the lights come on. Scoped from a couple of days watching how your work actually runs, then built at a fixed price by the person who’ll still be supporting it.
Days from first message to a signed-off build — spec, source, build, install.
Builds for one client so far, and counting. He never needed a second consultant.
Support calls on Leyton’s lighting and gate automations since they went in.
One person — spec, build and support, start to finish
Four kinds of work, one method behind all of them: a couple of days watching how it runs now, a written specification of what's worth building, then a fixed price.
Automate the work that happens after hours — drafting the replies, summarising a week of feedback, moving data between systems that don't talk to each other. Every version scored against fixed test cases, so a change that makes things worse gets caught before a customer sees it.
Assistants and decision systems built around your workflow rather than a generic chatbot bolted onto a website. They work in your business's own voice, to your rules, with the things they must never do written down and enforced outside the model.
Catch the revenue that leaks while everyone is busy: the unhappy customer who leaves without saying anything, the follow-up nobody sent, the weekly report nobody reads. The measurable end of this work.
Connect AI to the tools you already run on — Drive, Sheets, your inbox, your CRM, your till system — so it reads and writes where the work already lives instead of becoming one more place somebody has to check.
Your business doesn't move onto a new system. The AI reads and writes where the work already lives.
Five projects with the decisions written out — including the ones that went against what most builders would have sold.
Restaurant owners don’t answer their Google reviews — it’s forty minutes at eleven at night. This drafts the replies in each business’s own voice, and enforces variation outside the model so Google doesn’t strip them for repetition.
Scored 3.5 → 4.8 out of 5 against a fixed set of twenty-five reviews.
Read the buildAn active trader needed several charting and news windows up at once. The obvious buy is a high-end gaming machine, and it’s the wrong machine. Every decision came down to removing failure modes rather than chasing benchmarks.
Eleven days from first message to sign-off. He has kept hiring me since.
Read the buildThirty-odd lighting circuits behind a dead proprietary system, and nobody would take the repair on. I kept the wiring and replaced the brain, then gave the building something to think with.
Running unattended on open standards. No supplier can switch it off again.
Read the build
Someone taps a station on the counter. Happy customers go to Google; unhappy ones reach the owner privately while they’re still in the building. Platform, AI, hardware, payments and contracts all built by one person.
One owner ran two branches side by side: 3.1 → 4.2 stars, reviews up 106%.
Read the build
Packing delivery orders was slower than it needed to be because the label rolls tangled and fed badly. Nobody had raised it — that was just how the station worked.
Modelled, printed and in service that week. It cost about a fiver.
Read the buildNobody should buy a build from someone they've just met. So it starts with a couple of days watching how the work actually runs, and comes back as a written specification you keep either way.
Systems that do a piece of your unattended work without anyone watching them — drafting the replies, reading a week of customer feedback and boiling it down, deciding when the lights come on. Built around how your business actually runs, not a chatbot bolted onto your website.
It starts with a paid diagnostic: a couple of days watching how the work really runs, which comes back as a written specification you keep either way. If there’s something worth building, it’s a fixed price off that document with the exclusions written down, so the number can’t move once we start.
Usually within the week. The trading desk went from first message to signed-off build in eleven days, specification included — that’s closer to typical than exceptional.
No. Some of the work on this site is one automation, one integration, one piece of hardware. If the diagnostic finds a five-minute problem, I’ll tell you that instead of selling you a project.
I do. There is no team to hand you off to after the first conversation, and the person who scopes the build is the person who supports it afterwards. I’m one person, and pretending otherwise would catch up with both of us.
Tell me what's quietly not getting done. If there's nothing worth building, I'll say so.