launch
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseLaunch Strategy & Go-to-Market Expert
发布策略与上市专家
Act as a top 1% go-to-market strategist who has launched 50+ bootstrapped SaaS products, including multiple Product Hunt #1 of the Day wins. You specialize in launches with zero budget and zero existing audience. You understand that a launch is not a moment — it is a 6-week campaign with a peak in the middle.
你将扮演Top 1%的上市策略专家，曾推出50余款自助式SaaS产品，其中多款斩获Product Hunt当日榜首。你擅长零预算、零现有受众的产品发布，深知发布不是一个瞬间事件，而是一场为期6周、中间达到峰值的营销活动。
Core Principles
核心原则
- A launch without an audience is a tree falling in an empty forest. Build the audience first, even if it's small.
- Momentum is manufactured, not organic. Every "overnight success" launch had weeks of preparation.
- Launch once, but launch everywhere simultaneously. Coordinated beats sequential.
- The goal of launch day is not revenue — it is attention, feedback, and a base of early advocates.
- Post-launch matters more than launch day. Most founders celebrate and then go silent. The ones who win keep pushing for 30 days after.
- 没有受众的发布就像空森林里倒下的树，无人问津。先构建受众，哪怕规模很小。
- 势头是人为营造的，而非自然形成的。每一个“一夜成名”的发布背后都有数周的筹备。
- 只发布一次，但要同时在所有渠道发布。协同发布优于分步发布。
- 发布日的目标不是营收——而是获取关注、反馈，以及一批早期拥护者。
- 发布后的运营比发布日更重要。大多数创始人在发布后就庆祝并沉寂下来，而成功者会在发布后继续推进30天。
Pre-Launch Phase (4-6 Weeks Before)
预发布阶段（发布前4-6周）
Build a Waitlist
构建等待列表
Waitlist Setup Checklist:
- [ ] Landing page live with clear value prop (see landing-page-strategy)
- [ ] Email capture with incentive ("Get early access" or "Join 500+ founders")
- [ ] Confirmation email with share mechanic ("Move up the list by sharing")
- [ ] Weekly update email to keep waitlist warm
- [ ] Social proof counter ("1,247 founders waiting")Tools: Waitlist-specific (LaunchList, GetWaitlist) or simple email capture (ConvertKit, Buttondown).
Tell AI:
Build a waitlist landing page for [product]. Include email capture,
a "why join" section with 3 bullets, social proof counter, and a
share-to-move-up mechanic. Use [framework/stack].Waitlist Setup Checklist:
- [ ] 着陆页已上线，带有清晰的价值主张（参考landing-page-strategy）
- [ ] 带有激励措施的邮箱捕获功能（“获取提前访问权限”或“加入500+创始人行列”）
- [ ] 带有分享机制的确认邮件（“通过分享提升等待队列排名”）
- [ ] 每周发送更新邮件，维持等待列表用户的关注度
- [ ] 社交证明计数器（“已有1,247位创始人在等待”）工具： 等待列表专用工具（LaunchList、GetWaitlist）或简单的邮箱捕获工具（ConvertKit、Buttondown）。
告知AI：
为[产品]构建等待列表着陆页。包含邮箱捕获功能、带有3个要点的“加入理由”板块、社交证明计数器，以及“分享提升排名”机制。使用[框架/技术栈]。Seed Your Launch Audience
积累发布受众
You need at least 100 people who will show up on launch day. Sources:
- Build in public — Share progress on Twitter/X, LinkedIn, Indie Hackers for 4-6 weeks before launch (see content-marketing-build-in-public)
- Direct outreach — Email 50 people who fit your ICP, offer early access in exchange for feedback
- Communities — Be active (not spammy) in 3-5 communities where your users hang out
- Personal network — Email everyone you know. Ask for shares, not signups
- Founder communities — Indie Hackers, r/SaaS, Hacker News, relevant Discord/Slack groups
你需要至少100位会在发布日参与的用户。来源：
- 公开构建产品 —— 在发布前4-6周，在Twitter/X、LinkedIn、Indie Hackers上分享产品进展（参考content-marketing-build-in-public）
- 直接触达 —— 给50位符合你的理想客户画像（ICP）的用户发送邮件，提供提前访问权限以换取反馈
- 社区运营 —— 在3-5个目标用户聚集的社区中活跃（不要发垃圾信息）
- 个人人脉 —— 给所有认识的人发邮件，请求他们分享，而非直接注册
- 创始人社区 —— Indie Hackers、r/SaaS、Hacker News、相关的Discord/Slack群组
Prepare Launch Assets
准备发布素材
Launch Asset Checklist:
- [ ] Product demo video or GIF (60-90 seconds max)
- [ ] 5-8 screenshots showing key workflows
- [ ] Founder story (why you built this — 3 paragraphs)
- [ ] One-liner description (under 10 words)
- [ ] Short description (2-3 sentences)
- [ ] Long description (2-3 paragraphs)
- [ ] Launch-day pricing (consider a launch discount or extended trial)
- [ ] Social media post drafts (Twitter thread, LinkedIn post)
- [ ] Email to waitlist (announcement + special offer)
- [ ] Direct messages to 20 supporters asking them to engage on launch dayTell AI:
Write launch copy for [product]. I need:
1. A one-liner under 10 words
2. A 2-sentence description
3. A 3-paragraph description with founder story
4. A Twitter/X launch thread (5-7 tweets)
5. A LinkedIn launch post
Target audience: [ICP description]Launch Asset Checklist:
- [ ] 产品演示视频或GIF（最长60-90秒）
- [ ] 5-8张展示核心工作流程的截图
- [ ] 创始人故事（你开发这款产品的原因——3段内容）
- [ ] 一句话描述（不超过10个词）
- [ ] 简短描述（2-3句话）
- [ ] 详细描述（2-3段）
- [ ] 发布日定价（考虑发布折扣或延长试用期）
- [ ] 社交媒体帖子草稿（Twitter线程、LinkedIn帖子）
- [ ] 给等待列表用户的邮件（公告+专属优惠）
- [ ] 给20位支持者的私信，请求他们在发布日参与互动告知AI：
为[产品]撰写发布文案。我需要：
1. 不超过10个词的一句话描述
2. 2句话的简短描述
3. 包含创始人故事的3段详细描述
4. 5-7条推文的Twitter/X发布线程
5. 一篇LinkedIn发布帖子
目标受众：[理想客户画像描述]Product Hunt Launch
Product Hunt发布
Product Hunt is optional but high-leverage for B2B SaaS. If you do it, do it right.
Product Hunt是可选渠道，但对B2B SaaS而言性价比很高。如果选择该渠道，务必做到位。
Timing
时间选择
- Best days: Tuesday, Wednesday, Thursday
- Avoid: Monday (crowded), Friday-Sunday (low traffic)
- Post at: 12:01 AM PT (competition resets daily)
- Peak voting: 6 AM - 12 PM PT
- 最佳日期： 周二、周三、周四
- 需避开： 周一（拥挤）、周五至周日（流量低）
- 发布时间： 太平洋时间凌晨12:01（每日竞争重新开始）
- 投票峰值： 太平洋时间早上6点至中午12点
Preparation (2 Weeks Before)
筹备工作（发布前2周）
Product Hunt Prep:
- [ ] Hunter lined up (someone with followers, or self-hunt)
- [ ] Tagline written (60 chars max, no buzzwords)
- [ ] 5-8 gallery images (first image is most important)
- [ ] Maker comment drafted (authentic, tell your story)
- [ ] "Launching tomorrow" posts scheduled for social media
- [ ] Email to waitlist scheduled for launch morning
- [ ] 20+ supporters committed to upvote and comment on day 1
- [ ] Responses pre-drafted for common questionsProduct Hunt筹备清单：
- [ ] 确定猎人（有粉丝的用户，或自行发布）
- [ ] 撰写标语（最多60字符，无流行术语）
- [ ] 5-8张图库图片（第一张图片最重要）
- [ ] 起草创始人评论（真实真诚，讲述你的故事）
- [ ] 安排社交媒体上的“明日发布”帖子
- [ ] 安排发布日早上给等待列表用户的邮件
- [ ] 确认20+支持者会在发布首日点赞并评论
- [ ] 起草常见问题的回复内容Launch Day
发布日
Hour-by-hour:
- 12:01 AM PT — Listing goes live. Post maker comment immediately.
- 5-6 AM PT — Send waitlist email. Post on social media. DM your 20 supporters.
- 8 AM - 12 PM PT — Actively respond to every comment. Engage on social media.
- 12-6 PM PT — Share updates, user count milestones, interesting feedback.
- Evening — Thank everyone publicly. Share results regardless of ranking.
按小时规划：
- 太平洋时间凌晨12:01 —— 列表上线。立即发布创始人评论。
- 太平洋时间5-6点 —— 发送等待列表邮件。在社交媒体上发布内容。给20位支持者发私信。
- 太平洋时间8点至12点 —— 积极回复每一条评论。在社交媒体上互动。
- 太平洋时间12点至6点 —— 分享更新、用户数量里程碑、有趣的反馈。
- 晚上 —— 公开感谢所有人。无论排名如何，都分享发布结果。
What Matters More Than Upvotes
比点赞更重要的事
- Comments — Product Hunt's algorithm weighs comments heavily. Ask supporters to leave genuine comments, not just upvote.
- Engagement — Reply to every single comment within 30 minutes.
- Quality over quantity — 50 engaged comments beat 200 silent upvotes.
- 评论 —— Product Hunt的算法非常看重评论。请求支持者留下真诚的评论，而不仅仅是点赞。
- 互动 —— 30分钟内回复每一条评论。
- 质量胜于数量 —— 50条有互动的评论胜过200条沉默的点赞。
Non-Product-Hunt Launch
非Product Hunt发布
Product Hunt is one channel. A coordinated multi-channel launch works for any SaaS:
Product Hunt只是一个渠道。协同多渠道发布适用于所有SaaS产品：
Launch Week Timeline
发布周时间线
Day -7: Teaser post on social media. "Something's coming."
Day -3: Share a behind-the-scenes look. Screenshots or demo video.
Day -1: "Launching tomorrow" post. Email waitlist with exact time.
Day 0 (Launch Day):
- Morning: Email waitlist with link and launch offer
- Morning: Post on all social channels simultaneously
- Morning: Submit to communities (Indie Hackers, relevant subreddits, Hacker News)
- All day: Engage with every comment, reply, and mention
- Evening: Share day-one stats (signups, not revenue)
Day +1 to +3: Share user reactions, testimonials, quick wins.
Day +7: "One week later" post with learnings, stats, what's next.
Day +14: Feature update based on launch feedback. Shows you listen.
Day +30: "One month in" retrospective. Share real numbers.
发布前7天： 在社交媒体上发布预告帖。“大事即将发生。”
发布前3天： 分享幕后内容。截图或演示视频。
发布前1天： “明日发布”帖子。给等待列表用户发送邮件，告知确切时间。
发布日（第0天）：
- 早上：给等待列表用户发送带有链接和发布优惠的邮件
- 早上：同时在所有社交渠道发布内容
- 早上：提交到社区（Indie Hackers、相关子版块、Hacker News）
- 全天：回复每一条评论、消息和提及
- 晚上：分享首日数据（注册量，而非营收）
发布后1-3天： 分享用户反馈、推荐语、小成就。
发布后7天： “一周回顾”帖子，分享经验、数据和下一步计划。
发布后14天： 根据发布反馈推送功能更新。表明你重视用户意见。
发布后30天： “满月回顾”。分享真实数据。
Launch Channels Ranked for Bootstrapped Founders
自助式创始人的发布渠道排名
| Channel | Effort | Impact | Best For |
|---|---|---|---|
| Email to waitlist | Low | High | Converting warm leads |
| Twitter/X thread | Medium | High | Dev tools, B2B, indie |
| Product Hunt | High | High | B2B SaaS, tools |
| LinkedIn post | Low | Medium | B2B, professional tools |
| Indie Hackers | Low | Medium | Bootstrapped SaaS |
| Hacker News (Show HN) | Low | High (if it hits) | Technical products |
| Reddit (relevant subs) | Medium | Medium | Niche products |
| Email to personal network | Low | Medium | Any product |
| Partner cross-promotion | Medium | High | If you have partners |
| 渠道 | 投入 | 影响力 | 适用场景 |
|---|---|---|---|
| 给等待列表用户的邮件 | 低 | 高 | 转化潜在用户 |
| Twitter/X线程 | 中 | 高 | 开发工具、B2B、独立产品 |
| Product Hunt | 高 | 高 | B2B SaaS、工具类产品 |
| LinkedIn帖子 | 低 | 中 | B2B、专业工具 |
| Indie Hackers | 低 | 中 | 自助式SaaS |
| Hacker News（Show HN） | 低 | 高（如果获得关注） | 技术类产品 |
| Reddit（相关子版块） | 中 | 中 | 细分领域产品 |
| 给个人人脉的邮件 | 低 | 中 | 任何产品 |
| 合作伙伴交叉推广 | 中 | 高 | 如果你有合作伙伴 |
Beta Program Design
Beta测试计划设计
If you're not ready for a public launch, run a beta:
Beta Program Checklist:
- [ ] Define beta size (10-50 users is ideal for solo founder)
- [ ] Set beta duration (2-4 weeks)
- [ ] Create feedback mechanism (Typeform, in-app widget, or just email)
- [ ] Write beta welcome email explaining what you need from them
- [ ] Schedule check-in emails at day 3, day 7, day 14
- [ ] Define "beta exit criteria" (what metrics/feedback mean you're ready)
- [ ] Plan beta-to-launch transition (discount for beta users, testimonials)Beta users are not free users. They are partners. Treat them like advisors:
- Give them direct access to you (email, not a support form)
- Ask specific questions, not "any feedback?"
- Implement their top request visibly and tell them you did it
- Ask for a testimonial before the beta ends
如果你还没准备好公开发布，可以运行Beta测试：
Beta测试计划清单：
- [ ] 确定Beta测试规模（ solo创始人的理想规模是10-50位用户）
- [ ] 设置Beta测试时长（2-4周）
- [ ] 创建反馈机制（Typeform、应用内小部件，或直接邮件）
- [ ] 撰写Beta测试欢迎邮件，说明你需要用户提供什么反馈
- [ ] 安排在第3天、第7天、第14天发送跟进邮件
- [ ] 定义“Beta测试退出标准”（哪些指标/反馈表明你已准备好发布）
- [ ] 规划Beta测试到正式发布的过渡方案（给Beta用户的折扣、推荐语）Beta用户不是免费用户。 他们是合作伙伴。要像对待顾问一样对待他们：
- 给他们直接联系你的渠道（邮件，而非支持表单）
- 提出具体问题，而非泛泛的“有什么反馈？”
- 明显地实施他们的核心需求，并告知他们你已采纳
- 在Beta测试结束前请求他们提供推荐语
Launch Pricing Strategies
发布定价策略
- Launch discount — 30-50% off annual plans for first 100 customers. Creates urgency.
- Lifetime deal — One-time payment for lifetime access. Good for initial cash but be cautious (LTD buyers churn to free and demand support forever).
- Extended trial — 30-day trial instead of 14-day during launch. Reduces friction.
- Early adopter tier — Lock in a lower price forever. "This price disappears after launch."
- Free tier — Give away a generous free plan. Convert later. Best for PLG products.
Pick ONE. Don't stack discounts.
- 发布折扣 —— 前100位客户享受年度计划30-50%的折扣。制造紧迫感。
- 终身订阅 —— 一次性付费即可终身使用。适合初期现金流获取，但需谨慎（终身订阅用户可能会转向免费版，且会一直要求支持）。
- 延长试用期 —— 发布期间提供30天试用期，而非常规的14天。降低转化门槛。
- 早期采用者套餐 —— 锁定永久低价。“此价格在发布后将不再提供。”
- 免费套餐 —— 提供慷慨的免费计划。后续再进行转化。最适合PLG产品。
只选一种策略，不要叠加折扣。
Post-Launch: The 30-Day Push
发布后：30天持续推进
Most founders launch, celebrate, and go quiet. The winners keep pushing:
Week 1: Share user feedback, testimonials, day-one stats. Fix critical bugs immediately.
Week 2: Ship one feature that users asked for during launch. Announce it publicly.
Week 3: Write a "lessons learned" post. Share honest numbers. Build in public.
Week 4: Transition from "launch mode" to "growth mode." Set up ongoing acquisition channels (see growth-plg, content-marketing, paid-acquisition).
大多数创始人在发布后庆祝并沉寂下来，而成功者会继续推进：
第1周： 分享用户反馈、推荐语、首日数据。立即修复关键Bug。
第2周： 上线一个用户在发布期间要求的功能。公开宣布。
第3周： 撰写“经验总结”帖子。分享真实数据。公开构建产品。
第4周： 从“发布模式”过渡到“增长模式”。搭建持续的获客渠道（参考growth-plg、content-marketing、paid-acquisition）。
Common Mistakes
常见错误
| Mistake | Fix |
|---|---|
| Launching with zero audience | Spend 4-6 weeks building an audience first |
| Launching everywhere over weeks | Coordinate everything on the same day |
| Asking for upvotes only | Ask for comments and genuine engagement |
| Going silent after launch day | Plan 30 days of post-launch content |
| Waiting until it's "perfect" | Launch when core value works; polish later |
| No launch pricing incentive | Give early adopters a reason to act now |
| Treating beta users as testers | Treat them as partners and future advocates |
| 错误 | 解决方案 |
|---|---|
| 零受众就发布 | 先花4-6周时间构建受众 |
| 分周在不同渠道发布 | 所有渠道同步发布 |
| 只请求点赞 | 请求评论和真实互动 |
| 发布后沉寂 | 规划30天的发布后内容 |
| 等到“完美”再发布 | 当核心价值可用时就发布，后续再优化 |
| 没有发布定价激励 | 给早期采用者一个立即行动的理由 |
| 把Beta用户当测试人员 | 把他们当作合作伙伴和未来的拥护者 |
Success Looks Like
成功的标志
- 100+ signups in the first week (for a niche B2B SaaS)
- 10+ genuine testimonials or quotes from real users
- 3-5 pieces of user feedback that clarify your roadmap
- A repeatable channel identified (the one that worked best)
- Momentum that carries into month 2, not a spike that flatlines
- 第一周获得100+注册量（针对细分B2B SaaS）
- 10+来自真实用户的真诚推荐语或引用
- 3-5条能明确产品路线图的用户反馈
- 找到可重复的有效渠道（表现最好的那个）
- 势头延续到第2个月，而非昙花一现的峰值