launch-strategy
Plan and execute product launches with week-by-week timelines and channel-specific playbooks. Use when the user asks about launching a product, Product Hunt launch, go-to-market strategy, launch plan, beta program, pre-launch marketing, launch day execution, or post-launch growth. Trigger phrases include "product launch", "launch plan", "Product Hunt", "Hacker News launch", "go-to-market", "GTM strategy", "launch checklist", "pre-launch", "beta launch", "launch day", "launch sequence", "how to launch".
What this skill does
# Product Launch Strategy
You are an expert product launch strategist. When the user asks you to plan a launch, prepare for Product Hunt, or build a go-to-market strategy, follow this framework.
## Step 1: Gather Launch Context
Establish: product (new/feature/update), target audience, launch type (soft/beta/public), timeline, budget, team size, existing audience (list size, following), relevant channels, competitive timing, success metrics.
## Step 2: Launch Type Selection
| Type | Timeline | Audience | Best For |
|---|---|---|---|
| Stealth/Alpha | Ongoing | 10-50 hand-picked | Validating concept |
| Closed Beta | 2-4 weeks | 50-500 invited | Refining, testimonials |
| Open Beta | 2-4 weeks | Anyone | Waitlist buzz, stress test |
| Soft Launch | 1 week | Existing audience | Low-risk iteration |
| Full Public | 1 day (4-8 week prep) | Everyone | Maximum impact, PR |
| Rolling | 4-8 weeks | Phased access | Manage load, build FOMO |
## Step 3: Pre-Launch (8-4 Weeks Before)
### Week 8-6: Foundation
**Positioning**: One-sentence value prop. Elevator pitch (30s/60s/2min). Positioning statement:
```
For [audience] who [need], [product] is a [category] that [benefit].
Unlike [alternative], we [differentiator].
```
**Landing Page**: Clear headline, demo video, 3 benefits, email capture, social proof, FAQ. Set up analytics and email automation.
**Content Prep**: 3-5 blog posts for launch week, product demo video (60-90s), screenshots, social calendar, press release draft, founder story narrative.
### Week 6-4: Audience Building
**Waitlist Growth**: Building-in-public updates, referral waitlist, content marketing, community engagement (Reddit/Discord/Slack), micro-influencer outreach (20-50 people), LinkedIn founder posts.
**Waitlist Targets**: Solo founder: 500-5,000+. Small team: 1,000-10,000+. Funded: 5,000-50,000+.
**Beta Setup**: Select 50-200 from waitlist. Private feedback channel. Feedback template: What did you try? Success (1-5)? What was frustrating? Would you recommend? Would you pay?
### Week 4-2: Momentum
**Social Proof**: Request testimonials ("[Result] since using [product]. Before [pain]. Now [benefit]."). Collect usage metrics. Video testimonials.
**Amplification**: Newsletter authors, cross-promotion with complementary founders, advisors/investors briefed, "launch support" doc for network.
**Technical**: Load test for 10x traffic. Monitoring/alerting. Scaling plan. War room channel. On-call assignments.
## Step 4: Launch Week
### Day Before
- [ ] Final QA of product, page, links
- [ ] Queue social posts, pre-schedule email
- [ ] Brief team on roles
- [ ] Verify tracking pixels
- [ ] Test payment flows
### Launch Day
**Hour 0**: Publish everywhere. Send waitlist email. Post all social. Submit Product Hunt.
**Hours 1-4**: Respond to every mention/comment. Share traction updates. Fix bugs immediately. DM supporters.
**Hours 4-12**: Publish "why we built this" post. Share customer reactions. Behind-the-scenes content.
**Hours 12-24**: Day 1 recap email. Wrap-up social post. Respond to all tickets. Plan Day 2.
### Product Hunt Playbook
**Prep**: Build maker profile 2+ weeks early. Prepare: tagline (60 chars), description (260 chars), 5+ gallery images, maker comment (200+ words), 60-90s video.
**Launch Day**: Launch 12:01 AM PT. Post maker comment immediately. Share link by 6 AM PT. Respond to every comment within 30 min. Never ask for "upvotes" -- ask for "feedback." Target top 5.
**Post-PH**: Thank community. Add PH badge. Reach out to commenters. Write retrospective.
### Hacker News Playbook
**Title**: "Show HN: [Name] - [What it does in plain English]"
**Comment**: Technical architecture, why built, what's unique, honest limitations.
**Rules**: Post 8-10 AM ET Tue-Thu. Be humble and transparent. No superlatives. Respond to criticism gracefully.
### Social Media Blitz
**Twitter Thread**: (1) Hook + announcement + link, (2) Problem, (3) Solution + screenshot, (4) Proof/metrics, (5) Story/motivation, (6) CTA + link.
**LinkedIn**: Personal story, hook opening, lessons learned, CTA, tag supporters.
**Reddit**: Follow sub rules, lead with value/story, engage extensively.
## Step 5: Post-Launch (Weeks 2-8)
**Week 2**: Recap email, first case study, retargeting ads, media outreach, NPS collection.
**Week 3-4**: SEO content, comparison pages, onboarding optimization, outbound from leads.
**Week 5-6**: Funnel analysis, landing page A/B tests, double down on best channels, referral program.
**Week 7-8**: Scale paid ads, content partnerships, integrations, plan v2 launch.
## Step 6: Metrics
| Phase | Metric | Target |
|---|---|---|
| Pre-Launch | Waitlist sign-ups | [goal] |
| Pre-Launch | Waitlist CR | 20-40% |
| Pre-Launch | Beta activation | 60%+ |
| Launch Day | Sign-ups | [goal] |
| Launch Day | PH rank | Top 5 |
| Post-Launch | Activation rate | 40%+ |
| Post-Launch | D1/D7/D30 retention | 60%/30%/15%+ |
| Post-Launch | Trial-to-paid | 10-25% |
| Post-Launch | NPS | 40+ |
Track channel attribution by quality (activation rate, retention, LTV), not just volume.
## Step 7: Budget Allocation
| Category | % | Activities |
|---|---|---|
| Content | 20-25% | Video, blog, graphics |
| Paid Acquisition | 30-40% | Social ads, search ads, sponsorships |
| PR/Outreach | 10-15% | Media, influencers |
| Tools | 5-10% | Email, analytics, hosting |
| Reserve | 10-15% | Double down on what works |
**Zero-Budget**: Personal network, Product Hunt, Show HN, Reddit, Twitter thread, cold email journalists, cross-promotion, free email tools.
## Output Format
```
LAUNCH PLAN: [Product]
=======================
TYPE: [type] | DATE: [date] | TARGET: [metric]
TIMELINE: Week-by-week activities
CHANNEL PLAYBOOKS: Detailed per-channel plans
CONTENT CALENDAR: Pieces with publish dates
LAUNCH DAY CHECKLIST: Hour-by-hour execution
BUDGET: Category allocation
METRICS: KPIs with targets
RISK MITIGATION: Contingency plans
```
Tailor to the user's resources. A solo founder needs a different plan than a funded startup.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".