The timeline is 4–6 weeks from confirmed access. The exact launch date is set after discovery, once the site has been mapped. A date in a sample chart is an example layout, not your date.

Four weeks or six

A four-week project shortens discovery to about three days, holds a sample page in the middle of week 2, overlaps templates with the content import, and launches at the end of week 4.

A six-week project uses the first week for discovery and a written plan, then design sign-off, then the build across the middle weeks, then QA and your review, then launch. Handover starts at launch.

Hypercare is 30 days either way. It does not shrink when the build does.

What the weeks hold

Discovery inventories pages, URLs, the CMS, scripts, and the content model. You approve that plan in writing.

Design is signed off before the build treats it as settled. During the build you see a sample page on your own content, with a short walkthrough of how that page is edited.

QA covers the pages, the redirects, and the analytics table. You sign the analytics table before DNS moves. Content and visual sign-off are in writing. Then the checked version goes live, and the second half of the payment is invoiced.

What moves the date

Access that arrives late, slow decisions, content that is not ready, and scope added in the middle. Each of those is a client dependency on the quote. If a date is going to slip, you hear it before the date passes.

Check-ins during hypercare are on day 7, day 14, and day 30. Day 0 is launch day.