// Build a go-to-market launch plan for a new product, feature, or segment — audience, channels, narrative, sequencing, metrics. Use on "launch plan for <product>", "GTM for the new feature", or "how do we take this to market?".
Generate a targeted lead list with Apollo — filter by title, company size, industry, tech stack — and export to CSV/HubSpot/Sheets. Use when the user says "build me a prospect list", "find 100 VPs of X", or "source leads for the campaign".
Build a competitive battlecard — when to land-grab vs. when to walk away, key wedges, objection handling, landmines to set. Use on "build a battlecard against <competitor>", "how do we beat <X>", or "compete review".
Check Google Calendar availability and book meetings — find slots across time zones, send invites, hold prep time. Use on "find time with X", "book a demo", "check my availability next week".
Write high-response cold emails — short, specific, prospect-centric. Use when the user asks to "write a cold email", "rewrite my outbound", or "this email is getting no replies". Produces 3 variants with rationale.
Run a cold email outreach campaign via Gmail. Use when the user wants to send personalized cold emails to a list of prospects, draft outbound sequences, or launch a small outreach batch from a CSV/sheet of leads. Proactively invoke when the user mentions "send cold emails", "outreach campaign", or "blast my leads".
Prep for a discovery call — research the account, the attendee, set hypothesis for their pains, write the question stack, define success. Use on "prep for my discovery call", "research this account before tomorrow", or "what should I ask <prospect>?".
| name | gtm-launch-plan |
| description | Build a go-to-market launch plan for a new product, feature, or segment — audience, channels, narrative, sequencing, metrics. Use on "launch plan for <product>", "GTM for the new feature", or "how do we take this to market?". |
| allowed-tools | ["Read","Write","AskUserQuestion"] |
A launch is an orchestrated moment. Without sequencing, you just have a list of activities.
./launches/<name>.md.# <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>.