How Long Does It Take to Build a Website? Honest UK Timelines

"How long will my website take to build?" gets the vaguest answers of any web question in the UK — vendors promise "a few weeks" and deliver in four months, or quote six months for what needed six weeks. The truth is that timelines are predictable once you know the site type, the route, and the one factor that delays more UK builds than anything else combined: content. This article gives you the real ranges and the week-by-week anatomy of a typical build.

The ranges first, sourced properly: a basic informational website takes 2–4 weeks, a small business site with custom design takes 4–8 weeks, ecommerce takes 6–12 weeks, and custom web applications run 12–16 weeks (Runningfish development timeline guide, 2026). UK designers report similar spans, with simple custom sites at 2–6 weeks (Big Cat Creative, 2026). What varies most is not the technology — it's how quickly decisions, content and feedback arrive from your side of the table. Build time is a team sport, and you're on the team.

Key Highlights

• Basic brochure site: 2–4 weeks from brief to launch with a freelancer or builder.
• Custom-designed small business site: 4–8 weeks is the realistic UK norm for an agency build.
• Ecommerce: 6–12 weeks; custom web applications: 12–16 weeks and above.
• Content is the #1 delay cause — copy and images not being ready stalls more builds than all technical issues combined.
• Roughly 40% of delayed projects in agency experience stall waiting for client content; scope changes and slow feedback make up most of the rest (illustrative agency estimates).
• Every week of decision delay on your side pushes launch a week — feedback latency is the owner's timeline lever.
• Speed targets matter at launch: ~60% of visits are mobile (StatCounter, 2026) and 75% of consumers judge credibility on design (Stanford) — testing takes the time it takes.
• A focused owner who supplies content on schedule routinely cuts the quoted timeline by 1–2 weeks.

The Honest Answer: Typical UK Timelines

Match your project to the table below and you have your realistic window. These are working ranges, not best cases — they assume a decisive client, a competent vendor and content that arrives on schedule. If a quote promises the lower bound with your content still unwritten, treat the promise as marketing, not planning.

Key takeaway: site type sets the floor and content readiness sets the actual date — pick your row honestly before you schedule anything around the launch.

Step 1: Discovery and Planning (Weeks 1–2)

Every solid build starts with a compressed burst of clarity: what the site must do, who it serves, what pages exist, and what "success" measures. Discovery is where the one-page brief becomes a sitemap, a page-by-page content plan and a signed-off scope. Skimp here and the project pays interest later — changes discovered in week 6 cost multiples of changes agreed in week 1.

Your job in this phase is speed, not perfection: answer questions in days, not weeks, and lock the success metric. Our project brief guide walks the exact document that makes this phase a formality. Agencies in this phase typically finalise the statement of work, milestone dates and the acceptance criteria you'll sign against at launch.

Key takeaway: two disciplined weeks of discovery save five undisciplined ones later — this is the cheapest phase to accelerate and the most expensive to skip.

Step 2: Design Direction (Weeks 2–4)

Design is where the site stops being a spreadsheet and becomes something you can react to. Expect wireframes (the layout skeleton), then a homepage design direction, then interior page templates — presented for your feedback in structured rounds. Well-run projects cap revisions (typically two formal rounds) with feedback consolidated by one decision-maker on your side, because five stakeholders emailing contradictory notes is how design phases double in length.

Judge design on your own phone, not just the presentation screen — ~60% of web traffic is mobile (StatCounter, 2026) and 75% of consumers judge credibility on design (Stanford web credibility research), so the small-screen experience is the brand for most visitors. Approve the direction decisively: every day a design sits "in review" pushes development behind it.

Key takeaway: consolidated feedback from one decision-maker is the difference between a 2-week design phase and a 6-week one.

Step 3: Content — The Hidden Critical Path

Here is the phase nobody budgets time for and every project depends on. Copy, photography, product data, service descriptions — content is technically "parallel work", but in practice it's the critical path: the most common single cause of delayed launches is client content that wasn't ready (agency experience puts it near 40% of stalled projects, with scope changes and feedback delays covering most of the rest). A developer cannot finish a page whose text doesn't exist; a photographer's schedule won't compress because your launch date is fixed.

The fix is unglamorous: decide in week 1 who writes and supplies what, and start before development begins. Supplying a content sitemap — text per page, image list per page — with your brief routinely saves 1–2 weeks end to end. Our business website checklist doubles as a content planning tool if you're starting from a blank page.

Key takeaway: treat content as the critical path, not an afterthought — the builds that launch on time are the ones where writing started in week one.

Step 4: Development (Weeks 4–8)

This is the phase that looks quiet from your side and isn't from theirs: pages built, CMS configured, forms wired, payments or bookings integrated, and the design turned into fast, responsive templates. Good vendors show a staging link early and keep it current — weekly, ideally — because the cheapest bugs are the ones you spot in week 5 rather than week 10. Ecommerce and booking builds run longer here (see the ecommerce storefront case study for the engineering a real shop carries).

Key takeaway: development runs on rhythm — a staging link you review weekly is worth more than any project management tool.

Step 5: Testing, Revisions and Sign-Off (Weeks 8–10)

Testing is where timelines die by optimism. Every page gets checked on real phones and tablets, every form and payment path gets exercised end to end, speed gets measured against Core Web Vitals targets, and content gets a final proofread. Compress this phase and you launch the bugs straight to your customers; skip it and the 94% of people who mistrust poorly designed sites meet yours at its worst — our Core Web Vitals case study shows what disciplined speed work looks like when it is done properly.

The effort splits predictably across four workstreams:

Key takeaway: book testing time in the calendar as seriously as the launch itself — it is the last phase where fixes are cheap.

What Makes Builds Faster — or Slower

After the phases, four levers decide where in the range your project lands. Content-first is worth 1–2 weeks (see Step 3). Decision speed is worth as much again: vendors who get answers in 24 hours launch weeks earlier than those waiting on committee.

Existing brand assets — logo files, photography, a colour system — remove a week of guesswork. And staged scope, launching the core site first and adding the nice-to-haves in phase two, converts a 12-week wait into a 6-week launch plus a planned improvement cycle.

Key takeaway: most "slow developer" stories are actually slow-content and slow-decision stories — control your levers and the timeline compresses on its own.

What Your Business Should Do

Days 1–30: Prepare like a vendor would.

• Write the one-page brief and the page-by-page content plan; list every image you already own.
• Collect three quotes with milestone dates against your real site type — not a fantasy lower bound.
• Appoint one decision-maker and set a 48-hour internal response rule for vendor questions.

Days 31–60: Drive the middle phases.

• Approve the design direction in structured rounds; consolidate feedback before it's sent.
• Start writing (or commissioning) content in parallel — first draft due before development ends.
• Review the staging site weekly on your own phone; log issues in one shared list.

Days 61–90: Test, launch, verify.

• Run the five-row testing table above end to end before sign-off.
• Launch, then verify indexing, analytics and enquiry routing in week one.
• Book the 90-day review: speed, rankings and conversion — and plan phase-two improvements.

The Bottom Line

A UK business website takes 2–4 weeks basic, 4–8 weeks with custom design, and 6–12 weeks for ecommerce — and the difference between the quoted range and the lived experience is almost always content and decision speed on the client side. Pick your site type honestly, start content in week one, and respond fast; the timeline rewards owners who treat the build as a team sport. If you want milestone dates you can actually plan a marketing campaign around, book a free strategy call or send us a message — we'll map your build week by week before we quote it.