How long should it take to build a small business website?

Two to six weeks is the honest range for a small business site, and the spread inside that range has almost nothing to do with how fast anyone writes code.

Projects that finish in two weeks and projects that drag past three months usually involve the same amount of build work. The difference is how quickly decisions get made and how ready the content was.

What actually takes the time?

A rough breakdown of where the weeks go on a typical five to ten page build:

Discovery and offer: a few days to two weeks. Deciding what the site says, who it is for, and what the primary action is. This is the step most likely to expand, because it is the step where a business has to commit to positioning it may never have written down.

Design and build: one to two weeks. The part everyone imagines is the whole project. On a focused site with a clear offer it is the most predictable phase.

Content: the wildcard. If copy and photography exist, days. If they need writing and shooting, this becomes the critical path and can double the timeline on its own.

Integrations and tracking: a few days. Booking tools, CRM connections, analytics, conversion tracking. Predictable unless something needs custom work.

Review and launch: a few days. Feedback, revisions, testing, going live.

Why do projects stall?

Nearly always for one of four reasons, and only one is technical.

Content that never arrives. The single most common cause. The site is built, the layout is waiting, and it needs the actual words about your actual services. Weeks pass. Nothing else can proceed because there is nothing to proceed with.

Feedback with no deadline. A round of revisions sent to someone running a business gets looked at when there is time, which is often not this week. Two rounds with a week of drift each adds two weeks nobody planned for.

Scope added mid-build. “Could we also add a booking system?” is a reasonable request and a different project. Every mid-build addition costs more than the same work would have cost if scoped at the start, because it means revisiting decisions already made around it.

Waiting on third parties. Domain access nobody can find, a hosting login belonging to a former employee, a Facebook page admin who left the company. These are invisible until they block everything, and they are worth checking in week one rather than week five.

How do I keep it moving?

Four things, in order of how much time each saves:

1. Have the content ready, or agree who is writing it, before kickoff. If the answer is “we’ll get to it,” the project will take twice as long. If copywriting is part of the engagement, say so at the start.

2. Put a date on every feedback round. Not “when you get a chance.” A specific date, agreed in advance, with the understanding that the timeline moves if it slips.

3. Gather logins in week one. Domain registrar, hosting, Google Business Profile, analytics, any tool that will be connected. Chasing a password nobody has cost more projects a week than any technical problem.

4. Freeze scope, and keep a list. New ideas during a build are normal and often good. Write them down and do them after launch. A site live in three weeks with six things on a follow-up list beats a perfect site still unlaunched in month four.

Is faster always better?

No, and there is one place where taking longer is correct.

Rushing the offer (who this is for, what they get, what happens next) produces a site that is fast to build and does not work. That decision is worth an extra week, because everything else is downstream of it. A beautifully built page pointed at a vague offer converts badly, and no amount of design fixes it.

Everything else benefits from speed. A site live and imperfect starts producing information no amount of pre-launch deliberation can generate: what people click, where they leave, what they ask on calls. You cannot learn from a site that has not launched.

What about bigger builds?

Beyond ten pages, or with e-commerce, memberships, or custom integrations, the range moves out to two or three months and the shape of the risk changes. The timeline stops being driven by content and starts being driven by integration complexity and testing.

For those, the number worth asking for is not the total but the milestone dates: when discovery ends, when design is approved, when content is due, when testing starts. A single “about three months” with no checkpoints is how a three-month project becomes a six-month one without anyone noticing until month four.

The two-to-six-week range holds for the focused builds most service businesses need. That is what a full lead generation build is scoped around, so the site goes live while the offer is still current.