The 3-Week Launch: How We Ship Websites Fast Without Cutting Corners

When we tell new clients that their site can be live in three weeks, the first reaction is usually scepticism. They've been through 12 week agency projects before. They've experienced the scope creep, the revision cycles that never seem to end, the waiting for feedback to come back from someone who's been in meetings all week.

We've been running three week launches since 2021. Not as a race, and not by skipping steps, but by designing a process that eliminates the phases where time actually disappears in most agency engagements.

Where time actually gets wasted

In a traditional agency project, the majority of elapsed time is spent waiting: waiting for internal review, waiting for client approval, waiting for assets, waiting for a developer to become available after the previous project finishes. The actual work of designing and building a marketing website for a small to medium business takes, at most, 80 to 100 hours of focused effort.

Twelve week timelines exist because of handoff friction, unclear ownership, and processes built around the agency's internal workflow rather than the client's outcome. We rebuilt our process around a single question: what does the client actually need at each stage, and what's the minimum overhead to deliver it?

Week one: discovery and design

Every project starts with a 90 minute discovery call where we capture everything we need to build the site: brand guidelines, target audience, key messages, competitor context, conversion goals, and any hard constraints. We do this live, in one session, rather than sending a questionnaire that comes back incomplete three days later.

By the end of week one, we've produced high fidelity Figma designs for all key pages. We don't do wireframes as a separate phase: they add a review cycle without adding value once you've had a proper discovery conversation. Clients review designs in a shared Figma file with a video walkthrough, and we consolidate all feedback into a single revision round.

Week two: build

Development starts on Monday of week two against approved designs. We build in Next.js with a headless CMS pre configured so clients can update content from day one. Because designs are finalised before we write a line of code, there are no mid build design pivots, the single most common cause of blown timelines.

• All pages built to pixel accurate spec against approved Figma
• CMS integrated and trained to match the content model
• SEO fundamentals implemented: structured data, sitemap, meta, Open Graph
• Performance optimization built in, not added as a post launch task
• Cross browser and mobile testing on real devices

Week three: review, QA, and launch

Week three is structured around a single client review session on Monday or Tuesday, a QA pass on Wednesday, and a launch window on Thursday or Friday. We handle DNS migration, redirect mapping from the old site, and a post launch monitoring period to catch anything unexpected.

The launch is never the end of the engagement. Most clients move onto a monthly maintenance retainer from week four onwards, where we continue improving the site based on real user data.

“We launched in 18 days. I kept waiting for something to go wrong. It didn't.”

What this requires from you

A three week launch is only possible with a responsive client. We need decision makers in the room (or on the call) during discovery, and we need feedback on designs within 24 hours of delivery. The process is fast because both sides move fast. If approvals take a week each time, the timeline extends proportionally. That's not a failure of process, it's just maths.