Diaries open from 3 November — two project slots left for the first quarter.
Check your datesIndependent designer & front-end builder
I design and write the whole front end myself — no page builders, no bloated themes. You get a site you can edit, that loads quickly on a phone, and that reads clearly to someone deciding whether to get in touch.
What I do
Most practices need all four. If you already have part of it covered — a brand, a copywriter, a developer for the back end — we drop that lane and the estimate comes down.
01
Structure before surface: what each page is for, in what order, and what the visitor should do next.
Typically two to three weeks
02
Semantic HTML, hand-written CSS and a small amount of vanilla JavaScript. Nothing you need a licence to keep.
Typically two weeks
03
I don't write your copy from nothing, but I will shape what you have into something a reader can scan.
Runs alongside design
04
Checked as the build happens rather than bolted on at the end, where it rarely survives.
Final week, before handover
Selected work
Small sites with a job to do. Each note says what the problem was, what we decided, and what changed afterwards.
The old site needed a developer for every new project entry, so it stalled after four. I rebuilt the archive around a single repeatable template with three image slots and a short fact list, then wrote the editing guide as one page. The practice has added eleven projects since handover without calling me.
Six scattered pages of service descriptions became one page with a short form, written so a first-time client knows what happens after they press send. Built in a fortnight on their existing host.
Their site had grown eleven button styles. I documented four, rebuilt the CSS around tokens, and now handle a short list of changes each month so the pattern holds.
I keep a longer set of case notes — including the projects that went sideways and why — and I'm happy to walk through the one closest to your situation on our first call.
How a project runs
A fixed-scope site usually runs about six weeks from signed estimate to handover. The part most people underestimate is their own: gathering content takes longer than designing around it.
01
Week zero
A 30-minute call, an honest read on whether I'm the right fit, and a referral elsewhere if I'm not.
Your current site if there is one, a rough budget band, and the date you'd like to be live.
02
Week one
A written scope listing every page and lane of work, a fixed fee, a schedule, and what sits outside it.
One decision-maker named, and sign-off on the scope before design starts.
03
Weeks two to four
Wireframes, then two visual directions, then finished layouts — each with a review call and two revision rounds.
Consolidated feedback within three working days, and your text and images for the key pages.
04
Weeks five to six
The built site on a staging link, accessibility and performance checks, a walkthrough recording, and all source files.
Host and domain access, and a final read of the live pages before we switch over.
Ways to work
If you know what you need, take the fixed project. If you need to prove something quickly, take the sprint. If the site already works and just drifts, take the monthly slot.
Suits a full site, a relaunch, or a practice whose site no longer matches what it does.
One fixed fee, agreed in writing before any work begins
Suits one page that has to earn its keep — an enquiry page, a service page, a launch announcement.
Flat sprint fee, booked by the fortnight
Suits a site that already works but keeps accumulating small jobs nobody owns.
Monthly retainer, hours agreed up front
Questions
Yes, and it usually makes the project faster. Send me whatever exists — old pages, a brochure, a document of notes. I'll cut, reorder and line-edit it, then tell you plainly which pages need new writing. If a page needs more than editing, I'll say so rather than padding it out.
Most often a static build on your own hosting, or a lightweight CMS where you need to post regularly. I'll recommend the smallest thing that does the job, and I won't move you off a platform that's working just to suit my preferences. If your team already uses something, I'll build into it.
Then we use it. I'll ask for your logo files, typefaces and colour values, check the colours for contrast, and propose adjustments only where something fails legibility on screen. Brand design isn't part of my scope — if you need a full identity, I'll point you to someone who does that properly.
Two rounds at each design stage: wireframes, visual direction, and finished layouts. A round means one consolidated set of feedback from your side, not a trickle of separate messages. Changes that alter the agreed scope get quoted separately before I start them, never after.
Thirty days of fixes are included — anything broken or wrong against the agreed scope. After that you can book individual jobs as they come up, or move to a monthly slot. Either way you hold the source files and the hosting account, so you're never locked to me.
Often, yes. I'll spend an hour reading the code first and tell you honestly whether it's worth extending or whether you'd spend less rebuilding. Inherited sites with heavy page builders are the one case where I usually recommend starting again.
Fixed projects are staged: a deposit to hold the slot, a payment when design is signed off, and the balance at handover. Sprints are paid in full when the fortnight is booked. Monthly care is invoiced at the start of each month. Everything is agreed in the written scope first.
Start an enquiry
A few lines is enough to start. I read every enquiry myself and reply within two working days, including the ones I can't take on.