Skip to content

About

One person. Direct execution. No agency in the middle.

I build the systems clients hire me to build, from audit to scoping to code to handover. No account managers, no junior handoffs, no brief-to-delivery translation loss. The work goes from me to you.

Who I am

A software developer who happens to build AI implementations.

I'm a software developer based in the UK. Most of my career has been building web platforms, Astro, Next.js, Node.js, Postgres, Redis, the kind of work where you have to ship something that holds up under real load. I started doing AI implementation work in 2023 because the API surface got good enough to be the missing piece in a lot of the systems I was already building.

What that means for clients: when I say "I'll integrate this with your CRM and your accounting tool", I mean I'll integrate it. Not specify it for someone else. Not draw it on a slide. Build it, ship it, monitor it, fix it when it breaks.

Why one person

The one-person model is the feature, not the limitation.

Most "AI consultancies" run on the same shape: senior partner sells, project manager translates, junior delivers. By the time the work lands, three people have been between you and the person who actually built it. The deliverable suffers, the timeline stretches, the bill goes up.

When you hire me, the person scoping the work is the person doing the work. That has practical effects:

  • Faster decisions, if a build choice needs your input, I ask you directly. No "let me check with the team."

  • Direct access, you can WhatsApp me a question about something the system's doing and I'll answer it the same day, in technical detail if you want it.

  • Smaller surface area, fewer hands on the work means fewer places quality leaks. The system you get is opinionated and consistent because one person wrote it.

  • Lower cost, no agency overhead. The price you pay reflects the work, not the org chart.

What you don't get: a 24/7 support desk, multi-office presence, a "scale-up partner" with twelve specialisms. If you need those, you need an agency. For everything else, the one-person setup is faster and cleaner.

How I work

Four phases, no theatre.

  1. Audit, I look at what your team actually does day-to-day. Not a workshop, not a survey. Output: a written report of the workflows worth automating, ranked by ROI.

  2. Scope, we agree the single workflow to build first. I write the spec: success criteria, stack, timeline, fixed price. You sign or you don't.

  3. Build, direct work, 2–6 weeks depending on complexity. You can ask me anything technical any time. No status meetings for the sake of them.

  4. Measure, once it ships, we measure. Time saved, error rate, throughput. Short retrospective. Then we decide whether there's a phase two.

Pricing: engagements start at £500 for a focused bottleneck fix. Workflow automation builds with one or two integrations typically land between £2,000 and £8,000. Larger agent systems and ongoing retainers are quoted per project after scoping. Detail on pricing.

What I use

Stack, no black boxes, no proprietary lock-in.

01

AI / Language

Anthropic Claude (Sonnet for output, Haiku for orchestration). Structured outputs, prompt versioning, observability built in. UK/EU API regions where data residency matters.

02

Build

TypeScript, Node.js, Bun. Astro and Next.js on the frontend. Postgres and Redis where state matters. Playwright for the messy real-world automation work.

03

Integrations

Whatever your team already uses, Microsoft 365, Google Workspace, Notion, Airtable, Xero, QuickBooks, Clio, HubSpot, ClickUp, Linear. Direct API integrations, not no-code platforms.

Got a workflow in mind?

The fastest way to find out if I can help is a 30-minute scoping call. Bring the workflow, the volume, and the rough cost in hours. I'll tell you whether a build is the right answer. If it isn't, I'll say so.

Book a scoping call