By Mehdi HassanHow long does it take to build a website?
It takes as long as the slowest dependency in the project, and on most website projects that dependency is not the agency. A clear brief, final copy, one decision-maker and fast feedback make a website quick. Missing content, shifting scope and a committee of reviewers make the same website slow, even with the same team building it.
That's why honest agencies give a timeline as a set of phases with conditions, not a single number. We scope delivery on the intro call for exactly this reason: a six-page site with copy ready and one approver is a different project from a six-page site with no copy and four approvers, even though the price may be the same.
This guide is the hub for our series on website timelines and process. It covers the phases of a build, how a week-by-week plan for a six-page site is sequenced, the client-side delays that usually add weeks, and how migrations, rush projects and pricing models change the schedule. Each section links to a deeper article when you need more detail.
One rule runs through all of it. A timeline is only real when it names who owns each step. If an agency gives you a launch date without telling you when it needs your copy, your feedback and your domain access, the date is a hope, not a plan.
What are the phases of a website development timeline?
A website development timeline has six phases: discovery, copy, design, build, QA and launch. Each one has a different main driver of length, and knowing which driver applies helps you predict where your own project will slow down.
Phase | What happens | What decides how long it takes |
|---|---|---|
Discovery | Goals, audience, sitemap, competitors, technical needs | How quickly the right people can meet and agree |
Copy | Messaging, page structure, final text | Whether you have positioning and customer insight already |
Design | Visual direction, page designs, responsive states | Number of unique page templates and review rounds |
Build | Components, CMS, integrations, animation | Platform, integrations and how much is custom |
QA | Devices, browsers, forms, tracking, accessibility, speed | Number of pages, forms and third-party tools |
Launch | Domain, redirects, analytics, search setup | Access to DNS and accounts, and migration scope |
Phases overlap on a well-run project. The build can start on approved templates while the last pages are still in design, and QA can run page by page. What can't overlap is copy and design: a page laid out around placeholder text gets redesigned when the real words arrive. For a fuller walkthrough of each phase, read what happens in a web design project.
What does a week-by-week timeline for a 6-page site look like?
A six-page site is sequenced so that every approval starts the next phase: discovery and sitemap first, then copy for the homepage, then the homepage design, then the remaining pages, then build and QA. The homepage usually takes the longest per page because it sets the visual system every other page reuses.
The order matters more than the number of weeks. Teams that approve the sitemap and homepage copy early tend to keep their date. Teams that reopen the homepage after inner pages are designed tend to lose it, because every inner page then needs to change as well.
Hypothetical example: how a 6-page site might be sequenced week by week
For example, suppose a seed-stage SaaS company commissions a six-page site: home, product, pricing, about, blog index and blog post template. This is an illustration of sequencing, not a quote and not a Designify delivery commitment. Real timelines are scoped on the intro call.
Week 1: kickoff, discovery questions, sitemap agreed, homepage messaging drafted.
Week 2: homepage copy approved, visual direction and homepage design shared for one consolidated round of feedback.
Week 3: homepage design approved, remaining page copy and designs produced, build of shared components starts.
Week 4: inner pages approved, build continues, CMS and blog templates set up, content entered.
Week 5: QA across devices and browsers, forms and tracking tested, final fixes.
Week 6: launch, domain and redirects, search console and analytics checks.
In this example, a one-week delay on homepage copy in week 2 doesn't cost one week. It costs at least one week on every phase after it, and often more if the team that was booked has to be rescheduled.
Use the example to read any agency's proposal. Look for where each approval sits, how many feedback rounds are planned for the homepage, and whether build starts before the last page is designed. If those points are missing, ask for them.
Which client-side delays add weeks to a web design project timeline?
The delays that add the most time come from the client side of the project, and almost all of them are avoidable with planning. They aren't a sign of a bad client. They happen because the website is one of many priorities for a founder or marketing lead.
- Copy that isn't ready. The most common and most expensive delay. Design can't finish without final words.
- Feedback that arrives late or in pieces. Three partial rounds from three people take longer than one consolidated round.
- New approvers late in the project. A co-founder or investor who sees the design for the first time in week four often reopens the homepage.
- Missing assets. Logos, product screenshots, customer logos you have permission to use, team photos.
- Account access. DNS, hosting, analytics, CRM and form tools. Waiting on access can hold up a finished site.
- Legal and compliance review. Regulated industries often need sign-off on claims and disclosures.
- Scope additions. A new page, a new integration or a second language added mid-project.
The last item, scope additions, deserves its own plan. Our guide to scope creep in web design explains how to handle new requests without losing the launch date.
How long does it take to design a website compared with building it?
Design and build take different amounts of time depending on how custom each one is. A site built on a templated design system can move quickly through design and spend more time on content. A site with custom illustrations, animation and unique page layouts spends longer in design, and that work then has to be built faithfully.
The platform affects build time too. No-code tools like Framer and Webflow let a designer build directly, which shortens the gap between approved design and working page. A coded stack like Next.js takes more build effort but gives more control over performance, components and CMS structure. Neither choice is faster in every case; it depends on what the site needs to do.
What shortens both phases is the same thing: starting with the words. When the copy is written first, the designer designs the real content, the developer builds the real components, and there's less rework. We work this way on every project, because in our experience rework usually traces back to copy that changed after design was approved.
If you're comparing a website with a full product build, the timelines work differently. Our guide to the MVP timeline covers product work, where design and engineering run in longer, overlapping cycles.
Can you build a website faster without cutting quality?
Yes, if you cut scope rather than steps. The fastest professional launches are single landing pages with copy direction ready and one person approving. Skipping QA or feedback rounds to save time usually costs more time after launch than it saved before it.
Launch one page first
Ship a strong landing page for your main audience. Add the rest of the site after launch.
Decide the message before kickoff
Bring positioning, customer quotes and a rough outline so copy can be finalized in days, not weeks.
Name one approver
Give one person the final say, and have others feed their comments to that person.
Book review slots in advance
Put review times in the calendar at kickoff so feedback never waits on availability.
Collect access and assets on day one
Domain, analytics, logos, screenshots and any legal copy, all before design starts.
For an honest look at what fits a very short window and what doesn't, read can you launch a website in two weeks.
How do migrations and redesigns change how long a website build takes?
Migrations and redesigns take longer than a fresh build of the same size because they add work that a new site doesn't need: content inventory, URL mapping, redirects and SEO checks before and after launch. That work protects the search traffic you already have, and skipping it is the main reason traffic drops after a redesign.
Agencies quote wide ranges for this work. The ranges we found in our research included 2 to 5 weeks for a Framer to Webflow move, 6 to 10 weeks to move off HubSpot, and 6 to 12 weeks for a WordPress to headless Next.js rebuild. Ranges vary a lot by site size and agency, so treat them as typical quotes rather than benchmarks.
Migration work is scoped on the intro call, and we include redirects and SEO checks in any migration we take on. For the details, see how long a website migration takes, the website migration plan template, and our breakdown of Framer to Next.js migration cost.
How does the pricing model affect a website build time?
The pricing model affects the timeline because it decides who absorbs the cost of delay and change. Under a fixed price with a fixed scope, the agency has a reason to plan tightly and the client has a reason to decide quickly. Under time and materials, change is easier, but there's less pressure on either side to stop changing.
Subscriptions add a third pattern. A design subscription works through one or two requests at a time, so a website build competes with every other request in the queue. That's fine for small updates and slow for a full site. Our guide to web design subscriptions explains how build work moves through a queue, and if you're comparing subscription providers, our ManyPixels alternatives roundup covers options that include development.
Our view, from running a fixed-price studio, is that a fixed scope with named owners protects your date better than any other model. We explain the trade-offs, including when hourly billing is the better choice, in fixed price vs time and materials.
What should you ask an agency about its website timeline?
Ask questions that expose the dependencies behind the date. A good agency answers each one specifically. A vague answer to any of them is a sign the launch date hasn't been planned.
- What do you need from us, and by when, for each phase?
- How many feedback rounds are planned for the homepage and for inner pages?
- Who writes the copy, and when is it due?
- What happens to the date if our feedback is late by a week?
- Does build start before every page is designed?
- Who handles domain, redirects, analytics and search setup at launch?
- What counts as a change in scope, and how is it priced?
The answers also tell you what working together will feel like. Our guide to working with a design agency sets out a week-to-week cadence, and our list of the best web design agencies for startups explains how we'd compare studios.
Where should you go next in this series?
Pick the next article based on the question you're trying to answer. Each one goes deeper on a single part of the timeline.
If you want to know | Read next |
|---|---|
What happens in each phase | |
Whether a very fast launch is realistic | |
What a normal week with a studio looks like | |
Which pricing model keeps your date safer | |
How to stop the project growing | |
How long moving platforms takes |
