Design and development kept together, so the site you approve is the site you get. Below is what I take on, and what a project looks like from the first conversation to after launch.
Working out what each page has to say, in what order, and how someone moves through it. The part that decides whether a site feels obvious or feels like work.
The look of the thing, once the thinking is settled. Typography, colour, spacing, and the small decisions that make a page feel considered rather than assembled.
Turning the design into a real site. Hand-written front-end code, quick to load, and straightforward to update once it is yours.
When a site still works but no longer represents you. I keep what is earning its place, replace what is not, and bring the whole thing back up to standard.
A single page with one job — a launch, a campaign, a product you want to sell. Designed around the one action you want a visitor to take.
Sites drift if nobody watches them. I stay on for updates, small additions, and the occasional fix, so yours keeps working long after launch.
You will always know where the project is and what happens next. Most of the thinking happens early, which is what keeps the later stages calm.
We talk about who the site is for and what it has to do. No forms to fill in first — I would rather hear it in your own words.
Before anything is drawn, I map the pages and what each one says. Getting this right is most of the work; the design follows easily once it is settled.
I design the key screens properly and we refine them together until they feel right — while changes are still cheap.
The front end goes together by hand and gets tested on real devices, with a live link you can watch take shape.
We go live, I show you how to update it, and I stay reachable. A launch is a start, not a delivery.
The design files, the code, the domain, the hosting account. No part of your site is held somewhere you cannot reach.
We agree what the project includes before it starts. If something new comes up mid-way, we talk about it rather than letting it quietly appear on an invoice.
Every site is handed over with a walkthrough of how to change the things you will want to change. Coming back to me should be a choice, not a requirement.
I take on a small number of projects at a time so each one gets proper attention. If the timing does not line up, I will tell you straight away rather than keep you waiting.
That is normal, and it is a good reason to talk. Describe the problem and I will tell you what I think it actually calls for — even when the answer is less work than you expected.