I build websites, custom software and AI systems — the automated kind that take a manual process and make it run without you. Fifteen years in, the work is still the same: understand the business, ship the smallest thing that solves it.
No agency layer, no handoffs. You talk to the person writing the code — from the first call to the deploy.
Business sites, landing pages and marketing sites that load fast, rank, and stay simple enough for you to update yourself. Handed over cleanly — never locked to a subscription.
Web apps and internal tools shaped around how your team already works — dashboards, portals, booking and billing flows, and integrations between systems that were never meant to talk.
Assistants and agents wired into real business data, so they answer, qualify, summarise and file — instead of just chatting. Built with guardrails, logging and a human fallback.
Four shapes most projects take. Yours will be one of them, or a mix of two.
Clear positioning, real photography, a quote form that reaches a human — fast on a phone on mobile data, not just on your laptop.
Turned into a proper system with roles, history and an audit trail.
Answers from your own documents, and hands the uncertain cases to a person.
CRM to invoicing, form to warehouse, chat to ticket queue. Small, well-monitored glue that deletes a daily copy-paste job.
Short, written, and without a discovery phase that bills three weeks of meetings.
What it must do, what it must not, and what it costs — in writing before any code.
Working screens early and often. Not a slide deck and a silence.
Code, accounts and docs go to you. Nothing held hostage on my server.
A bug after launch is my problem first. Fix it, then explain what happened.
I started building websites in 2010, back when a business site was still a novel thing to own. Since then the work has moved through every layer of it: static pages, then CMS builds, then custom applications — and now AI systems sitting on top of the same business logic.
I work alone and on purpose. The person who scopes your project is the person who builds it and the person who answers when something breaks. It also means I take a small number of projects at a time, so the one you get is the one I am actually thinking about.
Most of my clients are small businesses and founder-led teams who need something built properly once, rather than something cheap that has to be rebuilt in a year.
A sentence about the business and a sentence about the problem is enough. You get a straight answer on scope, cost, and whether I am the right person for it.