Realistic timelines by project type, the phases that actually take the time, and the one thing that delays more website projects than anything else.
The honest answer is that development is rarely the bottleneck. Content is. A team that can supply final copy and images in week two ships months earlier than one that cannot, on identical scope.
Realistic ranges
| Project | Typical | Main variable |
|---|---|---|
| Template build, your content | 2–4 weeks | Content readiness |
| Bespoke marketing site | 8–16 weeks | Approval rounds, integrations |
| Site with CMS and multiple templates | 12–20 weeks | Content modelling and migration |
| Web product with accounts and data | Continuous | Ships in increments, never "finished" |
Where the time actually goes
- Discovery (1–2 weeks). Interviews, an audit, a written problem statement. Skipping it does not save time; it moves the cost to later.
- Design (2–5 weeks). The variable is approval rounds, not design work. Two rounds is normal. Five means the brief was wrong.
- Build (3–8 weeks). Reasonably predictable — this is the part agencies estimate best.
- Content (parallel, or the whole delay). Writing, editing, photography, legal review. Almost always the critical path.
- QA and launch (1–2 weeks). Cross-browser, accessibility, redirects, analytics. Do not compress this one.
The single biggest accelerator: name one person on your side who can approve without a committee. Projects with one decision-maker routinely finish weeks ahead of identical projects with four.
What actually causes overruns
- Content that never arrives. Agree deadlines per page with named owners, in the plan, at the start.
- Approval by committee. Every extra stakeholder adds a round trip.
- Scope added mid-build. Fine, if it comes with a cost and a date change agreed in writing.
- Third-party dependencies. Waiting on another vendor's API is out of everyone's control — start those conversations in week one.
- Legal and compliance review discovered late. Ask on day one whether it applies.
How to compress it honestly
- Launch fewer pages. Ten excellent pages beat forty half-finished ones, and the rest can follow.
- Use real content in design reviews. Lorem ipsum hides problems that surface later.
- Book the photography before design starts — it is almost always the longest lead item.
- Agree what "done" means for each phase, in writing, before that phase starts.
If you are still scoping, what a business website should cost covers the money side of the same decisions.
Frequently asked questions
Can a website be built in a week?
A template build with content ready, yes. Anything bespoke cannot be compressed that far without skipping discovery and QA, which is where the cost reappears later.
Why do agencies quote such different timelines?
Usually because they are quoting different scopes, or because one has assumed you will supply content and the other has priced writing it. Ask each what they assume you will provide, and by when.
Should I launch in phases?
Usually yes. A smaller launch that is genuinely finished beats a big launch that slips twice, and real traffic on real pages tells you what to build next.
