Back to Details

launch

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Product Launch Strategy Skill

产品发布策略Skill

Mandatory Content Standards

强制内容标准

  • Match output length to the skill, request, and deliverable type. Use concise answers for quick checks, structured detail for audits and plans, and full-length output only when the user asks for a complete deliverable.
  • Write in a way that sounds like a knowledgeable human wrote it. No robotic or templated phrasing.
  • Use short sentences. One idea per sentence. One focus per paragraph.
  • Use active voice. Never passive constructions.
  • Address the reader directly using "you" and "your."
  • Use bullet points only when they genuinely improve readability.
  • Replace all em dashes with commas, parentheses, semicolons, or a new sentence. No hidden Unicode characters.
  • End every sentence with a period.
  • No hashtags, emojis, or asterisks.
  • No introductory or closing filler phrases such as "in conclusion," "in summary," or "in a world where."
  • No warnings, notes, or disclaimers. Stick to requested output.
  • No AI cliches: no "game-changer," "unlock," "leverage," "dive into," "delve," "cutting-edge," "transformative," "revolutionize."
  • No excessive adjectives or adverbs. Let specifics do the work.
  • No broad generalizations. Every claim tied to specific context.
  • Use specific examples, data, and scenarios.
  • Pose at least one thought-provoking question per skill.
  • Mobile-friendly: short paragraphs, clear headers, scannable.
  • Practical and actionable. Every section connects to a next step.
  • 根据Skill类型、用户请求和交付物类型匹配输出长度。快速核查使用简洁回答，审计和计划使用结构化细节，仅当用户要求完整交付物时才输出全长度内容。
  • 写作风格要像专业人士撰写的内容，避免机械或模板化措辞。
  • 使用短句，每句表达一个观点，每段聚焦一个主题。
  • 使用主动语态，绝对避免被动结构。
  • 用"你"和"你的"直接称呼读者。
  • 仅在确实能提升可读性时使用项目符号。
  • 用逗号、括号、分号或新句子替代所有破折号，避免隐藏Unicode字符。
  • 每个句子末尾都加句号。
  • 禁止使用话题标签、表情符号或星号。
  • 禁止使用"总结来说"、"综上所述"或"在当今世界"等开头或结尾的填充语。
  • 禁止使用警告、注释或免责声明，严格按照请求输出内容。
  • 禁止使用AI陈词滥调：如"游戏规则改变者"、"解锁"、"利用"、"深入探讨"、"钻研"、"前沿"、"变革性"、"彻底革新"。
  • 避免过度使用形容词或副词，用具体细节体现价值。
  • 禁止宽泛概括，所有主张都要结合具体背景。
  • 使用具体示例、数据和场景。
  • 每个Skill至少提出一个引人深思的问题。
  • 适配移动端：段落简短、标题清晰、便于浏览。
  • 内容要实用且可落地，每个部分都关联下一步行动。

What This Skill Does

本Skill的作用

This skill covers the full lifecycle of a product launch, from early planning through post-launch analysis. It applies to full product launches, significant feature releases, and beta programs. It covers the strategic planning, the tactical execution, and the follow-through that most launch plans skip.
A launch is not a single event. It is a concentrated period of attention that, if managed well, creates a durable lift in visibility, signups, and brand awareness. If managed poorly, it wastes months of anticipation in a day.
The question worth answering before anything else: are you launching to validate, to grow, or to signal? The answer changes nearly every decision you make.
本Skill覆盖产品发布的完整生命周期，从早期规划到发布后分析。适用于完整产品发布、重要功能更新以及Beta测试项目。涵盖战略规划、战术执行，以及大多数发布计划会忽略的后续跟进工作。
发布不是单一事件，而是一段集中吸引关注的时期。如果管理得当，能持续提升产品知名度、注册量和品牌认知度；如果管理不善，会浪费数月的前期铺垫，功亏一篑。
在开始所有工作前，有一个值得回答的问题：你发布产品是为了验证需求、实现增长还是传递信号？答案几乎会改变你做出的每一个决策。

Part 1: Types of Launches and When to Use Each

第一部分：发布类型及适用场景

Not all launches serve the same purpose. Clarity on your launch type shapes your goals, channels, and success metrics.
并非所有发布都服务于同一目标。明确你的发布类型会影响目标设定、渠道选择和成功指标。

Beta Launch

Beta Launch

A beta launch brings a product to a small, controlled group of users before public availability. The goals are product validation, early feedback, and building a group of advocates before the public launch.
A beta launch is the right choice when:
  • Core functionality works but the product is not fully polished.
  • You need real usage data to make product decisions.
  • You want to build a group of early users who will amplify the public launch.
Beta launches should be exclusive but not opaque. Tell beta users what you are testing. Ask for specific feedback. Set expectations about when the product will be available publicly.
Beta发布是在产品公开可用前，将其推向一小群受控用户。目标是验证产品、获取早期反馈，并在公开发布前建立一批支持者。
适合选择Beta发布的场景：
  • 核心功能可用，但产品尚未完全打磨完善。
  • 需要真实使用数据来指导产品决策。
  • 希望建立一批早期用户，助力公开发布时的传播。
Beta发布应保持专属但透明。告知Beta用户你正在测试的内容，索要具体反馈，并明确产品公开可用的时间预期。

Public Launch

Public Launch

A public launch opens the product to anyone. The goals are signups, revenue, and press coverage. You have one shot at the "new product" story. Do not waste it on an unfinished product.
A public launch is the right choice when:
  • Core use cases work reliably.
  • You have an onboarding experience that can handle new users.
  • You have a plan for turning launch-day signups into activated users.
公开发布面向所有用户开放产品。目标是获取注册量、营收和媒体报道。你只有一次讲述"新产品"故事的机会，不要把它浪费在未完成的产品上。
适合选择公开发布的场景：
  • 核心使用场景运行可靠。
  • 拥有可应对新用户的引导流程。
  • 已制定将发布日注册用户转化为活跃用户的计划。

Feature Launch

Feature Launch

A feature launch announces a significant new capability within an existing product. The goals are customer retention, expansion revenue (upsell), and media coverage within your category.
Feature launches are underutilized. Most teams ship features with a changelog entry and nothing else. A well-executed feature launch for a significant capability can drive meaningful press, social engagement, and upgrade activity.
功能发布是在现有产品中宣布重要的新功能。目标是提升客户留存率、拓展营收（升级销售），以及获得所在领域的媒体报道。
功能发布的价值常被低估。大多数团队仅通过更新日志告知功能上线，除此之外没有其他动作。针对重要功能的精心策划的发布，能推动可观的媒体报道、社交互动和升级转化。

Soft Launch

Soft Launch

A soft launch makes the product available without a coordinated promotional push. You do not announce. You do not pursue press. You let people find it organically while you continue refining.
Soft launches are appropriate when you want real usage data before committing to a positioning strategy. They are not a substitute for a real launch. They are a precursor.
软发布是在不进行协调推广的情况下开放产品。不对外宣布，不寻求媒体报道，让用户自然发现产品，同时继续优化。
当你希望在确定定位策略前获取真实使用数据时，软发布是合适的选择。它不是正式发布的替代品，而是前期准备步骤。

Part 2: Pre-Launch Preparation

第二部分：发布前准备

Pre-launch is where most of the work happens. A launch day that goes smoothly is the product of four to eight weeks of preparation.
发布前是大部分工作的集中阶段。顺畅的发布日是4到8周准备工作的成果。

Set Your Launch Goals

设定发布目标

Write down specific, measurable goals before you do anything else.
Not this: "Have a successful launch." This: "Generate 500 trial signups in the first 72 hours. Finish in the top 3 on Product Hunt. Get coverage in at least two publications in our category."
Your goals determine your tactics. If your primary goal is Product Hunt performance, your prep looks different than if your primary goal is PR coverage.
在开始任何工作前，写下具体、可衡量的目标。
错误示例："成功完成发布。" 正确示例："在发布后72小时内获得500个试用注册量。在Product Hunt排名进入前三。获得至少两家所在领域媒体的报道。"
你的目标决定战术。如果首要目标是在Product Hunt取得好成绩，准备工作会与以公关报道为首要目标的情况截然不同。

Define Your Launch Narrative

定义发布叙事

Your launch narrative is the story you want the world to tell about your product. It answers:
  • Who is this for?
  • What problem does it solve that was not solved well before?
  • Why does this exist now? (What made it possible or necessary?)
  • What is the most surprising or specific thing about it?
Write a one-paragraph launch narrative before you write any launch copy. Every piece of launch content (press release, Product Hunt post, launch email, social posts) should tell the same story, differently.
A narrative built around a specific pain point converts better than a narrative built around features. "Teams of 3 to 10 spending 10+ hours per week on manual reporting now have an automated alternative" is a narrative. "We built a reporting tool" is not.
发布叙事是你希望外界讲述的关于产品的故事。它需要回答：
  • 产品面向谁？
  • 它解决了哪些之前未被妥善解决的问题？
  • 为什么现在推出这个产品？（是什么让它成为可能或必要？）
  • 它最令人惊讶或最独特的地方是什么？
在撰写任何发布文案前，先写一段发布叙事。所有发布内容（新闻稿、Product Hunt帖子、发布邮件、社交帖子）都应围绕同一个故事，以不同形式呈现。
围绕具体痛点构建的叙事比围绕功能构建的叙事转化率更高。"3到10人的团队每周花费10小时以上处理手动报表，现在有了自动化替代方案"是合格的叙事；"我们打造了一款报表工具"则不是。

Build Your Asset Library

构建资产库

Create all launch assets at least two weeks before launch:
  • Product Hunt listing (tagline, description, gallery images, maker comment).
  • Press release (for press outreach only, not for publishing publicly).
  • Launch email (for your existing list).
  • Social posts (LinkedIn, Twitter, and any other active channels).
  • Blog post or announcement post (for your website).
  • Demo video (60 to 90 seconds, showing the product working).
  • High-resolution product screenshots (labeled with context).
  • Founder headshot and bio (for press requests).
  • FAQ document (for your team to answer press and community questions consistently).
Having all of these ready in advance means launch day is execution, not creation.
在发布前至少两周准备好所有发布资产：
  • Product Hunt列表（标语、描述、图库图片、开发者评论）。
  • 新闻稿（仅用于公关 outreach，不公开发布）。
  • 发布邮件（面向现有用户列表）。
  • 社交帖子（LinkedIn、Twitter及其他活跃渠道）。
  • 博客文章或公告帖子（用于官网）。
  • 演示视频（60到90秒，展示产品实际运行）。
  • 高分辨率产品截图（标注上下文）。
  • 创始人头像和简介（用于媒体请求）。
  • FAQ文档（确保团队能一致回答媒体和社区问题）。
提前准备好所有资产意味着发布日只需执行，无需临时创作。

Part 3: Waitlist and Early Access Strategy

第三部分：等待列表与早期访问策略

A waitlist builds anticipation and creates a pool of ready-to-activate users before you launch publicly.
等待列表能提前营造期待感，并在公开发布前建立一批随时可激活的用户池。

When to Build a Waitlist

何时建立等待列表

A waitlist makes sense when:
  • Your product is not yet publicly available but you want to validate demand.
  • You plan a controlled rollout and need to manage capacity.
  • You want to create social proof (showing a high number on the waitlist signals desirability).
A waitlist does not make sense when:
  • Your product is already available to everyone.
  • You cannot deliver meaningful value to early waitlist members.
适合建立等待列表的场景：
  • 产品尚未公开可用，但你希望验证需求。
  • 计划分阶段推出，需要管理用户容量。
  • 希望打造社交证明（显示高等待人数意味着产品受欢迎）。
不适合建立等待列表的场景：
  • 产品已面向所有用户开放。
  • 无法为早期等待列表成员提供有意义的价值。

Waitlist Page Design

等待列表页面设计

A waitlist landing page has one job: get the email address of someone who is interested.
Include:
  • A specific headline describing what the product does and for whom.
  • A brief description (three to five sentences) of the core problem and solution.
  • Two to three benefits in specific language.
  • An email capture form.
  • If possible, a brief demo or screenshot showing what the product looks like.
Do not include pricing, a long FAQ, or detailed feature documentation on the waitlist page. Those belong on the main product site after launch. The waitlist page should be a focused, short page.
等待列表着陆页的唯一目标：获取感兴趣用户的邮箱地址。
需包含：
  • 明确的标题，描述产品功能及面向人群。
  • 简短描述（3到5句话），说明核心问题及解决方案。
  • 2到3个具体的产品优势。
  • 邮箱收集表单。
  • 如有可能，添加简短演示或截图，展示产品外观。
等待列表页面不要包含定价、长篇FAQ或详细功能文档，这些内容属于发布后的主产品网站。等待列表页面应简洁、聚焦。

Activating the Waitlist

激活等待列表

When you are ready to invite waitlist members, segment them if your list is large. Invite the first 10 to 20% manually, with a personalized note. These early invitees are your first advocates. Treat them like beta users.
Invite in waves. This creates anticipation among people still waiting and reduces the risk of overwhelming your onboarding and support capacity in a single day.
Send a waitlist survey before you start inviting. Ask what they want to accomplish with the product. Use those responses to personalize onboarding and to feed into your launch messaging.
当准备邀请等待列表成员时，如果列表规模较大，进行用户细分。手动邀请前10%到20%的用户，并附上个性化说明。这些早期受邀用户是你的第一批支持者，要像对待Beta用户一样对待他们。
分批次邀请。这能让仍在等待的用户保持期待，同时降低单日引导流程和支持服务过载的风险。
开始邀请前发送等待列表调研问卷，询问用户希望通过产品实现什么目标。用这些反馈个性化引导流程，并优化发布 messaging。

Part 4: Product Hunt Launch Playbook

第四部分：Product Hunt发布指南

Product Hunt is the most concentrated launch channel available to software products. A top-5 finish on launch day can drive 1,000 to 5,000 trial signups. A poorly prepared launch can barely register.
Product Hunt是软件产品最集中的发布渠道。发布日进入前五名可带来1000到5000个试用注册量；准备不足的发布则几乎不会获得关注。

30 Days Before Launch

发布前30天

Create or optimize your Product Hunt account. Follow products, comment on launches, and engage with the community. A maker profile with activity converts followers better than a brand new account with no history.
Identify a hunter. A hunter is the person who posts your product on Product Hunt. A hunter with a large, engaged following increases the visibility of your launch because followers receive notifications. Research hunters with followings in your category. Reach out with a personal note explaining what you built and why you think it would interest their followers.
Alternatively, post it yourself if you have an account with established followers.
Decide on your launch date. Tuesday, Wednesday, and Thursday are the highest-traffic days. Avoid Mondays (lower engagement) and weekends (significantly lower traffic). Schedule your launch to go live at 12:01 AM Pacific Time to get the full 24-hour window.
创建或优化你的Product Hunt账号。关注产品、评论发布内容、参与社区互动。有活跃记录的开发者账号比全新无历史的账号更易吸引关注者。
寻找猎人（hunter）。猎人是在Product Hunt上发布你产品的人。拥有大量活跃关注者的猎人能提升发布曝光度，因为关注者会收到通知。研究所在领域拥有关注者的猎人，发送个性化说明，解释你打造的产品及为什么他们的关注者会感兴趣。
如果你的账号已有一定关注者，也可以自行发布。
确定发布日期。周二、周三和周四是流量最高的日子。避开周一（参与度较低）和周末（流量显著降低）。安排在太平洋时间凌晨12:01上线，以获得完整的24小时展示窗口。

7 to 14 Days Before Launch

发布前7到14天

Prepare your Product Hunt listing in full:
Tagline (60 characters max): The most important piece of text on your listing. It appears everywhere your listing appears. Write five to ten options and test them with people outside your company. Choose the most specific and surprising one.
Description (260 characters): Expand on the tagline. Include who the product is for and what problem it solves.
Gallery images: 3 to 5 images minimum. Include labeled screenshots, a product demo GIF (if relevant), and a cover image that reads well as a thumbnail. Every image should have a title overlay explaining what the viewer is looking at.
Demo video: A Loom or YouTube video embedded in the listing. 60 to 90 seconds. Show the product working, not a slide deck.
First comment from maker: Written in advance. This appears at the top of the comments section when your listing goes live. Write about:
  • Why you built this.
  • Who it is for.
  • What you are most excited about.
  • A specific question inviting community feedback.
完整准备你的Product Hunt列表：
标语（最多60字符）： 列表中最重要的文本，会出现在所有展示位置。撰写5到10个选项，让公司外部人员测试，选择最具体、最令人惊讶的一个。
描述（260字符）： 拓展标语内容，说明产品面向人群及解决的问题。
图库图片： 至少3到5张图片。包含标注的截图、产品演示GIF（如有相关），以及作为缩略图可读性强的封面图。每张图片都要有标题覆盖层，说明展示内容。
演示视频： 嵌入列表的Loom或YouTube视频，时长60到90秒。展示产品实际运行，而非幻灯片。
开发者第一条评论： 提前撰写。列表上线后，这条评论会出现在评论区顶部。内容应包括：
  • 你打造这款产品的原因。
  • 产品面向人群。
  • 你最兴奋的点是什么。
  • 一个邀请社区反馈的具体问题。

Launch Day Execution

发布日执行

At 12:01 AM Pacific Time, your listing goes live. Within the first two hours:
  • Share to your existing email list (if you have one). Keep the email short: "We launched on Product Hunt today. If you find the product valuable, a comment or upvote would mean a lot." Include the direct link.
  • Post to LinkedIn, Twitter, and any other active channels. Show the listing, not just the product URL.
  • Post in relevant Slack communities and Discord servers. Do not spam. One or two communities that know your product is appropriate.
  • Notify your team, investors, and advisors. Give them the link and make it easy to support: "If you've used the product and want to share your experience, here's the link."
During launch day, respond to every comment within two to four hours. A listing with active maker engagement ranks better in Product Hunt's algorithm and looks more credible to voters.
Do not buy upvotes. Product Hunt penalizes this and it damages your credibility in the community.
太平洋时间凌晨12:01，你的列表上线。在前两小时内：
  • 分享给现有邮箱列表（如果有的话）。邮件要简短："我们今天在Product Hunt上线了。如果你觉得产品有价值，评论或点赞对我们意义重大。"附上直接链接。
  • 发布到LinkedIn、Twitter及其他活跃渠道。展示列表页面，而非仅产品URL。
  • 在相关Slack社区和Discord服务器分享。不要刷屏，选择1到2个了解你产品的社区即可。
  • 通知你的团队、投资者和顾问。提供链接，并简化支持流程："如果你使用过产品并想分享体验，点击这个链接。"
发布日当天，在2到4小时内回复所有评论。开发者积极互动的列表在Product Hunt算法中排名更高，对投票者来说也更可信。
不要购买点赞。Product Hunt会对此进行处罚，同时损害你在社区中的可信度。

Post-Launch on Product Hunt

Product Hunt发布后

Within 24 hours after your launch, post a "maker update" comment thanking the community and sharing one specific thing you learned from the feedback.
Send a follow-up email to everyone who commented with a note of appreciation and, where relevant, an answer to any question they raised.
Export every comment and note every specific piece of product feedback. Feed this into your roadmap.
发布后24小时内，发布一条"开发者更新"评论，感谢社区并分享从反馈中学到的一个具体要点。
给所有评论过的用户发送跟进邮件，表达感谢，并在相关情况下回复他们提出的问题。
导出所有评论，记录每一条具体的产品反馈，将其纳入产品路线图。

Part 5: Launch Day Execution Checklist

第五部分：发布日执行清单

A launch day without a checklist is a launch day you will regret.
没有清单的发布日会让你后悔。

The Night Before Launch

发布前一晚

  • Confirm all landing pages load correctly and forms submit.
  • Test the trial or signup flow end-to-end.
  • Confirm your email sequence triggers correctly for new signups.
  • Confirm your analytics tracking is working.
  • Set up real-time monitoring: a Slack channel with signup notifications if possible.
  • Confirm your team knows their roles for launch day.
  • 确认所有着陆页加载正常，表单提交功能可用。
  • 端到端测试试用或注册流程。
  • 确认新注册用户的邮件序列触发正常。
  • 确认分析追踪功能正常运行。
  • 设置实时监控：如有可能，创建带注册通知的Slack频道。
  • 确认团队成员清楚自己在发布日的职责。

Launch Day (First Two Hours)

发布日（前两小时）

  • Product Hunt listing goes live at midnight Pacific.
  • Send the launch email to your list.
  • Post on all social channels.
  • Share with communities.
  • Notify your personal networks.
  • Begin monitoring and responding to comments.
  • Product Hunt列表于太平洋时间午夜上线。
  • 向用户列表发送发布邮件。
  • 在所有社交渠道发布内容。
  • 在社区分享。
  • 通知个人人脉。
  • 开始监控并回复评论。

Launch Day (Ongoing)

发布日（持续进行）

  • Respond to all Product Hunt comments, social comments, and mentions.
  • Monitor for press coverage. Set up Google Alerts for your product name if you have not already.
  • Track signups in real time.
  • Address any critical bugs or onboarding issues immediately.
  • Escalate any support issues that could affect multiple users.
  • 回复所有Product Hunt评论、社交评论和提及。
  • 监控媒体报道。如果还没设置，为产品名称创建Google Alerts。
  • 实时追踪注册量。
  • 立即解决任何严重漏洞或引导流程问题。
  • 升级可能影响多个用户的支持问题。

Launch Day (End of Day)

发布日（当日结束）

  • Share a brief update on social channels: "Here's what day one looked like."
  • Send a thank-you message to anyone who actively supported the launch.
  • Note any immediate feedback themes to address in your post-launch communications.
  • 在社交渠道分享简短更新："这是我们第一天的成果。"
  • 向所有积极支持发布的人员发送感谢信息。
  • 记录需要在发布后沟通中解决的即时反馈主题。

Part 6: The Launch Email Sequence

第六部分：发布邮件序列

Your existing list is your highest-converting launch audience. They already know you. Email them before, during, and after the launch.
现有用户列表是你转化率最高的发布受众。他们已经了解你。在发布前、发布中、发布后都要给他们发邮件。

Pre-Launch Email (3 to 7 Days Before)

发布前邮件（发布前3到7天）

Tell your list that something is coming. Be specific about when.
"We're launching on Product Hunt this Thursday at midnight Pacific. [Product name] is [one sentence description]. We'll have more to share on Thursday, but wanted to give you an early heads-up."
This primes your audience to look for the launch email and increases open rates when the launch email arrives.
告知用户即将有新动作，明确具体时间。
"我们将于本周四太平洋时间午夜在Product Hunt发布[产品名称]。[产品名称]是[一句话描述]。周四我们会分享更多内容，先提前通知你。"
这能让受众提前关注发布邮件，提升发布邮件的打开率。

Launch Day Email

发布日邮件

Your most important marketing email for the launch. Keep it short.
  • One clear headline announcing the launch.
  • One to two sentences on what the product does.
  • One sentence explaining what you would appreciate (a visit to Product Hunt, a trial signup, a share).
  • Direct links to the Product Hunt listing and the product.
No lengthy feature lists. No padding. Short respects the reader's time and converts better.
这是发布期间最重要的营销邮件，要简短。
  • 清晰的标题宣布发布。
  • 1到2句话说明产品功能。
  • 1句话说明你希望获得的支持（访问Product Hunt、注册试用、分享）。
  • Product Hunt列表和产品的直接链接。
不要冗长的功能列表，不要冗余内容。简短的内容尊重读者时间，转化率更高。

Post-Launch Follow-Up Email (2 to 3 Days After)

发布后跟进邮件（发布后2到3天）

Share the results. Tell your list what happened.
  • How many upvotes, signups, or press mentions you received.
  • One or two pieces of feedback you received and how you plan to address them.
  • A reminder of what the product does for anyone who missed launch day.
This email builds community and demonstrates transparency. It is one of the highest-engagement emails you will send.
分享成果，告知用户发布情况。
  • 获得的点赞数、注册量或媒体报道数。
  • 收到的1到2条反馈及你的解决计划。
  • 提醒错过发布日的用户产品能为他们带来什么。
这封邮件能建立社区感，展示透明度，是你发送的参与度最高的邮件之一。

Part 7: PR Outreach for Launches

第七部分：发布公关Outreach

Press coverage for launches requires preparation, targeting, and a compelling story. Generic press releases sent to general tech journalists rarely result in coverage.
发布的媒体报道需要准备、精准定位和引人入胜的故事。向普通科技记者发送通用新闻稿几乎不会获得报道。

Targeting the Right Journalists and Publications

精准定位记者和媒体

Identify journalists who have recently covered:
  • Products in your exact category.
  • Launches from companies at your stage.
  • Stories about the problem your product solves.
A reporter who covered "the rise of AI writing tools" six months ago is a better target than a general tech reporter who covers anything.
Build a list of 20 to 40 targets. Include their name, publication, their most relevant recent article, and how your story connects to what they cover.
找出近期报道过以下内容的记者：
  • 你所在细分领域的产品。
  • 与你公司阶段类似的产品发布。
  • 与你产品解决的问题相关的故事。
六个月前报道过"AI写作工具兴起"的记者，比什么都报道的通用科技记者更合适。
建立20到40个目标对象的列表，包括他们的姓名、媒体、最近最相关的文章，以及你的故事与他们报道内容的关联点。

The Pitch

公关邀约

A press pitch is not a press release. It is a short, direct email that:
  • References a specific piece of content they published (demonstrating you read their work).
  • Connects that piece to your launch story.
  • Offers one concrete, specific angle: a data point, a customer stat, or a trend angle.
  • Offers an exclusive or a demo.
The email should be under 200 words. No attachments on the first contact. Offer to send more if they are interested.
公关邀约不是新闻稿，而是简短直接的邮件，内容包括：
  • 提及他们发表过的一篇具体内容（表明你读过他们的作品）。
  • 将该内容与你的发布故事关联起来。
  • 提供一个具体、明确的角度：数据点、客户统计或趋势视角。
  • 提供独家报道机会或演示权限。
邮件应控制在200字以内。首次联系不要添加附件，如有兴趣再提供更多内容。

Timing

时间安排

Send embargoed pitches two to four business days before launch. An embargo means you ask the journalist to hold publication until your launch date. In exchange, you offer an exclusive or early access. Most tech journalists respect embargoes and appreciate the advance notice.
Send non-embargoed pitches on launch day, in the morning. These compete with everything else happening that day, but the launch activity (Product Hunt ranking, social engagement) gives journalists a concrete hook.
在发布前2到4个工作日发送embargoed公关邀约。Embargoed意味着要求记者在你的发布日之前不发布内容。作为交换，你提供独家报道机会或提前访问权限。大多数科技记者会尊重embargoed要求，并感谢提前通知。
在发布日上午发送非embargoed公关邀约。这些邀约要与当天的其他事件竞争，但发布活动（Product Hunt排名、社交互动）能为记者提供明确的切入点。

Part 8: Beta Launch vs. Public Launch

第八部分：Beta Launch vs. Public Launch

The choice between a beta launch and a public launch is often treated as a sequencing question. It is better treated as a positioning question.
A beta launch signals: "We are still learning. We want collaborators." A public launch signals: "We are ready. We want customers."
Both can be correct at the right time. The mistake is doing a public launch posture with beta product readiness, or doing a quiet beta when you have a product good enough to support a public launch moment.
Beta发布和公开发布的选择常被视为顺序问题，但更应被视为定位问题。
Beta发布传递的信号是："我们仍在学习，寻求合作者。" 公开发布传递的信号是："我们已准备就绪，寻求客户。"
在合适的时机，两者都是正确选择。错误的做法是用公开发布的姿态推出Beta阶段的产品，或是在产品足够成熟可以进行公开发布时，却选择低调的Beta测试。

Running a Successful Beta

成功运行Beta测试

Recruit 30 to 100 beta users from your network, your waitlist, or communities where your ICP hangs out. Be specific about what you are testing.
Create a dedicated feedback channel (Slack channel or Discord server) for beta users. Check it daily. Respond to every piece of feedback.
Set a beta timeline. "We will be in beta for eight weeks, then we are launching publicly in [month]." This gives beta users a sense of commitment and creates urgency for the public launch.
Offer beta users something for their participation: early pricing, lifetime access to a feature tier, or simply public acknowledgment in the launch.
从你的人脉、等待列表或你的ICP所在的社区招募30到100名Beta用户。明确说明你要测试的内容。
为Beta用户创建专属反馈渠道（Slack频道或Discord服务器），每天查看，回复每一条反馈。
设定Beta测试时间表："我们的Beta测试将持续8周，之后将于[月份]公开发布。"这能让Beta用户感受到明确的预期，同时为公开发布营造紧迫感。
为Beta用户的参与提供回报：早期定价、某功能 tier的终身使用权，或是在发布中公开致谢。

Part 9: Post-Launch Follow-Through

第九部分：发布后跟进

Most launch energy disappears within 72 hours. The teams that extract the most value from a launch are the ones that plan the 30 days after launch with the same care as launch day.
大多数发布的热度会在72小时内消退。能从发布中获取最大价值的团队，会像重视发布日一样精心规划发布后的30天。

Post-Launch Week 1

发布后第一周

  • Review all feedback from Product Hunt comments, social mentions, and support tickets.
  • Identify the top three product friction points surfaced during launch.
  • Send a personal thank-you to your top 10 launch supporters.
  • Write and publish a "what we learned from our launch" post on your blog. This drives secondary traffic from people who find launches interesting.
  • 梳理所有来自Product Hunt评论、社交提及和支持工单的反馈。
  • 找出发布期间暴露的三大产品痛点。
  • 向你的Top 10发布支持者发送个性化感谢。
  • 撰写并发布一篇"我们从发布中学到了什么"的博客文章。这能吸引对发布内容感兴趣的用户，带来二次流量。

Post-Launch Weeks 2 to 4

发布后第2到4周

  • Run your first post-launch customer interview. Ask launch-day signups what brought them in, what they expected, and what they found.
  • Activate any press coverage by sharing it across your channels.
  • Start your post-launch nurture sequence for anyone who signed up but has not activated.
  • Track cohort-specific activation and retention for launch-day signups. This tells you whether your launch attracted the right users.
  • 进行首次发布后客户访谈。询问发布日注册用户是什么吸引了他们、他们的预期是什么，以及实际体验如何。
  • 通过各渠道分享获得的媒体报道，扩大传播。
  • 启动发布后培育序列，针对已注册但未激活的用户。
  • 追踪发布日注册用户的群组激活率和留存率。这能告诉你发布是否吸引了正确的用户。

Measuring Launch Success

衡量发布成功

Assess these metrics 30 days after launch:
  • Total signups from the launch period (define the window: 72 hours, 7 days).
  • Activation rate for launch signups vs. baseline.
  • Trial-to-paid conversion rate for launch signups vs. baseline.
  • Press mentions (number, publication quality, reach).
  • Backlinks generated from the launch.
  • Product Hunt rank and total upvotes.
  • Social impressions and engagement.
A launch that drives 1,000 signups with a 5% activation rate is worse than a launch that drives 300 signups with a 40% activation rate. Track both volume and quality.
Use these numbers to inform your next launch. Every launch teaches you something about which channels perform for your specific audience.
发布30天后评估以下指标：
  • 发布期间的总注册量（定义时间窗口：72小时、7天）。
  • 发布注册用户的激活率与基准值对比。
  • 发布注册用户的试用转付费转化率与基准值对比。
  • 媒体报道数（数量、媒体质量、覆盖范围）。
  • 发布带来的反向链接数。
  • Product Hunt排名和总点赞数。
  • 社交曝光量和互动量。
带来1000个注册量但激活率仅5%的发布，不如带来300个注册量但激活率达40%的发布。同时追踪数量和质量。
用这些数据指导下一次发布。每一次发布都会让你了解哪些渠道适合你的特定受众。