If you came here looking for the "3 — 6 days" claim that used to be on this site: it's gone. Below is the realistic version.
2 — 4 weeks for an SMB marketing site. 4 — 8 weeks for e-commerce. 6 — 12 weeks for a nonprofit with payments and events. The "3 — 6 days" claim on the previous site has been retired. That timeline was only ever plausible for a template-flip, and that is not what I do.
Page builders trade build time for ongoing tax — render-blocking JS, plugin churn, vendor lock-in. Custom blocks cost more on day 1 and less every day after. For B2B services that intend to be around in five years, custom wins on TCO. For a marketing site you plan to throw away in six months, a builder is fine.
Custom Gutenberg theme · ACF block library · WCAG 2.2 AA pass · sub-1s mobile LCP · Lighthouse perf 95+ · runbook PDF · 60-min admin training · 30 days post-launch bug fixes. Not included: copy, photography, branding, hosting fees, ongoing maintenance.
Yes. The whole point of the custom-blocks approach is that editorial parity is non-negotiable. Your marketing manager edits headlines, swaps images, adds case studies — without me. If they can't, the build failed.
30 days included on every build for bug fixes on what I shipped. After that, the Care Plan retainer is available at $400/mo. Or we close clean. Either way you keep everything.
Probably not. Start with the Audit Sprint (7 days, $1,500). The report will tell us whether you need a rescue (Performance / Accessibility) or a full rebuild. ~40% of audit clients act on the report alone.
I don't host. I recommend WP Engine for B2B, Kinsta for higher-tier, and Hostinger for nonprofits on tight budgets. No affiliate links. No referral kickbacks.
Fixed-price, milestone-based, 40 / 40 / 20. No hourly under any circumstance — hourly rewards slowness, and you should not be billed for my learning curve.
The SOW lists scope explicitly. Mid-project additions are quoted as a change order, signed before work begins. There are no surprise invoices.
You do. IP transfers on final payment. No "perpetual licence" clauses. You can fire me, fork the codebase, and hire anyone else to maintain it.
In the UK and EU, yes — the EAA took effect in 2025. In the US, ADA Title III routinely litigates inaccessible sites. Beyond compliance, ~15% of your potential audience can't use a site that fails WCAG. I treat WCAG 2.2 AA as the floor, not an upsell.
Yes. For scaffolding, refactoring, and code review. Every line of production code is read and signed off by me. Full policy and per-engagement disclosure on /ai-policy.
I'm UTC+1. Most of my clients are GMT to GMT-5. The Friday update + Slack + scheduled-call model works fluently across an 8-hour offset. Calls scheduled in your morning, my afternoon.
Book the 15-min intro call. If we're a fit and slots aren't open, you go on a dated waitlist. Slot openings are published on the homepage utility strip — that's the current state, in real time.