Go-to-Market Planner Skill
Produce a complete, cross-functional GTM plan that aligns product, marketing, sales, and support around a single launch — with clear owners, timelines, and success metrics.
Launch Tier Framework
Before planning, classify the launch:
Always confirm tier with the user before proceeding.
GTM Plan Output Format
GTM Plan — [Product/Feature Name] — [Launch Date]
Launch Tier: [1 / 2 / 3]
Launch Owner (PM): [Name]
Target Launch Date: [Date]
Soft Launch Date (Beta/Limited): [Date, if applicable]
1. What We're Launching
One-line description: [What it is, for whom, and why now]
Key customer problem solved: [Specific pain point]
Key differentiator: [Why ours, why now]
2. Target Audience
Primary segment: [Who benefits most — be specific]
Secondary segment: [Who else benefits]
Not for: [Who this is NOT for — helps sales and support]
3. Messaging
Headline: [Customer-facing headline — lead with outcome, not feature]
Sub-headline: [Supporting context — how it works or why it matters]
3 key messages:
- [Problem solved]
- [How it works / what's new]
- [Proof / social proof / data]
Elevator pitch (30 seconds):
[For [target user] who [has this problem], [product/feature] is a [category] that [key benefit]. Unlike [alternative], we [differentiator].]
4. Launch Activities by Function
5. Success Metrics
6. Risks & Contingencies
7. Launch Day Checklist
Required Inputs
Work from what is given. If any of these is missing, still produce the complete output: fill each gap with a reasonable assumption marked (assumed, confirm) and list those assumptions at the end. Ask a question first only when the core subject itself is missing (there is nothing to write about).
- Product or feature name
- Target launch date
- Launch tier (Tier 1 / 2 / 3 — or describe scope and the skill will classify)
- Target audience (who benefits and who it's NOT for)
- Key message (what's the headline outcome for the customer)
- PM and launch owner
Guidelines
- Never plan a Tier 1 launch without at least 8 weeks of lead time
- Always include a "Not for" section — it prevents misdirected sales and support tickets
- Recommend a soft launch to 5–10% of users before full rollout for any Tier 1 or 2 launch
- Post-launch retrospective should be scheduled at launch planning time — don't leave it to chance
Quality Checks
Anti-Patterns
Example Trigger Phrases
- "Plan a product launch."
- "Write a GTM strategy."
- "Define launch tiers."