The key points
- Discovery, design, development and launch are separate stages with their own time.
- Content that is ready on day one saves more time than any build shortcut.
- Every extra review round and integration adds days, not hours.
- A single landing page is quicker; its timeline is agreed in the proposal, not assumed.
What happens in each stage of a website build?
Discovery is the first week or so: what the business sells, who it sells to, what a visitor must believe before they get in touch, and which pages and integrations that implies. Skipping it does not save time; it moves the questions into the middle of the build, where each one is more expensive.
Design takes one to two weeks and produces the structure and the look on desktop and mobile, reviewed with you before development starts. Development is the longest stage at two to three weeks, covering the build, the forms, the integrations and the search setup. Launch takes about three days for testing, fixing and pointing the domain at the finished site.
What makes a website take longer than planned?
Content is the most common cause, which is why what you prepare before hiring a web developer matters so much. A site cannot be finished while the service descriptions, photographs and contact details are still being written, and a build that waits on content simply sits idle. The second cause is review rounds: each round that changes direction rather than refining detail restarts part of the design.
Integrations are the third. A booking calendar, a payment provider or a CRM connection each depend on accounts and access that someone has to set up, and third-party approvals are outside any developer's control. We identify these during scoping so they appear in the plan, not as surprises in week four.
- Copy and photography not ready when design starts
- Several people reviewing separately and contradicting each other
- Integrations that need accounts, approvals or access from a third party
- Scope added after sign-off without moving the date
How can you shorten the timeline without cutting quality?
Name one person who can approve work, and agree the review rounds in advance. Supply the facts about your business early, even as rough notes; shaping rough material into page copy is far quicker than starting from nothing. Decide the integrations up front and open the accounts they need in the first week.
If speed matters more than breadth, launch with the pages that earn enquiries (sometimes just a focused landing page) and add the rest afterwards. A smaller site that goes live and starts collecting enquiries is usually worth more than a complete one that arrives a month later.
The four stages of a business website build
Discovery
Agree the audience, the pages, the integrations and what a visitor must believe before contacting you. About one week.
Design
Produce the page structure and the look on desktop and mobile, reviewed with you before any code. One to two weeks.
Development
Build the site, forms and integrations, with search setup and performance checks. Two to three weeks.
Launch
Work through a launch checklist on real devices, fix what turns up and point the domain at the finished site. About three days.
Before you ask for a timeline
- Who is the one person who can approve each stage?
- Is the copy for the main pages written, even roughly?
- Do you have photographs you are allowed to use?
- Which integrations are essential for launch rather than nice to have?
- Do you control your domain registration and hosting accounts?
Sources
Rules and guidance this answer relies on. Policies change, so check the current version before acting on it.