composio-community/awesome-gtm-skills/gtm-launch-plan

# <Launch name> — Tier <n>  ·  Launch date: <date>
 
## One-line
<What it is — 15 words>
 
## Audience
Primary: <specific segment + role>
Secondary: <who benefits second>
 
## The ONE behavior change
We want <audience> to <do X> because <reason>. Success metric: <metric + target>.
 
## Narrative arc (the press-release-first test)
- Headline: <if TechCrunch wrote one>
- Why now: <the change in the world that makes this urgent>
- What changed: <the 1-2 things that make this possible>
- What it replaces: <old workflow or competitor>
- Proof: <design partners, beta data, quotes>
 
## Channels & owners
| Channel | Asset | Owner | Due |
|---|---|---|---|
| Website hero | … | … | T-7 |
| Docs | … | … | T-5 |
| Blog post | … | … | T-1 |
| Email to customers | … | … | T0 |
| Twitter/X thread | … | … | T0 |
| LinkedIn post | … | … | T0 |
| HN / Product Hunt | … | … | T0 |
| Webinar / demo | … | … | T+7 |
| Sales enablement | battlecard + 1-pager + demo | … | T-5 |
| CS notification | … | … | T-3 |
 
## Sequencing (T = launch day)
- T-21: internal alignment, narrative lock
- T-14: assets drafted
- T-7: beta customers briefed, press embargo sent (if Tier 1)
- T-3: rehearsal, final QA on demo flow
- T0: publish + coordinated posts
- T+1: Q&A / AMA
- T+7: retro
 
## Success metrics (leading + lagging)
Leading (T+3): page visits, demo requests, signup/activation
Lagging (T+30): pipeline generated, deals won, revenue
 
## Kill criteria
We paused or rolled back if: <specific condition — e.g., crash rate > X, support volume > Y>.