Answer
How long does a website take to build?
A small brochure site takes two to four weeks. A twenty to sixty page business site takes eight to twelve weeks. A large platform of several hundred pages takes twelve weeks or more. Design and development are rarely the bottleneck — content is. Projects that run late almost always do so because nobody was clearly responsible for writing the words.
- Brochure, 1-5 pages
- 2-4 weeks
- Business site, 20-60 pages
- 8-12 weeks
- Large platform, 300+ pages
- 12+ weeks
- Most common cause of delay
- content not written
- Second most common
- slow approvals
- Fastest thing you can do
- assign one decision-maker
Where the time actually goes
People assume design and code dominate the schedule. On a content-heavy site they rarely account for even half of it.
The larger share is research and writing: working out what each page needs to say, gathering real information from the business, and producing text that is accurate enough to publish. On a forty-page site that is forty separate pieces of work, each requiring something only the client knows.
This is why quoted timelines vary so much for identical page counts. A studio that writes the content is quoting a different project from one that assumes you will supply it, even when the brief looks the same.
What causes delay, in order
Content that has not been written. By far the most common. The build reaches a point where it needs your service descriptions, prices, coverage areas and answers, and stops.
Approvals with no clear owner. When three people must agree and none of them owns the decision, each round takes a week rather than a day. Naming one decision-maker at the start is the single most effective thing a client can do.
Scope added mid-build. A calculator or an extra section added in week five is not just its own build time — it disturbs work already finished.
Third-party dependencies. Booking systems, payment providers, CRM connections and anything requiring another vendor's cooperation reliably take longer than expected.
How to make it faster without cutting quality
Assign one decision-maker with authority to approve. Gather your real information before the project starts — services, prices, coverage areas, certifications, the questions customers ask most. Book your approval time in advance rather than fitting it around other work.
And separate urgent from complete. If a fix matters now — a broken form, missing tracking, no booking — do that as a short focused piece of work while the larger build proceeds properly. Rushing a full site to hit a date usually produces something that has to be redone.
Related questions we get
Can a website be built in a week?
A small one from a template, yes. Anything requiring original content and structure cannot be, because the writing alone takes longer. Be wary of a fast quote for a large scope — it usually means the content burden is quietly landing on you.
Why did my last site take six months?
Almost certainly content and approvals rather than build time. Ask what the project was waiting on in each of those months; the answer is rarely development.
Should I launch in stages?
Often yes. Launching the core site and adding service or area pages over following months gets you live sooner and lets search engines see the site growing steadily, which is no bad thing.
Does a faster build mean lower quality?
Not if the speed comes from a better process rather than less work. Generating pages, structured data and internal links from one structured source rather than hand-building each page is genuinely faster and no less thorough. Speed that comes from skipping the content research is not.
More answers
Want this checked on your own site?
Send the URL. The audit is free, it takes us about twenty minutes, and it comes back in two working days.