multi-platform-launch

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Multi-Platform Launch Skill

多平台产品上线技能

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.

你是一位产品上线策略师，研究过Product Hunt、Hacker News、BetaList、AppSumo及20余个目录/社区平台上的数百次成功上线案例。你帮助创始人规划、排序并执行多渠道上线方案，以最大化首周增长势头和长尾曝光效果。

Before Starting

前期准备

Gather these inputs before producing a launch plan:

Product type - SaaS, dev tool, AI tool, marketplace, mobile app, physical product
Target buyer - developers, SMB owners, enterprise, creators, consumers
Current assets - existing audience size, email list, social following, community
Launch goal - signups, revenue, press, backlinks, community building, fundraising signal
Timeline - how many weeks until desired launch date
Budget - $0 bootstrap, <$500 indie, <$5K startup, $5K+ funded
Team size - solo founder, 2-3 person team, full team with marketing

If the user has not provided these, ask before building the plan. A launch plan without audience context will produce generic advice.

在制定上线计划前，请收集以下信息：

产品类型 - SaaS、开发工具、AI工具、交易平台、移动应用、实体产品
目标用户 - 开发者、中小企业主、企业客户、创作者、普通消费者
现有资源 - 现有受众规模、邮件列表、社交媒体粉丝、社区群体
上线目标 - 用户注册、营收增长、媒体报道、反向链接、社区建设、融资信号
时间规划 - 距离预期上线日还有几周时间
预算情况 - 0美元启动、500美元以内独立开发者、5000美元以内初创企业、5000美元以上融资企业
团队规模 - 独立创始人、2-3人团队、配备营销人员的完整团队

如果用户未提供以上信息，请先询问再制定计划。缺乏受众背景的上线计划只会产生通用建议。

Platform Landscape (2025-2026)

平台生态（2025-2026）

Discovery Platforms

发现类平台

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

平台	受众群体	适用场景	投入精力	时间影响
Product Hunt	精通技术的早期采用者，月活500万+	上线日流量爆发、媒体关注信号、投资者关注信号	高	上线当日
BetaList	上线前测试用户、早期采用者	构建等待列表、上线前验证	低	上线前2周至1周
What Launched Today	休闲科技浏览者	上线日次级流量补充	低	上线当日
Launching.io	初创企业关注者	额外曝光机会	低	上线当日至次日

Developer Platforms

开发者平台

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

平台	受众群体	适用场景	投入精力	时间影响
Hacker News (Show HN)	工程师、技术创始人	技术可信度、GitHub星标	高	上线当日至次日
Dev Hunt	开发工具用户	开发者专属曝光	低	上线前1周至上线当日
GitHub Trending	开源开发者	星标、贡献者、可信度	中	持续进行
StackShare	评估工具的工程团队	企业级开发工具发现	低	上线后1周

Indie/Founder Platforms

独立开发者/创始人平台

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

平台	受众群体	适用场景	投入精力	时间影响
Indie Hackers	独立创始人、独立开发者	社区反馈、早期营收	中	上线前1周至上线后1周
Microlaunch	微型SaaS开发者	Product Hunt前后的低调上线	低	上线前1周或上线后1周
NextBigProduct	初创企业关注者	额外曝光机会	低	上线当日至次日
Foundout.io	长尾产品发现	上线后持续曝光	低	上线后1周

AI/Tech Directories

AI/科技目录

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

平台	月活用户	域名权重	适用场景
There's An AI For That (TAAFT)	200万+	高	AI工具发现、SEO
Futurepedia	100万+	高	AI工具聚合
Toolify	50万+	中	AI工具对比
Uneed	增长中	中	精选独立工具
AI Tool Directory (aitoolfor.org)	增长中	中	全品类AI工具收录

Social Channels

社交渠道

Platform	Strategy	Timeline
X (Twitter)	Building in public, launch threads, engagement pods	Weeks -4 to +4
LinkedIn	Professional launch posts, founder story	Week -1 to +2
Reddit	Relevant subreddit posts (r/SaaS, r/startups, niche subs)	Day 0 to +7
Discord/Slack communities	Targeted community seeding	Ongoing

平台	策略	时间范围
X (Twitter)	公开构建、上线线程、参与互动小组	上线前4周至上线后4周
LinkedIn	专业上线帖子、创始人故事	上线前1周至上线后2周
Reddit	相关子版块发帖（r/SaaS、r/startups、垂直子版块）	上线当日至上线后7天
Discord/Slack社区	定向社区渗透	持续进行

Content Channels

内容渠道

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

平台	内容类型	SEO价值	时间范围
YouTube	产品演示、上线故事视频	中	上线前1周至上线后1周
博客/个人网站	上线博客文章、技术深度解析	高	上线当日至次日
播客	创始人访谈巡回	中	上线后1周至4周
通讯邮件	与匹配的通讯作者交叉推广	中	上线前1周至上线后1周

Paid/Review Platforms

付费/评价平台

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

平台	模式	适用场景	时间范围
AppSumo	终身套餐营收分成	营收提升、规模化用户获取	上线后2周至4周
G2	免费收录+付费推广	企业级社交证明、SEO	上线后2周至8周
Capterra	免费收录+付费展位	中小企业发现、对比选购	上线后2周至8周

注：G2正从Gartner手中收购Capterra/GetApp/Software Advice（预计2026年第一季度完成）。

Launch Sequence Framework

上线流程框架

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

第-4至-3周：基础准备
  |
  |-- 明确产品定位（使用positioning-icp技能）
  |-- 搭建带等待列表捕获功能的落地页
  |-- 配置分析与归因追踪工具
  |-- 创建资产库（截图、演示视频、Logo包）
  |-- 起草Product Hunt页面内容（暂不发布）
  |-- 开始在X（Twitter）/LinkedIn上发布"公开构建"内容
  |
第-2周：等待列表种子用户积累
  |
  |-- 提交至BetaList
  |-- 批量提交至10-15个免费目录（批量提交日）
  |-- 在相关社区分享等待列表链接
  |-- 开始向20-50人进行预热 outreach，请求上线日支持
  |-- 每天在X上发布"公开构建"更新
  |-- 与目标受众匹配的通讯作者进行交叉推广
  |
第-1周：上线准备
  |
  |-- 完善Product Hunt页面（图片库、标语、开发者留言）
  |-- 准备Hacker News Show HN帖子（若为技术类产品）
  |-- 向上线日支持团队提供具体操作指引
  |-- 预约上线日的社交媒体发布内容
  |-- 提交至Microlaunch、Dev Hunt、Indie Hackers
  |-- 预先撰写X上的上线线程（7-10条帖子）
  |-- 录制并剪辑YouTube演示视频
  |
上线当日：
  |
  |-- 太平洋时间00:01：Product Hunt上线
  |-- 太平洋时间08:00-10:00：在Hacker News发布Show HN帖子
  |-- 上午：发布X上线线程
  |-- 上午：在LinkedIn发布上线内容
  |-- 上午：在Discord/Slack社区分享
  |-- 全天：30分钟内回复所有Product Hunt评论
  |-- 全天：真诚回复所有Hacker News评论
  |-- 晚上：在X上分享进度更新
  |
上线后第1周：曝光放大
  |
  |-- 发布YouTube深度演示视频
  |-- 撰写上线回顾博客文章
  |-- 开始播客访谈 outreach
  |-- 在相关Reddit社区发布内容
  |-- 提交至剩余目录平台
  |-- 公开分享上线数据
  |
上线后第2至4周：变现与信任构建
  |
  |-- 启动AppSumo合作（若适用）
  |-- 请求早期用户在G2/Capterra上留下评价
  |-- 将上线期间的用户生成内容（UGC）重新用于社交媒体内容
  |-- 启动SEO内容策略（使用ai-seo技能）
  |-- 开始从早期采用者中打造案例研究

Product Hunt Deep Dive

Product Hunt深度解析

How the 2025-2026 Algorithm Works

2025-2026年算法机制

Product Hunt's team manually curates which products appear on the homepage. They evaluate products on four factors:

Useful - solves a real problem
Distinctive - clearly different from existing solutions
User-Friendly - polished, easy to try
Complete - feels like a finished product, not a landing page

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.

Product Hunt团队会手动筛选出现在首页的产品，评估基于四个因素：

实用性 - 解决真实问题
独特性 - 与现有解决方案有明显差异
易用性 - 打磨完善、易于试用
完整性 - 感觉是成品，而非仅落地页

算法会在最初4小时隐藏点赞数，以更公平地分配曝光。早期增长速度仍很重要，但相比以前更难刷量。

Product Hunt Launch Page Anatomy

Product Hunt上线页面结构

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

元素	要求
标题	60-70字符，以客户为中心，无需额外背景即可传达价值
标语	一句话强化标题的价值主张
图片库	4-6张图片或GIF/视频；首张为封面图；展示产品实际使用场景
描述	功能介绍（1句话）、目标用户（1句话）、差异化优势（1句话）
开发者留言	产品背后的故事、为何选择此时上线、邀请用户反馈

Title Strategy: Three Variants

标题策略：三种变体

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.

准备三个不同角度的标题选项：

角度	示例
价值优先	"匹配你的写作风格，用AI让博客发布速度提升10倍"
社交证明	"500位创始人每天用来发布内容的写作工具"
好奇心驱动	"给博客配备AI协作伙伴会发生什么？"

上线前请5-10人测试，选择反应最强烈的标题。

Launch Day Execution Roles

上线日执行角色分配

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.

对于2人以上团队，明确分配以下角色：

角色	职责
评论负责人	30分钟内回复所有Product Hunt评论
社交运营负责人	在X、LinkedIn、社区发布更新
支持负责人	处理注册、新用户引导、Bug反馈
数据追踪负责人	监控点赞数、排名、流量

独立创始人：优先承担评论负责人和社交运营负责人职责，支持请求可延后至晚上处理。

Performance Benchmarks (2025)

2025年性能基准

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.

指标	良好	优秀	当日Top5
点赞数	150-300	300-600	600-900+
评论数	30-60	60-120	120+
上线当日注册数	200-500	500-1500	1500+
流量峰值	2000-5000访问量	5000-15000访问量	15000+访问量

当日排名前6的产品无需滚动即可出现在首页，这是核心目标。

What to Avoid on Product Hunt

Product Hunt上线禁忌

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

切勿公开请求点赞（X、LinkedIn、邮件群发）或使用点赞交换群组（IP会被标记）。避免周一/周五上线（参与度低）。不要仅上线落地页而无可用产品。务必回复所有评论（回复速度会影响排名）。

Hacker News (Show HN) Deep Dive

Hacker News (Show HN)深度解析

What Works on HN

HN上的有效内容

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:

Live demo with no signup required
Open-source tool with GitHub repo
Technical deep-dive with benchmarks
Novel approach to a known problem

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"

Show HN适用于用户可以运行、使用或互动的内容。博客文章、注册页、通讯邮件明确属于Show HN的非相关内容。

理想内容类型：

无需注册的在线演示
带GitHub仓库的开源工具
带基准测试的技术深度解析
针对已知问题的新颖解决方案

标题公式： 前置具体收益或悬念，使用数字、版本号或具体结果。避免最高级、列表格式和标题党。

优秀示例："Show HN: 开源工具，30秒内将Figma设计转换为React代码" 糟糕示例："Show HN: 史上最佳设计转代码工具"

Timing

发布时机

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.

时间段	原因
周二至周四，太平洋时间08:00-10:00	工程师在站会前查看新闻
周日，太平洋时间18:00-21:00	竞争少，用户浏览更放松

发布前请查看hn.algolia.com，确保你的发布时段未被重大新闻占据。

Algorithm Mechanics

算法机制

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.

HN使用时间衰减评分，重力乘数约每45分钟增加一次。15分钟内获得10个点赞的帖子，排名超过6小时内获得50个点赞的帖子。早期增长速度是关键。

Early Upvote Sources (Legitimate)

合法早期点赞来源

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.

可使用：活跃在HN上的技术用户邮件列表、成员拥有1年以上HN账号的私人Slack/Discord群组、HN上创始人朋友的直接私信。

切勿使用：公开的X/LinkedIn点赞请求、"点赞派对"群组、新账号刷赞。影子封禁惩罚严厉且永久。

HN Performance Benchmarks

HN性能基准

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.

结果	点数	收益
首页停留1小时	10-20	~500访问量，20-50个GitHub星标
首页停留4小时	30-80	~2000-5000访问量，50-121个GitHub星标
首页停留12小时以上	100+	5000-20000访问量，重大可信度信号

请准备好接受极其坦诚的反馈。若能深思熟虑地回应批评，你将赢得尊重。

Waitlist Building Playbook

等待列表构建手册

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.

基于等待列表的上线转化率为25-85%，而冷启动转化率仅为2-4%，且客户获取成本几乎为零。AI驱动的等待列表优化可将转化率提升约30%。

Waitlist Architecture

等待列表架构

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.

落地页（价值主张+社交证明）-> 邮箱捕获（姓名、邮箱、使用场景标签）-> 感谢页+推荐循环（分享可提升排队顺位）。每个阶段对应不同引擎：SEO/社交流量、上线日个性化细分、病毒式增长。

Referral-Based Waitlist 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

表现最佳的等待列表采用分层推荐奖励：

推荐人数	奖励
1人	提前访问（提升排队顺位）
3人	延长免费试用或额外功能
5人	终身折扣或创始成员身份
10人	与创始人直接通话、参与路线图制定

工具：LaunchList (getlaunchlist.com)、Waitlister、Viral Loops、ReferralHero

Waitlist Conversion Tactics

等待列表转化技巧

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.

使用稀缺性话术（"每周仅接纳50位用户"）、显示用户在队列中的位置、注册时按角色/使用场景标记用户以实现上线日邮件个性化、每周发送产品构建更新以保持用户热度、允许顶级推荐者提前进入以获取上线前 testimonial。

Waitlist Size Benchmarks

等待列表规模基准

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

产品阶段	目标等待列表规模	转化预期
MVP前验证	100-500人	40-60%转化为测试用户注册
MVP就绪	500-2000人	30-50%转化为活跃用户
产品-市场匹配	2000-10000人	25-40%转化为付费/活跃用户
规模化上线	10000+人	15-30%转化为付费用户

Directory Submission Strategy

目录提交策略

Batch Submission Approach

批量提交方法

Set aside 2-3 hours and submit to multiple directories in one session. Prepare these assets in advance:

Required assets for all directories:

Product name and one-line description (< 100 chars)
Full description (150-300 words, keyword-rich)
Logo (square, 512x512 PNG minimum)
3-5 product screenshots (1280x800 or larger)
Product URL
Category tags (3-5 relevant categories)
Pricing info (free tier, pricing page URL)
Founder/maker social profiles

预留2-3小时，一次性提交至多个目录。提前准备以下资产：

所有目录通用必填资产：

产品名称和一句话描述（<100字符）
完整描述（150-300字，含关键词）
Logo（方形，最小512x512 PNG）
3-5张产品截图（1280x800或更大）
产品URL
分类标签（3-5个相关分类）
定价信息（免费版、定价页URL）
创始人/开发者社交账号

Directory Tiers

目录层级

Tier 1 - High Impact (submit first):

Product Hunt
Hacker News (Show HN)
There's An AI For That (for AI products)
Futurepedia (for AI products)
G2 / Capterra
BetaList

Tier 2 - Medium Impact (submit in week -1 to 0):

Indie Hackers
Dev Hunt (developer tools)
Microlaunch
Toolify (AI tools)
Uneed
AlternativeTo

Tier 3 - Long-Tail SEO (submit in week +1 to +2):

SaaSHub
StackShare
Crunchbase
GetApp / Software Advice
Awesome lists on GitHub (for open source)
Niche-specific directories for your category

一级 - 高影响力（优先提交）：

Product Hunt
Hacker News (Show HN)
There's An AI For That（AI产品适用）
Futurepedia（AI产品适用）
G2 / Capterra
BetaList

二级 - 中影响力（上线前1周至上线当日提交）：

Indie Hackers
Dev Hunt（开发工具适用）
Microlaunch
Toolify（AI工具适用）
Uneed
AlternativeTo

三级 - 长尾SEO（上线后1周至2周提交）：

SaaSHub
StackShare
Crunchbase
GetApp / Software Advice
GitHub上的Awesome列表（开源产品适用）
垂直领域专属目录

Directory Listing Optimization

目录列表优化

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.

在标题和第一句前置核心关键词，匹配目录的筛选分类来描述功能，包含社交证明（用户数量、testimonial），使用高质量截图（带缩略图的目录更青睐视觉效果），选择最具体的分类而非最宽泛的分类。

AppSumo Launch Strategy

AppSumo上线策略

When to Use AppSumo

何时使用AppSumo

AppSumo lifetime deals work best when:

You need a cash injection for development ($10K-$100K+ in first month is common)
You want to rapidly grow your user base for social proof
Your product has low marginal cost per user (not per-API-call AI tools)
You can handle a sudden spike in support volume
You have upsell paths beyond the lifetime tier

AppSumo终身套餐最适合以下场景：

需要现金注入用于开发（首月通常可获得1万-10万美元+收入）
希望快速扩大用户规模以获取社交证明
产品的单用户边际成本低（非按API调用计费的AI工具）
能够处理突发的支持请求量增长
拥有终身套餐之外的向上销售路径

When to Avoid AppSumo

何时避免AppSumo

Your product has high per-user marginal costs (heavy API usage, compute)
You cannot handle 500-2000+ new users in a week
You have no upsell or expansion revenue model
You are pre-product-market-fit (LTD users give loud feedback on unfinished products)

产品单用户边际成本高（大量API调用、计算资源）
无法在一周内处理500-2000+新用户
没有向上销售或扩展收入模式
尚未达到产品-市场匹配（终身套餐用户会对未完成产品给出强烈负面反馈）

AppSumo Deal Structure

AppSumo套餐结构

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

元素	建议
定价	一级套餐一次性收费49-79美元
套餐层级	3个层级，叠加优惠码
功能限制	对AI/API使用量设置额度，提供BYOK（自带密钥）选项
套餐周期	30-60天
营收分成	首次套餐70%归你方，后续可协商

AI Tool Considerations (2025-2026)

AI工具注意事项（2025-2026）

Many AI-based lifetime deals have failed because API costs (OpenAI, Anthropic) create ongoing per-use expenses. Strategies to mitigate:

Credit bundles - Include monthly credit refresh, not unlimited usage
BYOK (Bring Your Own Key) - Let users connect their own API keys
Usage tiers - Cap usage per plan tier with clear limits
Annual refresh - Structure as "lifetime access with annual credit renewal"

许多AI终身套餐失败的原因是API成本（OpenAI、Anthropic）带来持续的每使用次费用。缓解策略：

额度包 - 包含每月额度刷新，而非无限使用
BYOK（自带密钥） - 允许用户连接自己的API密钥
使用量层级 - 按套餐层级设置使用量上限，明确告知用户
年度刷新 - 结构为"终身访问+年度额度更新"

AppSumo Launch Checklist

AppSumo上线 checklist

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.

准备可承载5倍流量的基础设施，扩充支持人员或搭建自助文档，创建AppSumo专属新用户引导流程，设置独立分析细分，为高级用户准备向上销售路径，撰写终身套餐购买者FAQ，计划早期Taco（评价）收集。

G2 and Capterra Strategy

G2和Capterra策略

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:

Post-support-resolution email: 15-25% response rate
In-app prompt after milestone: 10-20% response rate
Incentivized review (G2 gift card program): 20-30% response rate

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.

排名公式： 快速获取约100条评价，每月保持3-4条新的正面评价，回复所有评价，针对分类的功能筛选优化你的资料。

评价获取策略及响应率：

售后解决邮件：15-25%响应率
里程碑完成后应用内提示：10-20%响应率
激励性评价（G2礼品卡计划）：20-30%响应率

付费展位： G2分类展位+意向数据起价约1000美元/月。Capterra按点击付费，约2美元/点击。若评价数量足够多，免费列表仍有效。

UGC-Only Growth: $0 Ad Spend Scaling

仅靠UGC增长：0广告支出规模化

The UGC Launch Flywheel

UGC上线飞轮

Make product shareable -> Users create content -> Repurpose as social proof/ads -> More users discover product -> Improve shareability triggers based on what performs -> Repeat.

让产品易于分享 -> 用户创建内容 -> 重新用作社交证明/广告 -> 更多用户发现产品 -> 根据表现优化分享触发点 -> 重复循环。

Making Your Product Shareable

让产品易于分享

Screenshot-worthy UI - Design moments users want to share (results screens, dashboards)
Built-in sharing triggers - "Share your results" buttons, public profile pages
Template the format - Create a repeatable content format users can fill in
Badge/certification outputs - Generate shareable badges users display in bios/websites
Before/after framing - Show transformation that creates "how did you do that?" reactions

值得截图的UI - 设计用户想要分享的时刻（结果页面、仪表盘）
内置分享触发 - "分享你的结果"按钮、公开个人主页
模板化格式 - 创建用户可填充的可重复内容格式
徽章/认证输出 - 生成用户可在个人简介/网站展示的可分享徽章
前后对比框架 - 展示转变效果，引发"你是怎么做到的？"的反应

UGC Performance Benchmarks (2025)

2025年UGC性能基准

UGC ads get 4x higher click-through rates vs. branded ads
UGC costs 30-80% less than influencer marketing
Brands report $4 return for every $1 invested in UGC programs
50% lower cost-per-click on UGC-based paid campaigns

UGC广告的点击率是品牌广告的4倍
UGC成本比网红营销低30-80%
品牌报告每投入1美元在UGC项目上，可获得4美元回报
基于UGC的付费广告点击率降低50%

Zero-Budget UGC Tactics for Launch

上线零预算UGC策略

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.

策略	成本	预期产出
X上的"展示你的设置"挑战	0美元	20-50条早期用户帖子
带品牌的模板/素材库	0美元	用户使用模板时被动分享
创始成员个人资料徽章	0美元	用户个人简介中的社交证明
带投票功能的公开路线图	0美元	社区互动内容
通讯中的用户 spotlight	0美元	激励其他用户分享

交叉参考：ai-ugc-ads技能，将UGC规模化用于付费广告。

Budget Decision Framework

预算决策框架

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

预算	核心新增项	预期结果
0美元启动	Carrd/Notion落地页、X上的公开构建、BetaList、Product Hunt、Show HN、15-20个免费目录、Reddit/社区	500-3000注册量，1000-10000访问量
500美元以内	+ 自定义落地页模板、自行录制的演示视频、邮件培育工具、LaunchList推荐等待列表、通讯交换	1000-5000注册量，3000-20000访问量
5000美元以内	+ 专业视频（500-1500美元）、付费通讯赞助、AppSumo套餐、G2/Capterra付费展位、微型网红渗透、PR服务	3000-15000注册量，10000-50000访问量

Platform-Specific Timing

平台专属发布时机

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
LinkedIn	Tue-Thu	7-9 AM local	Professional morning scroll
X (Twitter)	Tue-Thu	8-10 AM PT	Engagement peaks
Reddit	Mon-Wed	6-9 AM PT	Fresh content for US morning

平台	最佳日期	最佳时间	原因
Product Hunt	周二、周三、周四	太平洋时间00:01	算法重置；周中流量峰值
Hacker News	周二至周四	太平洋时间08:00-10:00	站会前浏览；早期增长速度高
Hacker News（备选）	周日	太平洋时间18:00-21:00	竞争少的窗口
LinkedIn	周二至周四	当地时间07:00-09:00	职场人士晨间浏览高峰
X (Twitter)	周二至周四	太平洋时间08:00-10:00	互动峰值
Reddit	周一至周三	太平洋时间06:00-09:00	为美国用户提供新鲜内容

Launch Day Hour-by-Hour

上线日逐小时安排

12:01 AM PT - PH goes live; share link with inner circle via DM only
6:00 AM PT - Check PH position, respond to overnight comments
8:00 AM PT - Post Show HN, publish X thread, post LinkedIn, share in communities
10:00 AM PT - Reddit posts, send launch email to waitlist
12:00 PM PT - Midday engagement check, share early metrics on X
3:00 PM PT - Respond to all new PH/HN comments
6:00 PM PT - Evening progress update on X
9:00 PM PT - Final PH comment sweep, plan Day 1 content

太平洋时间00:01 - Product Hunt上线；仅通过私信与核心圈子分享链接
太平洋时间06:00 - 查看Product Hunt排名，回复隔夜评论
太平洋时间08:00 - 发布Show HN，发布X线程，发布LinkedIn内容，分享至社区
太平洋时间10:00 - 发布Reddit帖子，向等待列表发送上线邮件
太平洋时间12:00 - 中午互动检查，在X上分享早期数据
太平洋时间15:00 - 回复所有新的Product Hunt/HN评论
太平洋时间18:00 - 在X上发布晚间进度更新
太平洋时间21:00 - 最后一次查看Product Hunt评论，规划次日内容

Measuring Launch Success

上线成功衡量指标

Core Launch Metrics

核心上线指标

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

指标	说明	良好上线目标
上线当日总注册量	需求信号	200-1000
上线首周总注册量	持续关注度	500-3000
激活率	产品-市场匹配信号	30-60%
Product Hunt排名	社交证明层级	当日Top5
HN点数	技术可信度	50+
等待列表转化率	上线前用户质量	25-50%
目录推荐流量	长尾价值	每月100+访问量
邮件列表增长	自有受众	500-2000新订阅者
社交提及量	口碑传播	50+独立提及
收集的评价数（G2/Capterra）	买家信心	首月10-20条

Attribution Tracking

归因追踪

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.

上线前配置：每个分享链接添加UTM参数，为每个平台设置独立落地页或查询参数，推荐来源追踪（Plausible、PostHog、Mixpanel），Product Hunt推荐数据，HN流量峰值关联分析。

7-Day Post-Launch Review

上线后7天回顾

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.

上线一周后进行回顾，内容包括：结果与目标对比（注册量、激活率、营收）、各平台表现（Product Hunt排名/点赞数、HN点数、目录推荐、社交提及、邮件增长）、最有效的3件事、最需改进的3件事、未来30天行动计划。

Common Launch Mistakes

常见上线错误

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

阶段	错误	解决方案
上线前	上线前未搭建等待列表	提前4周以上开始收集邮箱
上线前	仅上线落地页而非可用产品	先发布可用的MVP
上线前	未协调支持者	向20-50人提供具体操作指引
上线前	所有平台使用相同信息	根据平台规范定制语气
上线当日	公开请求点赞	仅使用私信，切勿公开发帖
上线当日	未回复评论	30分钟内回复所有评论
上线当日	周五上线	周二至周四上线以获取峰值流量
上线当日	无在线演示	提供即时试用体验
上线后	上线当日后保持沉默	上线首周每天发布更新
上线后	未收集评价	请求每位活跃用户在G2/Capterra上留评
上线后	跳过目录提交	批量提交至15-20个目录

Quick Reference Checklists

快速参考Checklist

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.

上线前2周： 落地页+等待列表上线，Product Hunt页面起草完成，BetaList提交完成，资产库准备完毕（Logo、截图、视频），20-50位支持者收到指引，社交媒体内容日历设置完成，UTM追踪配置完成，X线程起草完成，Show HN帖子起草完成，目录资产准备完毕。

上线当日： Product Hunt于太平洋时间00:01上线，Show HN于太平洋时间08:00-10:00发布，X线程发布，LinkedIn内容发布，等待列表邮件发送，社区帖子分享，所有Product Hunt/HN评论30分钟内回复，晚间进度更新发布。

上线后1周： YouTube演示视频发布，上线回顾博客发布，播客 outreach发送（5-10个节目），G2/Capterra资料创建，评价请求发送，剩余目录提交，上线数据整理完成，30天行动计划制定完成。

Questions to Ask

需询问的问题

When helping a user plan a multi-platform launch:

What does your product do, and who is the primary buyer?
Do you have an existing audience (email list, social following, community)?
What is your launch timeline - when do you want to go live?
What is your budget for launch activities?
Is this a first launch or a relaunch with significant updates?
Do you have a working product or is this pre-MVP waitlist building?
Are you targeting developers, business users, or consumers?
Do you want to prioritize signups, revenue, press coverage, or all three?
Have you launched on Product Hunt or Hacker News before?
Do you have 20+ people who would support your launch on Day 0?

当帮助用户规划多平台上线时：

你的产品功能是什么，主要目标用户是谁？
你是否有现有受众（邮件列表、社交媒体粉丝、社区）？
你的上线时间规划是什么时候？
你用于上线活动的预算是多少？
这是首次上线还是重大更新后的重新上线？
你有可用产品还是处于MVP前的等待列表构建阶段？
你的目标用户是开发者、商业用户还是普通消费者？
你优先考虑注册量、营收、媒体报道，还是三者兼顾？
你之前是否在Product Hunt或Hacker News上发布过产品？
你是否有20+人会在上线日支持你？