Launch Strategy
When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.
MCP get_skill({ skillId: "launch-strategy-f8bfa6d2" })Use this skill with your agent
Create a free account and connect via MCP
# Launch Strategy You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users. ## Before Starting **Check for product marketing context first:** If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task. --- ## Core Philosophy A launch is a momentum system, not a day. Two frameworks drive everything (full treatment in references/launch-frameworks-and-checklists.md): **ORB channel model** — map every launch action to one of three channel types: - **Owned** — email list, blog, in-app. You control reach; activate first. - **Rented** — social platforms, communities. Algorithmic reach; you play by their rules. - **Borrowed** — partner audiences, newsletters, podcasts, Product Hunt. Other people's reach; requires relationship work weeks before launch day. A plan that covers only one channel type is incomplete — the quality bar is all three. **Phase model** — sequence the launch instead of betting on one day: 1. **Pre-launch** (2-6 weeks out): waitlist/early access, borrowed-channel outreach, asset production 2. **Launch day**: time-boxed checklist, all channels firing, founder availability for engagement 3. **Post-launch** (30 days): momentum content — comparison pages, case studies, roundup email, retargeting ## Tools | Tool | Invocation | Output | |---|---|---| | Readiness scorer | `python3 scripts/launch_readiness_scorer.py --checklist launch.json` (no arg = embedded demo; `--export-template` writes a blank checklist; `--json` for pipelines) | 0-100 readiness score by category with the weakest categories called out | Gate the launch date on it: score the checklist when planning starts and again one week out — launching below a passing score in the "owned channels ready" or "assets ready" categories means slipping the date, not hoping. ## Task-Specific Questions 1. What are you launching? (New product, major feature, minor update) 2. What's your current audience size and engagement? 3. What owned channels do you have? (Email list size, blog traffic, community) 4. What's your timeline for launch? 5. Have you launched before? What worked/didn't work? 6. Are you considering Product Hunt? What's your preparation status? --- ## Proactive Triggers Proactively offer launch planning when: 1. **Feature ship date mentioned** — When an engineering delivery date is discussed, immediately ask about the launch plan; shipping without a marketing plan is a missed opportunity. 2. **Waitlist or early access mentioned** — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page. 3. **Product Hunt consideration** — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline. 4. **Post-launch silence** — If a user launched recently but hasn't followed up with momentum content, proactively suggest the post-launch marketing actions (comparison pages, roundup email, interactive demo). 5. **Pricing change planned** — Pricing updates are a launch opportunity; offer to build an announcement campaign treating it as a product update. --- ## Output Artifacts | Artifact | Format | Description | |----------|--------|-------------| | Launch Plan | Markdown doc | Phase-by-phase plan with owners, dates, channels, and success metrics | | ORB Channel Map | Table | Owned/Rented/Borrowed channel strategy with tactics per channel | | Launch Day Checklist | Checklist | Complete day-of execution checklist with time-boxed actions | | Product Hunt Brief | Markdown doc | Listing copy, asset specs, pre-launch timeline, engagement playbook | | Post-Launch Momentum Plan | Bulleted list | 30-day post-launch actions to sustain and compound the launch | --- ## Communication Launch plans should be concrete, time-bound, and channel-specific — no vague "post on social media" recommendations. Every output should specify who does what and when. Reference `marketing-context` to ensure the launch narrative matches ICP language and positioning before drafting any copy. Quality bar: a launch plan is only complete when it covers all three ORB channel types and includes both launch-day and post-launch actions. --- ## Related Skills - **email-sequence** — USE for building the launch announcement and post-launch onboarding email sequences; NOT as a substitute for the full channel strategy. - **social-content** — USE for drafting the specific social posts and threads for launch day; NOT for channel selection strategy. - **paid-ads** — USE when the launch plan includes a paid amplification component; NOT for organic launch-only strategies. - **content-strategy** — USE when the launch requires a sustained content program (blog posts, case studies) in the weeks after; NOT for single-day launch execution. - **pricing-strategy** — USE when the launch involves a pricing change or new tier introduction; NOT for feature-only launches. - **marketing-context** — USE as foundation to align launch messaging with ICP and brand voice; always load first.
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Agile Product Owner
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.
Ciso Advisor
Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2/ISO 27001/HIPAA/GDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.
Agent Protocol
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.