Mar 12, 2026 · 5 min read · Process

Why most websites take six weeks (and mine don't).

Where the weeks actually go on a typical agency build, and the four decisions that compress the same project into seven days. It isn't working harder. It's saying no to the right meetings.

When I started taking on rebuilds, the first thing every client said was a version of the same sentence. "I went to an agency two years ago. They quoted six weeks. It took five months. The site they delivered was fine, but I didn't recognize half the decisions they made."

The six-week timeline is real. It's how agency builds genuinely take that long. But almost none of the time is the actual building. Here's where it goes.

Week 1 to 2: discovery phase.

This is the part nobody on the client side ever questions, because the agency has framed it as essential. You sit through a "stakeholder interview." You fill out a 12-page brand audit questionnaire. You attend a "moodboard workshop." Three people you've never met before review the moodboard and add notes.

None of this is fake work. It's also not necessary to ship a good website. The honest version is: a 30-minute call where I ask what your business actually does, who pays you, and what's currently broken. The rest is theatre.

Week 3 to 4: design in Figma.

The agency builds high-fidelity Figma mockups. You review them. You ask for changes. The designer makes the changes. The agency lead reviews the changes. You review again. Three weeks pass. You've approved beautiful pictures of a website that does not exist yet.

Here's the catch: when those Figma designs get handed to the development team in week 5, things change. Layouts that worked in static mockups break on real screens. Animations that looked simple in the comp turn out to be complex. The developer makes calls without checking back, because checking back would add another week, and you're already behind.

By launch, the site you have is meaningfully different from the Figma you approved. You either don't notice, or you do and the agency calls it "implementation reality."

Week 5 to 6: development.

This is the only week where actual code is being written. One developer. Five days of real work. The site ships in week 6 if there are no surprises, week 8 to 10 if there are (and there always are).

The total: roughly 6 weeks of calendar time for about 5 to 7 days of actual building work. The rest is process overhead that exists to justify the team size, not to make the website better.

Four decisions that compress this to seven days.

One. Replace the discovery phase with one 30-minute call. The information you need to make good design decisions for a small business is genuinely small. You can get there in half an hour with the right questions.

Two. Skip the Figma stage entirely. Review on a real, working site from day one. This sounds backwards but it's actually faster: you see the design in its actual medium, the developer doesn't have to translate twice, and feedback can go live the same day instead of going through a handoff cycle.

Three. One person makes all the decisions. The site has one designer-developer, and the client has one decision-maker. No committees, no "let me run this by the team," no async approval cycles that add a week each. Decisions happen in hours, not weeks.

Four. Cap scope before the first day. A website with 5 well-built pages is better than a website with 18 pages where three of them got built and the rest are stubs. Most small business sites need 5 pages. Start there. You can add more after launch when you actually know what visitors are looking for.

The thing that takes six weeks isn't the work. It's the meetings to coordinate the work.

What you lose with the fast version.

Honest answer: you lose the comfort of a thick process. You don't get to feel like you've done your due diligence by attending six discovery meetings. You don't get a 40-page brand strategy document to put on the shelf. You don't get the "we're building something special together" feeling that long projects produce.

What you get instead is a working site in a week and your time back. For most small businesses, that's the better trade. If you genuinely need a complex multi-stakeholder build with phased rollouts and translation workflows, a six-week timeline is correct and a one-week one is foolish. Hire an agency, that's exactly what they're good at.

If you're a service business with a website that's quietly costing you leads, you don't need six weeks. You need a working site, fast.


The four decisions above are how I ship in 5 to 7 days. If you've been delaying a rebuild because you can't carve out six weeks, email me: dylan@djdesigns.ca. We'll figure out if your project actually needs six weeks or just feels like it does.

← Back to all posts Start a project →