The short answer

A well-scoped five- to ten-page small-business website often needs four to eight weeks from kickoff to launch. The calendar can be shorter when copy and assets are ready, or much longer when decisions, content, integrations, and approvals are unresolved.

Plan milestones, not one launch date

Build the schedule backward from these stages:

1. Discovery, requirements, and access.
2. Sitemap and content plan.
3. Copy and asset delivery.
4. Visual direction and key-page design.
5. Build and content loading.
6. Responsive, accessibility, form, and performance testing.
7. Client review and revisions.
8. Launch, verification, and handoff.

Assign an owner and due date to each stage. A simple site might receive one week for discovery and content, one for design, two for build, one for revision and testing, and a few days for launch. Add breathing room instead of scheduling every stage to finish at midnight before a hard event.

Name the delay risks at kickoff

The most common are missing copy, too many decision-makers, late photos, unclear scope, third-party account access, custom integrations, and feedback arriving in pieces. Put content deadlines, consolidated-feedback rules, and a pause/restart policy in the project plan.

Do not promise that domain changes happen instantly. DNS updates and provider processes can introduce waiting, so keep the old site live while the new one is tested and prepare a rollback plan.

Protect testing time

Testing is project work, not spare time left after design. Google recommends responsive design and equivalent content across mobile and desktop (Google mobile-first guidance). W3C’s tutorials show that headings, images, forms, and other components need accessible structure too (W3C accessibility tutorials).

Send a weekly status with completed work, next decisions, client responsibilities, risks, and current launch date. When a delay happens, show its effect early. A calm revised schedule is more professional than pretending the deadline is safe until launch morning.

Sources and further reading

• Google Search Central: Mobile-first indexing best practices
• W3C Web Accessibility Initiative: Tutorials

A free next step

You don't have to build this alone

Bring your questions, share what you're working on, and meet other women building businesses from home. It is free to join.

Join Our Community Free

Related Questions

• What deposit and payment schedule should I use for a web design project?
• How many revisions should I include in a web design project, and how do I prevent scope creep?
• What information and assets should I collect from a web-design client before work begins?
• Who should own and pay for a client's domain name and hosting account?

Related WAHMN resource

If you want to turn this website task into a service or build a stronger process for your own site, this system walks through the work in more depth. See Website & Landing Page Build System.