How Long Does a Website Take to Build? Real Timelines, Phase by Phase

It's the second question in every first meeting, right after the price: "and when will it be ready?". The honest answer is slightly uncomfortable, because it doesn't depend only on whoever builds it. A six-page corporate site goes up in three or four weeks if the content is ready, and in four months if it isn't. That difference isn't set by the development team. It's set by you.

This article breaks down real timelines by site type, how much each phase actually weighs, what genuinely delays projects — it's almost never what people assume — and how to compress the calendar without sacrificing anything that matters.

The short answer, by site type

These ranges assume something that rarely holds true: that the content — copy, logo, photos, legal details — is available when the project starts. If it isn't, add two to six weeks to any row in the table.

If someone promises a complete corporate site in five days, it almost always means one of two things: it's a template with your logo on top, or you'll be the one pasting in the content by hand after delivery. Neither is necessarily bad — but it's worth knowing before you sign, not after.

Phase by phase: where the time goes

A well-run web project has five phases, and the proportions between them surprise nearly everyone. Design and development — the "visible" parts — rarely take more than half the calendar.

1. 01Discovery and structure (10–15%). Goals, audience, sitemap and which pages are actually needed. The cheapest phase to do well and the most expensive one to skip.
2. 02Content (20–35%). Copy, photos, video, legal details. The most underestimated phase and the one that most often halts the whole project.
3. 03Design (15–25%). Visual direction and layout of the key pages. Everything else derives from those.
4. 04Development (25–35%). Build, responsive behaviour, forms, integrations, performance and accessibility.
5. 05Testing and launch (10%). Review on real devices, fixes, domain, email, analytics and going live.

Look closely at phase 2. In most projects that slip, the team finished on schedule and then sat waiting for the client's content. If you don't want to lose a month, start writing before any design exists — how to write your website copy solves exactly that bottleneck.

What actually delays a project

After enough projects, the reasons for delay repeat with an almost boring consistency. Hardly any of them are technical.

• Content that never arrives. The number one cause by a wide margin. Copy that's been "nearly ready" for six weeks.
• Approvals spread across too many people. When four people have to weigh in on the same colour, every round costs days.
• Scope changes halfway through. "While we're at it, can we add a shop?" isn't a tweak. It's another project.
• Logins nobody can find. The domain was registered by a cousin in 2016 with an email address that no longer exists. This surfaces in launch week.
• An unscheduled photo shoot. Original photography needs a date, a location and sometimes a permit. Nobody plans it at the start.
• Long silences. Two weeks with no answer to a blocking question delays the project by two weeks, not two days.

A realistic six-week calendar

This is what a well-organised six-page corporate site looks like. Use it as a mental template for judging any proposal that reaches you.

Notice the right-hand column: the client appears in all six weeks. A project where you disappear after the kick-off and reappear at the end to give an opinion is a project that will take twice as long and please you half as much.

How to speed things up without breaking anything

• Name one person who decides. They can consult anyone they like, but the final word is one voice. This alone cuts weeks.
• Hand over the content before you see the design. Designing on real text is faster and the result is better.
• Shrink the scope of version one. Launch with six solid pages and add the rest later; launching late costs more than launching short. Working out how many you really need is in how many pages a website needs.
• Batch your corrections. One ordered list beats fifteen scattered messages across ten days.
• Gather the logins in week one. Domain, hosting, social accounts, Google. Find them now, not in week six.
• Accept that version one isn't final. A website gets corrected after launch, with real usage data.

Red flags in a promised timeline

• There's no written schedule, just a "you'll have it in a month" over WhatsApp.
• The timeline doesn't depend on you delivering content. That means they plan to fill it with generic text.
• There's no testing phase on the calendar. It'll happen in production, with your customers as the test subjects.
• The price is suspiciously low for the promised timeline. Ranges and the assumptions behind them are in how much a professional website costs.
• No mention of training or handing over access. A "finished" project you don't hold the keys to isn't finished.

If you're comparing proposals, compare calendars as well as prices: the one that spells out phases, dependencies and your delivery dates is usually the one that has done this many times before. How to read those proposals is in how to choose a web design agency.