Approach
How a project runs
Six to ten weeks, four stages, and something you can look at every week.
The weeks below, as dates. Nothing is skipped for holidays, and a stage moves when a sign-off does.
Week 1–2
Strategy
One idea, a sitemap, and a written brief you sign off on.
You get
- The one idea, on one page
- Sitemap and content plan
- First draft of the key copy
The one ideaConcrete and Light
An architecture practice sells one thing, and it isn’t floor plans. It’s how a room feels at four in the afternoon.
Week 2: the one idea, on one page Week 3–5
Design
Real pages in the browser, not slides.
You get
- Type and color system
- Desktop and phone pages you can click
- Art direction for the images
Week 4: the week-one sketch under the page it became Week 6–8
Motion and build
Animation with a purpose. Performance budgets from day one.
You get
- Motion running on your own content
- A reduced-motion version of everything
- The production build, page by page
- Page ready on a phone
- 976msof 2.5 s
- Tap answered on a phone
- 88msof 200 ms
Week 7: the budget, measured on every build (this site’s own) Week 9–10
Launch and handoff
Deployed, documented, and yours. No lock-in.
You get
- Deployment and DNS
- Repository, documentation and a handoff call
- A QA report that says it passed
your-site/ README.md how to run it, on one page docs/decisions.md why each choice was made src/ the site, yours to change qa-reports/ every release gate and its numbers
Week 10: the repository, handed over
You talk to the people doing the work. There is no account manager.
Approach