How a build runs
Every build follows the same four-phase rhythm. The discipline is what makes the four-week deadline reliable.
Week 1 — Discovery + brief
A 60-minute call to understand the business, the audience, and the success metric. By Friday you have a brief.json capturing every decision: brand colours, services offered, regulators that apply, lead-capture wiring, where forms should go.
This file drives the entire build. If you change your mind in week 3, you change the brief, the engine regenerates the affected pages, and we move on. No “code rewrite required.”
Week 2 — Generation + design concept
I scaffold the whole site from the brief in under an hour. By Wednesday there’s a working static site to review on a staging URL. By Friday a design concept lands — typography, palette, hero treatment, component personality. Approval here triggers the 50% deposit. If you don’t like the concept, the engagement ends and you owe nothing.
Week 3 — Content + imagery
I write the copy. You review and adjust. Imagery is hand-selected from your library or generated to match a locked camera/focal style guide so every shot looks like it came from the same shoot. Author bio + credentials baked in. By Friday all core pages are content-complete.
Week 4 — Deploy + handover
Cloudflare Pages production deploy on Monday. Custom domain wiring Tuesday. Lighthouse audit + fixes Wednesday. IndexNow submission to Google + Bing Thursday. Friday: handover walkthrough on Loom (30 minutes), GitHub repo handed to your account, optional Decap CMS overlay activated if requested.
Final 50% payment is due on Friday. From here onwards the site is yours; the optional Care Plan covers ongoing edits at £29/month if you want them.