You have decided to get a website, and now the practical question lands: when will it actually be live? Maybe you have a launch date in mind, a busy season approaching, or you are simply trying to judge whether the agency quoting you six weeks is being honest. It is one of the first questions every client asks, and it is completely fair — you have a business to run, and you need to plan around a real date. So, how long does it take to build a website — really?
The honest answer is that it depends, but not in a vague, evasive way. The range is wide because websites vary enormously, and most of the time it takes is not the technical building — it is everything around it. This guide gives you the realistic timelines most UK agencies work to, shows you where the weeks actually go, and tells you what makes projects run late, so you can plan properly and keep yours on track.
The quick answer: typical UK timelines
If you just want the ballpark figures, these are the timeframes most professional UK web designers would recognise for a typical small-business project, from kick-off meeting to launch day:
Landing page (one focused page, contact form, basic tracking): 1–2 weeks.
Simple brochure website (5–8 pages, no complex features): 3–6 weeks.
Professional business website (10–20 pages, custom layouts, quote forms, blog, SEO foundations): 6–12 weeks.
Online shop (products, payments, delivery setup, testing): 6–12 weeks.
Bespoke platform (bookings, customer logins, integrations, custom functionality): 3–6 months or more.
Treat these as sensible planning ranges, not guarantees. Two websites with the same number of pages can take very different amounts of time depending on their design ambition, their features, and — more than anything — how quickly decisions get made along the way.
If you would rather see those phases laid out properly than guess at them, our website design and development service shows exactly what happens at each stage — and what we need from you to keep it moving.
Where the weeks actually go: the six phases
Most of the calendar on a website project is not somebody typing code. Understanding the phases shows you where time goes, and more importantly, where you can influence the date.
1. Discovery and planning (1–2 weeks)
Every solid project starts with working out what the site actually has to achieve: who it is for, what pages it needs, and what each page should make the visitor do. This includes the sitemap, the goals for each page, and practical decisions like hosting and which system the site will run on. Skipping this stage feels fast and costs you a fortnight later, because you end up redesigning pages that should never have existed.
2. Design (2–4 weeks)
The designer produces the look of the site, usually starting with the homepage and getting it signed off before drawing the rest. Once the direction is agreed, the inner page templates follow much more quickly because the big decisions are already made. Expect one or two rounds of feedback on the homepage and lighter rounds after that. This is also where your branding, photos, and real content start to matter — designs built around real words and real images are always better than ones built around placeholder text.
3. Content (running alongside design)
Words and pictures. This phase overlaps with design, but it deserves its own mention because it is the single biggest cause of late launches — we will come back to that. Somebody has to write the copy for every page, choose or commission the photos, and pull together the details: opening hours, prices, testimonials, service descriptions. Many agencies offer copywriting as part of the project, which is worth considering if writing is not your strength.
4. Build (2–4 weeks)
The approved designs are turned into a working website: pages built, forms wired up, the contact system tested, the site connected to its content management system so you can update it yourself. For an online shop, this is where products, payments, delivery options, and transactional emails get configured and tested properly.
5. Testing (a few days to a week)
Before launch, the site gets checked properly: does every form work, does every page look right on a phone, does it load quickly, are there broken links, is the tracking set up? Good agencies test on real devices, not just their own laptop. Rushing this stage is how businesses launch with a contact form that sends enquiries nowhere.
6. Launch (a day or two, with a week of settling in)
The site goes live, redirects are set up from the old site if there is one, and everything is checked again in the real world. Most launches need a few days of small fixes afterwards — a typo here, a photo to swap there. A good agency stays available through this settling-in period rather than disappearing at the moment of launch.

What actually causes delays (hint: it is usually not the developer)
Ask any web designer why projects run late and you will hear the same three answers, in the same order, every time.
Content arrives late. The number one cause of a slipping launch date, by a distance. The build can be finished and waiting while everyone waits for the final wording, the team photos, or the price list. The design needs real content to be designed around, and the build needs real content to be built with. If you take one practical tip from this article, it is this: start gathering your content the day you sign the project, not the day somebody asks for it.
Feedback is slow or contradictory. Every round of feedback adds days. That is fine when feedback is prompt and consolidated — one person, one clear set of changes, decided within a couple of days. It becomes a problem when three people send conflicting comments, or when a round of feedback sits in an inbox for two weeks. Nominating a single decision-maker on your side is one of the most effective schedule protections there is.
The scope grows without the timeline being adjusted. “While you’re at it, could we add a booking system?” Halfway through a project, that innocent sentence can add weeks. New features mean new design, new build, and new testing. There is nothing wrong with adding features — but they belong in an agreed second phase with their own timeline, not squeezed silently into the existing one. Any agency that says yes to scope changes without mentioning the schedule is doing you no favours.
How to keep your project on schedule
You have more control over the timeline than you might think. Most of the leverage sits on the client’s side of the table:
Have your content ready early. Write the words and gather the photos before the design starts if you can. At minimum, have them ready when the designer asks — not a month later.
Name one decision-maker. Feedback from one person with the authority to sign things off moves projects along. Feedback by committee, with everyone cc’d and nobody deciding, stalls them.
Give feedback in batches, on time. Collect all your thoughts on a design round and send them together, within the agreed window. Dripping comments in one at a time over three weeks restarts the clock each time.
Freeze the scope. Agree what the project includes at the start, and put new ideas on a “phase two” list. You can always build more after launch.
Reply to your agency promptly. Every unanswered question is a day the project cannot move. Treat your developer’s emails like customer enquiries — because in schedule terms, they are.
What about DIY website builders — how fast are they really?
Website builders like Wix, Squarespace, and Shopify promise a site in a weekend, and for a very simple site that is roughly true. The honest picture: the tool is fast, but the work is the same. You still need the words, the photos, the structure, and the decisions — the builder just removes the developer from the equation and hands all of that work to you. Most owners find the “weekend project” stretches across several evenings and weekends, and the result reflects how much time they could spare rather than what the business needed. Builders are a legitimate option for the simplest sites; they are just not the shortcut they look like once you count your own hours.
A realistic week-by-week picture of a small business build
To make this concrete, here is what a typical 5–6 page brochure website for a UK small business looks like when it runs well:
Week 1: Kick-off call, discovery, sitemap and plan agreed. You start gathering photos and writing service descriptions.
Weeks 2–3: Homepage design produced and signed off; you send your first round of content.
Weeks 3–4: Inner page designs; remaining content arrives; copy tweaks happen.
Weeks 4–5: Build: pages constructed, forms wired, mobile layouts checked.
Week 6: Testing, your final review, small fixes, launch.
Notice how much of that calendar involves you. The projects that hit their dates are the ones where the business owner treats their side of the work — content, decisions, feedback — with the same seriousness as the agency treats the build.

Planning a website? Start with a realistic date
If you have a launch in mind — a busy season, a rebrand, a new service going live — work backwards from it and add a buffer, because almost every project meets at least one small delay. And if an agency promises you a full professional website in a week, ask what is being skipped to make that possible: it is usually the discovery, the testing, or your input, and you will pay for at least one of those later.
Replacing an existing site rather than starting from one? Run a free AI SEO audit on your current website first — it shows what is worth keeping, what needs fixing, and what the new build has to beat.
Book a free strategy call with Vantrix360 and we will map out a realistic timeline for your project — what it includes, where the weeks go, and what we would need from you to hit your date. No inflated promises, no mystery process: just a clear plan you can actually schedule around.
