How long does it take to build a website?

How long does it take to build a website? For most small and medium businesses, a professionally built brochure website takes roughly 6 to 10 weeks from kick-off to launch. A larger CMS-driven site or an online shop usually takes 3 to 5 months, and a custom web application can take longer still.

The build itself is rarely what slows things down. Content, feedback and decisions are. Below is a realistic breakdown so you can plan around it.

The short answer

• Brochure website (5 to 15 pages): typically 6 to 10 weeks.
• CMS-driven marketing site (blog, case studies, resources, more templates): typically 8 to 16 weeks.
• E-commerce site: typically 8 to 12 weeks on a well-built Shopify theme, longer for a headless or custom shop.
• Web application or platform: typically 3 to 6 months for a first version, and often an ongoing project after that.

These are typical UK ranges for a small senior team working with a client who responds promptly. A template site you put together yourself can be live in days. A large organisation with many stakeholders can take a year.

How long does each type of website take?

Brochure websites

A brochure site explains who you are, what you do and how to get in touch. There are usually a handful of page templates (home, about, services, contact) and limited functionality. The design and build are fairly quick. The common bottleneck is getting final copy and photos together.

CMS-driven marketing websites

Once you want your team to publish blog posts, case studies, landing pages or resources without a developer, the site needs a proper content management system and more templates. That means more design work, content modelling and testing, and some time training your team to use the editor.

E-commerce websites

An online shop adds products, payments, shipping, tax, stock and order emails. On Shopify, much of that is handled by the platform, so a well-planned store can be ready in a couple of months. A headless or custom build takes longer because more of it is built from scratch. Our guide to Shopify vs custom e-commerce explains the trade-offs.

Web applications

Customer portals, booking systems, dashboards and SaaS products involve user accounts, data, integrations and business logic. They need more discovery, more testing and usually a phased release. It's normal to launch a smaller first version and keep building.

What happens in each phase?

Most website projects follow the same broad stages. The durations below are typical for a brochure or small CMS site.

1. Discovery and planning (1 to 2 weeks). Agreeing goals, audience, pages, features and what success looks like. A clear brief shortens this a lot.
2. Content planning and sitemap (1 to 2 weeks, often overlapping). Deciding what goes on each page and who is writing it.
3. Design (2 to 3 weeks). Usually key pages first, then the rest once the direction is agreed. Each round of feedback adds time.
4. Build (2 to 4 weeks). Turning designs into a working site, setting up the CMS, forms, analytics and integrations.
5. Content entry and testing (1 to 2 weeks). Loading real content, checking across devices and browsers, accessibility and performance checks.
6. Launch (a few days). Domain and DNS changes, redirects from old URLs, final checks.

Some of these overlap. A good team starts the build on approved templates while later designs are still in progress.

What causes website projects to be delayed?

Content, by a long way

The single most common cause of delay is content that isn't ready. Copy, photography, product data, team bios and case studies take far longer to produce than most people expect, and they usually fall to someone who already has a full-time job. A site can be built and waiting for weeks while the words are written.

Slow or scattered feedback

If design feedback takes a fortnight and comes from five people with different views, each round can cost weeks. Nominate one decision-maker who gathers comments from everyone else.

Changing scope mid-project

Adding new features or pages after the build has started is normal, but each change has a knock-on effect on design, build and testing time. Small additions are fine. A new section or integration resets part of the timeline.

Third parties

Waiting on login details for a domain registrar, an old hosting account, a CRM or a payment provider is a surprisingly common hold-up. Gather these early.

Migrations and SEO

Moving from an old site means mapping old URLs to new ones and moving existing content. Rushing this risks losing search rankings, so it's worth the time. Our post on redesigning a website without losing SEO covers what's involved.

How can I get my website built faster?

• Write a clear brief. Goals, audience, must-have features, examples you like and a budget range. Our guide on how to write a website brief walks through it.
• Start content on day one. Don't wait for designs. Draft copy in a shared document against the agreed sitemap.
• Appoint one decision-maker. Someone with the authority to approve designs and copy.
• Agree feedback windows. For example, two working days per round. Put them in the plan.
• Launch with the essentials. Get the core site live, then add the nice-to-haves in a second phase.
• Use proven tools. A good headless CMS or a well-chosen platform avoids building things that already exist.
• Sort access early. Domain, hosting, analytics and any third-party accounts, all in your business's name.

Does a faster website build cost more?

Sometimes. Compressing a timeline usually means more people working in parallel or a team prioritising your project over others, which can add cost. More often, though, a project goes faster simply because the client is organised. Ready content and quick decisions save time without costing anything extra. If you're also working out a budget, our guide to how much a website costs in the UK gives typical ranges.

A realistic way to plan

Take the typical range for your type of site, then add a buffer of a few weeks for content and feedback. If you have a fixed deadline, such as a product launch or a trade show, tell your developer at the start. A good team will work backwards from the date and tell you honestly what fits.

If you'd like a realistic timeline for your own project, get in touch with a short outline of what you need and when, and we'll tell you what's achievable.