Start a project
/ 01
Design & Branding
Featured

Not sure where to start? Book a discovery call.

A free 20-minute call to talk through your goals — no pitch, no pressure.

Start a project

How long does it take to build a website? (2026 UK timeline guide)

Home/Journal/How long does a website take?
Journal  ·  Web Design  ·  9 min read

How long does it take to build a website?

A realistic 2026 timeline guide for UK businesses — what every stage actually takes, what slows projects down, and how to plan around your launch date.

If you’re a UK business planning a new website in 2026, the honest answer to “how long will it take?” is somewhere between 2 weeks and 4 months, depending on the size, complexity, and how quickly you (the client) can turn things around. Agencies that promise “two weeks for everything” are oversimplifying. Agencies that quote “six months” for a simple brochure site are padding. This guide breaks down what each stage actually takes and what you can do to keep the project moving.

The short answer

Typical timelines for a properly built (not template-rushed) website in 2026:

  • 1–2 weeks — Single-page sites, simple template builds, urgent launches
  • 3–5 weeks — Standard small business sites, 5–10 custom-designed pages
  • 6–10 weeks — Bespoke sites with custom design, deeper content work
  • 8–14 weeks — E-commerce builds with proper product setup and integrations
  • 3–6 months — Enterprise builds, custom applications, large content platforms

Most UK SMBs end up in the 3–10 week range. The rest of this guide walks through what’s actually happening in those weeks, and what makes some projects take 5 weeks while others (with identical scope) drag out to 15.

Stage 1: Discovery and planning (Week 1)

Before any pixel gets pushed, a good agency will spend time understanding your business, goals, target audience, and competitive landscape. This usually takes 3–5 working days.

What happens in this stage:

  • Kickoff meeting — goals, audience, competitors, success metrics
  • Sitemap drafted (what pages exist, how they connect)
  • Content audit — what you have, what’s needed, who’s writing it
  • Technical setup — hosting, domain, integrations decisions
  • Moodboard or visual direction agreed

What you need to do: Show up to the kickoff. Send over any brand guidelines, past sites, examples you like. Be honest about your goals and constraints. Skip this stage at your peril — every hour spent in discovery saves about three hours of rework later.

Stage 2: Design (Weeks 2–3)

The visual side of the project. For a standard small business site this typically takes 1–2 weeks; for bespoke sites, 3–4 weeks.

What happens in this stage:

  • Wireframes — rough layouts showing what goes where on each page
  • Visual design — homepage and 1-2 key pages designed first
  • Review and revisions — typically 1-2 rounds for standard projects, 3-4 for bespoke
  • Remaining pages designed based on approved direction

What you need to do: Review designs within 48 hours of receiving them. Consolidate feedback across your team before sending it (not five separate emails from five different people). Be specific about what’s not working — “I don’t like it” is unhelpful, “the headline feels too corporate, can it be warmer?” is gold.

This is the stage where most projects slip. Slow client feedback in the design stage is the single biggest cause of project overrun. A 5-week project becomes a 10-week project simply because each review round took the client 5 days instead of 2.

Stage 3: Build and development (Weeks 3–5)

Once designs are approved, the developer turns them into a working website. For a 5–10 page site on WordPress or Webflow, this typically takes 1.5–2 weeks. Custom functionality and e-commerce adds more time.

What happens in this stage:

  • Designs converted to working HTML/CSS pages
  • Mobile-responsive layouts built and tested
  • CMS configured (so you can edit content later)
  • Forms, integrations, and any custom functionality wired up
  • Content loaded into pages

What you need to do: Mostly stay out of the way and let the team build. The exception: if you owe copy, photography, or product data, get it sent over. Many projects stall here because the agency is waiting on content the client promised three weeks ago.

Stage 4: Content, QA, and pre-launch (Week 5)

The site exists but isn’t quite ready. This stage typically takes 3–5 working days.

What happens in this stage:

  • Final content review and proof-reading
  • SEO setup — meta titles, descriptions, schema markup, sitemap
  • Cross-browser testing (Chrome, Safari, Firefox, mobile devices)
  • Accessibility checks (WCAG AA at minimum)
  • Performance optimisation (image compression, caching, page speed)
  • Analytics, Search Console, and tracking pixels installed
  • Final client review and sign-off

What you need to do: Do one final full read-through. Click every button. Test every form. Check the contact info is correct. Don’t sign off without doing this — fixing things post-launch is more painful than fixing them now.

Stage 5: Launch and aftercare (Week 5+)

Launch day is anti-climactic — for a well-prepared site it’s about 1-2 hours of DNS changes and final checks. The 30 days afterward is where the value really compounds.

What happens at launch:

  • Domain pointed to new site (DNS changes, can take up to 24 hours to propagate fully)
  • 301 redirects in place for any old URLs that have changed
  • Sitemap submitted to Google Search Console
  • Training session for client on how to edit content
  • 30 days of post-launch support to catch any issues

What slows projects down (and how to avoid it)

Almost every overdue website project shares the same root causes. Here are the top ones, in rough order of frequency:

  1. Slow client feedback. Every day you take to review a design is a day the project doesn’t move. Aim for 48-hour turnarounds.
  2. Missing content. Especially copy and photography. Either commit to writing it yourself early, or hire it out (your agency probably offers copywriting and photography for an additional fee).
  3. Decision-makers not in the loop. If the MD only sees the work at the end and changes their mind about direction, you’re starting over. Get everyone on the kickoff call.
  4. Scope creep. “Can we also add a booking system?” mid-build pushes the timeline. Decide what’s in and out before kickoff. If you do need to add something, accept it’ll extend the timeline.
  5. Third-party delays. Waiting on someone else (your accountant, your photographer, your existing tech provider). Identify these dependencies early and chase them.
  6. Round of revisions taking longer than the original design. If you find yourself on round 4 of homepage feedback, something’s wrong with the brief. Take a step back and have a strategy conversation, not another design round.

Can you rush it?

Yes — but expect to pay for it, and accept the trade-offs.

Rush options:

  • Template-based build: 1-2 weeks. Trade-off: site looks generic and may not convert as well as a custom design.
  • Custom site with rush fee: 2-3 weeks instead of 5. Trade-off: typically 30-50% rush fee, fewer revision rounds, longer working hours from the team.
  • Phased launch: Launch a minimum viable site (homepage + key pages) in 3 weeks, then add the rest over the following months. Often the smartest approach.

What you can’t rush: getting a site that genuinely converts, has solid SEO foundations, and works flawlessly across devices. Speeding through those parts costs you more in the long run than the time saved upfront.

A realistic timeline at BPE Digital

For transparency, here’s what our typical project timeline looks like:

  • Starter projects (£350–£800): 1–2 weeks from kickoff
  • Standard projects (£1,000–£2,500): 3–5 weeks from kickoff
  • Bespoke projects (£2,500+): 6–10 weeks from kickoff
  • E-commerce: Add 2-4 weeks to whichever tier above

We don’t generally accept rush projects — every site we build needs the time to be done properly. But if your launch date is genuinely fixed (a product launch, a rebrand, a moving date), tell us at the discovery call and we’ll be honest about whether we can hit it. Book a discovery call here.

The bottom line

Most UK SMBs should plan for 4–8 weeks from kickoff to launch for a properly built website. Less than that and you’re either getting a template build or a rushed custom site. More than that and someone (probably the client) is the bottleneck.

If you have a specific launch date in mind, the best next step is a free 30-minute discovery call. We’ll walk through your scope, work backwards from your deadline, and tell you honestly what’s achievable. Book a discovery call here.

Related reading

Got a launch deadline?

Book a free 30-minute discovery call. We’ll talk through your scope, work backwards from your deadline, and tell you honestly what’s achievable.