How Long Does It Take to Build a Website?

The honest answer is two to six weeks of work spread across four to twelve weeks of calendar, and the gap between those two numbers is almost entirely you.

That sounds like blame-shifting. It is not — it is the most useful thing anybody can tell you before you start, because it is the only part of the timeline you control completely.

Where the Time Actually Goes

Week 1 — Discovery and Structure

What the site has to achieve, who it is for, what currently gets in the way. Then the sitemap and a page-by-page content plan. This week feels like nothing is happening and it is the week that determines whether the rest goes smoothly.

Skipping it does not save a week. It moves the same decisions to week four, where they cost more because things have been built on top of them.

Week 2 — Design

Real pages in a browser, reviewed on a phone, rather than a static picture of a page. Expect one round of substantive feedback and one round of refinement. Two rounds is normal; five means the brief was wrong, which is worth diagnosing rather than iterating through.

Weeks 3–4 — Build

Templates, content loaded, forms wired up, tested across browsers and screen readers. Mostly invisible to you, which is why weekly progress notes matter more here than anywhere else.

Week 5 — Testing and Launch

Cross-browser and mobile testing, performance, accessibility, redirect mapping, analytics verification, a final review. Then launch, deliberately boring.

After — 30 Days of Settling

Small fixes, questions, the things nobody notices until real people use it. Any serious quote includes a support window; ours is 30 days as standard on every build.

Content Is the Delay

The pattern is remarkably consistent. Design finishes on schedule, the build is ready for content, and everything stops for three weeks because nobody has written the About page.

It stalls for understandable reasons — it is genuinely hard, it is nobody's actual job, and it always loses to work that is billable today. But the arithmetic is brutal: a two-week build waiting six weeks for copy is an eight-week project, and the invoice usually reflects the calendar rather than the effort.

Three ways out, in order of preference:

1. Write it before the project starts. Rough is fine. A document per page with the real facts beats polished copy that arrives in November.
2. Pay someone to write it. Usually the best value line in the whole budget, and it removes the bottleneck entirely.
3. Launch with what you have and improve it live. A working site with adequate copy earns more than a perfect one that does not exist.

The Other Delays

• Photographs. The same problem as content. Book the photographer in week one, not week five.
• Access. Nobody can find the domain login. This takes days to resolve and is entirely predictable — check it before you start, not at launch.
• Approval by committee. Every additional approver adds days. One named decision-maker is worth more to the timeline than any amount of project management.
• Scope growing mid-build. A page added in week four is not one page of work; it may touch the navigation, the templates and the plan.
• Third parties. Payment gateway verification, booking systems, SSL on a stubborn host. Often out of everyone's hands and worth starting early.

How to Genuinely Go Faster

1. Have the content ready before week one. Halves most timelines.
2. Name one decision-maker and give them authority.
3. Gather access up front — domain, host, analytics, social.
4. Book photography early.
5. Give feedback in one batch rather than in fourteen messages across a week. Batched feedback is faster to act on and produces better results.
6. Reduce the scope, not the quality. Six pages done properly now and four more in month two beats ten pages in four months.

The intake form we use exists for exactly this reason — it front-loads the questions that otherwise get asked one at a time by email across two weeks. There is more on briefing well in how to write a request that comes back right.

When Somebody Promises a Week

It is possible, and it means a template with your logo and your text pasted in. That is a legitimate product and occasionally the right one — a business that needs something live before a trade show on Friday should buy it.

What it is not is a custom site built quickly. If the deadline is immovable and close, say so at the quoting stage; a good supplier will tell you honestly whether to buy the fast thing instead, which is on our when we are the wrong choice list for precisely this situation.

Common Questions

How Long Does It Take to Build a Small Business Website?

Two to three weeks for a five-page site and four to six for around twelve pages, measured in working time. The calendar is usually longer — four to twelve weeks — and the gap is almost entirely waiting on content, photographs, access and approvals from the client side.

What Causes Website Projects to Run Late?

Content, in roughly nine cases out of ten. Design finishes on schedule, the build is ready, and everything stops while somebody writes the About page. The other common causes are missing account access, approval by committee, and scope added mid-build.

How Can I Make My Website Project Go Faster?

Have the content written before week one — that alone halves most timelines. Then name a single decision-maker with authority, gather all account access up front, book photography early, and give feedback in one batch rather than across a week of messages.

Should I Write My Own Website Copy?

Only if you will actually do it promptly. Rough copy with the real facts, delivered before the project starts, beats polished copy that arrives six weeks late. If it is likely to stall, paying someone to write it is usually the best-value line in the whole budget.

Can a Website Be Built in a Week?

Yes, as a template with your logo and your text pasted in — which is a legitimate product and sometimes exactly right, such as needing something live before a trade show. It is not a custom site built quickly. If your deadline is immovable and close, say so while quoting.