GTM Launch Checklist

Context

Use this to reduce launch risk and prevent missed dependencies across product, marketing, and sales.

Procedure

1. Define launch scope, KPI, and success criteria.
2. Break work into pre-launch, launch-day, and post-launch phases.
3. Assign owner, due date, and dependency for each task.
4. Add risk log with mitigation and rollback plan.
5. Validate measurement, alerts, and reporting cadence.

Output Format

# GTM Launch Checklist

## Launch Goal

- Objective:
- KPI:
- Target Segment:

## Task Checklist

| Phase       | Task | Owner | Due Date | Dependency | Status |
| ----------- | ---- | ----- | -------- | ---------- | ------ |
| Pre-launch  |      |       |          |            |        |
| Launch-day  |      |       |          |            |        |
| Post-launch |      |       |          |            |        |

## Risk Register

| Risk | Probability | Impact | Mitigation | Owner |
| ---- | ----------- | ------ | ---------- | ----- |
|      |             |        |            |       |

## Go/No-Go Gate

- Data instrumentation validated: Yes/No
- Rollback path tested: Yes/No
- Stakeholder alignment complete: Yes/No

QA Rubric (scored)

• Completeness (0-5): all phases represented.
• Ownership clarity (0-5): no unassigned critical tasks.
• Risk preparedness (0-5): mitigation and fallback quality.
• Operational readiness (0-5): go/no-go criteria are objective.

Examples (good/bad)

• Good: “Launch-day tasks include analytics smoke check and escalation owner.”
• Bad: “Checklist has tasks but no owners or dependencies.”

Variants

• Fast feature launch variant (48-hour cycle).
• Major launch variant with embargo, PR, and partner enablement tracks.