Skip to main content
← Journal
Guides5 min read

What to expect from a website project: a UK small business timeline

Most UK small business websites take 4–8 weeks from kickoff to launch. Here's the week-by-week breakdown, what slows projects down, and what speeds them up — so you can plan around it.

By James Sheen

Most UK small business websites take between four and eight weeks from a confirmed brief to launch. If you have been quoted two weeks, someone is cutting corners. If you have been quoted six months, the scope has bloated or capacity is the real constraint. The answer to how long does it take to build a website honestly sits in that four-to-eight-week window for most SMB projects — and the spread is almost entirely determined by how ready you are, not how fast the agency is. The full UK website cost guide covers what drives the price; what follows covers what drives the timeline.

Week 1: Discovery and brief lock

Nothing gets designed until the brief is agreed. Week one is a scoping call (or two), a written back-brief from the designer, and sign-off from you. This is the week where the scope gets fixed.

What gets agreed: the list of templates, platform choice, integrations required, content responsibilities, revision rounds, and go-live date. If you are providing copy yourself, week one is also when you confirm you have it, or agree a date when you will.

Projects that skip a written back-brief almost always run over time. The discovery call feels like enough, but it is not. Honestly, I've seen more timelines slip in week one than in any other week. Getting scope agreed in writing is the single cheapest thing you can do to protect the timeline.

Weeks 2–3: Design phase

Creative direction, layout exploration, and a round of revisions. Week two is typically initial concepts; week three is refinement and sign-off.

The design phase is where tight briefing pays off. If you read the briefing guide before your kick-off call, you will have given the designer enough to work from without the "we'll know it when we see it" loop. That loop is the most common reason the design phase extends into week four.

One decision point matters more than any other here: the homepage. If you can get the homepage design signed off cleanly, the rest of the templates follow a consistent pattern. Partial sign-off creates cascading changes in the build phase. That is the slow path. I ask clients to sit with the homepage for 24 hours before giving feedback, rather than reacting in the room.

Weeks 4–6: Build phase

Templates are built. Not pages: templates. A ten-page site might use five or six templates, and the build work scales with unique template complexity, not raw page count. This is the same principle that drives your quote (see the cost guide Section 2) and it shapes the build timeline too.

Week four: core templates built (homepage, key landing page, global navigation and footer). Week five: secondary templates (services, about, blog index). Week six: content population, integrations wired, and first internal QA pass.

Integrations are where build schedules slip most often. A booking system or CRM connection that looks simple on paper can take a week alone if credentials are missing, the third-party API needs a paid tier, or the integration requires configuration on your side. I have quoted projects where a single integration discovery added £500 to the scope because the access issue surfaced mid-build rather than in week one. Name every integration at brief lock and confirm access levels before the build starts.

Week 7: Content and revisions

This is the week most projects stall. The design is built. The site is technically working. And then it sits, waiting for copy. In practice, a sole trader I worked with recently held up launch by three weeks because the about page copy kept getting "almost done." The site was ready; the words weren't.

If you are providing the content yourself, week seven is when it lands. If copy is late, the go-live date slides one week for every week the copy is delayed. It is not negotiable — the developer cannot launch placeholder text, and QA cannot run on incomplete pages.

Stakeholder review also happens here. If multiple people need to sign off, agree the review window in week one: "You have five business days in week seven to review. Feedback must be consolidated before it comes back to the developer." Consolidated feedback means one document, one voice. Scattered feedback from three separate emails adds revision cycles.

Week 8: Launch and handover

Pre-launch QA covers broken links, mobile layout, page speed, and redirect mapping if you are replacing an existing site. Domain transfer or DNS cutover typically takes 24-48 hours to propagate. A go-live day should not be a Monday — if something goes wrong, you want the team available.

After launch: a handover session (one hour), documentation for your CMS, and a two-week settling period where small post-launch fixes are addressed. Startups.co.uk notes that ongoing support arrangements vary widely. Some businesses self-manage from day one; others prefer a retainer for ongoing changes. That decision is worth agreeing before launch, not after.

What slows projects down (and what speeds them up)

Factor Slows it down because Speeds it up by
Content readiness Missing copy pushes QA and launch. Each week of delay = one week on the timeline. Providing final copy at brief lock removes the single biggest variable from the schedule.
Decision-maker availability Partial sign-off and multi-stakeholder review loops add revision cycles that compound. One named decision-maker with a five-day review window per phase keeps the process moving.
Scope creep New features requested mid-build go to the back of the queue or push the launch date. Locking scope in the brief means new requests become a separate conversation, not a blocker.
Integrations Third-party access issues, API limits, or paid tier requirements can stall build for days. Confirming credentials, plan levels, and access in week one eliminates the most common build-phase blocker.

Where this fits in the bigger picture

Four to eight weeks is the typical range. Eight-plus weeks usually means one of the four factors above has slipped, or the scope was larger than a typical SMB project from the start. Two weeks or fewer means something is templated to the point of being off-the-shelf, not designed to your brand. The catch is that the faster anyone promises to move, the more that speed is being funded by assumptions about your readiness.

Understanding the timeline is part of understanding the cost. The full UK website cost guide covers how page complexity, platform choice, and content responsibilities translate into a quote. If you are preparing a brief and want to understand what information to give a designer upfront, the briefing guide walks through it. A good brief is the most reliable way to shorten a project timeline without cutting corners.

References

A headshot picture of Sheen Digital Media founder James Sheen

James Sheen

Founder + Senior Software Engineer

Senior software engineer with 14 years of experience and the founder of Sheen Digital Media. Writes about web development for UK small businesses.

More about James →

Got a project in mind? Let’s talk it through.

Get a quote

More in Guides