From Idea to Launch: Our 4-Week Website Sprint Process
Most website projects take three to six months and still miss the mark. We rebuilt our process from scratch. Here's how we deliver in four weeks without cutting corners.
Why most projects take three months
The honest answer: most agencies build the same website over six weeks of revisions that they could have built in two weeks of decisions. The bottleneck isn't talent. It's the structure of the engagement.
Our four weeks
Week 1 — Decisions. No design. No code. Just a single document by Friday: the audience, the offer, the three CTAs, the proof, and one of three "directional" wireframes signed off by the client.
Week 2 — Design. Full hi-fi for every page in the sitemap, including the empty states and the email confirmations. We share one Loom on Friday and ask for one round of consolidated feedback.
Week 3 — Build. Engineers build against the approved design. The client doesn't see anything mid-week. Friday they get a staging URL and ten days of context-free testing.
Week 4 — Polish + launch. We fix bugs, set up analytics and forms, brief the client team, and go live Friday at 9am.
What makes it work
Three things, none of them about speed:
- A signed scope before week 1. No starts without it.
- One client point-of-contact. No "the team will get back to you."
- Feedback in writing, on a deadline. Verbal feedback gets re-litigated. Written feedback ships.
The trade-off
We say no to projects that can't operate this way. The ones that can — about eight in ten — get a better website at half the price of a six-month engagement.