The three-week launch
April 10, 2026 · Kai Nakamura
Week one — kickoff
We map the goals, competitors, and the one thing that has to be true on launch day for you to call it a win. That single sentence — the "definition of done" — becomes the tiebreaker for every decision that follows.
By Friday you have a strategy document, a sitemap, and a mood direction. No design yet. Just the argument for what the site should do.
Week two — build
Design, copy, dev — all under one roof. You review one link, once a day. There is no ping-pong between an agency, a copywriter, and a developer, because they are the same team.
Two rounds of feedback are baked in. A third is available if the strategy shifts, but in practice it rarely does — the week-one work usually holds.
Week three — launch
Automations wired in, analytics live, training video recorded. You keep the keys. We spend the final two days on the parts most agencies skip:
- Redirects from the old URLs so you keep your search rankings
- Structured data so Google understands the new pages
- A written runbook so anyone on your team can update copy without calling us
Why three weeks, not three months
Long timelines are usually a scheduling problem, not a work problem. When one senior team owns the whole build, the calendar collapses. You get the same quality with a fraction of the meetings and none of the drift.
