How Long Does It Take to Build a Website? Realistic Timelines

A simple brochure website for a small business typically takes two to six weeks from agreed brief to launch. A larger business site with custom design and more pages usually takes six to twelve weeks, an e-commerce site eight to sixteen weeks, and a custom web platform with bespoke features three months or more. The biggest factor is rarely the build itself: it's how quickly content, feedback and decisions arrive.

These are typical ranges, not promises. Use them to sense-check quotes and plan your launch.

Typical website timelines by type

The stages of a website project

1. Discovery and planning (1–2 weeks for most small sites)

The team learns about your business, customers, competitors and goals, then agrees the pages, features and content. For large public services, the UK Government's service manual describes a separate discovery phase in which teams understand users and the problem before building, and says 4 to 8 weeks is typical. A small business website needs far less, but skipping planning altogether is the most common cause of rework later.

2. Design (1–3 weeks)

Designs for the key pages, usually the homepage and one or two templates, are created and refined. The number of revision rounds, and how quickly you respond, drives this stage.

3. Content (runs alongside design)

Text, photos, logos, team details, prices and testimonials. This is the stage most likely to delay a launch. Websites are often ready weeks before the content is.

4. Development (2–8 weeks or more)

The site is built, content is added and features such as forms, booking, payments or integrations are connected. Custom functionality and integrations with other systems take the longest.

5. Testing (several days to two weeks)

Checking pages on different devices and browsers, forms, payments, speed, accessibility and SEO basics. Accessibility testing against the WCAG standard, which the W3C describes as explaining how to make web content more accessible to people with disabilities, is worth including from the start rather than bolting on.

6. Launch (a day, plus monitoring)

Pointing the domain at the new site, setting up redirects from old pages, connecting analytics and Search Console, and watching closely for the first week. If you're moving from an existing site, plan the switch so there's no downtime; Google's guidance on changing hosting recommends preparing and testing the new setup before changing DNS.

A sample timeline for a 10-page business website

Here is how a typical eight-week project for a small business site with custom design might run, assuming content and feedback arrive on time:

If content arrives in week six instead of week three, the launch usually moves by the same three weeks. That is why the content plan deserves as much attention as the design. If you're short of time to write, ask for copywriting to be included, or launch with fewer, better pages and add the rest after go-live.

What affects the cost as well as the time

Time and cost move together. The main drivers are the number of unique page designs, custom features and integrations, the amount of content to write or migrate, the number of products for a shop, and how many revision rounds are needed. A clear brief and fast decisions save both.

What makes a website project take longer

Most delays come from a handful of familiar causes:

• Content not ready. Waiting for text, photos or product data is the number one cause of late launches.
• Slow feedback. Every round of comments that takes a week adds a week.
• Too many decision-makers, or a key person unavailable at sign-off.
• Scope creep. New features added mid-project without adjusting the timeline.
• Integrations with booking systems, CRMs, stock or accounting software, especially older ones.
• Product data for shops: photographing, describing and pricing hundreds of products.
• Content migration from an old site, particularly when pages need rewriting or redirects mapping.

How to get your website built faster

• Write a clear brief before the project starts: goals, pages, features, examples you like and must-haves.
• Name one decision-maker who can approve designs and content.
• Prepare content early, or include copywriting in the project.
• Agree feedback deadlines, such as replies within three working days.
• Launch in phases. Go live with the core pages, then add the blog, extra features or more products.
• Use proven building blocks for standard features rather than custom-building everything.

Does faster mean worse?

Not necessarily. A small, well-planned site built quickly can be better than a large one that drags on for months. What suffers when timelines are squeezed too far is usually testing, accessibility, speed and SEO setup, which are hard to see at launch but cost you later.

Be wary of quotes that promise a complex site in a few days. Ask what is included, what is template-based and what testing happens before launch.

Questions to ask about timelines

1. What are the stages, and how long is each?
2. What do you need from us, and by when?
3. How many rounds of design revisions are included?
4. What happens to the timeline if we add a feature?
5. Who will be working on the project, and how often will we get updates?
6. What testing happens before launch?
7. What happens in the first few weeks after going live?

Frequently asked questions

If you'd like a clear plan and timeline for your new website, our web development team starts every project with a short discovery and a written schedule, and our UI/UX and brand design work keeps the design stage focused.