How Long Should a Small Business Website Take to Build?

There are two honest answers to how long a website should take. The first is 'as long as you and the designer agree upfront'. The second is 'longer, if either of you goes quiet'. Here are the realistic timelines for small business websites in 2026, and — more usefully — what actually causes them to slip.

The realistic timelines

5–7 working days: a 5-page template-based site

This is a properly-built starter site with your content, your logo, mobile responsive, contact form, and basic SEO. It's fast because the designer has done this shape of project many times and has a repeatable process.

What that timeline assumes: you send all your content and photos on day one, respond to feedback the same day, and don't ask for a redesign midway.

10–15 working days: a conversion-focused business site

8 pages, custom-ish design, conversion planning, analytics setup, service-plus-location structure. The extra week is genuine work, not padding.

Assumes: you have content or clear input on it, you can be reached during the project, and you have one decision-maker.

4–6 weeks: a category-competitive site

12 pages, professional copywriting, custom design system, schema, blog. Most of the extra time is copywriting — writing good sales copy takes days, not hours.

8–16 weeks: a full agency build

Strategy phase, multiple stakeholders, complex integrations, custom development. Below 8 weeks at this scale usually means something's being cut.

The five things that actually cause delays

1. Content that isn't ready

This is by far the biggest cause of a website taking three months instead of three weeks. The designer builds a placeholder page, waits for your real text, sends a reminder, waits, sends another reminder, and eventually gives up and moves to another client. Two months later you finally send the content and now they need to schedule you back in.

2. Too many decision-makers

If your website needs sign-off from you, your business partner, your accountant and your cousin who 'knows about websites', it will take three times as long as one where you decide alone. Not because the feedback is bad, but because coordinating four opinions is a project in itself.

3. Mid-project scope changes

'Actually, can we add an online shop?' halfway through a brochure-site build isn't just extra work — it means redesigning pages that were already built. Every scope change costs more time than the actual change.

4. Vague feedback

'I don't like it, can you try something different?' is one of the most expensive sentences in web design. Specific feedback — 'the hero heading is too long, and the yellow feels off-brand' — moves projects forward. Vague feedback stalls them for days.

5. The designer taking on too much

The other honest half. A designer with eight active projects has to context-switch constantly, and your project sits in a queue. Ask upfront how many projects they run in parallel.

What a well-run project looks like

In our experience the projects that finish on time share four things:

• The client sends content in the first week, even if it's rough
• One person is the decision-maker
• Feedback comes back within two working days
• The scope is fixed at kickoff and any changes are treated as change requests, not free additions

The one-question test

Before you engage a designer, ask them: 'if I send you content on day one and reply to feedback within a day, what will slow this project down on your side?' If they can answer specifically, they've thought about it. If they say 'nothing', they haven't run enough projects.