Launch Strategy

openclaudia/openclaudia-skills/skills/launch-strategy

by openclaudia28bf209f393aNo license711 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 2 weeks ago

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

AI-generated overview

Plans product launches with week-by-week timelines, channel playbooks, checklists, budgets and metrics.

What it does
This skill guides an agent through building a product launch plan, from gathering launch context and choosing a launch type through pre-launch, launch week and post-launch phases. It supplies frameworks for positioning, waitlist growth, beta programs, social proof and technical readiness, plus channel playbooks for Product Hunt, Hacker News, Twitter, LinkedIn and Reddit. It produces a structured launch plan covering timeline, channel playbooks, content calendar, hour-by-hour launch day checklist, budget allocation, metrics with targets and risk mitigation.
When to use it
Use it when someone asks for a product launch plan, go-to-market strategy, Product Hunt or Hacker News launch preparation, a beta program, pre-launch marketing or post-launch growth. It fits founders and teams planning a new product, feature or update launch.
Requirements
No scripts or special tooling; it is instructions only. It works from information the user provides about the product, audience, timeline, budget and team.

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

TypeTimelineAudienceBest For
Stealth/AlphaOngoing10-50 hand-pickedValidating concept
Closed Beta2-4 weeks50-500 invitedRefining, testimonials
Open Beta2-4 weeksAnyoneWaitlist buzz, stress test
Soft Launch1 weekExisting audienceLow-risk iteration
Full Public1 day (4-8 week prep)EveryoneMaximum impact, PR
Rolling4-8 weeksPhased accessManage 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

PhaseMetricTarget
Pre-LaunchWaitlist sign-ups[goal]
Pre-LaunchWaitlist CR20-40%
Pre-LaunchBeta activation60%+
Launch DaySign-ups[goal]
Launch DayPH rankTop 5
Post-LaunchActivation rate40%+
Post-LaunchD1/D7/D30 retention60%/30%/15%+
Post-LaunchTrial-to-paid10-25%
Post-LaunchNPS40+

Track channel attribution by quality (activation rate, retention, LTV), not just volume.

Step 7: Budget Allocation

Category%Activities
Content20-25%Video, blog, graphics
Paid Acquisition30-40%Social ads, search ads, sponsorships
PR/Outreach10-15%Media, influencers
Tools5-10%Email, analytics, hosting
Reserve10-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 activitiesCHANNEL PLAYBOOKS: Detailed per-channel plansCONTENT CALENDAR: Pieces with publish datesLAUNCH DAY CHECKLIST: Hour-by-hour executionBUDGET: Category allocationMETRICS: KPIs with targetsRISK MITIGATION: Contingency plans

Tailor to the user's resources. A solo founder needs a different plan than a funded startup.

Source and attribution

Source:openclaudia/openclaudia-skillsinskills/launch-strategyat commit28bf209

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal