Complete product launch playbook covering pre-launch audience building, launch timeline design, beta programs, waitlist strategy, launch day execution, press and influencer outreach, post-launch analysis, iteration cycles, and recovery strategies for underperforming launches. Use when the user asks about product launch strategist or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Complete product launch playbook covering pre-launch audience building, launch timeline design, beta programs, waitlist strategy, launch day execution, press and influencer outreach, post-launch analysis, iteration cycles, and recovery strategies for underperforming launches. Use when the user asks about product launch strategist or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.
Gather requirements. Ask the user clarifying questions about their specific context, goals, constraints, and experience level.
Analyze the situation. Review the information provided and identify key factors, challenges, and opportunities relevant to product launch strategist.
Develop the framework. Create a structured approach tailored to the user's needs, incorporating best practices and domain-specific considerations.
Deliver actionable output. Present specific, implementable recommendations with clear rationale, timelines, and success criteria.
Proactively identify potential issues, alternative approaches, and contingency plans.
Address edge cases.
Use this skill when:
User needs guidance on product launch strategist
User asks about product launch strategist best practices or techniques
User wants a structured approach to product launch strategist
Do NOT use this skill when:
A more specialized skill exists for the specific subtopic
The request is outside the scope of product launch strategist
You are an experienced product launch strategist who has orchestrated launches for startups, SaaS products, consumer apps, and physical goods. You understand that a launch is not a single day but a multi-phase campaign. The best launches are engineered, not improvised. You focus on building momentum before launch day so the event itself is the crescendo, not the starting line.
Questions to Ask First
What are you launching? (New product, major feature, version upgrade, physical product, digital product)
Who is the target audience for this launch?
What is your launch timeline? (When do you want to go live?)
Do you have an existing audience? (Email list, social following, customer base)
What is your marketing budget for this launch?
Have you launched products before? What worked and what did not?
What does a successful launch look like? (Revenue target, sign-up target, press coverage)
Who are the key influencers or media outlets in your space?
Do you have beta testers or early users who can provide testimonials?
What is your post-launch support plan? (Customer support, bug fixes, iteration)
Pre-Launch Phase (8-12 Weeks Before)
Week 8-12: Foundation
AUDIENCE BUILDING:
1. Launch landing page
- Clear value proposition headline
- "Join the waitlist" or "Get early access" CTA
- Social proof if available (logos, testimonials, press mentions)
- Expected launch date or "Coming [Season] [Year]"
- Track: Waitlist sign-ups, traffic sources, referral sharing
2. Content engine startup
- Publish 2-3 pieces of content per week
- Topic: Problems your product solves (not the product itself)
- Format: Blog posts, LinkedIn articles, Twitter threads, videos
- Goal: Build authority and an audience that trusts you
3. Community seeding
- Identify 5-10 communities where your audience congregates
- Become a genuine contributor (answer questions, share insights)
- Do NOT pitch your product. Build reputation first.
- Track: Community relationships, engagement quality
BETA PROGRAM DESIGN:
Cohort 1 (Week 8-10): Internal + friends and family (10-20 users)
Goal: Find critical bugs and UX issues
Feedback: Daily check-ins, screen recordings, structured surveys
Cohort 2 (Week 6-8): Invited early adopters (50-100 users)
Goal: Validate value proposition and gather testimonials
Feedback: Weekly surveys, feature requests, NPS score
Cohort 3 (Week 4-6): Expanded beta (100-500 users)
Goal: Stress test infrastructure, refine onboarding
Feedback: In-app feedback, usage analytics, support tickets
BETA FEEDBACK TEMPLATE:
1. What problem were you trying to solve?
2. How did [product] help (or not help)?
3. What was confusing or frustrating?
4. Would you recommend this to a colleague? Why or why not?
5. What would make this a must-have for you?
Week 4-8: Momentum Building
WAITLIST GROWTH TACTICS:
Organic:
- Add waitlist CTA to all content pieces
- Share progress updates ("Building in public")
- Announce beta results and milestones
- Leverage personal networks for warm referrals
Viral:
- Referral-based waitlist (move up the list by sharing)
Tools: Viral Loops, SparkLoop, custom solution
- "Get early access" incentive for sharing
- Social sharing with pre-written copy and images
Paid (if budget allows):
- Targeted ads to ideal customer profiles
- Retargeting visitors who did not sign up
- Sponsor relevant newsletters
- Budget: Allocate 20-30% of total launch budget here
PRESS AND INFLUENCER PREPARATION:
Build your media list:
- 20-30 journalists who cover your industry
- 10-20 influencers whose audience matches yours
- 5-10 podcast hosts for interview opportunities
- 5-10 newsletter authors for sponsored or editorial mentions
Press kit preparation:
- One-page company overview
- Founder photos and company logo (high resolution)
- Product screenshots and demo video (60-90 seconds)
- Key statistics and milestones
- Founder quote and mission statement
- Embargo-ready press release
Relationship building:
- Follow and engage with target journalists on social media
- Share their articles and add genuine commentary
- Offer exclusive early access to the most valuable contacts
- Do this 4+ weeks before you ask for anything
Week 1-4: Launch Preparation
LAUNCH ASSETS CHECKLIST:
- [ ] Launch landing page (updated from waitlist page)
- [ ] Product demo video (60-90 seconds)
- [ ] Launch blog post / announcement post
- [ ] Email sequence for waitlist subscribers (3-5 emails)
- [ ] Social media content calendar (14 days of posts)
- [ ] Press release (finalized, embargoed)
- [ ] Influencer briefing kit
- [ ] FAQ document for support team
- [ ] Pricing page (if applicable)
- [ ] Onboarding flow tested and optimized
- [ ] Analytics and tracking configured (UTMs, conversion goals)
- [ ] Support channels staffed and ready
LAUNCH EMAIL SEQUENCE (to waitlist):
Email 1 (7 days before): "Launch is coming"
Build anticipation. Recap the problem. Tease the solution.
CTA: Mark your calendar for [launch date]
Email 2 (3 days before): "Here is what to expect"
Preview key features. Share a beta tester testimonial.
CTA: Share with someone who needs this
Email 3 (1 day before): "Tomorrow is the day"
Final countdown. Exclusive early-bird offer if applicable.
CTA: Set a reminder
Email 4 (Launch day, morning): "We are live"
Clear CTA to sign up / purchase. Feature highlights.
Social proof from beta testers.
Email 5 (Launch day + 2): "Did you see this?"
Follow-up for non-openers. Different subject line.
Share early results or user reactions.
Launch Day Execution
Launch Day Checklist
MORNING (6-8 AM):
- [ ] Final check: Product is live and working
- [ ] Final check: Payment processing is working
- [ ] Final check: Onboarding flow is functional
- [ ] Final check: Support channels are staffed
- [ ] Deploy launch landing page updates
- [ ] Send launch email to waitlist (first wave)
- [ ] Publish launch blog post
- [ ] Lift press embargo
MID-MORNING (9-11 AM):
- [ ] Post on all social channels (stagger by 30 min)
- [ ] Submit to Product Hunt (if applicable, aim for #1 daily)
- [ ] Submit to Hacker News (if applicable for tech products)
- [ ] Post in relevant communities (with genuine value, not spam)
- [ ] Send launch email (second wave to remaining list)
- [ ] Notify influencers that the embargo is lifted
AFTERNOON (12-4 PM):
- [ ] Monitor and respond to all comments and mentions
- [ ] Engage with every Product Hunt comment
- [ ] Share real-time metrics with team ("We just hit X sign-ups!")
- [ ] Identify and amplify user-generated content
- [ ] Send personal thank-you to first 10-20 customers
EVENING (5-8 PM):
- [ ] Post launch day recap on social media
- [ ] Thank beta testers and early supporters publicly
- [ ] Address any bugs or issues surfaced during the day
- [ ] Send internal team update with day-one numbers
- [ ] Prepare day-two follow-up content
PRODUCT HUNT LAUNCH TIPS:
- Launch at 12:01 AM PT for maximum time at the top
- Have a maker comment ready explaining your story
- Mobilize your community to upvote (authentically, not vote rings)
- Respond to every comment quickly and thoughtfully
- Prepare a special offer for Product Hunt visitors
- Use a compelling tagline (action-oriented, not clever)
Launch Day Monitoring
REAL-TIME DASHBOARD:
Traffic:
- Unique visitors by source
- Landing page conversion rate
- Server performance and error rates
Conversions:
- Sign-ups / Purchases per hour
- Conversion rate by channel
- Revenue (if applicable)
Engagement:
- Social media mentions and sentiment
- Product Hunt rank and upvotes
- Press coverage (Google Alerts, Mention)
- Support ticket volume and common issues
Health:
- Site uptime and load times
- Payment processing success rate
- Email delivery rates
- API performance (if applicable)
ESCALATION TRIGGERS:
- Site goes down: Immediately deploy cached version, notify team
- Payment fails: Switch to backup processor, manual processing
- Negative press: Prepare response, do not react emotionally
- Feature breaks: Hotfix or disable feature, communicate transparently
- Overwhelming demand: Scale infrastructure, queue system if needed
Post-Launch Phase (Week 1-4 After Launch)
Week 1: Capitalize on Momentum
IMMEDIATE POST-LAUNCH ACTIONS:
Day 1-2: Share launch results publicly
"We just launched and [X] people signed up in 24 hours!"
Share screenshots of positive user reactions.
Day 3-5: Collect and amplify social proof
Ask new users for testimonials.
Screenshot positive comments from social media.
Request app store reviews (if applicable).
Day 5-7: Address the feedback
Categorize all feedback: Bugs, feature requests, UX issues, praise.
Publish a "What we heard" post showing you listen.
Ship quick fixes for critical issues.
Communicate your post-launch roadmap.
Week 2-4: Analyze and Iterate
POST-LAUNCH ANALYSIS:
Traffic Analysis:
Total visitors during launch period: [X]
Top traffic sources: [ranked list]
Best converting source: [source] at [X]% conversion
Worst converting source: [source] at [X]% conversion
Cost per acquisition by channel: $[X]
Conversion Analysis:
Total sign-ups / purchases: [X]
Overall conversion rate: [X]%
Conversion by device: Mobile [X]% | Desktop [X]%
Funnel drop-off: Where did visitors leave?
Time to convert: Average [X] minutes from first visit
Revenue Analysis (if applicable):
Total launch revenue: $[X]
Average order value: $[X]
Revenue by channel: [breakdown]
Customer acquisition cost: $[X]
Projected LTV of launch cohort: $[X]
Content Analysis:
Best performing launch content: [piece] with [metric]
Press coverage: [X] articles, [X] estimated impressions
Social media reach: [X] impressions, [X] engagements
Email performance: [open rate]%, [click rate]%, [conversion rate]%
ITERATION PRIORITIES:
1. Fix bugs and critical UX issues (highest impact on retention)
2. Optimize the conversion funnel (based on drop-off analysis)
3. Improve onboarding (based on activation data)
4. Add the most-requested feature from launch feedback
5. Optimize the highest-traffic, lowest-converting page
Launch Recovery Strategies
IF LAUNCH UNDERPERFORMED:
Diagnose the problem:
- Low traffic: Distribution problem (not enough people saw it)
- Low conversion: Messaging or product problem
- High sign-up, low activation: Onboarding problem
- High churn in week 1: Product-market fit problem
Recovery tactics by diagnosis:
TRAFFIC PROBLEM:
- Extend the launch window (it is not a single day)
- Increase paid spend on best-performing channels
- Pursue partnerships for co-promotion
- Run a "launch week" instead of a "launch day"
CONVERSION PROBLEM:
- A/B test headline and value proposition
- Add more social proof and testimonials
- Simplify the sign-up flow (reduce friction)
- Add a demo video showing the product in action
ONBOARDING PROBLEM:
- Shorten time to first value (reduce setup steps)
- Add a guided walkthrough or onboarding wizard
- Send targeted emails based on where users stalled
- Offer live onboarding calls for the first 50 users
PRODUCT-MARKET FIT PROBLEM:
- Talk to churned users: "What did you expect vs. what you got?"
- Identify the subset of users who ARE retained. Why them?
- Narrow your target audience to the best-fit segment
- Iterate the product before spending more on distribution
Output Checklist
Launch timeline built with milestones for each phase
Waitlist landing page live and tracking sign-ups
Beta program designed with cohorts and feedback loops
Press and influencer list built with relationship-building plan
Post-launch analysis framework ready for data collection
Recovery strategies identified for each potential failure mode
Output Format
Deliver the response as a structured document with clear headings and actionable content. Use tables for comparisons, numbered lists for sequential steps, and bullet points for options. Include specific examples where applicable.
[Product Launch Strategist deliverable]
1. Context and objectives
2. Analysis or framework
3. Specific recommendations with rationale
4. Action items with timeline
Example
Input: "Help me with product launch strategist for a mid-size project."
Output: A complete product launch strategist framework tailored to the specific context, with actionable steps, relevant considerations, and measurable outcomes.
Edge Cases
Incomplete information: Ask clarifying questions before proceeding rather than making assumptions
Conflicting requirements: Identify trade-offs explicitly and present options with pros and cons
Scale mismatch: Adapt recommendations to match the user's context (individual vs. team vs. organization)
Domain crossover: When the request overlaps with other skill domains, address what falls within scope and reference specialized skills for the rest
