launch-strategy

coreyhaines31/marketingskills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/coreyhaines31/marketingskills --skill launch-strategy
0 commentsdiscussion
summary

Structured framework for planning product launches, feature announcements, and go-to-market strategies.

  • Organizes launches across five phases (internal, alpha, beta, early access, full) with specific actions and goals for each stage
  • Uses the ORB framework to balance owned channels (email, blog, community), rented channels (social, app stores), and borrowed channels (guest posts, influencers, partnerships)
  • Includes dedicated Product Hunt strategy with pre-launch preparation, launch-da
skill.md

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 .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.

A strong launch isn't about a single moment. It's about:

  • Getting your product into users' hands early
  • Learning from real feedback
  • Making a splash at every stage
  • Building momentum that compounds over time

The ORB Framework

Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.

Owned Channels

You own the channel (though not the audience). Direct access without algorithms or platform rules.

Examples:

  • Email list
  • Blog
  • Podcast
  • Branded community (Slack, Discord)
  • Website/product

Why they matter:

  • Get more effective over time
  • No algorithm changes or pay-to-play
  • Direct relationship with audience
  • Compound value from content

Start with 1-2 based on audience:

  • Industry lacks quality content → Start a blog
  • People want direct updates → Focus on email
  • Engagement matters → Build a community

Example - Superhuman: Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.

Rented Channels

Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.

Examples:

  • Social media (Twitter/X, LinkedIn, Instagram)
  • App stores and marketplaces
  • YouTube
  • Reddit

How to use correctly:

  • Pick 1-2 platforms where your audience is active
  • Use them to drive traffic to owned channels
  • Don't rely on them as your only strategy

Example - Notion: Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.

Platform-specific tactics:

  • Twitter/X: Threads that spark conversation → link to newsletter
  • LinkedIn: High-value posts → lead to gated content or email signup
  • Marketplaces (Shopify, Slack): Optimize listing → drive to site for more

Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.

Borrowed Channels

Tap into someone else's audience to shortcut the hardest part—getting noticed.

Examples:

  • Guest content (blog posts, podcast interviews, newsletter features)
  • Collaborations (webinars, co-marketing, social takeovers)
  • Speaking engagements (conferences, panels, virtual summits)
  • Influencer partnerships

Be proactive, not passive:

  1. List industry leaders your audience follows
  2. Pitch win-win collaborations
  3. Use tools like SparkToro or Listen Notes to find audience overlap
  4. Set up affiliate/referral incentives (for channel partner launches, use Introw to manage deal registration and commissions)

Example - TRMNL: Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.

Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.


Five-Phase Launch Approach

Launching isn't a one-day event. It's a phased process that builds momentum.

Phase 1: Internal Launch

Gather initial feedback and iron out major issues before going public.

Actions:

  • Recruit early users one-on-one to test for free
  • Collect feedback on usability gaps and missing features
  • Ensure prototype is functional enough to demo (doesn't need to be production-ready)

Goal: Validate core functionality with friendly users.

Phase 2: Alpha Launch

Put the product in front of external users in a controlled way.

Actions:

  • Create landing page with early access signup form
  • Announce the product exists
  • Invite users individually to start testing
  • MVP should be working in production (even if still evolving)

Goal: First external validation and initial waitlist building.

Phase 3: Beta Launch

Scale up early access while generating external buzz.

Actions:

  • Work through early access list (some free, some paid)
  • Start marketing with teasers about problems you solve
  • Recruit friends, investors, and influencers to test and share

Consider adding:

  • Coming soon landing page or waitlist
  • "Beta" sticker in dashboard navigation
  • Email invites to early access list
  • Early access toggle in settings for experimental features

Goal: Build buzz and refine product with broader feedback.

Phase 4: Early Access Launch

Shift from small-scale testing to controlled expansion.

Actions:

  • Leak product details: screenshots, feature GIFs, demos
  • Gather quantitative usage data and qualitative feedback
  • Run user research with engaged users (incentivize with credits)
  • Optionally run product/market fit survey to refine messaging

Expansion options:

  • Option A: Throttle invites in batches (5-10% at a time)
  • Option B: Invite all users at once under "early access" framing

Goal: Validate at scale and prepare for full launch.

Phase 5: Full Launch

Open the floodgates.

Actions:

  • Open self-serve signups
  • Start charging (if not already)
  • Announce general availability across all channels

Launch touchpoints:

  • Customer emails
  • In-app popups and product tours
  • Website banner linking to launch assets
  • "New" sticker in dashboard navigation
  • Blog post announcement
  • Social posts across platforms
  • Product Hunt, BetaList, Hacker News, etc.

Goal: Maximum visibility and conversion to paying users.


Product Hunt Launch Strategy

Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.

Pros

  • Exposure to tech-savvy early adopter audience
  • Credibility bump (especially if Product of the Day)
  • Potential PR coverage and backlinks

Cons

  • Very competitive to rank well
  • Short-lived traffic spikes
  • Requires significant pre-launch planning

How to Launch Successfully

Before launch day:

  1. Build relationships with influential supporters, content hubs, and communities
  2. Optimize your listing: compelling tagline, polished visuals, short demo video
  3. Study successful launches to identify what worked
  4. Engage in relevant communities—provide value before pitching
  5. Prepare your team for all-day engagement

On launch day:

  1. Treat it as an all-day event
  2. Respond to every comment in real-time
  3. Answer questions and spark discussions
  4. Encourage your existing audience to engage
  5. Direct traffic back to your site to capture signups

After launch day:

  1. Follow up with everyone who engaged
  2. Convert Product Hunt traffic into owned relationships (email signups)
  3. Continue momentum with post-launch content

Case Studies

SavvyCal (Scheduling tool):

  • Optimized landing page and onboarding before launch
  • Built relationships with productivity/SaaS influencers in advance
  • Responded to every comment on launch day
  • Result: #2 Product of the Month

Reform (Form builder):

  • Studied successful launches and applied insights
  • Crafted clear tagline, polished visuals, demo video
  • Engaged in communities before launch (provided value first)
  • Treated launch as all-day engagement event
  • Directed traffic to capture signups
  • Result: #1 Product of the Day

Post-Launch Product Marketing

Your launch isn't over when the announcement goes live. Now comes adoption and retention work.

Immediate Post-Launch Actions

Educate new users: Set up automated onboarding email sequence introducing key features and use cases.

Reinforce the launch: Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.

Differentiate against competitors: Publish comparison pages highlighting why you're the obvious choice.

Update web pages: Add dedicated sections about the new feature/product across your site.

Offer hands-on preview: Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.

Keep Momentum Going

It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.


Ongoing Launch Strategy

Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.

How to Prioritize What to Announce

Use this matrix to decide how much marketing each update deserves:

Major updates (new features, product overhauls):

  • Full campaign across multiple channels
  • Blog post, email campaign, in-app messages, social media
  • Maximize exposure

Medium updates (new integrations, UI enhancements):

  • Targeted announcement
  • Email to relevant segments, in-app banner
  • Don't need full fanfare

Minor updates (bug fixes, small tweaks):

  • Changelog and release notes
  • Signal that product is improving
  • Don't dominate marketing

Announcement Tactics

Space out releases: Instead of shipping everything at once, stagger announcements to maintain momentum.

Reuse high-performing tactics: If a previous announcement resonated, apply those insights to future updates.

Keep engaging: Continue using email, social, and in-app messaging to highlight improvements.

Signal active development: Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.


Launch Checklist

Pre-Launch

  • Landing page with clear value proposition
  • Email capture / waitlist signup
  • Early access list built
  • Owned channels established (email, blog, community)
  • Rented channel presence (social profiles optimized)
  • Borrowed channel opportunities identified (podcasts, influencers)
  • Product Hunt listing prepared (if using)
  • Launch assets created (screenshots, demo video, GIFs)
  • Onboarding flow ready
  • Analytics/tracking in place

Launch Day

  • Announcement email to list
  • Blog post published
  • Social posts scheduled and posted
  • Product Hunt listing live (if using)
  • In-app announcement for existing users
  • Website banner/notification active
  • Team ready to engage and respond
  • Monitor for issues and feedback

Post-Launch

  • Onboarding email sequence active
  • Follow-up with engaged prospects
  • Roundup email includes announcement
  • Comparison pages published
  • Interactive demo created
  • Gather and act on feedback
  • Plan next launch moment

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?

Related Skills

  • marketing-ideas: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
  • email-sequence: For launch and onboarding email sequences
  • page-cro: For optimizing launch landing pages
  • marketing-psychology: For psychology behind waitlists and exclusivity
  • programmatic-seo: For comparison pages mentioned in post-launch
  • sales-enablement: For launch sales collateral and enablement materials
how to use launch-strategy

How to use launch-strategy on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add launch-strategy
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/coreyhaines31/marketingskills --skill launch-strategy

The skills CLI fetches launch-strategy from GitHub repository coreyhaines31/marketingskills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/launch-strategy

Reload or restart Cursor to activate launch-strategy. Access the skill through slash commands (e.g., /launch-strategy) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.834 reviews
  • Ira Torres· Dec 24, 2024

    Useful defaults in launch-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kabir Gill· Dec 20, 2024

    We added launch-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Mei Reddy· Nov 15, 2024

    I recommend launch-strategy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aarav Sethi· Nov 11, 2024

    launch-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Yash Thakker· Nov 7, 2024

    Solid pick for teams standardizing on skills: launch-strategy is focused, and the summary matches what you get after install.

  • Aanya Garcia· Nov 3, 2024

    launch-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Dhruvi Jain· Oct 26, 2024

    launch-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Aanya Haddad· Oct 22, 2024

    launch-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aisha Ghosh· Oct 6, 2024

    Keeps context tight: launch-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kabir Mensah· Oct 2, 2024

    launch-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 34

1 / 4