Weeks 1 to 2
Discover
Before anything is built, we run a structured workshop with your team to learn your customers, your goals, your competitors, and the constraints that aren't written down anywhere.
Process
How we work.
Five phases, published timing, no surprise invoices. Every artifact below is one we've handed to a real client.
- Weeks 3 to 4
Strategize
Discovery findings get translated into a concrete plan - what we'll build, what we'll measure, and in what order. No surprises after this phase.
- Weeks 5 to 7
Design
Mid-to-high fidelity Figma prototype. Two design directions explored in the first review round, then narrowed to one and refined across a second round.
- Weeks 8 to 12
Launch
Engineered in Next.js against measurable performance and accessibility budgets. Tested across devices, automated where it makes sense, reviewed by humans where automation doesn't catch nuance.
- Month 4+ (rolling)
Grow
Ongoing growth retainer beginning the month after launch. SEO, paid media, content, conversion tuning - choose the stack that fits your stage.
Artifacts
Everything we hand over.
The full table of artifacts produced at each phase. You own all of them, in editable source format.
| Phase | Artifact | Timing |
|---|---|---|
| 01Discover | Stakeholder interview notes | Weeks 1 to 2 |
| Audience definition + buyer-stage map | Weeks 1 to 2 | |
| Competitive + SERP audit | Weeks 1 to 2 | |
| Written strategy document | Weeks 1 to 2 | |
| Initial sitemap and content inventory | Weeks 1 to 2 | |
| 02Strategize | Refined sitemap and information architecture | Weeks 3 to 4 |
| Low-fidelity wireframes for every page | Weeks 3 to 4 | |
| Content outline and ownership matrix | Weeks 3 to 4 | |
| KPI dashboard plan + measurement spec | Weeks 3 to 4 | |
| 03Design | Figma prototype (you own the source) | Weeks 5 to 7 |
| Design system: type, color, components, motion | Weeks 5 to 7 | |
| Final content review with copy locked | Weeks 5 to 7 | |
| Pre-build accessibility and contrast audit | Weeks 5 to 7 | |
| 04Launch | Production site on Vercel with custom domain | Weeks 8 to 12 |
| Source repo in your GitHub org | Weeks 8 to 12 | |
| CMS training session (1 hour) + cheat sheet | Weeks 8 to 12 | |
| GA4 / Vercel Analytics dashboard with conversions | Weeks 8 to 12 | |
| 05Grow | Monthly written report + 30-minute call | Month 4+ (rolling) |
| Channel deliverables (articles, ads, posts, fixes) | Month 4+ (rolling) | |
| Quarterly strategy + competitive review | Month 4+ (rolling) | |
| Shared Slack channel for day-to-day requests | Month 4+ (rolling) |
FAQ
Process questions.
How long does a typical engagement take?
A full site build runs 8 to 14 weeks from Discover through Launch, scoped during week 1. Retainer engagements begin month 4 and run month to month with 30-day notice on either side.How much access to your team do I get?
One dedicated project lead plus specialist designers and marketers brought in by phase. We hold a weekly call during build, biweekly during growth, plus a shared Slack channel for everything else.How many design revisions are included?
Two full review rounds at the end of the Design phase, plus targeted iterations inside each round. The scope of revisions is agreed at kickoff so they don't drift into endless tweaks.What if scope changes mid-engagement?
Small changes get absorbed within the active phase at no extra cost. Substantial scope changes go through a simple written amendment with a transparent fee - never a surprise invoice.Do you work fixed-bid or hourly?
Builds are fixed-bid with milestone payments tied to phase completion. Retainers are flat monthly. We only quote hourly for narrow consulting engagements where the scope itself is the deliverable.
Ready to start phase 1?
Discover begins with a 60-minute workshop. We'll send a prep doc 48 hours before so the time is spent answering, not catching up.
Or skim a real engagement first - see case studies.