Delivery plan · draft · 20-week roadmap
PerryGolf Website Modernization — Aug–Dec 2026
Contract execution 4 Aug (Day 1) · staging 30 Oct (Day 90) · Acceptance 1 Dec (Day 120)
August
September
October
November
December
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11
W12
W13
W14
W15
W16
W17
W18
W19
W20
Build to staging
Validate · launch · retire
Workshop
Day 23–24 · Aug 26–27
Scope Lock
Day 45 · Sep 17
Go-live
Day 120 · Dec 1–2
Staging delivery
Day 90 · Oct 30
Program & governance
Program Management & Governance · 7
Build the new site
Site Clone & Rebuild · 17
UI & UX Modernization · 5
Custom Registration & MGC Retirement · 5
Cruise Partner Integrations · 6
Content & discovery
CMS & Content Migration · 8
Recommended Net-New Pages · 2
AI-Optimized Blog Architecture · 4
Measurement & assurance
Analytics Implementation · 6
Consent Management · 4
Security Validation · 4
Team Enablement & Training · 3
AWS retirement
AWS Retirement · 8
Program & governance
Build the new site
Content & discovery
Measurement & assurance
AWS retirement
● = milestone week · 13 modules · ~80 outcomesAction required · owner-side
PerryGolf inputs needed
What PerryGolf provides or decides, and by when. The early access grants and product lists are in hand; the open items — the pages-to-retire call and the supplier, cruise-credential and image inputs — are what we still need. We send a detailed preread ahead of each decision.
In-flight itinerary & trip product list
Active products, so inventory, trip parity and search reflect priorities.
JonnieO requirements — w/ Harrison
Endpoints, payloads, gift-code flow. Feasibility due 24 Aug.
Pages to retire — PerryGolf's call
You decide which pages to sunset from the site inventory; we share a recommended cut-list as a preread. Sets CMS-migration and retirement scope.
Supplier source-of-truth call
Which system is authoritative per field — PGGO, Console or the CMS. Sets the supplier-data reconciliation; a workshop decision.
Google Search Console — property access
So search-visibility and indexing checks run on real data.
Cruise-partner credentials
API / booking access for the cruise integrations (e.g. Silversea). Feeds the Cruise Partner Integrations lane, W6–W12.
PGGO Dev access — w/ Gordon Pierce
Gates entity placement, migration and live sync. Needed by Scope Lock.
Supplier records to clean up
The description-drift list — venues that need a manual content pass before launch, named record by record.
Image rights & licensing
Source and usage rights for every image before it goes live, plus who owns post-trip photos.
Recommended · in addition to weekly governance
Standing website working session
A separate weekly IT / website sync with Sasha to walk progress and specific site items.
S
Sasha
Marketing · CMS
B
Brett
Sponsor
A
Alex
Optional · weekly
Weekly · ~30 min · separate from the governance call
High-level roadmap for steering-committee reference · drill into the delivery-plan workbook for task-level detail. Retirement follows go-live: nothing the live site depends on is switched off before launch.
100%