# Launch tier matrix · [Product or portfolio] · v[n] · [Date] **Owner:** [Launch council chair or product ops lead] **Review:** every half year ## Tier criteria (a launch meets a tier when it meets any two of its criteria) | | Tier 1 | Tier 2 | Tier 3 | |---|---|---|---| | New product, SKU or price | | | | | Changes how buyers evaluate us | | | | | Revenue or pipeline target attached | | | | | Regulatory or trust exposure (AI autonomy, new data use) | | | | | New capability for existing customers | | | | | Changes an admin or user workflow | | | | | Improvement, fix or minor change | | | | AI rule: an AI feature that acts on the customer's behalf moves up one tier. ## What each tier gets | | Tier 1 | Tier 2 | Tier 3 | |---|---|---|---| | Announcement artifacts | Press release, blog post, customer FAQ, internal FAQ, release notes, transparency note (AI) | Blog post, customer FAQ, internal FAQ, release notes | Release notes | | Readiness | All nine functions | Affected functions | Docs and support | | Rollout | Design partners, early access, LA, GA | Opt-in or percentage | Flag to GA | | Enablement | Certification | Brief | None | | Go/no-go decider | [VP or GM] | [PM lead] | [Engineering lead] | | Post-launch review | 30 and 90 days | 30 days | On trigger | ## Stage definitions we use | Stage | Access | Support | SLA | Production use | Price | |---|---|---|---|---|---| | Design partners (private preview) | Named accounts under NDA | Direct with product team | None | [Agreed in writing / no] | [Free / discounted] | | Early access (preview) | Admin opt-in | Best effort | None | [No / at own risk] | [ ] | | Limited availability | [Platforms, regions or scale limit] | Full | [None stated / ] | Yes, within scope | [ ] | | General availability | All eligible customers | Full | [SLA] | Yes | List | ## Tier decisions this quarter | Launch | Proposed tier | Criteria met | Confirmed by | Date | |---|---|---|---|---| | | | | | |