Jump to a section +
There is no universal website timeline because “a website” can mean a five-page lead-generation site, a 300-page migration, or an online store connected to inventory and accounting systems. For planning purposes, a straightforward small-business build often fits within six to twelve weeks. That is a working range, not an industry promise. The schedule should be built from the actual work and the people who must approve it. The hiring and project-planning guide hub covers the other decisions that affect a smooth engagement.
A useful timeline starts with dependencies
The critical path is the longest chain of dependent work. A developer may be able to build the header while copy is being edited, but cannot finish a service-page layout without knowing whether it holds three short offerings or twelve detailed ones. A photographer can schedule a shoot before design approval, yet needs a shot list based on planned pages. The best website design process identifies these dependencies early and gives each one an owner and due date.
Illustrative schedules for three common scopes; every proposal should replace these ranges with project-specific milestones.
| Project | Reasonable planning range | What must be ready | Frequent delay |
|---|---|---|---|
| Focused 4–6 page site | 4–8 weeks | Approved sitemap, usable copy, brand assets, one clear approver | Owner writes copy between other duties |
| Custom 10–25 page lead site | 8–14 weeks | Page priorities, interviews, proof, form and CRM requirements | Several reviewers send conflicting notes |
| Large redesign or migration | 12–24+ weeks | Content inventory, redirect plan, integrations, analytics baseline, staged launch plan | Unknown legacy URLs or data appear late |
The seven variables that move a launch date
Estimate these before choosing a date
Page and template count
Twenty pages based on four reusable layouts can be easier than eight pages with eight unique experiences. Count page types, CMS collections, and special states—not URLs alone.
Content readiness
Finished, approved copy changes the schedule dramatically. Interviews, positioning, legal review, photography, product data, and case studies each add work and handoffs.
Decision speed
A two-business-day review window keeps momentum. A committee that meets monthly creates idle time even when the production team is available.
Feature uncertainty
A familiar contact form is predictable. A calculator, member portal, booking flow, payment system, or CRM sync needs discovery, configuration, failure handling, and testing.
Migration risk
An existing site brings URLs, files, rankings, analytics, form histories, and account ownership. Google’s official site-move guidance recommends mapping old URLs to new ones and monitoring the move; that work deserves its own schedule.
Quality standard
Responsive checks, keyboard testing, error states, proofing, performance work, structured data, and analytics validation take real time. W3C notes that tools assist accessibility evaluation but do not replace the full range of checks and human judgment.
Launch coordination
DNS access, domain ownership, backups, redirects, email risk, stakeholder availability, and a rollback plan can make launch a one-hour switch or a multi-day operation.
Some work can overlap, but each gate needs enough information to make the next decision responsibly.
A sample eight-week small-business schedule
| Week | Production focus | Client decision |
|---|---|---|
| 1 | Kickoff, analytics review, audience and goal alignment | Confirm one accountable approver and success measures |
| 2 | Sitemap, content inventory, page briefs | Approve pages and supply missing source material |
| 3 | Home-page direction and core copy | Choose one design direction; consolidate feedback |
| 4 | Responsive system and remaining page designs | Approve system, not isolated personal preferences |
| 5 | Development, CMS, forms, initial content entry | Provide final legal and contact details |
| 6 | Remaining build, integrations, redirects, metadata | Test workflows with real staff accounts |
| 7 | Cross-device QA, accessibility checks, proofing | Complete one formal acceptance review |
| 8 | Launch, analytics check, post-launch monitoring | Name the person who can approve fixes quickly |
That schedule works only if the inputs arrive on time. If photography is booked for week six, the build cannot use final portraits in week five. If service claims require an attorney’s approval, that review belongs before final page acceptance rather than on launch morning. Put both production work and client work on the same calendar. The website project kickoff checklist helps surface these responsibilities before they become delays.
How to shorten the project without cutting the wrong work
- Name one final approver. Other stakeholders can advise, but one person resolves conflicts and confirms acceptance.
- Finish the sitemap and page purpose before polishing sentences. This prevents copy for pages that later disappear.
- Use structured review windows: one document, one deadline, one consolidated response, and notes tied to agreed goals.
- Release in phases when appropriate. A complete core site can launch before a resource library if the later phase has its own navigation and redirect plan.
- Reuse a deliberate component system. Repeated cards and sections should be consistent without forcing every page into the same story.
- Freeze launch scope. Place late ideas in a post-launch list unless they are required for safety, accuracy, access, or a core workflow.
Do not compress the schedule by skipping backups, form tests, redirects, accessibility review, or ownership checks. Those shortcuts simply move risk past launch. A better trade is to reduce scope while keeping the quality bar: launch six complete pages instead of twelve half-finished ones, or use a manual intake process before automating it in phase two.
Questions to ask when a provider promises a fast launch
- Which deliverables are included before launch, and which are deferred?
- How many business days do we have for each review?
- What happens to the date if copy, photos, access, or approval is late?
- Will the site use our final content or temporary text at acceptance?
- Which browsers, screen sizes, forms, integrations, and accessibility checks are tested?
- Who maps old URLs, installs redirects, checks analytics, and monitors launch?
- What is the change process if we add pages or features after kickoff?
Can a small-business website be built in two weeks?
Sometimes, if the scope is small, content and brand assets are finished, features are familiar, one person can approve quickly, and the production team has reserved capacity. Ask what testing, strategy, and custom work fit inside that window. A two-week target is not suitable for every migration or integration.
Does writing content happen before design?
The page purpose and core message should be known before detailed design. Copy and design can then overlap, especially when a writer works from approved page briefs. Designing around placeholder text often creates rework when the real content has a different length or structure.
How much time should client reviews take?
Two to five business days per formal checkpoint is common enough for planning, but the right window depends on the organization. Agree on a deadline that gives the necessary people time to review without letting the project go cold.
When is a website actually finished?
A launch is a controlled release, not the end of ownership. The agreed launch scope should be complete and tested, but analytics, user feedback, security updates, content changes, and conversion improvements continue after the site is live.
Evidence behind the guide
Sources and further reading
- Site Moves and MigrationsGoogle Search Central
- Evaluating Web Accessibility OverviewW3C Web Accessibility Initiative
- Web Accessibility Evaluation Tools ListW3C Web Accessibility Initiative
Continue on Web Respawn
Pages that actually connect to this decision.
These links are selected for the subject of this guide. They are not a generic service dump.
Explore the strategy, content, design, build and launch foundation.
Open page ↗RELEVANT PAGEWebsite & Growth ServicesSee the complete Web Respawn service system in one place.
Open page ↗RELEVANT PAGEAbout Web RespawnSee the company, approach and standards behind the work.
Open page ↗RELEVANT PAGEWebsite Design FAQsGet concise answers about scope, timelines, ownership, SEO and care.
Open page ↗
