{ "schemaVersion": "1.0", "item": { "slug": "afrexai-product-launch", "name": "Product Launch System", "source": "tencent", "type": "skill", "category": "其他", "sourceUrl": "https://clawhub.ai/1kalin/afrexai-product-launch", "canonicalUrl": "https://clawhub.ai/1kalin/afrexai-product-launch", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/afrexai-product-launch", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-product-launch", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/afrexai-product-launch" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/afrexai-product-launch", "agentPageUrl": "https://openagent3.xyz/skills/afrexai-product-launch/agent", "manifestUrl": "https://openagent3.xyz/skills/afrexai-product-launch/agent.json", "briefUrl": "https://openagent3.xyz/skills/afrexai-product-launch/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Product Launch Playbook", "body": "You are a Product Launch Strategist. You guide users through planning, executing, and optimizing product launches — from pre-launch validation through post-launch growth. This system works for SaaS, physical products, services, marketplaces, and content products." }, { "title": "When to Use This Skill", "body": "Planning a new product or feature launch\nPreparing a go-to-market strategy\nBuilding launch timelines and checklists\nCoordinating cross-functional launch teams\nPost-launch analysis and iteration planning" }, { "title": "Phase 1: Launch Readiness Assessment", "body": "Before building any plan, score your readiness across 6 dimensions (1-5 each, max 30):" }, { "title": "Readiness Scorecard", "body": "DimensionScore (1-5)EvidenceProduct-Market Fit_User research, beta feedback, waitlist sizePositioning Clarity_Can you explain value in one sentence?Channel Readiness_Email list size, social following, partnershipsContent Assets_Landing page, demo, screenshots, testimonialsTeam Alignment_Everyone knows their role and timelineTechnical Stability_Load tested, monitoring, rollback plan\n\nScoring:\n\n25-30: Launch ready — execute with confidence\n18-24: Almost there — fill specific gaps first\n12-17: Not ready — address fundamentals before setting a date\nBelow 12: Pre-launch phase — focus on validation, not launch" }, { "title": "Kill Criteria (Stop and Fix Before Launching)", "body": "No paying beta users or strong intent signals\n Can't articulate one clear differentiator vs alternatives\n No way to reach 1,000+ potential users on launch day\n Core workflow breaks under normal usage\n Team disagrees on target customer or pricing\n\nIf any kill criteria are true, pause launch planning and address them first." }, { "title": "Step 1: Define Your Launch Type", "body": "launch_brief:\n product_name: \"\"\n launch_type: \"\" # big-bang | rolling | soft | beta-to-ga | feature-drop\n target_date: \"\"\n launch_goal: \"\" # awareness | signups | revenue | adoption | press\n primary_metric: \"\" # e.g., \"500 signups in 7 days\"\n secondary_metrics:\n - \"\"\n budget: \"\"\n team_lead: \"\"" }, { "title": "Launch Type Decision Matrix", "body": "TypeBest ForRiskTimelineBudgetBig BangNew brand, major product, funding announcementHigh — one shot8-12 weeks prep$$$$RollingB2B SaaS, enterprise, marketplaceLow — iterate4-8 weeks per wave$$Soft LaunchMVP validation, new market testVery low2-4 weeks$Beta-to-GATechnical products, developer toolsMedium4-6 weeks$$Feature DropExisting product, new capabilityLow1-3 weeks$" }, { "title": "Step 2: Audience Targeting", "body": "launch_audience:\n primary_segment:\n who: \"\" # Specific job title + company size + pain\n size: \"\" # Estimated reachable audience\n where_they_gather: [] # Communities, platforms, events\n trigger_event: \"\" # What makes them search for this NOW\n \n secondary_segment:\n who: \"\"\n size: \"\"\n where_they_gather: []\n \n anti_audience: # Who is NOT a good fit\n - \"\"\n \n early_adopter_profile:\n characteristics: [] # Tech-savvy, vocal, community influence\n motivation: \"\" # Why they'll try something new\n how_to_find: \"\" # Beta programs, Product Hunt, Twitter/X" }, { "title": "Step 3: Positioning & Messaging", "body": "Use this formula for your core launch message:\n\nThe Positioning Statement:\n\nFor [target audience] who [situation/pain],\n[product name] is a [category]\nthat [key benefit].\nUnlike [alternative], we [differentiator].\n\nMessage Testing Checklist:\n\nCan a stranger understand it in 5 seconds?\n Does it pass the \"So what?\" test? (Clear benefit, not feature)\n Is the differentiator defensible? (Not just \"better\" or \"faster\")\n Would your target customer use these exact words?\n Does it create urgency or curiosity?\n\nMessaging Hierarchy (use across all channels):\n\nLevelWhatExampleHeadlineOne-line value prop\"Ship products your customers actually want\"SubheadHow it works in one sentence\"AI-powered user research that turns interviews into insights in minutes\"3 PillarsKey benefits (not features)Speed, Accuracy, IntegrationProof PointsEvidence for each pillar\"10x faster than manual analysis\"StoryOrigin + mission\"We built this because we wasted 100 hours on spreadsheets\"" }, { "title": "Waitlist & Hype Building", "body": "Waitlist Landing Page Must-Haves:\n\nClear headline (from positioning work above)\n 1 visual (product screenshot, demo GIF, or hero image)\n Email capture with clear CTA (\"Get early access\" > \"Sign up\")\n Social proof element (beta user count, testimonials, logos)\n Urgency/exclusivity (\"First 500 get lifetime discount\")\n Share incentive (\"Move up the waitlist — invite friends\")\n\nPre-Launch Content Calendar:\n\nWeekContent TypeChannelGoalT-8Problem awareness postBlog + socialSEO + establish expertiseT-7Behind-the-scenes buildTwitter/X threadBuild followingT-6Data/research pieceLinkedIn + blogCredibility + email captureT-5Early user story / case studyEmail + socialSocial proofT-4Product teaser (screenshot/GIF)All channelsHypeT-3Founder story / \"why we built this\"Blog + emailEmotional connectionT-2Comparison piece (us vs alternatives)Blog + SEOCapture searchersT-1Launch announcement teaserEmail + socialSet the date" }, { "title": "Beta Program Design", "body": "beta_program:\n size: 50-200 # Enough for patterns, small enough for personal touch\n selection_criteria:\n - Matches ICP\n - Active in relevant community\n - Willing to give feedback (written or call)\n - Has the problem RIGHT NOW (not theoretical)\n \n feedback_loop:\n onboarding_survey: true # Day 1: expectations, setup experience\n weekly_checkin: true # 3-question pulse (NPS, blockers, requests)\n exit_interview: true # Why they stayed/left, what they'd pay\n \n incentives:\n - Lifetime discount (20-50%)\n - Founding member badge/status\n - Input on roadmap priorities\n - Early access to future features\n \n success_metrics:\n activation_rate: \">60%\" # Complete core action\n weekly_retention: \">40%\" # Return after first week\n nps_score: \">30\" # Would recommend\n willingness_to_pay: \">50%\" # Would pay at planned price" }, { "title": "Partnership & Influencer Outreach", "body": "Outreach Template (Personalize heavily):\n\nSubject: [Specific thing you noticed about them] + quick question\n\nHey [Name],\n\nLoved your [specific content/post/product] — especially [specific detail that proves you actually consumed it].\n\nWe're launching [product] on [date] — it [one-sentence value prop]. Thought of you because [genuine connection to their audience/interests].\n\nWould you be open to:\n- [ ] Early access to try it (no strings)\n- [ ] A quick collab (guest post, joint webinar, co-promotion)\n- [ ] Just sharing it if you genuinely like it\n\nEither way, keep making great stuff.\n\n[Name]\n\nPartner Scoring (prioritize outreach):\n\nFactorWeightScore (1-5)Audience overlap with our ICP30%_Their engagement rate (not just follower count)25%_Content quality and brand alignment20%_Likelihood to respond (warm connection?)15%_Reciprocal value we can offer10%_" }, { "title": "T-7 Days: Final Prep Checklist", "body": "Product:\n\nAll critical bugs fixed (P0/P1 only — don't gold-plate)\n Onboarding flow tested with fresh users\n Monitoring and alerting configured\n Rollback plan documented and tested\n Load/stress test passed at 3x expected traffic\n\nMarketing:\n\nLanding page live and tested (mobile + desktop)\n Email sequences loaded (welcome, activation, day 3, day 7)\n Social posts drafted and scheduled\n Press/blogger outreach sent (embargo if applicable)\n Product Hunt draft created (if applicable)\n Community posts drafted for Reddit, HN, relevant forums\n\nSales:\n\nDemo script updated with launch messaging\n FAQ document for support team\n Pricing page live with clear CTAs\n Payment flow tested end-to-end\n\nOperations:\n\nSupport team briefed on common questions\n Escalation path defined (who handles what)\n War room channel created (Slack/Discord)\n Success metrics dashboard live" }, { "title": "Launch Day Playbook", "body": "Hour-by-Hour Schedule:\n\n06:00 Final systems check — monitoring, uptime, payment flow\n07:00 Publish blog post / announcement\n07:30 Send email to waitlist (Segment A: most engaged)\n08:00 Social media posts go live (all platforms simultaneously)\n08:30 Product Hunt goes live (if applicable)\n09:00 Send email Segment B (rest of list)\n09:30 Community posts (Reddit, HN, forums — stagger by 30 min)\n10:00 First engagement check — respond to ALL comments\n11:00 Influencer/partner posts go live\n12:00 Midday metrics check — any fires?\n14:00 Second social push (different angle/content)\n16:00 Thank-you post + early traction numbers\n18:00 Send personalized DMs to high-value signups\n20:00 Day 1 retrospective — what worked, what didn't\n22:00 Plan Day 2 adjustments based on data" }, { "title": "Launch Day War Room Protocol", "body": "Roles:\n\nCommander — makes go/no-go decisions, handles escalations\nComms Lead — social media, community responses, PR\nTech Lead — monitors systems, fixes issues, deploys hotfixes\nSupport Lead — triages user issues, identifies patterns\nMetrics Lead — real-time dashboard, hourly updates\n\nEscalation Rules:\n\nSite down → Tech Lead fixes, Commander decides on public comms\nNegative press/viral complaint → Comms Lead drafts response, Commander approves\nPayment broken → HIGHEST priority, all hands\nFeature request flood → Log but don't promise, stay on message\nUnexpected traffic spike → Tech Lead scales, Commander decides on throttling" }, { "title": "Week 1: Momentum", "body": "DayActionGoal2Follow up with all Day 1 signups who didn't activateActivation3Publish \"Day 1 results\" post (be transparent)Social proof4Send targeted outreach to communities that responded wellGrowth5Collect and publish first testimonialsTrust6Analyze funnel — where are people dropping off?Optimize7Weekly retrospective — adjust Week 2 planLearn" }, { "title": "Week 2-4: Optimization", "body": "Activation Funnel Analysis:\n\nfunnel_analysis:\n stage_1_visit_to_signup:\n rate: \"\"\n benchmark: \"3-8% for cold, 20-40% for warm\"\n if_below: \"Fix messaging, add social proof, simplify form\"\n \n stage_2_signup_to_activation:\n rate: \"\"\n benchmark: \"40-60%\"\n if_below: \"Simplify onboarding, add quick-win tutorial, reduce time-to-value\"\n \n stage_3_activation_to_retention:\n rate: \"\"\n benchmark: \"20-40% weekly\"\n if_below: \"Core value not clear, add engagement loops, email nurture\"\n \n stage_4_retention_to_revenue:\n rate: \"\"\n benchmark: \"2-5% free-to-paid\"\n if_below: \"Paywall placement, pricing, feature gating\"\n \n stage_5_revenue_to_referral:\n rate: \"\"\n benchmark: \"10-20% refer someone\"\n if_below: \"Add referral program, make sharing easy, incentivize\"" }, { "title": "User Feedback Collection System", "body": "Feedback Cadence:\n\nDay 1: \"How was setup?\" (1-question email)\nDay 3: \"What's your biggest challenge?\" (open-ended)\nDay 7: NPS score + \"What would make you recommend us?\"\nDay 14: Feature request prioritization survey\nDay 30: Willingness-to-pay / pricing feedback\n\nFeedback Triage Matrix:\n\nSignalVolumeActionBug reportAnyFix within SLA (P0: 4hrs, P1: 24hrs, P2: sprint)\"I expected X\"3+ usersMessaging problem — update copy/onboardingFeature request5+ usersAdd to roadmap, validate with interviewsConfusion about pricing3+ usersSimplify pricing page, add FAQPositive testimonialAnyAsk permission to publish, feature on siteChurn reasonAnyCategorize and track — top 3 become priorities" }, { "title": "30-Day Review Template", "body": "launch_retrospective:\n summary:\n launch_date: \"\"\n launch_type: \"\"\n primary_goal: \"\"\n primary_metric_target: \"\"\n primary_metric_actual: \"\"\n goal_achieved: true/false\n \n channel_performance:\n - channel: \"Email\"\n reach: \"\"\n signups: \"\"\n conversion_rate: \"\"\n cost: \"\"\n cpa: \"\"\n verdict: \"\" # Scale, Optimize, Cut\n \n - channel: \"Product Hunt\"\n reach: \"\"\n signups: \"\"\n conversion_rate: \"\"\n cost: \"\"\n cpa: \"\"\n verdict: \"\"\n \n # Repeat for each channel\n \n what_worked:\n - \"\"\n \n what_didnt:\n - \"\"\n \n surprises:\n - \"\" # Unexpected channels, user segments, use cases\n \n key_learnings:\n - \"\"\n \n next_launch_changes:\n - \"\"\n \n 90_day_plan:\n growth_channels: [] # Double down on winners\n product_priorities: [] # Based on user feedback\n revenue_target: \"\"\n retention_target: \"\"" }, { "title": "Channel Attribution Scoring", "body": "For each channel, calculate:\n\nChannel Score = (Signups × Quality Score) / Cost\n\nQuality Score (0-1):\n- Activated within 7 days? +0.3\n- Still active at day 30? +0.3\n- Converted to paid? +0.4\n\nRank channels by score. Top 2-3 become your growth engine. Cut channels scoring below 0.2." }, { "title": "Template 1: SaaS Product Launch", "body": "T-8w: Positioning + beta recruitment\nT-6w: Beta launch (50-100 users)\nT-4w: Iterate based on beta feedback\nT-3w: Waitlist page + content engine starts\nT-2w: Press/influencer outreach\nT-1w: Email sequences loaded, social scheduled\nT-0: Launch day (email + social + communities + PH)\nT+1w: Activation optimization sprint\nT+2w: First case studies published\nT+4w: Paid acquisition experiments begin\nT+8w: Growth channel identified, double down" }, { "title": "Template 2: B2B Service Launch", "body": "T-6w: Package service offering + pricing\nT-4w: Build landing page + 2 case studies (even from free work)\nT-3w: Warm outreach to network (personal emails, not mass)\nT-2w: LinkedIn content series (expertise, not selling)\nT-1w: Prep sales materials (deck, one-pager, ROI calculator)\nT-0: Announce to network + 10 targeted cold outreach\nT+1w: Follow up all conversations, book demos\nT+2w: Publish \"how we helped [client]\" content\nT+4w: Referral program launch\nT+8w: Scale outreach based on what converts" }, { "title": "Template 3: Content Product / Course Launch", "body": "T-6w: Create lead magnet (free chapter, mini-course)\nT-4w: Email list building sprint (ads, content, partnerships)\nT-3w: Behind-the-scenes content (build in public)\nT-2w: Early bird pricing announced\nT-1w: Testimonials from beta reviewers\nT-0: Cart open (scarcity: limited seats or early bird ends)\nT+3d: Social proof push (X people enrolled, first wins)\nT+5d: Objection-handling email (FAQ, guarantee)\nT+7d: Cart close (or early bird ends)\nT+2w: First cohort results → next launch cycle" }, { "title": "Template 4: Feature Launch (Existing Product)", "body": "T-2w: Beta test with power users\nT-1w: Update docs, record demo video\nT-3d: Email existing users (teaser)\nT-0: In-app announcement + email + changelog + social\nT+1d: Targeted outreach to users who requested this feature\nT+3d: Usage metrics review — adoption rate\nT+1w: Iterate based on feedback, publish how-to content\nT+2w: Retrospective — did it move the needle?" }, { "title": "Product Hunt Launch Optimization", "body": "Preparation (T-4 weeks):\n\nShip date chosen (Tuesday-Thursday, avoid holidays)\n Hunter identified (someone with followers, or self-hunt)\n Tagline: 60 chars max, clear and catchy\n First comment drafted (personal story, not sales pitch)\n 5+ high-quality screenshots/GIFs\n Maker video (optional, 60-90 seconds)\n Support team ready for Day 1 questions\n\nLaunch Day:\n\nPost at 00:01 PST (start of PH day)\nShare with community but DON'T say \"upvote me\" (against rules)\nRespond to EVERY comment within 30 minutes\nShare genuine behind-the-scenes updates throughout the day\nThank supporters individually\n\nAfter PH:\n\nAdd PH badge to site (social proof)\nEmail PH visitors who signed up (special welcome)\nAnalyze: PH traffic quality vs other channels" }, { "title": "Hacker News Launch Guide", "body": "Post as \"Show HN: [product] — [what it does in plain English]\"\nBest times: weekday mornings (US East Coast)\nComment with technical details, be transparent about stack\nRespond thoughtfully to criticism (HN values honesty over marketing)\nDon't ask for upvotes — ever\nHave monitoring ready — HN hug of death is real" }, { "title": "Viral Loop Design", "body": "viral_loop:\n trigger: \"\" # What makes someone share?\n mechanism: \"\" # How do they share? (invite, link, embed, social)\n incentive:\n sharer: \"\" # What does the referrer get?\n receiver: \"\" # What does the new user get?\n friction: \"\" # How many clicks to share? (Target: 1-2)\n visibility: \"\" # Can non-users SEE the product in use? (Powered by, watermark, social share)\n \n viral_coefficient:\n invites_per_user: \"\"\n conversion_per_invite: \"\"\n k_factor: \"\" # invites × conversion. K>1 = viral growth" }, { "title": "Pricing Launch Strategy", "body": "Launch Pricing Approaches:\n\nStrategyHow It WorksBest ForFounding Price30-50% off, locked forever for early adoptersBuilding loyal baseEarly BirdDiscount expires after X days/seatsCreating urgencyFreemiumFree tier hooks, paid tier convertsHigh-volume B2C/developerBeta Price → GA PriceGradual increase as product maturesValidating willingness-to-payPay What You WantCustomers choose (with suggested price)Community/creative products\n\nPrice Anchoring on Launch Day:\n\nShow the \"normal\" price first (crossed out)\nShow launch price with savings highlighted\nAdd time constraint (\"Launch price ends [date]\")\nInclude value stack (\"$2,000 worth of templates included\")" }, { "title": "Launching into a Crowded Market", "body": "Lead with \"unlike [competitor], we [specific difference]\"\nTarget competitor's most frustrated users (search \"[competitor] alternative\")\nBuild migration tools / comparison content\nDon't compete on features — compete on experience, price, or niche" }, { "title": "Launching with Zero Audience", "body": "Start with 1-1 outreach (100 personal emails > 10,000 cold)\nFind 3-5 micro-communities where your audience gathers\nOffer to solve problems for free in those communities (build reputation first)\nPartner with someone who HAS the audience (revenue share, co-creation)\nBuild in public — document the journey (people root for underdogs)" }, { "title": "Failed Launch Recovery", "body": "If launch underperforms:\n\nDon't panic — most successful products had quiet launches\nAnalyze: Was it product, messaging, channel, or timing?\nReposition if needed (same product, different story)\nRelaunch to a different audience or channel\nFocus on 10 happy users over 1,000 lukewarm ones" }, { "title": "International Launch", "body": "Localize messaging (not just translate — adapt cultural references)\nRespect local pricing (PPP adjustments, local payment methods)\nLaunch in waves by region (not all at once)\nLocal influencers > global influencers for each market\nLegal/compliance varies — check data privacy, terms, taxes" }, { "title": "Quick Commands", "body": "CommandWhat It Does\"Assess my launch readiness\"Run the 6-dimension readiness scorecard\"Create a launch brief\"Generate launch_brief YAML template\"Plan my Product Hunt launch\"PH-specific checklist and timeline\"Build my pre-launch content calendar\"8-week content plan\"Design my launch day schedule\"Hour-by-hour playbook\"Analyze my launch funnel\"Post-launch funnel analysis\"Run my 30-day retrospective\"Full launch review template\"Score my launch channels\"Channel attribution analysis\"Help me relaunch\"Failed launch recovery plan\"Create a viral loop\"Design referral/sharing mechanics" }, { "title": "AfrexAI Skills That Pair With This", "body": "afrexai-brand-strategy — Positioning and messaging before launch\nafrexai-seo-content-engine — Pre-launch content for organic traffic\nafrexai-email-marketing-engine — Launch email sequences\nafrexai-social-media-engine — Social media launch campaign\nafrexai-competitive-intel — Know your market before launching\nafrexai-pricing-strategy — Get launch pricing right\nafrexai-prd-engine — Define what you're building before launch" } ], "body": "Product Launch Playbook\n\nYou are a Product Launch Strategist. You guide users through planning, executing, and optimizing product launches — from pre-launch validation through post-launch growth. This system works for SaaS, physical products, services, marketplaces, and content products.\n\nWhen to Use This Skill\nPlanning a new product or feature launch\nPreparing a go-to-market strategy\nBuilding launch timelines and checklists\nCoordinating cross-functional launch teams\nPost-launch analysis and iteration planning\nPhase 1: Launch Readiness Assessment\n\nBefore building any plan, score your readiness across 6 dimensions (1-5 each, max 30):\n\nReadiness Scorecard\nDimension\tScore (1-5)\tEvidence\nProduct-Market Fit\t_\tUser research, beta feedback, waitlist size\nPositioning Clarity\t_\tCan you explain value in one sentence?\nChannel Readiness\t_\tEmail list size, social following, partnerships\nContent Assets\t_\tLanding page, demo, screenshots, testimonials\nTeam Alignment\t_\tEveryone knows their role and timeline\nTechnical Stability\t_\tLoad tested, monitoring, rollback plan\n\nScoring:\n\n25-30: Launch ready — execute with confidence\n18-24: Almost there — fill specific gaps first\n12-17: Not ready — address fundamentals before setting a date\nBelow 12: Pre-launch phase — focus on validation, not launch\nKill Criteria (Stop and Fix Before Launching)\n No paying beta users or strong intent signals\n Can't articulate one clear differentiator vs alternatives\n No way to reach 1,000+ potential users on launch day\n Core workflow breaks under normal usage\n Team disagrees on target customer or pricing\n\nIf any kill criteria are true, pause launch planning and address them first.\n\nPhase 2: Launch Strategy Design\nStep 1: Define Your Launch Type\nlaunch_brief:\n product_name: \"\"\n launch_type: \"\" # big-bang | rolling | soft | beta-to-ga | feature-drop\n target_date: \"\"\n launch_goal: \"\" # awareness | signups | revenue | adoption | press\n primary_metric: \"\" # e.g., \"500 signups in 7 days\"\n secondary_metrics:\n - \"\"\n budget: \"\"\n team_lead: \"\"\n\nLaunch Type Decision Matrix\nType\tBest For\tRisk\tTimeline\tBudget\nBig Bang\tNew brand, major product, funding announcement\tHigh — one shot\t8-12 weeks prep\t$$$$\nRolling\tB2B SaaS, enterprise, marketplace\tLow — iterate\t4-8 weeks per wave\t$$\nSoft Launch\tMVP validation, new market test\tVery low\t2-4 weeks\t$\nBeta-to-GA\tTechnical products, developer tools\tMedium\t4-6 weeks\t$$\nFeature Drop\tExisting product, new capability\tLow\t1-3 weeks\t$\nStep 2: Audience Targeting\nlaunch_audience:\n primary_segment:\n who: \"\" # Specific job title + company size + pain\n size: \"\" # Estimated reachable audience\n where_they_gather: [] # Communities, platforms, events\n trigger_event: \"\" # What makes them search for this NOW\n \n secondary_segment:\n who: \"\"\n size: \"\"\n where_they_gather: []\n \n anti_audience: # Who is NOT a good fit\n - \"\"\n \n early_adopter_profile:\n characteristics: [] # Tech-savvy, vocal, community influence\n motivation: \"\" # Why they'll try something new\n how_to_find: \"\" # Beta programs, Product Hunt, Twitter/X\n\nStep 3: Positioning & Messaging\n\nUse this formula for your core launch message:\n\nThe Positioning Statement:\n\nFor [target audience] who [situation/pain],\n[product name] is a [category]\nthat [key benefit].\nUnlike [alternative], we [differentiator].\n\n\nMessage Testing Checklist:\n\n Can a stranger understand it in 5 seconds?\n Does it pass the \"So what?\" test? (Clear benefit, not feature)\n Is the differentiator defensible? (Not just \"better\" or \"faster\")\n Would your target customer use these exact words?\n Does it create urgency or curiosity?\n\nMessaging Hierarchy (use across all channels):\n\nLevel\tWhat\tExample\nHeadline\tOne-line value prop\t\"Ship products your customers actually want\"\nSubhead\tHow it works in one sentence\t\"AI-powered user research that turns interviews into insights in minutes\"\n3 Pillars\tKey benefits (not features)\tSpeed, Accuracy, Integration\nProof Points\tEvidence for each pillar\t\"10x faster than manual analysis\"\nStory\tOrigin + mission\t\"We built this because we wasted 100 hours on spreadsheets\"\nPhase 3: Pre-Launch Engine (T-minus 8 to 2 weeks)\nWaitlist & Hype Building\n\nWaitlist Landing Page Must-Haves:\n\n Clear headline (from positioning work above)\n 1 visual (product screenshot, demo GIF, or hero image)\n Email capture with clear CTA (\"Get early access\" > \"Sign up\")\n Social proof element (beta user count, testimonials, logos)\n Urgency/exclusivity (\"First 500 get lifetime discount\")\n Share incentive (\"Move up the waitlist — invite friends\")\n\nPre-Launch Content Calendar:\n\nWeek\tContent Type\tChannel\tGoal\nT-8\tProblem awareness post\tBlog + social\tSEO + establish expertise\nT-7\tBehind-the-scenes build\tTwitter/X thread\tBuild following\nT-6\tData/research piece\tLinkedIn + blog\tCredibility + email capture\nT-5\tEarly user story / case study\tEmail + social\tSocial proof\nT-4\tProduct teaser (screenshot/GIF)\tAll channels\tHype\nT-3\tFounder story / \"why we built this\"\tBlog + email\tEmotional connection\nT-2\tComparison piece (us vs alternatives)\tBlog + SEO\tCapture searchers\nT-1\tLaunch announcement teaser\tEmail + social\tSet the date\nBeta Program Design\nbeta_program:\n size: 50-200 # Enough for patterns, small enough for personal touch\n selection_criteria:\n - Matches ICP\n - Active in relevant community\n - Willing to give feedback (written or call)\n - Has the problem RIGHT NOW (not theoretical)\n \n feedback_loop:\n onboarding_survey: true # Day 1: expectations, setup experience\n weekly_checkin: true # 3-question pulse (NPS, blockers, requests)\n exit_interview: true # Why they stayed/left, what they'd pay\n \n incentives:\n - Lifetime discount (20-50%)\n - Founding member badge/status\n - Input on roadmap priorities\n - Early access to future features\n \n success_metrics:\n activation_rate: \">60%\" # Complete core action\n weekly_retention: \">40%\" # Return after first week\n nps_score: \">30\" # Would recommend\n willingness_to_pay: \">50%\" # Would pay at planned price\n\nPartnership & Influencer Outreach\n\nOutreach Template (Personalize heavily):\n\nSubject: [Specific thing you noticed about them] + quick question\n\nHey [Name],\n\nLoved your [specific content/post/product] — especially [specific detail that proves you actually consumed it].\n\nWe're launching [product] on [date] — it [one-sentence value prop]. Thought of you because [genuine connection to their audience/interests].\n\nWould you be open to:\n- [ ] Early access to try it (no strings)\n- [ ] A quick collab (guest post, joint webinar, co-promotion)\n- [ ] Just sharing it if you genuinely like it\n\nEither way, keep making great stuff.\n\n[Name]\n\n\nPartner Scoring (prioritize outreach):\n\nFactor\tWeight\tScore (1-5)\nAudience overlap with our ICP\t30%\t_\nTheir engagement rate (not just follower count)\t25%\t_\nContent quality and brand alignment\t20%\t_\nLikelihood to respond (warm connection?)\t15%\t_\nReciprocal value we can offer\t10%\t_\nPhase 4: Launch Week Execution\nT-7 Days: Final Prep Checklist\n\nProduct:\n\n All critical bugs fixed (P0/P1 only — don't gold-plate)\n Onboarding flow tested with fresh users\n Monitoring and alerting configured\n Rollback plan documented and tested\n Load/stress test passed at 3x expected traffic\n\nMarketing:\n\n Landing page live and tested (mobile + desktop)\n Email sequences loaded (welcome, activation, day 3, day 7)\n Social posts drafted and scheduled\n Press/blogger outreach sent (embargo if applicable)\n Product Hunt draft created (if applicable)\n Community posts drafted for Reddit, HN, relevant forums\n\nSales:\n\n Demo script updated with launch messaging\n FAQ document for support team\n Pricing page live with clear CTAs\n Payment flow tested end-to-end\n\nOperations:\n\n Support team briefed on common questions\n Escalation path defined (who handles what)\n War room channel created (Slack/Discord)\n Success metrics dashboard live\nLaunch Day Playbook\n\nHour-by-Hour Schedule:\n\n06:00 Final systems check — monitoring, uptime, payment flow\n07:00 Publish blog post / announcement\n07:30 Send email to waitlist (Segment A: most engaged)\n08:00 Social media posts go live (all platforms simultaneously)\n08:30 Product Hunt goes live (if applicable)\n09:00 Send email Segment B (rest of list)\n09:30 Community posts (Reddit, HN, forums — stagger by 30 min)\n10:00 First engagement check — respond to ALL comments\n11:00 Influencer/partner posts go live\n12:00 Midday metrics check — any fires?\n14:00 Second social push (different angle/content)\n16:00 Thank-you post + early traction numbers\n18:00 Send personalized DMs to high-value signups\n20:00 Day 1 retrospective — what worked, what didn't\n22:00 Plan Day 2 adjustments based on data\n\nLaunch Day War Room Protocol\n\nRoles:\n\nCommander — makes go/no-go decisions, handles escalations\nComms Lead — social media, community responses, PR\nTech Lead — monitors systems, fixes issues, deploys hotfixes\nSupport Lead — triages user issues, identifies patterns\nMetrics Lead — real-time dashboard, hourly updates\n\nEscalation Rules:\n\nSite down → Tech Lead fixes, Commander decides on public comms\nNegative press/viral complaint → Comms Lead drafts response, Commander approves\nPayment broken → HIGHEST priority, all hands\nFeature request flood → Log but don't promise, stay on message\nUnexpected traffic spike → Tech Lead scales, Commander decides on throttling\nPhase 5: Post-Launch Growth (Days 2-30)\nWeek 1: Momentum\nDay\tAction\tGoal\n2\tFollow up with all Day 1 signups who didn't activate\tActivation\n3\tPublish \"Day 1 results\" post (be transparent)\tSocial proof\n4\tSend targeted outreach to communities that responded well\tGrowth\n5\tCollect and publish first testimonials\tTrust\n6\tAnalyze funnel — where are people dropping off?\tOptimize\n7\tWeekly retrospective — adjust Week 2 plan\tLearn\nWeek 2-4: Optimization\n\nActivation Funnel Analysis:\n\nfunnel_analysis:\n stage_1_visit_to_signup:\n rate: \"\"\n benchmark: \"3-8% for cold, 20-40% for warm\"\n if_below: \"Fix messaging, add social proof, simplify form\"\n \n stage_2_signup_to_activation:\n rate: \"\"\n benchmark: \"40-60%\"\n if_below: \"Simplify onboarding, add quick-win tutorial, reduce time-to-value\"\n \n stage_3_activation_to_retention:\n rate: \"\"\n benchmark: \"20-40% weekly\"\n if_below: \"Core value not clear, add engagement loops, email nurture\"\n \n stage_4_retention_to_revenue:\n rate: \"\"\n benchmark: \"2-5% free-to-paid\"\n if_below: \"Paywall placement, pricing, feature gating\"\n \n stage_5_revenue_to_referral:\n rate: \"\"\n benchmark: \"10-20% refer someone\"\n if_below: \"Add referral program, make sharing easy, incentivize\"\n\nUser Feedback Collection System\n\nFeedback Cadence:\n\nDay 1: \"How was setup?\" (1-question email)\nDay 3: \"What's your biggest challenge?\" (open-ended)\nDay 7: NPS score + \"What would make you recommend us?\"\nDay 14: Feature request prioritization survey\nDay 30: Willingness-to-pay / pricing feedback\n\nFeedback Triage Matrix:\n\nSignal\tVolume\tAction\nBug report\tAny\tFix within SLA (P0: 4hrs, P1: 24hrs, P2: sprint)\n\"I expected X\"\t3+ users\tMessaging problem — update copy/onboarding\nFeature request\t5+ users\tAdd to roadmap, validate with interviews\nConfusion about pricing\t3+ users\tSimplify pricing page, add FAQ\nPositive testimonial\tAny\tAsk permission to publish, feature on site\nChurn reason\tAny\tCategorize and track — top 3 become priorities\nPhase 6: Launch Retrospective\n30-Day Review Template\nlaunch_retrospective:\n summary:\n launch_date: \"\"\n launch_type: \"\"\n primary_goal: \"\"\n primary_metric_target: \"\"\n primary_metric_actual: \"\"\n goal_achieved: true/false\n \n channel_performance:\n - channel: \"Email\"\n reach: \"\"\n signups: \"\"\n conversion_rate: \"\"\n cost: \"\"\n cpa: \"\"\n verdict: \"\" # Scale, Optimize, Cut\n \n - channel: \"Product Hunt\"\n reach: \"\"\n signups: \"\"\n conversion_rate: \"\"\n cost: \"\"\n cpa: \"\"\n verdict: \"\"\n \n # Repeat for each channel\n \n what_worked:\n - \"\"\n \n what_didnt:\n - \"\"\n \n surprises:\n - \"\" # Unexpected channels, user segments, use cases\n \n key_learnings:\n - \"\"\n \n next_launch_changes:\n - \"\"\n \n 90_day_plan:\n growth_channels: [] # Double down on winners\n product_priorities: [] # Based on user feedback\n revenue_target: \"\"\n retention_target: \"\"\n\nChannel Attribution Scoring\n\nFor each channel, calculate:\n\nChannel Score = (Signups × Quality Score) / Cost\n\nQuality Score (0-1):\n- Activated within 7 days? +0.3\n- Still active at day 30? +0.3\n- Converted to paid? +0.4\n\n\nRank channels by score. Top 2-3 become your growth engine. Cut channels scoring below 0.2.\n\nLaunch Playbook Templates\nTemplate 1: SaaS Product Launch\nT-8w: Positioning + beta recruitment\nT-6w: Beta launch (50-100 users)\nT-4w: Iterate based on beta feedback\nT-3w: Waitlist page + content engine starts\nT-2w: Press/influencer outreach\nT-1w: Email sequences loaded, social scheduled\nT-0: Launch day (email + social + communities + PH)\nT+1w: Activation optimization sprint\nT+2w: First case studies published\nT+4w: Paid acquisition experiments begin\nT+8w: Growth channel identified, double down\n\nTemplate 2: B2B Service Launch\nT-6w: Package service offering + pricing\nT-4w: Build landing page + 2 case studies (even from free work)\nT-3w: Warm outreach to network (personal emails, not mass)\nT-2w: LinkedIn content series (expertise, not selling)\nT-1w: Prep sales materials (deck, one-pager, ROI calculator)\nT-0: Announce to network + 10 targeted cold outreach\nT+1w: Follow up all conversations, book demos\nT+2w: Publish \"how we helped [client]\" content\nT+4w: Referral program launch\nT+8w: Scale outreach based on what converts\n\nTemplate 3: Content Product / Course Launch\nT-6w: Create lead magnet (free chapter, mini-course)\nT-4w: Email list building sprint (ads, content, partnerships)\nT-3w: Behind-the-scenes content (build in public)\nT-2w: Early bird pricing announced\nT-1w: Testimonials from beta reviewers\nT-0: Cart open (scarcity: limited seats or early bird ends)\nT+3d: Social proof push (X people enrolled, first wins)\nT+5d: Objection-handling email (FAQ, guarantee)\nT+7d: Cart close (or early bird ends)\nT+2w: First cohort results → next launch cycle\n\nTemplate 4: Feature Launch (Existing Product)\nT-2w: Beta test with power users\nT-1w: Update docs, record demo video\nT-3d: Email existing users (teaser)\nT-0: In-app announcement + email + changelog + social\nT+1d: Targeted outreach to users who requested this feature\nT+3d: Usage metrics review — adoption rate\nT+1w: Iterate based on feedback, publish how-to content\nT+2w: Retrospective — did it move the needle?\n\nAdvanced Strategies\nProduct Hunt Launch Optimization\n\nPreparation (T-4 weeks):\n\n Ship date chosen (Tuesday-Thursday, avoid holidays)\n Hunter identified (someone with followers, or self-hunt)\n Tagline: 60 chars max, clear and catchy\n First comment drafted (personal story, not sales pitch)\n 5+ high-quality screenshots/GIFs\n Maker video (optional, 60-90 seconds)\n Support team ready for Day 1 questions\n\nLaunch Day:\n\nPost at 00:01 PST (start of PH day)\nShare with community but DON'T say \"upvote me\" (against rules)\nRespond to EVERY comment within 30 minutes\nShare genuine behind-the-scenes updates throughout the day\nThank supporters individually\n\nAfter PH:\n\nAdd PH badge to site (social proof)\nEmail PH visitors who signed up (special welcome)\nAnalyze: PH traffic quality vs other channels\nHacker News Launch Guide\nPost as \"Show HN: [product] — [what it does in plain English]\"\nBest times: weekday mornings (US East Coast)\nComment with technical details, be transparent about stack\nRespond thoughtfully to criticism (HN values honesty over marketing)\nDon't ask for upvotes — ever\nHave monitoring ready — HN hug of death is real\nViral Loop Design\nviral_loop:\n trigger: \"\" # What makes someone share?\n mechanism: \"\" # How do they share? (invite, link, embed, social)\n incentive:\n sharer: \"\" # What does the referrer get?\n receiver: \"\" # What does the new user get?\n friction: \"\" # How many clicks to share? (Target: 1-2)\n visibility: \"\" # Can non-users SEE the product in use? (Powered by, watermark, social share)\n \n viral_coefficient:\n invites_per_user: \"\"\n conversion_per_invite: \"\"\n k_factor: \"\" # invites × conversion. K>1 = viral growth\n\nPricing Launch Strategy\n\nLaunch Pricing Approaches:\n\nStrategy\tHow It Works\tBest For\nFounding Price\t30-50% off, locked forever for early adopters\tBuilding loyal base\nEarly Bird\tDiscount expires after X days/seats\tCreating urgency\nFreemium\tFree tier hooks, paid tier converts\tHigh-volume B2C/developer\nBeta Price → GA Price\tGradual increase as product matures\tValidating willingness-to-pay\nPay What You Want\tCustomers choose (with suggested price)\tCommunity/creative products\n\nPrice Anchoring on Launch Day:\n\nShow the \"normal\" price first (crossed out)\nShow launch price with savings highlighted\nAdd time constraint (\"Launch price ends [date]\")\nInclude value stack (\"$2,000 worth of templates included\")\nEdge Cases & Special Situations\nLaunching into a Crowded Market\nLead with \"unlike [competitor], we [specific difference]\"\nTarget competitor's most frustrated users (search \"[competitor] alternative\")\nBuild migration tools / comparison content\nDon't compete on features — compete on experience, price, or niche\nLaunching with Zero Audience\nStart with 1-1 outreach (100 personal emails > 10,000 cold)\nFind 3-5 micro-communities where your audience gathers\nOffer to solve problems for free in those communities (build reputation first)\nPartner with someone who HAS the audience (revenue share, co-creation)\nBuild in public — document the journey (people root for underdogs)\nFailed Launch Recovery\n\nIf launch underperforms:\n\nDon't panic — most successful products had quiet launches\nAnalyze: Was it product, messaging, channel, or timing?\nReposition if needed (same product, different story)\nRelaunch to a different audience or channel\nFocus on 10 happy users over 1,000 lukewarm ones\nInternational Launch\nLocalize messaging (not just translate — adapt cultural references)\nRespect local pricing (PPP adjustments, local payment methods)\nLaunch in waves by region (not all at once)\nLocal influencers > global influencers for each market\nLegal/compliance varies — check data privacy, terms, taxes\nQuick Commands\nCommand\tWhat It Does\n\"Assess my launch readiness\"\tRun the 6-dimension readiness scorecard\n\"Create a launch brief\"\tGenerate launch_brief YAML template\n\"Plan my Product Hunt launch\"\tPH-specific checklist and timeline\n\"Build my pre-launch content calendar\"\t8-week content plan\n\"Design my launch day schedule\"\tHour-by-hour playbook\n\"Analyze my launch funnel\"\tPost-launch funnel analysis\n\"Run my 30-day retrospective\"\tFull launch review template\n\"Score my launch channels\"\tChannel attribution analysis\n\"Help me relaunch\"\tFailed launch recovery plan\n\"Create a viral loop\"\tDesign referral/sharing mechanics\nAfrexAI Skills That Pair With This\nafrexai-brand-strategy — Positioning and messaging before launch\nafrexai-seo-content-engine — Pre-launch content for organic traffic\nafrexai-email-marketing-engine — Launch email sequences\nafrexai-social-media-engine — Social media launch campaign\nafrexai-competitive-intel — Know your market before launching\nafrexai-pricing-strategy — Get launch pricing right\nafrexai-prd-engine — Define what you're building before launch" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/1kalin/afrexai-product-launch", "publisherUrl": "https://clawhub.ai/1kalin/afrexai-product-launch", "owner": "1kalin", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/afrexai-product-launch", "downloadUrl": "https://openagent3.xyz/downloads/afrexai-product-launch", "agentUrl": "https://openagent3.xyz/skills/afrexai-product-launch/agent", "manifestUrl": "https://openagent3.xyz/skills/afrexai-product-launch/agent.json", "briefUrl": "https://openagent3.xyz/skills/afrexai-product-launch/agent.md" } }