- 01Day 01
Brief
Opening conversation, goals, prior failures, KPI.
- Briefing notes
- Success metric
- Risk register
- 02Day 02
Competitor audit
Audit of top five competitors: promises, metrics, blockers.
- Competitor matrix
- Positioning sketch
- 03Day 03
Wireframes
Layouts without color. Structure and hierarchy only.
- Low-fi wireframes
- Sitemap
- 04Day 04
Design system
Typography, color, spacing, motion tokens. No components yet.
- Token sheet
- Type spec
- 05Day 05
High-fi design
Homepage and one interior template type.
- Desktop key art
- Mobile key art
- 06Day 06
Copy & approval
Copy for every page. Sign-off before build.
- Copy doc
- Approvals
- 07Day 07
Build — frame
Next.js bootstrap, layouts, design tokens, fonts.
- Live preview deploy
- 08Day 08
Build — content
Content fill, MDX, schema, hreflang.
- Content complete
- 09Day 09
Build — integrations
Forms, CRM, email, analytics, schema validation.
- API endpoints
- Form QA
- 10Day 10
QA & polish
Lighthouse, accessibility, cross-browser, copy lint.
- QA report
- Polish list
- 11Day 11
Ship
DNS, GA4, Search Console, handover, docs.
- Production deploy
- Owner handbook
A short cycle isn’t about speed. It’s about memory.
The simplest question we get: why eleven days and not thirty, why not ninety?
Because memory. Thirty days is enough for the client to drift back to daily duties and lose the brief's context. Ninety days is enough for the team to lose it too. Eleven is the line beyond which everyone still remembers why we started.
- Decide. No “let’s revisit this next week”.
- Cut. Nice-to-have moves to the next cycle, if it is still relevant.
- Ship daily. The cycle has a visible trajectory.