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,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

26 stars

Best use case

launch-strategy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

Teams using launch-strategy should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/launch-strategy/SKILL.md --create-dirs "https://raw.githubusercontent.com/TerminalSkills/skills/main/skills/launch-strategy/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/launch-strategy/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How launch-strategy Compares

Feature / Agentlaunch-strategyStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Launch Strategy

## Overview

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. This skill covers phased launch approaches, channel strategy (owned/rented/borrowed), Product Hunt launches, and ongoing launch momentum.

**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.

## Instructions

### 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. A strong launch is about getting your product into users' hands early, learning from real feedback, making a splash at every stage, and 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 (email list, blog, podcast, branded community, website). They get more effective over time with no algorithm changes. Start with 1-2 based on audience: industry lacks content then blog, people want updates then email, engagement matters then community.

**Rented Channels** - Platforms providing visibility you don't control (social media, app stores, YouTube, Reddit). Pick 1-2 where your audience is active. Use them to drive traffic to owned channels. Twitter/X for threads that link to newsletter, LinkedIn for posts that lead to gated content, marketplaces for optimized listings that drive to site.

**Borrowed Channels** - Tap into someone else's audience (guest content, collaborations, speaking engagements, influencer partnerships). List industry leaders your audience follows, pitch win-win collaborations, use tools like SparkToro to find audience overlap. Convert borrowed attention into owned relationships.

### Five-Phase Launch Approach

**Phase 1: Internal Launch** - Recruit early users one-on-one to test for free. Collect feedback on usability gaps. Goal: validate core functionality with friendly users.

**Phase 2: Alpha Launch** - Create landing page with early access signup. Announce the product exists. Invite users individually to start testing. Goal: first external validation and waitlist building.

**Phase 3: Beta Launch** - Work through early access list (some free, some paid). Start marketing with teasers. Recruit friends, investors, and influencers to test and share. Consider adding: coming soon page, "Beta" sticker in navigation, email invites, early access toggle for experimental features. Goal: build buzz and refine with broader feedback.

**Phase 4: Early Access Launch** - Leak product details (screenshots, GIFs, demos). Gather quantitative usage data and qualitative feedback. Run user research with engaged users. Throttle invites in batches (5-10% at a time) or invite all under "early access" framing. Goal: validate at scale and prepare for full launch.

**Phase 5: Full Launch** - Open self-serve signups. Start charging. Announce general availability across all channels. Touchpoints: customer emails, in-app popups, website banner, blog post, social posts, Product Hunt, BetaList, Hacker News. Goal: maximum visibility and conversion to paying users.

### Product Hunt Launch Strategy

**Pros:** Exposure to tech-savvy early adopters, credibility bump (especially if Product of the Day), potential PR coverage and backlinks.

**Cons:** Very competitive, short-lived traffic spikes, requires significant pre-launch planning.

**Before launch day:** Build relationships with influential supporters and communities. Optimize listing with compelling tagline, polished visuals, short demo video. Study successful launches. Engage in communities and provide value before pitching.

**On launch day:** Treat it as an all-day event. Respond to every comment in real-time. Encourage your existing audience to engage. Direct traffic back to your site for signups.

**After launch day:** Follow up with everyone who engaged. Convert traffic into owned relationships (email signups). Continue momentum with post-launch content.

### Post-Launch Product Marketing

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

**Reinforce the launch:** Include announcement in 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.

### Ongoing Launch Strategy

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, in-app messages, social media.
- **Medium updates** (integrations, UI enhancements): Targeted announcement -- email to relevant segments, in-app banner.
- **Minor updates** (bug fixes, small tweaks): Changelog and release notes to signal active development.

Space out releases to maintain momentum. Reuse high-performing tactics. Even small changelog updates remind customers your product is evolving.

### Launch Checklist

**Pre-Launch:** Landing page with clear value proposition, email capture / waitlist signup, early access list built, owned channels established, rented channel presence optimized, borrowed channel opportunities identified, 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, Product Hunt listing live (if using), in-app announcement, website banner active, team ready to engage, 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.

## Examples

### Example 1: B2B Analytics Tool Product Hunt Launch

**User prompt:** "We're launching our analytics platform for e-commerce teams on Product Hunt next month. We have 800 email subscribers and 2,000 Twitter followers. Help me plan the launch."

The agent will create a 4-week pre-launch timeline: Week 1 dedicates to optimizing the PH listing (tagline, visuals, 60-second demo video) and studying top-ranked analytics launches. Week 2 focuses on building borrowed channel opportunities -- pitching guest posts to 3 e-commerce newsletters and scheduling 2 podcast appearances. Week 3 activates the email list with a teaser campaign and recruits 20 power users as launch day supporters. Week 4 is final prep: schedule social content, prepare real-time response templates, and brief the team for all-day engagement. It will also map post-launch actions including converting PH traffic into email subscribers and a follow-up sequence for everyone who upvoted.

### Example 2: Feature Launch for Existing SaaS Product

**User prompt:** "We just built a new AI writing assistant feature for our project management tool. We have 5,000 paying customers and want to announce it. How should we structure the launch?"

The agent will classify this as a major update deserving a full campaign, then plan a phased rollout: Phase 1 (Week 1) is early access to 500 power users with a feedback form. Phase 2 (Week 2) is a beta label with in-app banner for all users. Phase 3 (Week 3) is the public launch with a blog post, email announcement segmented by use case, in-app popup with demo GIF, social media thread showing real examples, and a "New" badge in the navigation. It will recommend post-launch actions: feature-specific onboarding emails, a comparison page against standalone AI writing tools, and a customer spotlight featuring an early adopter's workflow.

## Guidelines

- Always start by understanding the user's current audience size and channels before recommending a launch plan. A 50-person beta is different from a 50,000-subscriber launch.
- Recommend phased launches over big-bang launches. Phased approaches reduce risk and build compounding momentum.
- Product Hunt is a tactic, not a strategy. It works best when combined with owned channel activation, not as a standalone plan.
- Every borrowed and rented channel effort should funnel back to owned channels. If a podcast appearance doesn't drive email signups, it's a missed opportunity.
- Space out announcements. Shipping 5 features at once gets one mention; shipping them weekly gets 5 moments of attention.
- Post-launch is as important as launch day. Plan the week after launch with the same rigor as the launch itself.
- Be specific about timelines and task owners. "Do social media" is not a plan; "Schedule 3 Twitter threads for launch week highlighting customer use cases" is a plan.

Related Skills

product-strategy

26
from TerminalSkills/skills

Expert guidance for product strategy, helping product leaders define product vision, craft positioning, analyze competitive landscapes, choose pricing models, and build outcome-driven roadmaps. Applies frameworks from Marty Cagan (Empowered), April Dunford (Obviously Awesome), Gibson Biddle (DHM Model), and Reforge.

pricing-strategy

26
from TerminalSkills/skills

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.

launchdarkly

26
from TerminalSkills/skills

Manage feature flags with LaunchDarkly. Use when a user asks to implement feature flags, roll out features gradually, do A/B testing, control feature access by user segment, or implement kill switches for features.

free-tool-strategy

26
from TerminalSkills/skills

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.

content-strategy

26
from TerminalSkills/skills

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.

cache-strategy

26
from TerminalSkills/skills

Design and implement caching layers for APIs and web applications using Redis or Memcached. Use when you need to reduce database load, improve response times, or handle traffic spikes. Covers cache-aside, write-through, and write-behind patterns, TTL strategies, cache invalidation, and stampede prevention. Trigger words: cache, Redis, Memcached, TTL, cache invalidation, response time, throughput, rate limiting.

zustand

26
from TerminalSkills/skills

You are an expert in Zustand, the small, fast, and scalable state management library for React. You help developers manage global state without boilerplate using Zustand's hook-based stores, selectors for performance, middleware (persist, devtools, immer), computed values, and async actions — replacing Redux complexity with a simple, un-opinionated API in under 1KB.

zoho

26
from TerminalSkills/skills

Integrate and automate Zoho products. Use when a user asks to work with Zoho CRM, Zoho Books, Zoho Desk, Zoho Projects, Zoho Mail, or Zoho Creator, build custom integrations via Zoho APIs, automate workflows with Deluge scripting, sync data between Zoho apps and external systems, manage leads and deals, automate invoicing, build custom Zoho Creator apps, set up webhooks, or manage Zoho organization settings. Covers Zoho CRM, Books, Desk, Projects, Creator, and cross-product integrations.

zod

26
from TerminalSkills/skills

You are an expert in Zod, the TypeScript-first schema declaration and validation library. You help developers define schemas that validate data at runtime AND infer TypeScript types at compile time — eliminating the need to write types and validators separately. Used for API input validation, form validation, environment variables, config files, and any data boundary.

zipkin

26
from TerminalSkills/skills

Deploy and configure Zipkin for distributed tracing and request flow visualization. Use when a user needs to set up trace collection, instrument Java/Spring or other services with Zipkin, analyze service dependencies, or configure storage backends for trace data.

zig

26
from TerminalSkills/skills

Expert guidance for Zig, the systems programming language focused on performance, safety, and readability. Helps developers write high-performance code with compile-time evaluation, seamless C interop, no hidden control flow, and no garbage collector. Zig is used for game engines, operating systems, networking, and as a C/C++ replacement.

zed

26
from TerminalSkills/skills

Expert guidance for Zed, the high-performance code editor built in Rust with native collaboration, AI integration, and GPU-accelerated rendering. Helps developers configure Zed, create custom extensions, set up collaborative editing sessions, and integrate AI assistants for productive coding.