If you’ve ever asked a web designer how long your website will take, you’ve probably heard some version of “it depends.” It’s not a dodge. A one-page landing site and a full ecommerce build genuinely don’t run on the same clock, so a single flat answer would be misleading rather than helpful.
As a rough guide: most UK small business websites take somewhere between 1 and 20 weeks from kickoff to launch, depending on the type of site, how much content needs writing, and how quickly you can turn around feedback.
A simple landing page sits at the fast end. A full ecommerce or membership build with logins, payments and integrations sits at the slow end. What actually decides where your own project lands is exactly what we’ll walk through below, along with typical timelines by website type and the stages that make up a build.
How long should the build take?
As a rough guide: a one-page landing site typically takes 1 to 3 weeks, a multi-page brochure site 4 to 8 weeks, an ecommerce website 10 to 16 weeks, and a membership or subscription site 12 to 20 weeks.
That’s the average time to design and build most small business websites in the UK. These are typical ranges rather than fixed timescales, the exact figure depends on how much content needs producing, how quickly you can review and approve work, and whether the build is bespoke or templated.
Here’s What Determines the Timline
Two projects that sound similar on paper can take very different amounts of time. Scope is only part of the story. What actually moves the timeline is usually one or more of the following:
- How much content, copy, images, and product data, needs writing or sourcing
- Whether the site needs ecommerce, bookings, or membership functionality
- How many rounds of design feedback and revisions you need
- How quickly you can turn around approvals and content on your end
- Integrations with other tools, such as CRMs, payment providers, or booking systems
- Whether the build is bespoke or based on a template
If you’re weighing up bespoke vs templated websites, templates are the faster route to launch since much of the structural design work is already done, while a bespoke build takes longer in exchange for a site designed entirely around your business. It’s the same trade-off that shows up in how much a website actually costs, just measured in weeks instead of pounds.
One thing worth being honest about upfront: the business often controls more of the timeline than the developer does. Slow feedback and late content are the single most common reason a project overruns its original estimate.
Website Timelines by Type
Here’s how those ranges break down by the kind of website you’re building, using the same four categories as our cost guide, since the two tend to move together.
| Website type | Typical UK timeline | What affects it most |
|---|---|---|
| One-page / landing website | 1 – 3 weeks | Design rounds, how quickly copy is ready |
| Brochure website (multi-page) | 4 – 8 weeks | Number of pages, content readiness |
| Ecommerce website | 10 – 16 weeks | Product catalogue size, payment integration, testing |
| Membership / subscription website | 12 – 20 weeks | User accounts, gated content, recurring billing setup |
If you’re building to sell online, it’s worth understanding what an ecommerce website actually involves before you scope a timeline, since payment integration adds testing time a brochure site simply doesn’t need. Card payments have to meet the PCI Data Security Standard, and testing that properly, rather than just switching a payment gateway on, is one of the main reasons ecommerce timelines run longer than the page count alone would suggest.
Membership sites sit at the slow end for the same reason they sit at the top of the cost range: logins, gated content, and recurring billing all need building and testing properly, not just switched on. It’s a category most timeline guides skip over entirely, which makes it easy to underestimate how long that kind of build actually takes.
What stages are needed for a website build?
Regardless of website type, most builds move through the same broad stages. Knowing what happens in each one makes it easier to spot where a project is likely to slow down.
Discovery and planning (1–2 weeks)
Before any design work starts, this stage is about understanding what the site actually needs to do, who it’s for, what pages it needs, and what it needs to integrate with. Rushing this stage is one of the more common reasons a project runs into delays further down the line, since decisions made here shape everything after it.
Design (1–4 weeks)
How long this takes usually comes down to how many rounds of feedback and revisions are needed, more than the design work itself. Agreeing on a fixed number of review rounds upfront keeps this stage predictable. It’s rarely time wasted either way, since how your site’s design affects the user experience has a direct bearing on whether visitors actually stick around once the site is live.
Development (2–6 weeks)
This is where the site actually gets built, and it’s also where your choice of platform has the biggest impact, not just on how long the initial build takes, but on how long and how expensive every change is after launch.
WordPress now powers around 41% of all websites globally, and it’s the platform we prioritise for exactly this reason: once a WordPress site is live, updating a page, adding new content, or making small changes doesn’t need a developer at all, which keeps things fast and affordable long after launch. It’s worth reading why businesses choose WordPress as their CMS if you want the fuller picture.
A fully custom-coded HTML website can look appealing if you want complete design freedom, but every change afterwards, even something as small as updating a phone number, generally needs a developer comfortable working directly in the code.
That’s usually fine for the initial build, but it tends to make ongoing changes slower and pricier than they need to be, something we’ll cover properly in an upcoming piece on website maintenance costs.
Content (often running in parallel)
Writing and gathering copy, images, and any product data often happens alongside design and development rather than after it, but it’s frequently the stage that adds the most delay if it’s not ready on time. Knowing the essential pages every website needs before the project starts, and having a plan for who’s writing what, keeps this stage from becoming the bottleneck.
Testing and launch (several days – 2 weeks)
Checking the site works properly across devices and browsers before it goes live, including responsive design checks on mobile and tablet, and, depending on your business, a look at UK accessibility requirements so the site works properly for visitors using assistive technology too.
What’s the fastest way to build a website?
The honest answer is a templated build with your content ready to go, since that removes the two slowest variables, design revisions and waiting on copy, from the equation.
But it’s worth understanding what you’re actually trading off first. A rushed build usually means less time for design revisions, less thorough testing, or a templated approach instead of a bespoke one.
None of those are automatically bad choices, provided you’re clear on what makes a good website in the first place and aren’t cutting something that actually matters. A templated brochure site with content ready to go can realistically launch in a couple of weeks.
What doesn’t compress well is ecommerce and membership functionality, since payment and account systems need proper testing regardless of how quickly you want to launch, and cutting that corner is where problems tend to show up after launch rather than before it.
If your timeline is tight, the more useful question usually isn’t “how fast can this go” but “what’s actually driving the number I’ve been quoted,” since that’s what tells you whether there’s genuine room to move it.
Keeping Your Project on Schedule
A few things that reliably keep a build on track, most of which are within your control rather than the developer’s (our guide to delivering projects on time, every time covers the fuller playbook):
- Have your content, copy, images, and any product data, ready before development starts, not partway through
- Agree on a fixed number of feedback rounds upfront, so revisions don’t drift
- Nominate one person to give final sign-off, rather than collecting feedback from several people separately
- Turn around approvals within a day or two rather than letting them sit
- Flag any must-have integrations at the very start, not once development is underway
None of these speed up the build itself. They just stop the timeline slipping for reasons that have nothing to do with development.
There’s Everything You Need to Know
Timelines and budgets tend to move together, so if you haven’t already, it’s worth reading how much a website actually costs alongside this, since the two decisions usually get made at the same time.
Once your new site is live, it’s worth thinking about how it actually gets found. Our guide to ranking in AI search covers what that looks like in 2026, and our digital marketing team is on hand if you’d rather hand that side over too.
When you’re ready to talk through what your own project would involve, our web design process page walks through exactly how we work, or our website design team is happy to talk it through with you directly, no pressure and no obligation.
Your Questions. Our Answers.
Most small business brochure sites take 4 to 8 weeks from kickoff to launch, depending on how many pages you need and how quickly content is ready.
Technically yes, using a website builder and a template, but it won’t include custom design, proper content, or testing. For anything meant to represent a business properly, budget at least a couple of weeks.
A templated build with your content ready in advance is the fastest realistic route, since most of the delay in any project comes from waiting on content or feedback, not the build itself.
Often close to it. A redesign still needs discovery, design, and testing, though having existing content and a clear sense of what didn’t work can shave time off the process.
Slow content delivery and multiple rounds of feedback are the two most common causes, ahead of anything to do with the build itself.
