How long a website actually takes to build.

A typical small business website takes 1.5 to 3.5 weeks from brief to launch. That is our real number, not a sales number, and the reason it surprises people is that almost nobody is delayed by the building. Projects are delayed by photos that never arrive and by feedback that sits in somebody's inbox.

So the useful version of the question is not how long the work takes. It is how long your project will take, and that depends more on you than on your supplier. Here is the whole timeline, what each phase is waiting on, and the handful of things that turn three weeks into five months.

The phases, with real durations

Add those up sequentially and you get five or six weeks. In practice copy and design overlap, your review runs alongside the build for pages already finished, and the pre-launch checks start before the last page is done. That compression is where 1.5 to 3.5 weeks comes from.

Two things change the shape of that table. A migration off an existing site adds the redirect mapping work, which is a real phase and is covered in moving off Wix, Squarespace or Framer. An ecommerce build expands the copy and build phases considerably, because product data, tax rules, shipping rules and checkout testing are each their own job. We quote that timeline with the fixed price rather than guessing at it here, because product count and integrations change it more than anything else does.

What actually causes delay

Ranked by how often it is the real cause, based on the projects we have run.

1. Photography. The single biggest cause, by a distance. The site is finished, the layout has nine slots for images of your own work, and nobody has taken them. Stock photography is the fallback and it immediately makes the site look like every competitor, so good suppliers resist it and you end up waiting. Booking a photographer takes a week of lead time. Not booking one takes months.

2. Content only you have. Service details, team names and roles, certifications, warranty terms, pricing you are willing to publish, the list of towns you actually serve. We draft the copy, but we cannot invent the facts, and every gap becomes an open question blocking a page.

3. Approval bottlenecks. A staging link sent on a Tuesday and opened the following Thursday costs nine days across two rounds. Nothing in the project moves while it sits there, and the gap is invisible on a timeline until the end.

4. Too many people reviewing. Three stakeholders with equal authority and no tiebreaker produce contradictory feedback, which produces a meeting, which produces a delay. This is the most expensive of all the causes because it also degrades the result.

5. Scope added mid-build. A booking system in week two, a members area in week three. Each addition is reasonable on its own and each one reopens decisions that were already closed.

6. Third parties. A payment gateway application, an inventory feed, a franchise brand approval, an insurer's compliance review. You do not control these and they do not care about your launch date.

7. Decisions that should have been made first. A new logo chosen during the design phase. A domain change raised in week three. A debate about the business name. These are not website problems and they stop a website cold.

Notice that six of the seven sit on the client side of the line. That is not an accusation. It is the single most useful thing to know before you start, because every one of them is preventable with a week of preparation.

The pattern that turns three weeks into five months

The shape is almost always identical.

Week one goes perfectly. The brief is answered, the page map is approved, everybody is enthusiastic. The copy draft goes over in week two with eleven questions attached, four of which need a decision from the owner.

Then a busy fortnight arrives. The questions go unanswered because they are not urgent and the business is. The supplier follows up twice and then goes quiet because there is nothing to do. Momentum, which is a real asset and is never on anybody's project plan, is gone.

Six weeks later the owner comes back, re-reads the copy with no memory of the earlier discussion, and asks for a different direction. Design restarts. By the time the site launches, the photos are of last season's work, somebody has left the team, and the original quote has been revisited twice.

Nobody behaved badly. The project simply lost its cadence, and cadence is the thing that keeps a build short.

What you can do to make it faster

Eight things, in order of how much time each one saves.

1. Name one decision-maker. One person with authority to approve copy and design. Others can advise. Only one signs off.
2. Book the photography before the project starts. See above. It is the difference between a three week build and a three month one.
3. Gather the facts in advance. A single document with your services, what each involves, the towns you serve, your certifications, your team, your hours and any pricing you will publish. Half a day of your time removes most of the open questions before they exist.
4. Hand over the logins on day one. Domain registrar, hosting, analytics, Google Business Profile. Access discovered in launch week is the most avoidable delay there is, and if you are not sure who holds what, check who actually owns your website first.
5. Put the review slots in your calendar at kickoff. Two hours, twice, on agreed dates. Treat them like a site visit you cannot miss.
6. Give feedback once, in one document, per round. Not six emails over nine days. One list, numbered, covering everything.
7. Describe the problem, not the fix. "This page does not make it obvious how to book" is useful. "Move the button and make it blue" is a fix for a problem you have not stated, and it usually does not work.
8. Park new ideas in a phase two list. Keep the list, genuinely build from it later. Just not during this build.

Do those eight and a site that would have taken four months takes three weeks. We have seen the same scope run both ways, and the difference was never the code.

When fast is the wrong goal

Speed is a means, not the point. Three situations where pushing the timeline costs you more than it saves.

You do not know what the site is for yet. If nobody can say in one sentence what the site should get people to do, the week spent working that out is the most valuable week in the project. Launching without it just means rebuilding sooner.

The copy has not been thought about. Pages written at speed to hit a date read exactly like that, and the copy is what actually sells. Thin copy is the most common regret we hear on a rushed build.

You are launching into a season you cannot support. A roofer who launches a site that works, in the first week of a heatwave, with no capacity to answer the phone, has created a problem rather than a result. Pick the date to suit the business, not the calendar.

There is also a floor. Below about ten working days, quality starts going backwards, because the review and testing phases are the first things compressed and they are the phases that catch what is broken. If somebody promises you a custom site in four days, ask what is being skipped. The question list in how to pick a web designer covers how to ask that without it becoming awkward.

A realistic calendar

For a typical eight to twenty page local business site, with a prepared client.

• Week one: brief, fixed quote, page map approved, photography booked, logins handed over.
• Week two: copy drafted and revised, key templates designed and approved.
• Week three: build, your review, pre-launch checks, launch.

Stretch that to three and a half weeks if photography slips a few days or the page count is at the top of the range. Stretch it to five or six if there is a migration with a few hundred URLs to map.

And know which phase you are the dependency in, because in most projects it is two of them, and knowing that in advance is worth more than any schedule.

---

Our quotes break the work into exactly these phases, each invoiced as it ships, so you can see what is complete before funding the next one. If you want a timeline for your own project rather than a range from a guide, send us the brief and you will get dates alongside the number.