When this skill is activated, always start your first response with the 🧢 emoji.
Product Launch
A practical framework for planning, executing, and measuring product launches. Most launches fail not because of the product but because of poor coordination, rushed checklists, and no rollback plan. This skill covers the full launch lifecycle: scoping a go-to-market strategy, designing a beta program, building function-level launch checklists, planning tiered rollouts, writing internal and external communications, coordinating cross-functional teams, and measuring launch success. Agents can use this to draft GTM plans, run betas, sequence rollouts, and run launch retrospectives.
When to use this skill
Trigger this skill when the user:
- Is planning or executing a product launch or major feature release
- Needs to build a go-to-market strategy or launch plan
- Wants to design or run a beta program (closed, open, or pilot)
- Needs a launch checklist broken down by function (eng, marketing, support, legal)
- Is planning a tiered or phased rollout (dark launch, beta, GA)
- Needs to write launch communications - internal announcements, press releases,
blog posts, or customer emails
- Wants to coordinate a cross-functional launch squad or assign RACI ownership
- Needs to define or review launch success metrics and run a launch retrospective
- Asks about launch tiers, rollout strategy, or go-to-market execution
Do NOT trigger this skill for:
- Detailed pricing model design (use the pricing-strategy skill instead)
- Feature flag implementation details or release engineering tooling (use a
deployment or CI/CD skill)
Key principles
- Launch is a process, not an event - A launch begins weeks before the
public announcement and ends weeks after. The announcement date is one milestone in a longer arc that includes internal readiness, beta feedback, and post-launch iteration. Plan the full timeline, not just the day-of.
- Tier launches by impact - Not every launch needs a press release and
a company all-hands. Match the launch tier to the blast radius of the change. A bug fix ships silently. A new pricing model gets a full GTM program. Define launch tiers upfront and assign different checklists to each tier.
- Internal launch before external - Every external launch should be preceded
by an internal launch. Sales, support, and success teams must be able to answer customer questions before the announcement goes live. "Internal GA" is a real milestone; treat it as one.
- Measure launch success - Define success metrics before launch, not after.
Decide in advance what a successful week one looks like: activation rate, trial starts, pipeline influenced, NPS, support ticket volume. Agree on a green threshold. Measure against it. Run a retrospective within 30 days.
- Have a rollback plan - For every launch, define the criteria that would
trigger a rollback or pause and the exact steps to execute it. Rollback plans are written in calm; they are executed in chaos. Write them now.
Core concepts
Launch tiers classify releases by scope and customer impact. Tier 1 is a major launch (new product, new market, major pricing change) - full GTM, press, exec involvement. Tier 2 is a significant feature - blog post, in-app announcement, sales enablement. Tier 3 is a minor improvement - release notes, internal notification. Tier 4 is a patch or internal change - changelog entry only. Assign tier at kickoff; the tier drives which checklist items are required.
GTM components are the building blocks of a go-to-market plan: target segment (who is this for), positioning (why this over alternatives), pricing and packaging, distribution channel (self-serve, sales-led, partner-led), launch timing, and success metrics. All six must be aligned before any launch activity begins.
Beta program types serve different purposes. A closed beta gives access to a hand-picked cohort for deep feedback - high quality signal, slow velocity. An open beta removes the gate - broader signal, noisier data. A pilot is a time-limited full deployment with a single customer or segment - best for enterprise products or regulated industries. Choose the type based on what you need to learn and how fast.
Launch metrics fall into three buckets: awareness (reach, share of voice, press mentions), activation (trial starts, sign-ups, demo requests, product qualified leads), and retention (week-1 return rate, feature adoption, churn delta in the 30 days post-launch). Track all three; optimize for the bucket that is weakest.
Common tasks
Create a GTM strategy
A go-to-market strategy answers six questions. Answer them in this order:
- Who - Define the target segment precisely. Not "SMBs" but "engineering
managers at Series A-C SaaS companies with 10-50 engineers."
- Problem - State the specific pain the product solves for that segment.
Quantify it if possible ("spend 4 hours/week on X").
- Positioning - Write a positioning statement:
"For [segment], [product] is the [category] that [key benefit] unlike [alternative] which [limitation]."
- Pricing and packaging - Which tier or plan is the entry point? What is
the upgrade path? Is there a free trial or freemium component?
- Distribution - How does the segment discover and buy? Self-serve
(product-led), sales-assisted (sales-led), or through a partner channel?
- Success metrics - What does a successful launch look like at 7, 30, and
90 days? Name specific numbers and who owns them.
Codify all six in a one-page GTM brief before any execution begins.
Design a beta program
Recruitment
- Define who qualifies: segment, use case, technical maturity, time commitment
- Aim for 15-50 participants for a closed beta (enough signal, manageable noise)
- Recruit from existing waitlist, active customers, or outbound to target accounts
- Set clear expectations: duration, feedback cadence, and what they get in return
(early access, pricing discount, public recognition, direct product influence)
Feedback loops
- Weekly check-in cadence: short async survey (5-7 questions) plus optional
30-minute call slot
- Track usage data alongside qualitative feedback - usage tells you what they do,
interviews tell you why
- Maintain a shared tracker of reported issues, feature requests, and blockers
with status updates visible to beta participants
Graduation criteria
- Define graduation gates before the beta starts, not during
- Minimum criteria: core user journey completion rate above threshold, no
critical bugs open, support volume sustainable at scale, NPS or CSAT baseline established
- Graduation is a decision meeting with eng, product, and CS present - not an
automatic date flip
Build a launch checklist
Break the checklist by function and time horizon. See references/launch-checklist.md for the full copy-paste checklist.
Engineering - feature flags, performance benchmarks, error monitoring, rollback procedure, capacity plan, data migration tested
Product - positioning finalized, pricing approved, feature documentation complete, beta graduation signed off, launch tier confirmed
Marketing - landing page live (dark or staged), blog post drafted, social copy approved, email sequence queued, press brief sent (if Tier 1)
Sales - pitch deck updated, objection handling doc written, demo environment current, sales training completed, CRM fields updated for tracking
Customer Success / Support - help center articles published, support scripts written, escalation path defined, internal FAQ distributed, surge plan in place
Legal / Compliance - Terms of Service updated (if needed), privacy review completed, trademark cleared, any regulated market approvals obtained
Plan a tiered rollout
A tiered rollout reduces risk by exposing new functiona