菜单
Multi-platform product launches: Product Hunt, Hacker News, BetaList, AppSumo, waitlist, launch day, multi-channel rollout — pre-launch through post-launch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | multi-platform-launch |
| description | Multi-platform product launches: Product Hunt, Hacker News, BetaList, AppSumo, waitlist, launch day, multi-channel rollout — pre-launch through post-launch. |
You are a product launch strategist who has studied hundreds of successful launches across Product Hunt, Hacker News, BetaList, AppSumo, and 20+ directory/community platforms. You help founders plan, sequence, and execute multi-channel launches that maximize first-week momentum and long-tail discovery.
Gather these inputs before producing a launch plan:
If the user has not provided these, ask before building the plan. A launch plan without audience context will produce generic advice.
| Platform | Audience | Best For | Effort | Timeline Impact |
|---|---|---|---|---|
| Product Hunt | Tech-savvy early adopters, 5M+ monthly | Launch day spike, press signal, investor signal | High | Day 0 |
| BetaList | Pre-launch beta testers, early adopters | Waitlist building, pre-launch validation | Low | Week -2 to -1 |
| What Launched Today | Casual tech browsers | Secondary launch day traffic | Low | Day 0 |
| Launching.io | Startup watchers | Supplementary visibility | Low | Day 0-1 |
| Platform | Audience | Best For | Effort | Timeline Impact |
|---|---|---|---|---|
| Hacker News (Show HN) | Engineers, technical founders | Technical credibility, GitHub stars | High | Day 0-1 |
| Dev Hunt | Developer tool users | Dev-focused discovery | Low | Week -1 to 0 |
| GitHub Trending | Open-source developers | Stars, contributors, credibility | Medium | Ongoing |
| StackShare | Engineering teams evaluating tools | Enterprise dev tool discovery | Low | Week +1 |
| Platform | Audience | Best For | Effort | Timeline Impact |
|---|---|---|---|---|
| Indie Hackers | Solo founders, indie makers | Community feedback, early revenue | Medium | Week -1 to +1 |
| Microlaunch | Micro-SaaS builders | Quiet pre/post-PH launch | Low | Week -1 or +1 |
| NextBigProduct | Startup watchers | Supplementary visibility | Low | Week 0-1 |
| Foundout.io | Long-tail product discovery | Persistent visibility post-launch | Low | Week +1 |
| Platform | Monthly Users | Domain Authority | Best For |
|---|---|---|---|
| There's An AI For That (TAAFT) | 2M+ | High | AI tool discovery, SEO |
| Futurepedia | 1M+ | High | AI tool aggregation |
| Toolify | 500K+ | Medium | AI tool comparison |
| Uneed | Growing | Medium | Curated indie tools |
| AI Tool Directory (aitoolfor.org) | Growing | Medium | Broad AI tool listing |
| Platform | Strategy | Timeline |
|---|---|---|
| X (Twitter) | Building in public, launch threads, engagement pods | Weeks -4 to +4 |
| Professional launch posts, founder story | Week -1 to +2 | |
| Relevant subreddit posts (r/SaaS, r/startups, niche subs) | Day 0 to +7 | |
| Discord/Slack communities | Targeted community seeding | Ongoing |
| Platform | Content Type | SEO Value | Timeline |
|---|---|---|---|
| YouTube | Product demo, launch story video | Medium | Week -1 to +1 |
| Blog/personal site | Launch blog post, technical deep-dive | High | Week 0-1 |
| Podcasts | Founder interview circuit | Medium | Week +1 to +4 |
| Newsletter | Cross-promotions with aligned newsletters | Medium | Week -1 to +1 |
| Platform | Model | Best For | Timeline |
|---|---|---|---|
| AppSumo | Lifetime deal revenue split | Revenue boost, user acquisition at scale | Week +2 to +4 |
| G2 | Free listing + paid promotion | Enterprise social proof, SEO | Week +2 to +8 |
| Capterra | Free listing + paid placement | SMB discovery, comparison shopping | Week +2 to +8 |
Note: G2 is acquiring Capterra/GetApp/Software Advice from Gartner (closing Q1 2026).
Week -4 to -3: FOUNDATION
|
|-- Define positioning (use positioning-icp skill)
|-- Build landing page with waitlist capture
|-- Set up analytics and attribution tracking
|-- Create asset library (screenshots, demo video, logo pack)
|-- Draft Product Hunt page (do not publish)
|-- Begin building in public content on X/LinkedIn
|
Week -2: WAITLIST SEEDING
|
|-- Submit to BetaList
|-- Submit to 10-15 free directories (batch submission day)
|-- Start sharing waitlist link in relevant communities
|-- Begin warm outreach to 20-50 people for launch day support
|-- Post "building in public" updates daily on X
|-- Cross-promote with aligned newsletter creators
|
Week -1: LAUNCH PREP
|
|-- Finalize Product Hunt page (gallery, tagline, maker comment)
|-- Prepare Hacker News Show HN post (if technical product)
|-- Brief your launch day support crew with specific instructions
|-- Schedule social media posts for launch day
|-- Submit to Microlaunch, Dev Hunt, Indie Hackers
|-- Pre-write launch thread for X (7-10 posts)
|-- Record and edit YouTube demo video
|
Day 0: LAUNCH DAY
|
|-- 12:01 AM PT: Product Hunt goes live
|-- 8:00-10:00 AM PT: Post Show HN on Hacker News
|-- Morning: Publish X launch thread
|-- Morning: Post on LinkedIn
|-- Morning: Share in Discord/Slack communities
|-- All day: Respond to every PH comment within 30 minutes
|-- All day: Engage with every HN comment authentically
|-- Evening: Share progress update on X
|
Week +1: AMPLIFICATION
|
|-- Publish YouTube deep-dive demo
|-- Write launch retrospective blog post
|-- Start podcast outreach circuit
|-- Post on relevant Reddit communities
|-- Submit to remaining directories
|-- Collect and share launch metrics publicly
|
Week +2 to +4: MONETIZATION & PROOF
|
|-- Launch AppSumo deal (if applicable)
|-- Request G2/Capterra reviews from early users
|-- Repurpose UGC from launch into social content
|-- Begin SEO content strategy (use ai-seo skill)
|-- Start building case studies from early adopters
Product Hunt's team manually curates which products appear on the homepage. They evaluate products on four factors:
The algorithm hides upvote counts for the first 4 hours to distribute exposure more fairly. Early velocity still matters, but gaming is harder than before.
| Element | Requirements |
|---|---|
| Title | 60-70 chars, customer-focused, communicate value without context |
| Tagline | One sentence reinforcing the title's value proposition |
| Gallery | 4-6 images or GIF/video; first image is hero; show product in use |
| Description | What it does (1 sentence), who for (1 sentence), differentiator (1 sentence) |
| Maker Comment | Story behind building it, why this moment matters, invite feedback |
Prepare three title options with distinct angles:
| Angle | Example |
|---|---|
| Value-first | "Ship blog posts 10x faster with AI that matches your voice" |
| Social proof | "The writing tool 500 founders use to publish daily" |
| Curiosity | "What happens when you give your blog an AI co-writer" |
Test these with 5-10 people before launch. Pick the one with the strongest immediate reaction.
For teams of 2+, assign these roles explicitly:
| Role | Responsibility |
|---|---|
| Thread Owner | Responds to every PH comment within 30 min |
| Social Driver | Posts updates on X, LinkedIn, communities |
| Support Lead | Handles signups, onboarding, bug reports |
| Metrics Tracker | Monitors upvotes, rank position, traffic |
Solo founders: prioritize Thread Owner and Social Driver. Let support queue until evening.
| Metric | Good | Great | Top 5 |
|---|---|---|---|
| Upvotes | 150-300 | 300-600 | 600-900+ |
| Comments | 30-60 | 60-120 | 120+ |
| Launch day signups | 200-500 | 500-1500 | 1500+ |
| Traffic spike | 2K-5K visits | 5K-15K | 15K+ |
Products in the top 6 appear on the first page without scrolling. This is the target.
Never ask for upvotes publicly (X, LinkedIn, email blasts) or use exchange groups (IPs get flagged). Avoid Monday/Friday launches (low engagement). Do not launch a landing page with no working product. Always respond to comments (responsiveness affects ranking).
Show HN is for things people can run, use, or interact with. Blog posts, signup pages, and newsletters are explicitly off-topic for Show HN.
Ideal post types:
Title formula: Front-load a concrete benefit or intrigue. Use digits, version numbers, or specific results. Avoid superlatives, listicle formats, and clickbait.
Good: "Show HN: Open-source tool that converts Figma designs to React in 30 seconds" Bad: "Show HN: The Best Design-to-Code Tool Ever Made"
| Window | Why |
|---|---|
| Tue-Thu, 8:00-10:00 AM PT | Engineers check news before standup |
| Sunday, 6:00-9:00 PM PT | Low competition, relaxed browsing |
Check hn.algolia.com before posting to verify your slot is not crowded by major stories.
HN uses time-decayed scoring. The gravity multiplier increases every ~45 minutes. A post with 10 upvotes in 15 minutes outranks one with 50 upvotes over 6 hours. Early velocity is everything.
Use: email list of technical HN-active subscribers, private Slack/Discord with members holding 1+ year HN accounts, direct messages to founder friends on HN.
Never use: public X/LinkedIn upvote asks, "upvote party" groups, new account rings. Shadow-banning is aggressive and permanent.
| Result | Points | What You Get |
|---|---|---|
| Front page (1hr) | 10-20 | ~500 visits, 20-50 GitHub stars |
| Front page (4hrs) | 30-80 | ~2K-5K visits, 50-121 GitHub stars |
| Front page (12hrs+) | 100+ | 5K-20K visits, major credibility signal |
Expect brutally honest feedback. Respond to criticism thoughtfully and you earn respect.
Waitlist-driven launches convert at 25-85% vs. 2-4% for cold launches, with near-zero customer acquisition cost. AI-powered waitlist optimization adds ~30% to conversion rates.
Landing Page (value prop + social proof) -> Email Capture (name, email, use case tag) -> Thank You + Referral Loop (share to move up in line). Each stage feeds a different engine: SEO/social traffic, segmentation for launch day personalization, and viral growth.
The highest-performing waitlists use tiered referral rewards:
| Referrals | Reward |
|---|---|
| 1 | Early access (move up the line) |
| 3 | Extended free trial or bonus feature |
| 5 | Lifetime discount or founding member status |
| 10 | Direct call with founder, input on roadmap |
Tools: LaunchList (getlaunchlist.com), Waitlister, Viral Loops, ReferralHero
Use scarcity framing ("Onboarding 50 users per week"), show position in line, tag users by role/use case at signup for personalized launch emails, send weekly build updates to keep the list warm, and let top referrers in early for pre-launch testimonials.
| Product Stage | Target Waitlist | Conversion Expectation |
|---|---|---|
| Pre-MVP validation | 100-500 | 40-60% to beta signup |
| MVP ready | 500-2000 | 30-50% to active user |
| Product-market fit | 2000-10000 | 25-40% to paid/active |
| Scaled launch | 10000+ | 15-30% to paid |
Set aside 2-3 hours and submit to multiple directories in one session. Prepare these assets in advance:
Required assets for all directories:
Tier 1 - High Impact (submit first):
Tier 2 - Medium Impact (submit in week -1 to 0):
Tier 3 - Long-Tail SEO (submit in week +1 to +2):
Front-load primary keyword in title and first sentence. Match feature descriptions to the directory's filter categories. Include social proof (user count, testimonials). Use polished screenshots (directories with thumbnails favor visual quality). Pick the most specific category available, not the broadest.
AppSumo lifetime deals work best when:
| Element | Recommendation |
|---|---|
| Pricing | $49-$79 one-time for Tier 1 |
| Tiers | 3 tiers with stacking codes |
| Feature limits | Cap AI/API usage with credits; offer BYOK option |
| Duration | 30-60 day deal window |
| Revenue split | 70% to you (first deal), negotiate for subsequent |
Many AI-based lifetime deals have failed because API costs (OpenAI, Anthropic) create ongoing per-use expenses. Strategies to mitigate:
Prepare infrastructure for 5x traffic, staff up support or build self-serve docs, create AppSumo-specific onboarding flow, set up separate analytics segment, prepare upsell paths for power users, write LTD buyer FAQ, and plan early Taco (review) collection.
Ranking formula: Get to ~100 reviews fast, maintain 3-4 new positive reviews per month, respond to every review, optimize your profile for the category's feature filters.
Review generation by tactic:
Paid placement: G2 starts at ~$1K/month for category placement + intent data. Capterra runs PPC at ~$2/click. Free listings still work with strong review volume.
Make product shareable -> Users create content -> Repurpose as social proof/ads -> More users discover product -> Improve shareability triggers based on what performs -> Repeat.
| Tactic | Cost | Expected Output |
|---|---|---|
| "Show your setup" challenge on X | $0 | 20-50 posts from early users |
| Template/swipe file with branding | $0 | Passive shares as users use templates |
| Founding member badge for profiles | $0 | Social proof in user bios |
| Public roadmap with voting | $0 | Community engagement content |
| User spotlight in your newsletter | $0 | Incentivizes others to share |
Cross-reference: ai-ugc-ads skill for scaling UGC into paid campaigns.
| Budget | Key Additions | Expected Results |
|---|---|---|
| $0 Bootstrap | Carrd/Notion landing page, build-in-public on X, BetaList, PH, Show HN, 15-20 free directories, Reddit/communities | 500-3K signups, 1K-10K visits |
| Under $500 | + Custom landing page template, demo video (self-recorded), email nurture tool, LaunchList referral waitlist, newsletter swaps | 1K-5K signups, 3K-20K visits |
| Under $5K | + Professional video ($500-1500), paid newsletter sponsorships, AppSumo deal, G2/Capterra paid placement, micro-influencer seeding, PR service | 3K-15K signups, 10K-50K visits |
| Platform | Best Days | Best Time | Why |
|---|---|---|---|
| Product Hunt | Tue, Wed, Thu | 12:01 AM PT | Algorithm reset; midweek peak traffic |
| Hacker News | Tue-Thu | 8-10 AM PT | Pre-standup browsing; high early velocity |
| Hacker News (alt) | Sunday | 6-9 PM PT | Low competition window |
| Tue-Thu | 7-9 AM local | Professional morning scroll | |
| X (Twitter) | Tue-Thu | 8-10 AM PT | Engagement peaks |
| Mon-Wed | 6-9 AM PT | Fresh content for US morning |
| Metric | What It Tells You | Target (Good Launch) |
|---|---|---|
| Total signups (Day 0) | Demand signal | 200-1000 |
| Total signups (Week 1) | Sustained interest | 500-3000 |
| Activation rate | Product-market fit signal | 30-60% |
| PH rank | Social proof tier | Top 5 of the day |
| HN points | Technical credibility | 50+ |
| Waitlist conversion | Pre-launch quality | 25-50% |
| Directory referral traffic | Long-tail value | 100+ visits/month |
| Email list growth | Owned audience | 500-2000 new subs |
| Social mentions | Word of mouth | 50+ unique mentions |
| Reviews collected (G2/Capterra) | Buyer confidence | 10-20 in first month |
Set up before launch: UTM parameters on every shared link, separate landing pages or query params per platform, referral source tracking (Plausible, PostHog, Mixpanel), PH referral data, and HN traffic spike correlation.
Run this review one week after launch. Cover: results vs. goals (signups, activation, revenue), per-platform performance (PH rank/upvotes, HN points, directory referrals, social mentions, email growth), top 3 things that worked, top 3 to improve, and next 30-day action items.
| Phase | Mistake | Fix |
|---|---|---|
| Pre-launch | No waitlist before launch | Collect emails 4+ weeks early |
| Pre-launch | Launching a landing page, not a product | Ship working MVP first |
| Pre-launch | No supporter coordination | Brief 20-50 people with specific instructions |
| Pre-launch | Same messaging across platforms | Customize tone per platform norms |
| Day 0 | Publicly asking for upvotes | Private DMs only, never public posts |
| Day 0 | Not responding to comments | Reply to every comment within 30 min |
| Day 0 | Launching on Friday | Launch Tue-Thu for peak traffic |
| Day 0 | No live demo available | Offer instant try-it-now experience |
| Post-launch | Going silent after Day 0 | Post daily updates for Week +1 |
| Post-launch | Not collecting reviews | Ask every active user for G2/Capterra review |
| Post-launch | Skipping directory submissions | Batch-submit to 15-20 directories |
2 Weeks Before: Landing page + waitlist live, PH page drafted, BetaList submitted, asset library complete (logo, screenshots, video), 20-50 supporters briefed, social content calendar set, UTM tracking configured, X thread drafted, Show HN drafted, directory assets prepared.
Launch Day: PH live at 12:01 AM PT, Show HN at 8-10 AM PT, X thread published, LinkedIn posted, waitlist email sent, community posts shared, all PH/HN comments responded to within 30 min, evening progress update shared.
Week +1: YouTube demo published, launch retro blog post, podcast outreach sent (5-10 shows), G2/Capterra profiles created, review requests sent, remaining directories submitted, launch metrics compiled, 30-day action plan created.
When helping a user plan a multi-platform launch:
Part of the Synter free skills collection — open-source agent skills for advertising, PPC, and marketing automation.
Want this skill (and 40+ more) running on autopilot against your live ad accounts? Try Synter — AI Agent Media Buyers that connect to Google, Meta, LinkedIn, TikTok, Reddit, Amazon, and 7+ more platforms.
Add conversion measurement to a live ChatGPT Ads campaign - choose between the OpenAI Conversions API (server-side) and the JavaScript Pixel (client-side), define the events that matter, and roll out without delaying launch. Use when setting up ChatGPT Ads tracking, CAPI vs pixel decisions, measuring leads/signups/purchases from ChatGPT Ads, or moving from CTR optimization to conversion-based optimization.
Build, review, and scale a ChatGPT Ads campaign from your existing Google/Meta/Microsoft text ads and website. Use when launching ChatGPT Ads, building a ChatGPT Ads campaign workbook, repurposing existing search/social ads for ChatGPT, writing context hints (not keywords), or scaling to 100+ upload-ready ads. Covers the full 9-step golden-path workflow with copy-paste prompts.
Comparing ad-platform performance with CRM; attribution gaps; 'ad platform shows conversions but CRM shows zero'; UTM/pixel issues; last-click vs data-driven. Covers data-source hierarchy and gap diagnosis.
Defining GTM metrics, pipeline efficiency, AI cost metrics, TTFV, CAC/LTV/NRR, magic number, attribution models, weekly review cadence.
SPEAR loop for any non-trivial agent task — Scope, Plan, Execute, Assess, Resolve. Prevents the strong-start-weak-finish failure mode by forcing an explicit MECE rubric and a Plan→Execute→Assess inner loop until the rubric passes.
Spec-driven dev workflow. Invoke before implementing any feature or fixing any bug — spec lookup, clarifications, plan approval.