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

A small business website takes four to eight weeks from kick-off to launch. A mid-sized site with real functionality takes eight to sixteen. E-commerce with anything unusual in it takes twelve to twenty-four.

Those are honest numbers for a project that runs normally. The reason projects overrun is almost never that the build took longer than expected. It is that the content was not ready, or feedback took three weeks instead of three days.

Where the time actually goes

For a typical eight-week small business build, the split looks roughly like this:

Discovery and planning — 1 week. What pages exist, what each is for, what the site needs to do. Skipping this feels like saving a week; it reliably costs three later, because the design gets built on assumptions that turn out to be wrong.

Design — 2 weeks. Homepage first, then the key page templates. Usually two rounds of revisions.

Build — 2 to 3 weeks. Turning approved designs into working pages, responsive across every screen size, with forms, integrations and the CMS set up so your team can edit it.

Content — runs alongside, and is the usual bottleneck. Copy, photographs, and getting existing material in.

Testing and launch — 1 week. Cross-browser and device testing, speed, accessibility, forms tested end to end, redirects from old URLs, analytics and Search Console, then the actual switch.

The three things that actually cause delay

Content. By a wide margin. Almost every project we have run late ran late because copy or photographs were not ready. It is not laziness — writing about your own business is genuinely hard, and it usually falls to whoever is busiest.

The fix is to start content in week one, not week five. Even rough copy is enough to design around, and rough copy that exists beats polished copy that does not.

Slow feedback. A design round that sits for two weeks moves the launch date by two weeks, every time. If sign-off needs three people, get the three of them in the same meeting rather than collecting opinions in sequence.

Scope changes. "Could we also add a booking system" in week five is a new project bolted onto an existing one. Sometimes it is genuinely worth it. It is never free, and anyone who says otherwise is going to be unhappy later.

What you can do to make it faster

Have your content ready, or budget for someone to write it. If copywriting is in scope, add two to three weeks and be relieved rather than annoyed.

Name one decision-maker. Projects stall when feedback arrives from four people who contradict each other and nobody can say yes.

Give feedback in batches. One consolidated list beats eleven separate emails, for you as much as for the studio.

Say no to nice-to-haves until version two. Launch, then improve. A site that is live and imperfect earns money; a site that is perfect and unlaunched does not.

Get your access sorted early. Domain registrar login, hosting, analytics, whatever the old site runs on. Hunting for a password nobody has had since 2019 is a genuinely common source of launch-week panic.

What "fast" costs

You can build a small site in a week. Some studios advertise it, and it is not a lie — it is a template, populated, with content you supply on day one and no revision rounds. For a brand new business that needs something live before a trade show, that can be exactly the right trade.

What you are giving up is the discovery conversation, custom design, and any chance to change your mind. If you know precisely what you want and you want it now, that is a fair deal. If you are not sure, speed is the most expensive thing you can buy.

What happens after launch

Launch is not the end, and treating it as one is why so many sites decay.

Expect a week or two of small fixes — things nobody spots until real people use it. Expect three to six months before organic search results mean anything; a new site does not rank quickly regardless of how well it is built. Expect to keep publishing if search matters to you.

And budget for maintenance from day one. Updates, backups, security, the occasional broken thing. A site nobody maintains is noticeably worse within a year and a liability within three.

A realistic timeline to plan against

If you need a site live for a specific date, work backwards and add a third. Eight weeks of work planned into eight weeks of calendar will slip; eight weeks of work planned into eleven usually lands early, which is a much nicer conversation to have.

And start on the content now, whoever ends up building it.

---

We give a fixed timeline with the scope written down before anything starts, and we say clearly which parts depend on you. Tell us your deadline.