How Long Does It Take to Build a Website?

Most small business websites take four to eight weeks from the first conversation to going live. A single landing page can be done inside a fortnight. A site with an online shop is more likely to run eight to fourteen weeks. The part that surprises people is that the building is rarely what takes the time. The schedule is set by how quickly words, photographs and approvals come back.

I get asked this in almost every first call, usually straight after price. It deserves a better answer than "it depends", so here is how the stages actually break down, where the weeks genuinely go, and the handful of things that decide whether a project lands on time or drifts into next season.

Typical timelines by type of website

These are the ranges I work to. They assume you are dealing with one person or a small studio rather than a large agency with several layers of account management, and that you can reply within a couple of days.

Type of website	Realistic timeline	Who it suits
Single landing page	1 to 2 weeks	One service, one offer, or a campaign page
Small business site (5 to 8 pages)	4 to 6 weeks	Most trades, consultants and local services
Larger brochure site (10 to 20 pages)	6 to 10 weeks	Several services or locations to cover
Online shop	8 to 14 weeks	Anyone selling and shipping products
Booking or membership system	12 weeks and up	Sites where the functionality is the product

If someone quotes a timeline well under these without asking a single question about your content, treat it the way you would a builder who prices an extension from the pavement. It is a guess, and guesses tend to be revised upward later.

Where the weeks actually go

A website project is not one long task. It is six shorter ones, and only three of them are mine. This is the honest split for a typical five to eight page build.

Stage	Typical duration	Who holds the work
Discovery and brief	2 to 5 days	Both of us
Content and photography	1 to 3 weeks	You
Design	1 to 2 weeks	Me
Build	1 to 2 weeks	Me
Review and revisions	3 to 7 days	Both of us
Testing, checks and launch	2 to 3 days	Me

Read down the last column and the pattern is obvious. The longest stage, and the one with the widest range, is the one sitting with the client. That is not a complaint, it is just where the variance lives. Knowing it up front is what lets you control your own timeline.

I have never had a project run late because the code took longer than expected. Every overrun I can think of traces back to content arriving in pieces.

The stage that decides everything

Content is the whole ball game. When a client sends everything through in the first week, a six week project routinely finishes in four. When content arrives a page at a time across a month and a half, the same project takes four months, because every gap creates a stop and every restart costs half a day of picking the thread back up.

It is worth understanding what a designer actually needs from you before the project starts, because gathering it takes longer than most people expect. I have written a separate piece on what to get ready before your web designer starts, covering the access, brand files and photographs that most often hold things up.

What makes a build run late

Six causes, in rough order of how much damage they do.

1. Content drip-fed page by page. The biggest by a distance. Half-finished pages cannot be designed properly, so the work stalls and restarts.
2. Too many people approving. Three opinions on one homepage headline can cost a fortnight. One person with authority to decide is worth more than any process.
3. Scope growing mid-build. A booking system added in week four is not a small change. It is a different project with a different timeline.
4. Missing access. Nobody knows who registered the domain, or the login belongs to a developer who stopped replying in 2021. This alone can add a fortnight.
5. Waiting on photography. Good photos are worth waiting for, but book the shoot in week one, not week five.
6. Slow feedback. A design sent Monday and reviewed a fortnight later has cost you a fortnight, not the designer.

What makes a build run fast

The inverse, and it really is this simple. Have your words and images ready before the project starts. Appoint one person to give approvals. Agree the scope in writing so nobody is guessing what is included. Reply within two working days. Do those four things and you will land at the fast end of every range in the table above, whoever you hire.

When seven days is genuinely possible

I offer a seven day website, and I am careful about how I describe it, because "website in a week" is exactly the sort of claim that deserves scrutiny.

What makes it work is not that the building is rushed. It is that the variables are removed before the clock starts: scope fixed, content supplied in full on day one, one person approving. Seven working days covers design and build only. If you still need to write your service pages and arrange photographs, that happens beforehand and takes as long as it takes.

So the honest version is this. Seven days is a real timeline for the part I control. It is not a way to skip the part you control.

Does a faster build mean a lower quality website?

Not if the speed comes from preparation and better tools rather than from skipping checks. The things that make a website good are not slow by nature. Fast loading, sensible structure, clean code and clear writing take skill, not months.

What you should never accept is a build that drops technical standards to hit a date. Page performance is measurable, and Google publishes the benchmarks openly as Core Web Vitals. Ask any designer to show you the scores on a site they launched recently. If a quick turnaround came at the cost of those numbers, it shows up there. There is more on how I keep the two compatible on the how we build page.

What happens after launch

Going live and being found are two different timelines, and treating them as one causes a lot of disappointment.

After launch	Typical timeframe
Google discovers and indexes the site	A few days to 3 weeks
Findable when someone searches your business name	1 to 3 weeks
Appearing in local map results	3 to 8 weeks, with a complete Google Business Profile
Ranking for competitive service searches	3 to 6 months of consistent work

Submitting a sitemap speeds up that first row considerably, and Google covers the basics well in its SEO starter guide. The last row is a different discipline altogether, which I have covered separately in how long SEO takes to work.

A realistic schedule for a Cornwall business

Here is how a six week build tends to land in practice for a local trade or service business, starting on a Monday in early September.

Week	What is happening
Week 1	Discovery call, brief agreed and signed, domain and hosting access sorted, photography booked
Weeks 2 and 3	You finish the words for each page. I work on structure and design direction
Week 4	Design presented, you review, one round of changes
Week 5	Build, plus mobile and speed testing
Week 6	Final review, technical checks, launch, sitemap submitted

Notice weeks 2 and 3 run in parallel. That only works when the brief is genuinely settled in week 1, which is the main reason I spend real time on discovery instead of rushing to a design.

The short version

Four to eight weeks is the honest answer for most small business websites. The design and build inside that is two to four weeks. Everything else is discovery, content and approvals, which means the timeline sits far more in your hands than most people assume when they start looking.

If a specific date matters, whether that is a season starting or a shop opening, say so in the first conversation. Working backwards from a real deadline is straightforward. Rescuing a date nobody mentioned is not. For what a build costs alongside how long it takes, there is an honest breakdown in what a website actually costs in Cornwall.