How a project actually goes.
No mystery and no agency theatre. This is the whole thing, start to finish, including the parts most people don’t tell you about.
From the first call to handover, in five steps
- 01
We talk
Thirty minutes, free, no obligation. You tell me what you want and why. I ask a lot of questions. Often the useful outcome of this call is realising the thing you need is smaller than the thing you asked for.
You know what it would take before you commit to anything.
- 02
We agree what we’re making
I write down what you’re getting, what it costs and when, in plain language, on about one page. You agree to that. There’s no forty-page contract nobody reads.
One page you can read in one sitting, and a price that doesn’t move.
- 03
I build it, where you can see it
You get a link, and the thing behind it grows week by week. You don’t wait until the end to find out I misunderstood you; when something’s wrong, we fix it there and then.
No six-week silences.
- 04
It gets checked, every time
Every time I change something, automatic checks run over the whole thing to make sure I haven’t broken anything that already worked. It’s the boring habit that separates software that lasts from software that falls over after three months.
It works before you ever see it.
- 05
It goes live, and it’s yours
I handle hosting, the domain, the certificates and the search-engine side. Then I hand over the keys: the code, the accounts, all of it. I’m happy to keep looking after it, but you’re never stuck with me.
Yours to keep, or to hand to somebody else.
Yes, I use AI. Here’s exactly how.
You’ve probably seen websites that were churned out by a machine: generic, slightly wrong, clearly nobody cared. I understand the worry.
I use AI agents for the parts of the job that used to be slow and repetitive: writing routine code, checking my work, running the tests, publishing releases. They work inside rules I wrote for your project, and nothing reaches you until it’s passed my checks and I’ve read it.
The thinking, the design and the judgement are mine; the tedium is automated. That’s why a well-built thing now takes weeks instead of months, and why I can take on projects that would once have been too small to do well.
What I never leave to a machine.
Here’s where the line is:
- Deciding what to build, and what to leave out. Most of the value in a project is in the things you decide not to do.
- Anything touching money or personal information. I read every line of that myself, every time.
- Talking to you. You get me in the conversation, not a summary of me.
Still sounds like a fit?
Tell me what you’re trying to make. The first call is free.