The honest answer is "it depends", and the thing it depends on is usually you, not the agency. That is not a dig. It is the single most useful thing we can tell you before you start, because once you know it, you can take weeks off your launch.

Here is a realistic picture of how long a website takes, where the time actually goes, and what speeds it up.

The short answer

For a UK business, typical timelines look like this:

• A small brochure site (around five to ten pages, custom design, no complex features): roughly three to six weeks.
• A larger, conversion-focused site (content strategy, proper SEO architecture, copywriting, a few custom features like booking or calculators): roughly six to twelve weeks.
• A web application or e-commerce build with real logic: months, and rightly so. You are building software, not a brochure.

If someone promises you a quality, custom site in a couple of days, be careful. They are either dropping your logo onto a template, or they are about to find out why it takes longer.

Where the time actually goes

A website project is not one long block of "building". It is a handful of phases, and the build is rarely the slow one.

• Discovery and planning. Working out what the site needs to do, who it is for, and what each page is there to achieve. Skipping this is how you end up rebuilding in a year.
• Design. Turning that into how it looks and feels. Usually the phase with the most back-and-forth.
• Content. The words, images, and proof. The most underestimated phase by a mile, and we will come back to it.
• Build. Turning the design into a real, working, fast site.
• Review and launch. Testing, fixing, checking it on real phones, going live.

The real bottleneck is almost never the code

Here is the thing nobody tells you: the build is the predictable part. We can estimate that accurately. What blows timelines is everything that needs a decision or a piece of content from your side.

The classic example is copy. A project is flying along, then it stops dead for three weeks because the "about" page text is sitting in someone's drafts. Multiply that across a whole site and you can see how a six-week project becomes a four-month one without anyone doing anything obviously wrong.

What speeds it up

• One decision-maker. A site designed by committee moves at the speed of the slowest reply. Name the person who gets the final say.
• Content sorted early. Either have it ready, or pay someone to write it, often the agency. Do not let the site wait on words.
• Fast, batched feedback. "Here are all my notes on the homepage" beats five separate emails over two weeks.
• A tight scope. Every "could we also add" is time. Park the extras for after launch and ship.

What slows it down

• Waiting on content that never quite gets finished.
• Feedback that arrives in pieces, days apart.
• Scope creep, the site quietly growing new pages and features mid-build.
• Too many opinions with nobody to settle them.

None of these are technical problems. All of them are within your control.

A sensible way to think about it

Ask your agency for a timeline broken into phases, with the points where they need something from you marked clearly. Then protect those points. If you know the content deadline three weeks out, you can actually hit it.

A good studio will also be straight with you about trade-offs. You can launch a strong, lean site quickly and grow it, which is often the smart move, or build the full thing up front and wait longer. Neither is wrong. Pretending you can have the full thing instantly is.

If you want a realistic timeline for your specific project, that is part of how we scope every website, and it pairs well with our honest take on what a website actually costs.