How long does it take to design and build a website?

Six weeks is the realistic answer for a custom marketing site. Two to three weeks if you're moving fast on a template. Eight to sixteen weeks once product design enters the picture.

Those are working numbers, not pitch numbers. Here's what happens inside them.

Week one goes to decisions, not pixels

Stakeholder conversations, a look at how comparable companies structure the same information, and agreement on the sitemap. No design happens. This feels like a wasted week to founders in a hurry, and it's the week that protects every week after it, because changing page structure once designs exist means redoing those designs.

Weeks two to four are design

The homepage comes first and takes the longest, because it establishes the typography, spacing, colour, and motion language that every other page inherits. Once it's approved, the remaining templates move quickly.

Budget for two rounds of feedback on that homepage. One is optimistic. Three usually means the direction was wrong and you're iterating toward something rather than refining it.

Weeks four to six are build and launch

Development, responsive work across breakpoints, CMS setup, motion, then QA. On Framer or Webflow this overlaps with design rather than following it, which is most of why those builds compress into six weeks instead of ten.

QA is the part people forget to schedule. Cross-browser checks, mobile behaviour, performance, redirects from the old URLs so you don't lose your search rankings on launch day. Two or three days, reliably.

The four things that actually blow up timelines

It's almost never the design work.

Copy isn't ready. The most common cause by a wide margin. Design can proceed on placeholder text. The build cannot finish without real words, so the project parks at ninety percent complete and stays there. Decide in week one who is writing it.

Feedback arrives slowly, or from too many people. A three-day turnaround per round across six rounds is nearly three weeks of calendar time with nobody working. Worse is feedback from five stakeholders who disagree, because someone has to reconcile it before anything moves.

Scope creeps. One more page. One more integration. Each request is genuinely small. Collectively they're why six-week projects finish in ten. A studio worth hiring will tell you at the time that a request moves the date.

Assets arrive late. Logos, photography, brand files, CMS credentials, domain access. Trivial items that block real work for days.

How to actually go faster

Name one decision-maker with authority to approve. Not a committee, and not a committee wearing one person's name. Someone who collects internal opinions and delivers a single answer. This alone routinely saves two weeks.

Have copy ready, even rough copy written with final intent. It exposes layout problems while they're still cheap to fix.

Batch feedback into one consolidated round instead of six trickled messages. You get better decisions too, because you're judging the whole page rather than reacting to one detail at a time.

And if speed is genuinely the priority, choose the platform for it. The fastest builds happen where design and development live in the same environment and nothing has to be handed between them.

A few specifics

Can a site launch in a week? Yes, on a template, with copy in hand, one decision-maker, and a short page count. You give up originality and a system built to grow. For hitting a funding deadline, that trade often makes sense.

Shopify? Three to six weeks for a theme-based storefront with custom design on the templates that matter. Longer for large catalogues, complex variants, or a custom Hydrogen build.

Product or app design? Eight to sixteen weeks for a meaningful redesign, more for platforms serving several user types. Research, flows, edge cases, and states are where the extra time goes, and skipping them is how you end up redesigning again in a year.

And after launch? Expect a short window of fixes as real traffic hits. Beyond that, changes either get scoped as small projects or absorbed into a retainer.