“How long will my new website take?” is the first question almost every client asks, and the honest answer is: most professional website design projects take 8 to 12 weeks from kickoff to launch. Not 3 days. Not 6 months. Somewhere in that window, assuming the project stays on track.
The problem is that “8 to 12 weeks” tells you nothing about what actually happens inside those weeks, when you will be asked to review something, or why some projects quietly slide into month five. So instead of another vague phase list, here is a genuine website design project timeline broken down week by week, including what we do, what we need from you, and where projects usually stall.
Quick Answer: The Website Design Project Timeline at a Glance
| Phase | Typical Duration | Main Deliverable | Client Time Needed |
|---|---|---|---|
| Discovery & strategy | Week 1 | Brief, goals, sitemap draft | 2 to 4 hours |
| Information architecture & wireframes | Weeks 2 to 3 | Sitemap, page layouts | 2 to 3 hours |
| Visual design | Weeks 3 to 6 | Homepage then inner pages | 3 to 5 hours |
| Development | Weeks 6 to 9 | Working staging site | 1 to 2 hours |
| Content population | Weeks 8 to 10 | Real copy and images in place | Varies, often the biggest ask |
| Testing & QA | Weeks 10 to 11 | Bug list cleared, UAT sign-off | 3 to 4 hours |
| Launch & handover | Week 12 | Live site, training, docs | 1 to 2 hours |
Important: these phases overlap. Development often begins before the last inner page design is approved, and content work runs in parallel from week 2 onward. A timeline is not a relay race.
Week 0: The Week Most Timelines Forget
Before week 1 even begins, a few things have to be in place. We call it week 0 because it is real time on the calendar but rarely appears on a project plan:
- Proposal accepted and contract signed
- Deposit invoice paid
- Kickoff call booked with every decision maker confirmed as attending
- Access gathered: current hosting, domain registrar, CMS logins, analytics, brand assets
If your legal team needs two weeks to review the contract, your 10-week project is now a 12-week project. Factor it in.
Weeks 1 to 2: Discovery, Strategy and Structure
Week 1: Discovery
The kickoff call is usually 60 to 90 minutes. We are trying to understand things that no brief ever captures properly:
- What does a successful website look like in numbers, not adjectives (leads per month, demo bookings, reduced support emails)?
- Who actually buys from you, and what stops them?
- Which pages on the current site earn their place, and which are dead weight?
- Who signs off, and who has a veto?
Alongside the call we review analytics, audit the existing site, look at 3 to 5 competitors, and check keyword data so the structure is built for search from day one.
What we need from you in week 1: analytics access, a list of stakeholders, brand guidelines, and three sites you admire with a sentence explaining why for each.
Week 2: Sitemap and Content Plan
We deliver a sitemap showing every page, how they nest, and what each one is supposed to do. This is the single most under-rated document in any website design project timeline, because changing a sitemap in week 2 costs an hour. Changing it in week 9 costs a week. This is handled with some care by one outfit doing this properly.
We also issue the content plan: which pages need new copy, who is writing it, and the deadline. Content deadlines sit in week 5 or 6, not week 11.
Your job: approve the sitemap within 3 working days and confirm who owns copywriting.
Weeks 3 to 6: Wireframes and Visual Design
Week 3: Wireframes
Wireframes are grey-box layouts for key templates: homepage, service or product page, blog article, contact, and any unusual template. No colour, no photography, no fonts. That is intentional. We want feedback on hierarchy and messaging order before anyone argues about a shade of blue.
Expect one round of revisions here. Two is normal on larger sites.
Week 4: Homepage Design Concept
The first full visual design lands. This is the emotional high point and the biggest risk point of the whole project. We present it live rather than emailing a PDF, because unexplained design gets picked apart by whoever has the strongest opinion in the room.
Good feedback sounds like: “the offer is not clear enough above the fold.” Unhelpful feedback sounds like: “my wife does not like it.”
How to give feedback that does not cost you a week
- Collect all internal opinions before sending anything to us
- Send one consolidated list, not six separate emails
- Reference the business goal, not personal taste
- Mark each item as must-change, nice-to-have, or question
Weeks 5 to 6: Inner Pages and Design Sign-Off
Once the homepage direction is approved, the visual language rolls out across remaining templates, plus mobile layouts, form states, button states, empty states and error messages. At the end of week 6 we ask for a written design sign-off. The team at codevix.com reached a similar conclusion.
Sign-off matters. After this point, design changes are change requests with cost and time attached, because code is being written against approved layouts.
Weeks 6 to 9: Development
This is the quietest stretch for you and the busiest for us. Typical work includes:
- Building templates on a staging server
- Setting up the CMS so your team can edit without breaking layouts
- Responsive behaviour across mobile, tablet and desktop breakpoints
- Forms, integrations, CRM or email platform connections
- Performance work: image handling, caching, script loading
- Accessibility basics: contrast, focus states, alt text structure, keyboard navigation
- SEO foundations: metadata fields, schema, clean URL structure, 301 redirect map
Around week 8 we usually share a staging link so you can see progress. Expect it to look unfinished, because it is. Reviewing a half-built site as if it were finished creates panic that helps nobody.
What we need from you during development: final copy, images, logos, team photos, and any third party account details. This is where most schedules break.
Weeks 8 to 10: Content Population
Real content replaces placeholders. If copy arrives on time, this phase is smooth. If it does not, everything behind it shifts by the same number of days, because we cannot test pages that have no content and we cannot build redirects for pages that do not exist yet.
A rough guide on content volume:
| Site Size | Copywriting Time (client-written) | Population Time |
|---|---|---|
| 5 to 8 pages | 2 to 3 weeks | 2 to 3 days |
| 15 to 30 pages | 4 to 6 weeks | 1 week |
| 50+ pages or ecommerce | 6 to 10 weeks | 2 to 3 weeks |
Weeks 10 to 11: Testing, QA and Client Review
Our testing
- Cross-browser checks on current versions of Chrome, Safari, Firefox and Edge
- Real device testing on iOS and Android
- Form submissions, autoresponders and CRM delivery
- Core Web Vitals and page speed scoring
- Broken links, redirect map validation, 404 handling
- Accessibility audit against WCAG 2.2 AA where in scope
- Analytics and conversion tracking verification
Your review (UAT)
You get a fixed window, normally 5 working days, to review everything and submit one consolidated bug and amend list. The critical distinction:
- Bug: something does not work as designed. Fixed free, inside the timeline.
- Change request: something works but you now want it different. Quoted separately or scheduled post-launch.
Being clear about this in advance prevents the single most common launch-week argument.
Week 12: Launch Week
Launch day is deliberately boring when the preparation is right. A typical sequence:
- Final backup of the existing site
- DNS changes scheduled for a low-traffic window, ideally Tuesday to Thursday morning
- Site pushed live, SSL verified, redirects tested in bulk
- Search Console and sitemap submission, robots.txt checked so nothing stays blocked
- Analytics and tracking confirmed firing on the live domain
- Smoke test of every form and key user journey
- CMS training session recorded for your team, plus handover documentation
Never launch on a Friday. DNS propagation can take up to 48 hours and nobody wants to discover a broken checkout on a Saturday night.
Weeks 13 to 14: Post-Launch Stabilisation
Rankings can wobble for a few weeks after a redesign, especially if URLs changed. We monitor Search Console for crawl errors, watch analytics for anything unexpected, fix small post-launch issues, and review early conversion data.
What Actually Causes Website Project Delays
| Delay Cause | Typical Cost | Prevention |
|---|---|---|
| Late or missing content | 2 to 6 weeks | Start writing in week 1, or buy copywriting |
| Slow feedback rounds | 1 to 3 weeks | Agree a 3-day response rule up front |
| A late stakeholder appearing at design stage | 1 to 4 weeks | Identify all approvers in week 1 |
| Scope creep after design sign-off | 1 to 5 weeks | Park ideas in a phase two list |
| Missing hosting, domain or API access | 3 days to 2 weeks | Collect credentials during week 0 |
| Holidays and peak trading periods | 1 to 3 weeks | Map absences onto the plan at kickoff |
Notice the pattern. Almost none of these are development problems. Roughly 8 out of 10 delayed web projects are delayed on the client side, and content is the usual culprit.
How Project Size Changes the Timeline
| Project Type | Realistic Timeline | Main Variable |
|---|---|---|
| Single landing page | 2 to 3 weeks | Copy and offer clarity |
| Small business site, 5 to 10 pages | 6 to 8 weeks | Feedback speed |
| Standard business site, 15 to 30 pages | 8 to 12 weeks | Content volume |
| Ecommerce store | 12 to 20 weeks | Catalogue, payments, shipping rules |
| Custom web application or portal | 16 to 30+ weeks | Integrations and user roles |
Your Client-Side Checklist to Stay on Schedule
- Name one decision maker who consolidates all internal feedback
- Commit to a 3 working day turnaround on every review
- Deliver content by the week 5 or 6 deadline, not launch week
- Book a professional photography session in week 1 if you need new imagery
- Hand over all credentials before design begins
- Keep a running phase two list so good ideas are captured, not crammed in
- Flag holidays, board meetings and busy seasons at kickoff
Frequently Asked Questions
How long does a website design project take on average?
Most professionally built business websites take 8 to 12 weeks from kickoff to launch. Simple brochure sites can finish in 6 weeks, while ecommerce and custom builds regularly run 12 to 20 weeks or more.
What are the main stages of a website design project timeline?
Discovery and strategy, information architecture and wireframes, visual design, development, content population, testing and QA, then launch and handover. A post-launch monitoring period of 2 to 4 weeks should follow. upanup.com walks through the specifics.
Why do web design projects go over schedule?
Late content, slow feedback, new stakeholders appearing mid-project and scope creep after design approval. These four account for the overwhelming majority of overruns, and all four are avoidable with clear deadlines at kickoff.
Can a website be built faster than 8 weeks?
Yes, if content is ready on day one, feedback comes back within 24 hours, the page count is small and the scope is locked. Speed is usually bought with decisiveness rather than money.
How much of my time will the project need?
Budget roughly 15 to 25 hours in total across an 8 to 12 week project, concentrated in discovery, design review, content supply and user acceptance testing. Content creation is extra if your team is writing it.
When should design changes stop?
At design sign-off, normally around week 6. After that, code has been written against approved layouts, so changes become change requests with their own cost and schedule impact.
What happens immediately after launch?
Redirect monitoring, Search Console checks, crawl error fixes, analytics verification and small refinements. Traffic can fluctuate for two to four weeks after a redesign before settling.
Planning Your Next Website Build?
A realistic website design project timeline is not a constraint, it is what protects the quality of the final result. When everyone knows what happens in week 4, what is needed by week 6 and what is locked by week 9, projects launch on time and nobody is surprised.
If you would like a timeline mapped to your specific project scope, get in touch and we will put together a week-by-week plan with clear deliverables and deadlines on both sides. Website Redesign Timeline covers this in more depth.