1) Kickoff and scope
Confirm what you’re launching. Lock owners, target dates, and sign-off criteria.
Decisions to confirm:
Brand name + legal entity
Service availability model (all ZIPs vs ZIP validation)
Plans and pricing model (1–4 plans)
Support model (Reach-managed L1 + brand-managed support)
Any bolt-ons required for launch
Output: scoped launch plan and owners.
Share the required business details and brand assets.
Brand provides:
Completed onboarding inputs (fields + assets)
Credentials and IDs for any brand-owned integrations (if applicable)
Output: onboarding packet marked complete.
3) Reach configuration and build
Reach sets up your tenant, journeys, content, and policies.
Common parallel workstreams:
Domain readiness (if using a custom domain)
Marketing and analytics tags (GTM / GA4)
Support tooling and contact points
Optional device store enablement (if in scope)
Output: staging environment ready for review.
4) Staging review and acceptance
Validate the end-to-end customer experience. Treat this as a release readiness review.
Minimum checks:
Homepage content renders correctly across devices
Plan selection, checkout, and payment descriptor
Eligibility gates (ZIP validation) behave as intended
Support contact details are correct
SEO and social cards preview correctly when shared
Output: sign-off to launch.
5) Launch and post-launch rhythm
Reach takes production live after sign-off. Then you move into BAU operations.
Align on:
Escalation path and operational contacts
Reporting cadence and distribution lists
Who approves future catalog, content, and policy changes
Output: brand live, with an operating rhythm.