How Long Does It Take to Build a Website? Honest Timelines by Project Type
“How long will it take?” is the second question every client asks (right after the price), and it deserves an honest answer rather than a sales answer. Here are realistic timelines by project type — and, more usefully, the things that actually cause websites to run late.
Typical timelines by project type
| Project type | Realistic timeline | What the time goes into |
|---|---|---|
| Starter / one-pager | 3 – 10 days | Setup, adapting a proven layout, your content, go-live |
| Small business site (5–15 pages) | 2 – 6 weeks | Design, content rounds, build, review cycles, SEO setup |
| E-commerce | 4 – 12 weeks | Catalogue setup, payments, shipping rules, testing real orders |
| Custom web application | 2 – 6+ months | Scoping, architecture, iterative development, testing |
If a quote promises a full custom e-commerce build in a week, something in that sentence is not true — usually the word “custom.”
What actually causes delays
In our experience the schedule is rarely blown by the technical work. The usual suspects:
- Content.The number one cause, by a distance. The site is built and waiting, but the About page copy, the product photos, or the team bios haven't arrived. If you take one thing from this article: start gathering content on day one, not after design sign-off.
- Feedback loops. Every review round where feedback takes two weeks adds two weeks. A single empowered decision-maker on your side is worth more to the schedule than any project management tool.
- Scope drift.“While you're in there, can we also add a booking system?” New ideas are healthy — but they belong in a phase two, not silently absorbed into the original deadline.
- Third-party dependencies. Payment gateway approvals, access to your existing domain or hosting accounts, courier API credentials — external parties move on their own schedules. Kick these off early.
A realistic week-by-week shape
For a typical small business site, the healthy rhythm looks like this:
- Week 1 — Discovery.Goals, audience, sitemap, and what “done” means. You start collecting content now.
- Weeks 2–3 — Design. Layout and visual direction, one or two focused revision rounds.
- Weeks 3–5 — Build. The approved design becomes a real, fast, responsive website with your content flowing in as it is approved.
- Week 6 — Launch. Final review, SEO checks, analytics, DNS switch-over, and monitoring after go-live.
This mirrors our own four-phase process — discovery, design, build, launch — and the overlap is deliberate: content and build run in parallel instead of in sequence, which is where most of the calendar time is saved.
How to keep your project on schedule
- Appoint one decision-maker with authority to approve things.
- Deliver content in the first week — even rough drafts unblock design decisions.
- Batch your feedback into consolidated rounds rather than a drip of small changes.
- Park new ideas in a phase-two list. Ship, then iterate.
- Sort access early: domain registrar logins, existing hosting, Google Business Profile. Chasing credentials is dead calendar time.
The bottom line
A simple site should take days to weeks; a serious business site, about a month and a half; custom software, months. Anyone quoting dramatically shorter is compressing quality or redefining the deliverable. If you want a timeline for your specific project, tell us what you're buildingand we'll map it week by week — or browse our packages to see what ships fastest.
Need a hand with this?
We build, host and maintain websites for South African businesses — transparent month-to-month pricing, no lock-ins.