Realistic Web Design Timeline From Kickoff to Launch
A realistic B2B web design timeline: discovery, IA, design, build, and launch QA. What belongs in each phase and what stretches a six-week focused rebuild.
From the archive. First published June 23, 2025.
Timelines vary. A simple brochure site can launch in 8 weeks. A complex B2B site with integrations can take 16+. Here’s what’s realistic and what affects it.
Typical Timeline by Phase
Discovery (1–2 weeks)
- Audit: Current site, analytics, technical SEO. What’s broken? What’s working?
- Interviews: Stakeholders, buyers. Who are they? What do they need?
- Information architecture: Sitemap, content structure. What pages? What hierarchy?
Discovery informs everything. Skip it and you build blind.
Design (2–4 weeks)
- Components: Buttons, forms, cards. Design system.
- Key pages: Homepage, service, contact. Core templates.
- Review: Feedback, revisions. 1–2 rounds typical.
Design can run parallel to content planning. Don’t wait for final copy to start.
Build (4–8 weeks)
- Page count: 10 pages vs. 50 pages. More pages, more time.
- Complexity: Custom forms, integrations, CMS. Each adds time.
- Content: Migration, entry. Who’s doing it? Delays here delay launch.
Launch (1 week)
- QA: Cross-browser, mobile, forms. Fix issues.
- Redirects: Old URLs to new. Preserve SEO.
- Go-live: DNS, SSL, final checks.
Total: 8–15 weeks for most B2B projects.
What Extends the Timeline
Scope Creep
- New pages: “Can we add 5 more?” Each adds time.
- New features: “Can we add a calculator?” Scope change.
- Fix: Lock scope at kickoff. Change requests go through a process.
Content Delays
- No content when build starts: Design and build wait. Or you design with placeholder. Both cost time.
- Fix: Have content (or a clear plan) before build. Content migration in parallel.
Review Cycles
- Too many stakeholders: 5 people reviewing. 5 different opinions. Long approval.
- Fix: Designate one decision-maker. Limit review rounds. 2–3 day turnaround.
Integrations
- CRM, ERP, analytics: Each integration adds complexity. API work, testing.
- Fix: Scope integrations early. Know the systems. Buffer time.
What Compresses It
Scope Lock
- Clear scope: Pages, features, exclusions. In writing.
- No mid-project additions: Additions go to phase 2.
Content Ready
- Content before build: Or at least key pages. Don’t hold up development.
- Migration plan: Who migrates? When? Parallel to build.
Fast Feedback
- Review within 2–3 days: Don’t hold up the sprint. Delays cascade.
- Single decision-maker: Or small group. Avoid committee approval.
Experienced Team
- Process: Weekly sprints. Clear deliverables. No surprises.
- Communication: Status updates. Issues surfaced early.
Red Flags
- “We’ll have it in 4 weeks”: For a 30-page B2B site? Unrealistic. Something gets cut.
- No discovery: Jumping to design. Building without understanding.
- No buffer: Timeline with zero slack. One delay breaks everything.
What to Ask Your Agency
- What’s the timeline by phase?: Discovery, design, build, launch.
- What could extend it?: Content, integrations, review.
- How do you handle scope changes?: Process? Impact on timeline?
- What do you need from us?: Content, feedback, access. When?
What we build now
Lead systems for high-ticket contractors and custom portals for growing teams.
Contractor lead systemsCustom portalsPricingBook paid discovery