How it works

Six steps from your first message to a live site. You can see what’s happening at every one of them.

A conversation
30 to 45 minutes
A call or an email thread. I want to understand the business before the software, including whether software is the right answer at all. If I’m not the right fit, I’ll say so and suggest someone who is.
A written scope and a fixed price
Two to four days
I write down exactly what I’ll build, what’s not included, and what it costs. From here the price is fixed. If you want something extra later, I quote it separately and you decide.
Design
Three days to a week
You see the layout and look of the main pages before I write production code. Changing a design is cheap and changing a finished build isn’t, so this is the time to be picky.
The build
Most of the timeline
I build on a private link you can open whenever you like, so you watch it come together instead of waiting for a big reveal. You get a short written update every week.
Your review
Three to five days
You go through everything and send me what you’d like changed. That round of changes is included. The final payment is only due once you’re happy.
Launch and handover
A day or two
I put it live on accounts in your name, set up analytics and Google Search Console, and walk you through it. You get the code and notes on how it all fits together. Fourteen days of free fixes start from launch.

What slows projects down

In my experience it’s rarely the building. It’s usually one of these, and knowing about them early is usually enough to avoid them.

Text and images are the most common hold-up. If you don’t have them yet, tell me at the start and we’ll plan around it.

It helps a lot to have one person who makes the final call.

Your domain, email and any system I’m connecting to. Sorting access out at the start saves a week of waiting at the end.