01 — Rate cardFixed prices, published
No hourly billing and no discovery call required to get a number. Quote your client from these figures directly.
| Build | Price | Turnaround |
|---|---|---|
| Landing pageSingle page, conversion-focused, one signature interaction | $1,200 | 4 business days |
| Marketing site — up to 5 pagesThe standard engagement. Home, about, services, case study, contact | $1,800 | 8 business days |
| Marketing site — up to 10 pagesAdds blog index, team, multi-service templates | $2,900 | 14 business days |
| Ecommerce or custom integrationScoped and quoted in writing before start | from $3,400 | quoted |
| Additional pageWithin an existing engagement | $220 | +1 day |
| RushTimeline compressed by up to half, subject to availability | +40% | — |
| Care planOptional, after a delivered build. Uptime monitoring, backups, one hour of content or design edits each month, same 1-business-day response. Cancel any month | $200/mo | ongoing |
What I don't do: the $500 AI-generated five-pager. That tier is commoditised and I would lose to a builder tool on price. These rates are for builds where accessibility, performance and cross-browser QA actually matter to the end client.
02 — ScopeWhat is and isn't included
Scope is locked in writing before work starts. Anything outside it is quoted separately rather than absorbed silently and rushed.
Included in every build
- Responsive implementation, 320px to 2560px
- Accessibility pass — keyboard navigation, focus states, contrast, skip links
- Cross-browser QA: Chrome, Safari, Firefox, Edge, iOS Safari, Android Chrome
- Reduced-motion support; site complete with animation disabled
- Graceful no-JavaScript fallback — no blank states
- Contact form wired to a live endpoint and test-sent
- Basic on-page SEO: titles, meta, headings, Open Graph, sitemap
- Deploy to your host or mine, credentials issued in your name
- Handoff pack: source, deploy steps, editing notes
- Two revision rounds, plus a 14-day defect window
Not included — quoted separately
- Copywriting and content strategy
- Photography, video, custom illustration
- Logo or brand identity design
- Hosting itself, and any third-party plan it runs on
- Maintenance beyond the optional care plan in section 01
- Third-party licences, fonts, stock or plugin fees
- CMS training sessions for the end client
- Migration of existing content at volume
- Paid ads, analytics strategy, or SEO campaigns
Revisions
- Two rounds included, requested within 10 business days of delivery
- Consolidated feedback per round, not drip-fed
- Further rounds $180 each, agreed before starting
03 — ProcessHow a build actually runs
- Scope lock (day 0)You send the brief and any designs. I return a fixed price, a fixed delivery date, and a written scope. Nothing starts until you approve it.
- Staging link (day 1)A live staging URL goes up on the first working day and updates continuously. You can see progress at any time without asking — no black box, no silence.
- Mid-build check (halfway)A short written update at the midpoint against the agreed date. If anything threatens the deadline you hear it then, not on delivery day.
- QA pass before handoffThe checklist in section 04 is run in full and the results sent with the build.
- HandoffSource, deploy instructions and credentials in your name. Two revision rounds follow, then a 14-day window where defects are fixed free.
04 — QAThe checklist run before every handoff
Results are sent with the build, not claimed in a sentence.
- No horizontal overflow at 320, 375, 768, 1280, 1920px
- Zero console errors or failed network requests
- Full keyboard traversal; visible focus on every control
- Renders complete with JavaScript disabled
- Renders complete with reduced-motion enabled
- All scroll and reveal states fire on jump-scroll and refresh
- Tap targets 44px minimum
- Body text contrast 4.5:1 or better
- Every internal link and anchor resolves
- Form submits and arrives at a real inbox
- Images sized, compressed and lazy-loaded below the fold
- Lighthouse performance and accessibility reported, not hidden
A worked example. In my own demo builds, scroll reveals were implemented with IntersectionObserver — the standard approach. QA caught that on a jump-scroll (an anchor link, or refreshing partway down) twelve of fourteen content blocks stayed permanently invisible, because IntersectionObserver only reports elements whose state changes. It was replaced with a direct scroll check and re-verified. That class of bug ships constantly and is invisible in a casual click-through. It is the reason the checklist exists.
05 — Working termsCommunication and white-label
White-label terms
- Delivery is unbranded; no credit, badge or backlink
- No contact with your client unless you request it
- Happy to appear as your team member on calls if useful
- NDA signed on request, before scoping
- You own the work outright on final payment
Payment
- 50% to start, 50% on handoff
- Under $1,000: single payment on handoff
- Bank transfer via Wise, in USD, GBP, AUD or EUR
- Net 14 for partners after the first completed build