How long does it take to build a website?
Two to three weeks for a straightforward small-business site, four to eight for a custom build, longer where payments or integrations are involved. Most of that elapsed time is not construction — it is waiting for content and decisions. Projects that arrive with copy and images ready routinely finish in half the time.
Where the time actually goes
Clients reasonably assume the long part is building. On a small site it is not. Construction of a template or small custom build is typically days of actual work. The calendar fills with everything around it.
| Stage | Working time | Usual elapsed time |
|---|---|---|
| Scope and structure agreed | Hours | Days — needs one decision-maker available |
| Design direction approved | Days | Days to weeks, depending on how many people review |
| Content supplied | Yours | Days to months — the usual bottleneck |
| Build and content loaded | Days | Days |
| Review, revisions, testing | Days | Days to weeks, depending on review rounds |
| Launch and DNS propagation | Hours | Up to 48 hours |
Read the right-hand column and the pattern is obvious: almost every risk to the timeline is a decision or a piece of content, not a technical task.
The content problem, stated honestly
Writing about your own business is harder than it sounds and never urgent. A build can sit for weeks at ninety per cent complete because nobody has written four service descriptions. This is so common that any builder who does not warn you about it has not done many projects.
Two things genuinely help. Write the content before the build starts, not during — even badly, since editing existing text is far easier than producing it. And use an AI tool for the first draft of each page from a few bullet points, then edit heavily for accuracy and voice. That converts a blank-page task into a review task, which is the difference between a fortnight and an afternoon.
What makes a project genuinely slower
- More than two approvers. Each additional reviewer adds a round, and rounds are measured in days of waiting, not hours of work.
- Anything that takes money. Payment integration adds testing, failure handling and a provider approval process outside your control.
- Migrating an existing site. Preserving URLs so you do not lose existing search visibility is careful work, and it is cheaper than recovering rankings afterwards.
- Photography. Waiting on a shoot is a scheduling dependency with weather and availability attached.
How to halve the elapsed time
Before you engage anyone: decide your page list, nominate one person who can approve without consulting others, write or draft the copy for every page, gather logo files and images, and confirm you can access your domain registrar account. A project arriving with those five things done is limited by build speed rather than coordination, which is the only state in which a two-week estimate is real.
This question comes up most often in our Web Development engagements.