Coweb·Hub
← All postsWeb & App Development

How long does it take to build a website?

Coweb Hub · 17 November 2026 · 3 min read

A small business website takes days of work. Most quotes say six weeks. Both of those are true at once, and the gap between them is worth understanding before you pay anybody.

The six weeks is mostly waiting

Building a straightforward marketing site is not six weeks of labor. It is somewhere between a few days and two weeks of actual work.

The six weeks is queue position. Your project sits behind other projects, gets touched, goes back in the queue. That is not dishonest; it is how a busy studio schedules. But it means the timeline you are quoted describes their calendar, not your site.

It is worth asking directly: how many days of work is this, and when do those days happen? A supplier who can answer that is telling you something real.

What genuinely takes time

Deciding what to say. This is the slow part and it is almost always underestimated. Four pages that answer the right questions take longer to get right than twelve pages of filler, because the deciding is the work.

Getting content from you. Photographs, service descriptions, prices, the details only you know. On most late projects, this is the actual cause.

Anything involving payments, bookings or a connection to a system you already use. These are not hard but they are fiddly, and they have to be tested properly rather than assumed.

Approvals, if more than one person has to agree.

What makes it slow down

More decision makers. A site with one person deciding moves in days. The same site with a committee takes months, because every question has to go round the table and come back.

Unclear positioning. If the business has not decided who it is for, the website cannot decide either, and you will go round in circles on wording that is really a strategy problem.

Revisions with no brief. Make it pop is not feedback anybody can act on; it is usually a symptom that the message is unclear rather than the design.

Waiting on photography. Start this on day one, not when the build is otherwise done.

How to make it fast

Pick one decision maker. Give them the authority to approve.

Write the answers to your five most common customer questions before the build starts, in your own words. That single document removes most of the back and forth.

Gather your photographs early, even imperfect ones taken on a phone. Real and rough beats polished and borrowed anyway.

Agree what launch means at the start. Not everything has to be finished to go live, and a site that is live and improving beats one that is perfect and three months late.

Launch day is not the end

This is the part that catches people out. A build has an end date; a website does not.

Launch day is the first day it starts working, not the last day anybody touches it. Sites that quietly rot do so because nobody owned them after the invoice was paid.

Decide who looks at it each month before you start. An hour is usually enough. But it has to belong to a person, or it belongs to nobody.

Keep reading

Comments

Comments from guests are checked before they appear. Logged-in comments post straight away.

One hub

8 services, one team

24-hour quote

On every inquiry

AI-native delivery

Built in, not bolted on

No lock-in

Project or retainer, your call