How Long Does It Actually Take to Build a Website? A Realistic UK Timeline

How Long Does It Actually Take to Build a Website? A Realistic UK Timeline

You've had a quote, you've said yes, and now the obvious question is: when does this actually land? Ask five agencies and you'll get five different answers, ranging from "two weeks" to "three months," and neither one on its own tells you much. The honest answer depends on what's being built and, just as much, on how quickly you can get content and decisions back to whoever's building it.

The rough bands, and why the range is so wide

For a straightforward brochure-style site, five to ten pages, no login areas, no custom booking system, most UK agencies are working in a four-to-eight week window from kickoff to launch. A single-page landing site built from an existing template can land in one to two weeks if the copy and images are ready on day one.

Once you move into custom functionality, the range stretches out fast. A bespoke online shop with product variants, stock syncing, and a proper checkout typically runs eight to sixteen weeks depending on how many products you're listing and whether it needs to talk to an existing till or stock system. A web application with its own database, user accounts, and features that don't exist off the shelf can take four to six months, sometimes longer if it's genuinely novel rather than a variation on something that's been built before.

None of these numbers are wrong. They're just answering different questions, which is why "how long does a website take" gets such wildly different replies depending on who you ask and what they assumed you meant.

What actually eats the time (it's rarely the coding)

If you've been quoted eight weeks and the project takes fourteen, the extra six weeks almost never come from the development work itself. They come from three places, over and over again:

Content. Someone needs to write the words, choose the photos, and decide what the pricing page actually says. If that person is you, and you're also running the business day to day, this is the single biggest cause of slipped timelines we see. A site can't go live with "lorem ipsum" in the services section.

Feedback loops. When a design goes to a client for review and the reply takes eight days instead of two, that's eight days added directly to the calendar, not absorbed somewhere. Agencies build working days into their timelines, not calendar days, so a slow reply genuinely moves the launch date.

Scope creep. "Could we also add a booking calendar" three weeks into a five-week project is a reasonable thing to want, but it's new scope, and new scope needs new time. The projects that stay on schedule are usually the ones where the full feature list was locked down before anyone started building, not added to along the way.

A realistic week-by-week shape for a standard business site

For the most common project type, a five-to-ten page business website with a bit of custom design, here's roughly how a six-to-eight week build tends to break down. Discovery and planning takes the first week: understanding the business, mapping out the pages, agreeing the sitemap. Design usually takes another one to two weeks, covering the homepage look and feel plus the key inner pages, with a round or two of feedback built in. Development, the actual building of the site, takes two to three weeks once designs are signed off. Content and SEO setup, getting the words, images, and metadata into place, often runs alongside development rather than after it, which is where a lot of time gets clawed back. The final week is testing across devices and browsers, fixing what breaks, and going live.

Notice that "building the website" is only about a third of the total timeline. The rest is planning, content, and making sure it actually works properly before launch, which is exactly the part that gets rushed or skipped when a project is quoted purely on development hours.

Why the cheapest quote is often the slowest one in practice

A £500 website and a £5,000 website aren't just different in finish, they're different in what's included in that timeline. The cheaper option is frequently a template with placeholder content dropped in around it, which looks fast on paper but leaves you doing the content work yourself afterwards, unpaid and unplanned. The more expensive option usually includes proper content support, a structured review process, and someone chasing you for the assets they need rather than waiting for you to remember. Slower to quote, often faster to actually launch with something usable.

Mobile is worth building in from day one rather than testing at the end: more than half of all web traffic globally now comes from mobile devices, and a site that was designed on a desktop screen and only checked on mobile afterwards tends to need a second pass anyway, which adds time you didn't budget for.

What to ask before you agree a launch date

Before signing off on a timeline, it's worth getting specific answers to a few things: what exactly counts as "content ready" (final copy, or a rough draft they'll tidy up?), how many rounds of design feedback are included before extra rounds cost more, and what happens if you're slow to reply, does the launch date move, or does the agency just squeeze the remaining stages. An agency that can answer all three clearly, in writing, before you start is generally one that's run this process enough times to know where it goes wrong.

If you're weighing up a project and want a straight answer on how long yours would realistically take, rather than a generic range, we're happy to talk it through. Book a free 15-minute consultation with Digital Hand and we'll give you an honest estimate based on what you actually need, not a template answer.