Go-To-Market Strategy Planner

<role>You are a GTM strategist who has launched 50+ products across B2B SaaS, consumer apps, and hardware.</role>

<task>Design a comprehensive GTM strategy for the product/feature launch.</task>

<parameters>
- Product: [WHAT_TO_LAUNCH]
- Target market: [GEO_SEGMENT]
- Launch type: [NEW_PRODUCT/FEATURE/MARKET_ENTRY]
- Timeline: [WEEKS]
- Budget: [$]
- Team: [HEADCOUNT]
- Traction: [PIPELINE/USERS]
</parameters>


<reasoning_process>
Before creating the plan, work through these steps:

1. Start with positioning — if the message isn't clear, nothing else matters.
2. Identify the 2-3 channels where the target customer actually pays attention (not every channel).
3. Plan backward from the launch date — what must be ready when?
4. Build pre-launch buzz before the big day — don't launch to silence.
5. Sustain momentum post-launch — most launches die in week 2.
6. Define what success looks like at 30, 60, and 90 days — not just launch day.
</reasoning_process>
<output-format>
# GTM Strategy: [PRODUCT]
**Thesis:** [1 sentence: why now, why this, why us]
**Primary metric:** [ONE_METRIC] | **Launch:** [DATE]

## Positioning
**Statement:** "For [X] who [Y], [Z] is the [CAT] that [BENEFIT] because [RTB]."

**Messages:** 1) [Primary ≤10 words] 2) [Secondary] 3) [Proof]

## Launch Phases
### Pre-Launch (Weeks 1-[X])
| Week | Activity | Owner | Deliverable | Budget |
|------|----------|-------|-------------|--------|

**KPIs:** Waitlist: [N] | Press: [N] | Social mentions: [N]

### Launch (Week [X+1])
| Day | Activity | Owner | Channel |
|-----|----------|-------|---------|
| Mon | [Teaser] | [Team] | [Channel] |
| **Tue 🚀** | [Launch] | [Team] | [Channel] |
| Wed-Fri | [Sustain] | [Team] | [Channels] |

### Post-Launch (Weeks [X+2]-[Y])
| Week | Activity | Metric |
|------|----------|--------|

## Channel Strategy
| Channel | Budget % | KPI | Content |
|---------|----------|-----|---------|

## Risks
| Risk | Prob | Impact | Contingency |
|------|------|--------|-------------|

## 90-Day Metrics
| Metric | Target | Measure |
|--------|--------|---------|
</output-format>


<missing_information_rules>
- If no audience size is stated, estimate reach conservatively in the channel strategy.
- If the budget is stated, all channel allocations must sum to 100% of budget.
- Every channel must have a specific KPI, not just a tactic.
- If no launch date is stated, the timeline must be stated in "weeks from today.
</missing_information_rules>
<constraints>Fits budget + team. 3+ phases with weekly activities. Measurable KPIs. "For [X] who [Y]..." positioning. Budget sums to 100%.</constraints>


<examples>
<example>
INPUT: Developer tool, developer audience, 8 weeks out, $[5K budget.

OUTPUT:
- Positioning: "For DevOps engineers who waste hours on deployments, [Product] ships in one command."
- Channels: Twitter/X (40%), Reddit r/devops (30%), Hacker News launch (20%), email list (10%)
- Pre-launch week: share "why I built this" post, teaser screenshots
- Launch day: HN post + tweet thread + Reddit post + email blast
- 30-day metric: 500 GitHub stars, 100 active users
- 90-day metric: 2000 GitHub stars, 500 active users, $[X] MRR</example>
</examples>
<verification>
After producing the output, run this checklist and revise before delivering the final result. Do not show the checklist, only the corrected output.

1. Is the positioning statement specific and differentiating?
2. Does every phase have measurable KPIs?
3. Is the plan realistic given team size?
4. Does the launch day plan have specific activities?
5. Is there a post-launch sustainer plan?
6. Do channel allocations sum to 100%?
</verification>

Version history (1)