Growth & Digital/Launch Runbook
EDIT VIA GITHUB · /content

Launch Runbook

The October platform launch, run as a checklist — the immovable anchor, the gates to clear, the countdown, and who holds what. Slippage compresses QA onto Verto hours and the two-seat team, so the gates burn down here in the open.

Program brief →
ANCHOR
October
platform launch — immovable
WM EXIT
Oct 31
notice Oct 1 · after launch
SCOPE
103 pages
QA BAR
WCAG 2.1 AA
+ Core Web Vitals + redirect re-crawl

The anchor

The October platform launch is the fixed point the whole H2 plan swings on: Woolly Mammoth builds through launch and exits Oct 31 (notice Oct 1), then the two-seat web team plus Verto hours carry the site. Everything on this page exists to land the launch before the hand-off, with QA done on WM's watch rather than after it.

Gates to clear before launch

Product naming separationAnswer engines repeat what we publish — names locked before launch content shipsPMM + commsOpen
Solutions snippets validated (42)Engineer review before any snippet publishesEngineeringOpen
Figures & benchmarks reviewedIllustrative numbers replaced or approvedPMM + DataOpen
Customer outcome lines migratedReal outcome claims onto Customers + proof bandsBrandOpen
Logos placedProof bands populated with the approved rosterBrandOpen
Offer fulfillment owners lockedEvery offer is a promise sales fulfills — Decision 03Spencer / Jon / Simba reviewOpen
GA4 sign-off publishedSite data trustworthy end to end — baselines lock against itData & TrackingIn progress
Redirect map live (807 URLs)Verified by re-crawl, index junk removedWeb + SEO/AEODay-30 bar
Per-page baselines lockedEvery treated page measured for liftData & TrackingPending GA4
CMS publishing bridgeKevin hands off Sep 30 — bridged by Stalin + Verto hoursWebSep 30

The countdown

September — build at full speed

  • Verto specialists live Sep 1; content passes begin on the template system.
  • Staging review environment carries every page before publish.
  • Glossary verdicts and blog seeds move through the copy gates (Content & Copy).
  • CMS bridge executed Sep 30 as Kevin exits.

October — the launch window

  • WM notice Oct 1; launch-readiness QA runs on WM's watch.
  • WCAG 2.1 AA remediation and Core Web Vitals pass across everything that ships.
  • Redirect map live and verified by re-crawl before cutover.
  • Launch, then stabilization; WM exits Oct 31 after the platform launch.

November — after the hand-off

  • Launch-month testing rides Verto's bank of hours; the coding-agent workflow absorbs the capacity risk.
  • The CRO agent enters shadow mode on launch-month data under the Growth backfill's ownership.
  • GrowthX exits; the AI content workflow and the Digital Media & Content Specialist run content as the standing operation.

Launch-week QA checklist

  • Every template audited against tokens — zero hardcoded hex, every CTA routes to Get Started.
  • WCAG 2.1 AA pass and cross-browser correctness on all shipped pages.
  • Tracking QA end to end: GA4 key events firing, UTM convention verified on live campaigns.
  • Redirect re-crawl clean; no index junk resurfacing.
  • Finalized by the launch owner before launch week. [owner to complete]

The anchor

The October platform launch is the fixed point the whole H2 plan swings on: Woolly Mammoth builds through launch and exits Oct 31 (notice Oct 1), then the two-seat web team plus Verto hours carry the site. Everything on this page exists to land the launch before the hand-off, with QA done on WM's watch rather than after it.

Gates to clear before launch

Product naming separationAnswer engines repeat what we publish — names locked before launch content shipsPMM + commsOpen
Solutions snippets validated (42)Engineer review before any snippet publishesEngineeringOpen
Figures & benchmarks reviewedIllustrative numbers replaced or approvedPMM + DataOpen
Customer outcome lines migratedReal outcome claims onto Customers + proof bandsBrandOpen
Logos placedProof bands populated with the approved rosterBrandOpen
Offer fulfillment owners lockedEvery offer is a promise sales fulfills — Decision 03Spencer / Jon / Simba reviewOpen
GA4 sign-off publishedSite data trustworthy end to end — baselines lock against itData & TrackingIn progress
Redirect map live (807 URLs)Verified by re-crawl, index junk removedWeb + SEO/AEODay-30 bar
Per-page baselines lockedEvery treated page measured for liftData & TrackingPending GA4
CMS publishing bridgeKevin hands off Sep 30 — bridged by Stalin + Verto hoursWebSep 30

The countdown

September — build at full speed

  • Verto specialists live Sep 1; content passes begin on the template system.
  • Staging review environment carries every page before publish.
  • Glossary verdicts and blog seeds move through the copy gates (Content & Copy).
  • CMS bridge executed Sep 30 as Kevin exits.

October — the launch window

  • WM notice Oct 1; launch-readiness QA runs on WM's watch.
  • WCAG 2.1 AA remediation and Core Web Vitals pass across everything that ships.
  • Redirect map live and verified by re-crawl before cutover.
  • Launch, then stabilization; WM exits Oct 31 after the platform launch.

November — after the hand-off

  • Launch-month testing rides Verto's bank of hours; the coding-agent workflow absorbs the capacity risk.
  • The CRO agent enters shadow mode on launch-month data under the Growth backfill's ownership.
  • GrowthX exits; the AI content workflow and the Digital Media & Content Specialist run content as the standing operation.

Launch-week QA checklist

  • Every template audited against tokens — zero hardcoded hex, every CTA routes to Get Started.
  • WCAG 2.1 AA pass and cross-browser correctness on all shipped pages.
  • Tracking QA end to end: GA4 key events firing, UTM convention verified on live campaigns.
  • Redirect re-crawl clean; no index junk resurfacing.
  • Finalized by the launch owner before launch week.
Statuses set by hand in `content/pages/runbook.md` as gates clear. Program detail: the website program brief. Scott runs the launch; launch-month testing rides Verto's bank of hours.