Skip to content
Every website comes with a free custom logo — on us.
← All posts
Web Design· 3 min read

How long does it take to build a website?

Most answers to this question are some version of “one to six months, it depends.” That range is so wide it tells you nothing. The honest answer is that build time is mostly not about the building — it is about how fast decisions and content arrive, and that is the part a timeline estimate usually hides.

The short answer

A straightforward small-business site — home, services, about, contact, a few supporting pages — is days of actual design and development work. On our plans you see a live, clickable preview in about five business days once we have your content, and most sites go live within roughly two weeks. Larger builds with e-commerce, booking systems, or custom functionality take longer because there is genuinely more to build and more to test.

When a project takes three months, the extra time is almost never production. It is waiting.

Where the time actually goes

Across the builds we run, delay clusters in four places, and only one of them is us:

  • Content. Photos, service descriptions, staff bios, prices. This is the single biggest cause of a two-week build becoming a two-month one. We write copy and source stock imagery to remove most of it, but only you can confirm what you sell and for how much.
  • Approvals. One decision-maker reviewing a draft keeps a build to two weeks. A committee with competing opinions does not, and no process fixes that from the outside.
  • Scope changes mid-build. Adding a booking system in week two restarts parts of the design. Perfectly reasonable, but it resets the clock.
  • Third parties. A domain held by a former developer, a payment provider's verification queue, a franchise brand approval. These are out of everyone's hands and worth starting early.

A realistic two-week timeline

This is the shape of a normal build when content is ready and one person approves:

  • Days 1–2: intake. What you sell, who buys it, what a win looks like, and what should happen when someone lands on the site.
  • Days 3–5: design and build of the real pages — not a mockup you have to imagine, a working draft you click through.
  • Day 5: you see the live preview. This is the point most people expect to be weeks away.
  • Days 6–10: revisions. Copy, layout, images, structure. Usually two rounds.
  • Days 11–12: technical setup — forms, analytics, hosting, SSL, redirects if an old site is being replaced.
  • Days 13–14: pre-launch checks and go live.

Why other quotes say two to three months

Three structural reasons, none of them dishonest:

  • Agency scheduling. Project shops run several clients in parallel, so your build occupies a slot in a queue rather than a continuous stretch of work.
  • Discovery phases. Larger engagements front-load research, workshops, wireframes and sign-off gates before anything is designed. That has real value on a complex project and adds weeks to a simple one.
  • Custom everything. A site designed from a blank page with bespoke illustration and custom functionality takes longer than one built on a system that has shipped before.

If you are comparing quotes, the useful question is not how many weeks but what is happening during them, and what you need to supply to keep it moving.

What makes a build genuinely take longer

Some projects should take longer, and a provider promising two weeks for these is not being straight with you:

  • A fully customised online store with many products, variants, shipping rules and tax configuration.
  • Booking, membership, or portal functionality that has to be built and tested rather than configured.
  • Migrating a large existing site where hundreds of URLs need mapping and redirecting carefully.
  • Multi-language sites, which multiply both the content and the review cycles.
  • Regulated industries where legal or compliance review sits between draft and launch.

How to make your build fast

If speed matters to you, these four things decide it more than your provider's capacity does:

  • Gather photos and your service list before the project starts, not during it.
  • Name one person who can approve drafts.
  • Decide what the site must do — calls, bookings, sales — before design begins, because that drives the layout.
  • Sort out domain access early. Chasing a login from a developer you parted with three years ago is a classic week lost.

Our own timeline and what each plan includes are on the pricing page, and the website design service page covers what we need from you to hit it.

Ready to launch your new site?

Tell us about your business. We'll send back a plan and a price — no pressure, no jargon.