The honest answer to how long a website takes is: it depends almost entirely on how quickly the client can provide content and make decisions. The technical build is rarely the bottleneck. This guide gives realistic timelines for different types of website projects and explains what typically causes delays.
Typical timelines by project type
A simple five-page business website with standard pages — home, about, services, case studies, contact — can be built in one to two weeks once content is ready. A ten to twenty page site with custom functionality typically takes two to four weeks. A full web application or platform with complex features, user accounts, and integrations typically takes six to twelve weeks. These are build timelines only — they assume content is ready and decisions are made promptly.
Why websites usually take longer than expected
The single most common cause of website delays is content. The developer is ready to build but the client is still writing copy, gathering images, or deciding what to say on the services page. A website project where the client provides all content before the build starts takes half the time of one where content is delivered piecemeal. If you are planning a website build, start gathering and writing content before the developer starts work.
The decision bottleneck
Every website project has decision points: design approval, content sign-off, functionality scope, revision requests. Projects where one person can make decisions move significantly faster than those involving committees, multiple stakeholders, or approval processes. If your website project requires sign-off from several people, account for that in your timeline — and ideally, agree upfront on what the approval process looks like and who has final say.
What a realistic timeline looks like
Week one: briefing, content gathering, design direction agreed. Week two: design mockups for key pages, feedback. Week three: design revisions, build begins. Week four to five: build complete, content loaded, internal review. Week six: revisions, testing, launch. This is a realistic timeline for a standard business website with a responsive client. Add two to four weeks for any project involving committee decision-making or late content delivery.
How to keep your project on track
Provide all content before the build starts. Nominate one person to be the point of contact and decision maker. Agree upfront on how many rounds of revisions are included. Review work promptly — a developer waiting two weeks for feedback on a design loses momentum and context. Ask your developer at the start of the project what they need from you and when, then commit to delivering it on time. The projects that launch on schedule almost always have a responsive, organised client.
Want to talk through your specific situation?
Book a free 30-minute call. Tell us what you need and we will tell you the best approach and what it would cost.
Book a free scoping call →