Build · Scoped per engagement

Your next hire should be software.

/001

I build the websites, internal tools, automation and AI agents that do the work you'd otherwise hire for, up to a full CompanyOS. I write the code, not a brief for someone else who will.

Tell me what you want built

/002 The problem

Your team is doing by hand what software should have taken over last year

Think of the person you'd least like to lose for a fortnight. Now picture the fortnight.

  • The enquiries from the website sit until they're back.
  • The site itself doesn't change, because they're the one who knows how.
  • Quotes go out on last year's template.
  • Someone guesses at the brand voice, the terms, which price list is current.
  • The work still gets done. Slower, and a little different every time.

That's because the rules of your business live in people, and people go on holiday.

I build the software that holds those rules instead: the brand, the voice, the documents, the legal, the way a job moves from enquiry to invoice. Your website, your tools and your automations all connect to it and follow it.

The person comes back to a business that kept going without them.

/003 What I build

Four things, usually in this order

  1. 01

    Websites

    A website is the only employee who talks to every customer.

    Most of them were hired for their looks. I build the kind that answers the question someone arrived with, then asks for the enquiry.

  2. 02

    Internal tools

    The spreadsheet holding the business together, rebuilt as something a sort can't break.

    Quoting, intake, bookings, the dashboard you check before anything else.

  3. 03

    Automation

    The work between your systems.

    Details that move themselves, follow-ups that send themselves, a report that's there at 8am Monday without anyone building it.

  4. 04

    AI agents and CompanyOS

    A CompanyOS is a team of AI agents, each running one part of the business around the clock, built around how the company already works.

    A person signs off on anything that touches money or a client.

    It's the far end of Build, not the start. Most businesses need two of the three above first.

/004 How it works

A fixed quote before anything starts

  1. 01

    You tell me what you want built.

    The form asks. Rough is fine.

  2. 02

    I map it.

    Every job that repeats, who does it, how often and what it costs you.

  3. 03

    You get a fixed quote.

    What I'll build, what I'll leave alone and why, and one price.

  4. 04

    I build it.

    The person who scoped it is the person writing it. Nothing is passed to a junior or a contractor.

You know the price before you've paid for a thing.

/005 The work

Two builds. One needed agents. One needed a form.

01Professional services · 9 staffBuild

The business that lived in three people's heads

The founder was working 60-hour weeks. Three people spent most of theirs on intake, follow-ups, scheduling and reporting, and none of it was written down. When one of them took a fortnight off, their work waited for them to come back.

I sat with each of them and wrote down how they did it. Then I built a CompanyOS on top of those rules. Each agent runs one part of the business, with a person signing off on anything that touches money or a client.

2828 hours a week back to the team. New enquiries answered in under 10 minutes.

The agents aren't clever. The jobs were already defined, they just lived in three people's heads. Writing them down was most of the work.

Left alone The people. Nobody lost a job. The 28 hours went to the client work nobody had time for.
02Local service business · 16 staffBuild

They asked for agents. They needed a form.

They came wanting AI agents to handle new enquiries. Enquiries arrived five different ways, in five different shapes, and a quarter of them were never logged. Replies took two days.

I rebuilt the quote form so it does half the work, including the calculations the team used to do by hand. Then I pulled every channel into one system that sorts each enquiry, sends it to the right person and gives them the script and the next step for the follow-up.

1 hrResponse time from two days to one hour. Every enquiry logged, up from three in four.

An agent can't sort what it can't read. Once every enquiry arrived the same way, simple rules did most of what they'd wanted the agents for.

Left alone The agents. They weren't needed yet.

/006 After it's built

Most builds are designed so you can't leave. Mine are designed so you can.

The code lives in your accounts, not mine. The hosting is in your name. Every system comes with one plain-English page: what it does, what it touches and what to check when it breaks. It's written so the next developer doesn't have to be me.

If you want me to keep it running, I will. You shouldn't need to.

/007 Start

Before you hire for it, let me quote for it.

Three engagements a quarter. A paragraph is enough, and you'll get a fixed quote before anything starts.

Tell me what you want built