"How long will it take?" is the second question every client asks, right after the price. The honest answer is that the build itself is rarely what takes longest. Decisions, content and feedback rounds usually set the pace. This guide shows realistic timelines for common projects and what you can do to keep yours on track.
The ranges below are typical for a small studio working with a responsive client. Your project can be faster or slower depending on scope and how quickly content and feedback arrive.
Typical timelines by project type
| Project | Typical duration | What drives it |
|---|---|---|
| Single landing page | 1 to 3 weeks | Copy and offer details |
| Small business website (5 to 10 pages) | 4 to 8 weeks | Content, design approval |
| Corporate website (15+ pages) | 8 to 14 weeks | Stakeholder reviews, content volume |
| Online store | 8 to 16 weeks | Product data, payments, delivery rules |
| Custom web application or portal | 3 months or more | Requirements, integrations, testing |
A redesign is not automatically faster than a new site. Moving content, redirecting old URLs and protecting search traffic adds work, as our redesign SEO checklist shows.
The stages of a website project
Most projects follow the same stages, even when they overlap.
- Discovery (about 1 week): agreeing goals, audiences, pages and features. A good website brief shortens this stage.
- Content and structure (1 to 3 weeks): the sitemap, page outlines and the actual words. This is where most delays start.
- Design (1 to 3 weeks): key page designs, then revisions. Two review rounds are common.
- Build (2 to 6 weeks): templates, the content system, forms, integrations and mobile layouts.
- Testing and launch (about 1 week): checks on phones and browsers, form tests, speed, redirects and search setup.
- After launch (ongoing): fixes, monitoring and the first improvements based on real visitors.
Why projects run late
In our experience the same four things cause most delays:
- Content is not ready. Designs can be approved in a week, but writing ten service pages from scratch takes much longer. Start writing in the discovery stage, or include copywriting in the scope.
- Feedback arrives slowly or from too many people. Each review round that takes two weeks instead of three days adds a week and a half.
- Scope grows mid-project. A "small" booking feature can add weeks of building and testing. Put new ideas on a list for phase two.
- Third parties are slow. Payment gateway approvals, domain transfers and access to an old developer's hosting can take days or weeks. Start these early. Our payment gateway guide explains what approval involves.
How to launch on time
- Name one decision maker who collects internal feedback.
- Agree the review schedule at the start: when designs arrive, and how many working days you have to respond.
- Prepare content in a shared document while the design is underway.
- Confirm who controls the domain, hosting and Google accounts in the first week.
- Separate must-have features from nice-to-haves, and launch with the must-haves.
Can it be done faster?
Yes, with trade-offs. Using an existing template, launching with fewer pages or supplying finished content can cut weeks from a project. What should not be cut is testing. A site that launches a week earlier with a broken enquiry form costs more than it saves.
If you have a fixed date, such as a launch event or campaign, tell the studio at the first meeting. A reliable studio will propose a scope that fits the date rather than promising everything.
What happens after launch
Launch is the start of the website's working life. Plan for a few weeks of small fixes as real visitors use it, and for a maintenance routine after that. Search results also take time to settle; read how long SEO takes for what to expect.
Want a timeline for your project? Tell us what you need and we will send a realistic schedule with the stages and the decisions we will need from you. Our packages page lists what each type of project includes.
