Skip to content
Back to journal
Process

How we ship a SaaS site in six weeks

Six weeks from kickoff to live, with strategy, brand, and engineering. Not magic — just a clear process.

2025-04-127 min readProcess · Sprints · Delivery

The most common question we get is how we hit 6 weeks where other studios take 4 months. The short answer: discipline and a single team. The long answer is below.

Week 0 · kickoff

Before week 1 we run a short kickoff: a 90-minute working session with the client team, business metrics, a single product owner on the client side, and a frozen ICP. Without this, week 1 turns into an open-ended conversation about taste.

Weeks 1–2 · strategy and architecture

In parallel: market and ICP research, brand voice, information architecture. The designer starts on tokens and grid; the engineer sets up the repo and base CI. Demo every Friday.

Weeks 3–4 · design and content

Screens in Figma, validation against ICP scenarios, copy in pair with the client. We don't wait for everything to be 'approved' — pilot blocks ship to engineering immediately.

Weeks 5–6 · engineering and launch

Animations, forms, CMS, analytics. By week 5 the site is on staging; we run a beta with 20–30 ICP-matching people and gather feedback before public release.

What breaks the process

More than two points of accountability on the client side, demanding 'final sign-off before engineering starts', a scope change in week 5. Any of those, and the timeline slips.

Start a project

Start a project