Back to Details

gtm-0-to-1-launch

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

0-to-1 Launch

从0到1的产品发布

Launch new products from idea to first customers. The goal isn't headlines — it's finding 10 customers who can't live without you.
将新产品从创意阶段推进到获取首批客户。我们的目标不是登上头条——而是找到10位离不开你的核心客户。

When to Use

适用场景

Triggers:
  • "How do we launch this product?"
  • "First customer acquisition strategy"
  • "We launched but nobody's using it"
  • "Product Hunt vs direct outreach?"
  • "We have awareness but no conversion"
  • "How do I know if this is working?"
Context:
  • New product launches
  • Feature launches that feel like new products
  • Finding first 10-50 customers
  • Validating product-market fit
  • Diagnosing why early traction stalls
触发信号：
  • “我们该如何发布这款产品？”
  • “首批客户获取策略”
  • “我们发布了产品，但没人使用”
  • “选择Product Hunt还是直接触达客户？”
  • “我们有品牌曝光但没有转化”
  • “我怎么知道这个策略是否有效？”
适用背景：
  • 全新产品发布
  • 相当于全新产品的功能发布
  • 寻找首批10-50位客户
  • 验证产品-市场契合度（PMF）
  • 诊断早期用户增长停滞的原因

Core Frameworks

核心框架

1. Press ≠ Growth (The Launch That Got 12 Signups)

1. 媒体报道≠用户增长（那个获得5万曝光却仅12人注册的发布案例）

The Pattern:
Coordinated a feature launch with full press tour. TechCrunch, VentureBeat, product blogs. Big announcement day.
Result:
  • 50K impressions
  • 12 signups
  • 2 conversions
Why It Failed:
Optimized for media buzz, not user value. The feature wasn't ready for self-serve. It needed education, context, hand-holding. Press gives you eyeballs. But eyeballs without activation = vanity.
What Works Better:
Email 50 target customers directly. "We built [feature] because teams like yours struggle with [problem]. Want early access?" Walk them through setup personally. Get feedback, iterate.
Result: 50 emails → 15 replies (30% reply rate) → 8 trials → 4 conversions (50% trial-to-paid).
The Lesson:
Early customers come from direct outreach, not press coverage. Press matters later (Series A announcement, major milestone). For 0-to-1, it's distraction.
案例经过：
协调了一场全渠道媒体宣传的功能发布，覆盖TechCrunch、VentureBeat及各类产品博客，打造了盛大的发布日。
结果：
  • 5万次曝光
  • 12人注册
  • 2人完成转化
失败原因：
过度优化媒体曝光，而非用户价值。该功能尚未做好自助服务准备，需要配套的指导、背景介绍和人工支持。媒体能给你带来流量，但没有激活的流量只是虚荣指标。
更优策略：
直接给50位目标客户发送邮件：“我们打造了[功能]，因为像你们这样的团队正面临[问题]的困扰。要不要提前体验？”亲自引导他们完成设置，收集反馈并迭代产品。
结果： 50封邮件 → 15条回复（30%回复率）→ 8人开启试用 → 4人完成转化（50%试用转付费率）。
经验教训：
早期客户来自直接触达，而非媒体报道。媒体宣传的价值在后期才会体现（比如A轮融资公告、重大里程碑发布）。对于从0到1的阶段，媒体宣传只会分散精力。

2. The Three-Layer Diagnosis (Why Launches Stall)

2. 三层诊断模型（解析发布停滞的原因）

The Pattern:
You launched. You have some awareness. But conversion is weak. The problem lives in one of three layers, and each requires a different intervention.
Layer 1: Positioning Problem
Symptoms:
  • Messaging sounds like competitors
  • Differentiation requires explaining complex technical details
  • Buyers see you as interchangeable with alternatives
  • Sales conversations get derailed by comparison questions
Diagnosis: You're "fighting an asymmetric war on the wrong front" — competing on features against better-funded companies. Map where competitors claim unique value. Find the position they can't easily copy.
Fix: Stake a claim you can own structurally (not just through product features). Test with outbound messaging before committing product resources.
Layer 2: Experience Problem
Symptoms:
  • Strong awareness but weak activation
  • Users sign up but don't complete first workflow
  • Multiple entry points creating decision paralysis
  • Documentation is feature-centric, not outcome-centric
Diagnosis: Flexibility without opinionated defaults is a liability, not a feature. Users face the "paradox of choice" — too many options, not enough guidance to the aha moment.
Fix: Identify 2-3 "undeniable use cases" that deliver immediate value. Restrict onboarding to those specific use cases. Gate advanced features behind a mastery path. Rewrite help content around jobs-to-be-done, not feature lists.
Layer 3: Alignment Problem
Symptoms:
  • Team reports being "out of bandwidth" for customers
  • Different functions optimize for different metrics
  • Every idea has equal weight (no tiebreaker)
  • No clear north star connecting activities to outcomes
Diagnosis: "Exploratory mode" — where every initiative has equal priority — becomes destructive when resources are constrained.
Fix: Define a single shared north star. Use it as tiebreaker for every decision: "Does this help us win a customer?" Cut activities that don't ladder up. Make progress visible weekly, not quarterly.
How to Use This:
When a launch stalls, diagnose which layer is broken before throwing resources at it. Fixing experience when the problem is positioning wastes engineering time. Fixing positioning when the problem is internal alignment wastes marketing spend.
常见情况：
你完成了产品发布，获得了一定曝光，但转化率极低。问题通常出在以下三个层面之一，每个层面需要不同的解决方案。
第一层：定位问题
症状：
  • 产品messaging与竞争对手同质化
  • 差异化需要复杂的技术解释
  • 买家认为你与其他竞品可替代
  • 销售对话常被竞品对比问题打断
诊断：你在“错误的战场打一场不对称战争”——在功能层面与资金更充足的公司竞争。梳理竞品宣称的独特价值点，找到他们无法轻易复制的定位。
解决方案：抢占一个你能从结构上（而非仅通过产品功能）占据的定位。在投入产品资源前，先通过outbound消息测试验证定位效果。
第二层：体验问题
症状：
  • 曝光量高但激活率低
  • 用户注册后无法完成首次核心操作
  • 多入口导致用户决策瘫痪
  • 文档以功能为中心，而非以用户成果为中心
诊断：没有预设最优路径的灵活性是负担，而非优势。用户会陷入“选择悖论”——选项太多，却缺乏引导至“aha时刻”的路径。
解决方案：确定2-3个能快速交付价值的“不可替代使用场景”。将新用户引导流程限制在这些场景内，把高级功能放在进阶路径之后。围绕用户“要完成的工作”重写帮助文档，而非罗列功能列表。
第三层：内部对齐问题
症状：
  • 团队反馈“没有精力服务客户”
  • 不同部门优化的指标不一致
  • 所有想法优先级相同（没有决策依据）
  • 没有清晰的北极星指标将行动与结果关联
诊断：“探索模式”——所有项目优先级相同——在资源有限时会产生破坏性影响。
解决方案：定义唯一的共享北极星指标。用它作为所有决策的判断标准：“这能帮我们赢得客户吗？”砍掉无法支撑该目标的活动。每周而非每季度同步进度。
使用方法：
当发布陷入停滞时，先诊断问题所在层面，再投入资源。如果问题是定位却去优化体验，会浪费工程资源；如果问题是内部对齐却去优化定位，会浪费营销预算。

3. The First 10 Customers Framework

3. 首批10位客户获取框架

Principle: First 10 customers are not for revenue. They're for learning.
What You're Learning:
  1. Does the product actually solve the problem?
  2. What's the activation flow? (How do they get value?)
  3. What objections come up? (Price, features, integrations?)
  4. Who's the real buyer? (Title, role, budget authority?)
  5. What's the sales cycle? (Days, weeks, months?)
How to Find Them:
Channel 1: Personal Network (first 2-3)
  • "I'm building [X], can I get your feedback?"
  • Convert to paying customers (don't give away for free — free users give different feedback than paying ones)
Channel 2: Direct Outreach (customers 3-20)
  • Build list of 100 target accounts
  • Personalize to their specific pain
  • Test messaging variants — which angle gets replies?
Channel 3: Ceiling Moment Targeting (highest-intent)
  • The highest-intent prospects are people who've already adopted a comparable solution and hit its limits
  • They've invested in learning a tool, hit its ceiling, and have low switching costs
  • Craft outreach around the limitation: "We see teams that outgrow [incumbent] when they need [capability]. That's what we built."
  • These convert 3-5x better than cold outreach because they already understand the problem
Channel 4: Community (developer products)
  • "Built [X] to solve [problem], looking for early users"
  • Offer white-glove onboarding
  • Best for products where users congregate in Slack/Discord/forums
核心原则： 首批10位客户的核心价值不是带来收入，而是为产品迭代提供学习反馈。
你需要学习的内容：
  1. 产品是否真的解决了用户的问题？
  2. 最优激活路径是什么？（用户如何快速获得价值？）
  3. 用户会提出哪些异议？（价格、功能、集成问题？）
  4. 真正的决策者是谁？（职位、角色、预算权限？）
  5. 销售周期是多久？（天、周、月？）
获取渠道：
渠道1：个人人脉（前2-3位）
  • “我正在打造[X]，能请你提供反馈吗？”
  • 转化为付费客户（不要免费赠送——免费用户的反馈与付费用户截然不同）
渠道2：直接触达（第3-20位客户）
  • 构建包含100个目标客户的列表
  • 根据他们的具体痛点个性化定制消息
  • 测试不同的消息变体——哪种角度的回复率更高？
渠道3：天花板时刻定位（最高意向客户）
  • 最高意向的潜在客户是那些已经使用同类解决方案并遇到瓶颈的人
  • 他们已经投入时间学习工具，遇到了上限，切换成本低
  • 围绕痛点撰写触达消息：“我们发现使用[竞品]的团队在需要[能力]时会遇到瓶颈，这正是我们产品要解决的问题。”
  • 这类客户的转化率是冷触达的3-5倍，因为他们已经深刻理解问题
渠道4：社区（面向开发者产品）
  • “我们打造了[X]来解决[问题]，正在寻找早期用户”
  • 提供白手套式的专属引导服务
  • 最适合用户聚集在Slack/Discord/论坛等社区的产品

4. The 2-Week Experiment Cycle

4. 两周实验周期

The Pattern:
Speed in early stages matters more than perfection. The constraint isn't whether you're right — it's how quickly you can test assumptions and iterate.
How to Execute:
  • Frame every test with clear success criteria before starting
  • Test one variable per experiment (messaging, channel, pricing, feature)
  • Run for 2 weeks maximum — if it's not showing signal by then, it won't
  • If it works, allocate 3x resources within a week
  • If it doesn't, kill it and move to the next test
  • Document what you learned regardless of outcome
The Playbook Rule:
Every successful experiment must become a playbook before scaling. Structure: Goal → Steps → Expected output → Metrics → Risks. If someone unfamiliar can't execute the playbook, it's not documented well enough.
Why This Matters:
One-off wins don't compound. Systematized experiments do. The goal isn't a single launch — it's building a repeatable machine for testing assumptions at speed.
Common Mistake:
Over-planning before testing. Waiting for "perfect" conditions before launching. Staying with failing experiments too long because you've invested emotional energy. Make decisions with 70% information.
核心逻辑：
早期阶段，速度比完美更重要。限制你的不是判断对错的能力，而是测试假设并迭代的速度。
执行步骤：
  • 在开始前，为每个测试设定清晰的成功标准
  • 每次实验只测试一个变量（消息、渠道、定价、功能）
  • 实验周期最长不超过两周——如果两周内没有看到积极信号，就终止
  • 如果实验成功，在一周内将资源投入增加3倍
  • 如果实验失败，立即终止并转向下一个测试
  • 无论结果如何，都要记录学习到的内容
行动手册规则：
每个成功的实验必须转化为可复用的行动手册才能规模化。结构：目标 → 步骤 → 预期输出 → 指标 → 风险。如果不熟悉项目的人无法按照手册执行，说明文档不够完善。
重要性：
单次成功无法形成复利效应，系统化的实验才能。我们的目标不是完成一次发布——而是打造一个能快速测试假设的可复用机制。
常见误区：
在测试前过度规划，等待“完美”的条件再启动。在实验失败后因情感投入而迟迟不终止。用70%的信息就可以做决策。

5. Partner-Led Market Entry (When You Don't Have Distribution)

5. 合作伙伴驱动的市场进入策略（当你没有自有分发渠道时）

The Pattern:
Rather than entering new markets through direct sales alone, use partnerships with established players to accelerate.
How to Execute:
  1. Identify market leaders in your target segment
  2. Approach with customer problem, not partnership pitch — "What if your users could access [capability]?" shifts from your need to their need
  3. Start small: Help them solve one specific problem (narrow integration, not full partnership)
  4. Prove value with a 3-6 month pilot before asking for broader commitment
  5. Build reference customers together — reduces their risk
  6. Leverage their GTM: once integrated, they market to their base
The Supernode Pattern:
Position yourself as the integration hub that other tools naturally connect through. You own critical data or workflows that other platforms need. This compounds — each new partner makes you more valuable to the next.
Category Sequencing:
Don't pursue partnerships everywhere. Dominate 2-3 categories per quarter:
  1. Lead with genuine use cases: "Our users ask for [partner] integration 50x per month"
  2. Once you partner with a top player, competitors feel urgency to work with you too
  3. After 2-3 successful partnerships in a category, create joint customer stories
Common Mistake:
Launching partnerships without clear integration pathways. Expecting partners to drive awareness without support. Treating partnerships as a sales channel rather than platform expansion.
核心逻辑：
不要仅通过直接销售进入新市场，与行业头部玩家合作能加速你的扩张。
执行步骤：
  1. 识别目标细分领域的市场领导者
  2. 以客户问题为切入点，而非直接提出合作请求——“如果你的用户能获得[能力]，会怎么样？”将焦点从你的需求转移到他们的需求
  3. 从小处着手：帮助他们解决一个具体问题（窄范围集成，而非全面合作）
  4. 在寻求更广泛的合作前，先用3-6个月的试点证明价值
  5. 共同打造参考客户——降低他们的风险
  6. 利用他们的GTM（上市）渠道：集成完成后，他们会向自己的用户群体推广你的产品
超级节点模式：
将自己定位为其他工具自然连接的集成枢纽。你掌握其他平台需要的关键数据或工作流。这种模式会形成复利效应——每新增一个合作伙伴，你对下一个合作伙伴的价值就越高。
品类排序：
不要同时在所有领域寻求合作。每个季度专注于2-3个品类：
  1. 从真实的用户需求出发：“我们的用户每月有50次请求集成[合作伙伴]”
  2. 一旦你与某个品类的头部玩家合作，竞品会有更强的合作意愿
  3. 在一个品类完成2-3次成功合作后，共创客户案例
常见误区：
在没有清晰集成路径的情况下启动合作。期望合作伙伴在没有支持的情况下为你带来曝光。将合作视为销售渠道而非平台拓展手段。

6. PMF Validation Checklist

6. PMF验证清单

Product-market fit is when customers pull you forward, not when you push them.
Retention:
  • 40%+ of Week 1 users return Week 4
  • Usage increasing over time
  • Customers renewing without sales push
Organic Growth:
  • Word-of-mouth referrals happening
  • Customers asking "can I add my team?"
  • Inbound interest without paid marketing
Sales Velocity:
  • Sales cycles shortening
  • Win rates >30% of trials
  • Customers saying "we need this now"
Qualitative:
  • >40% very disappointed if product went away (Sean Ellis test)
  • Customers can articulate what it's for (clear use case)
  • Customers advocating publicly
If you don't have these, you don't have PMF yet. Don't scale marketing/sales.
产品-市场契合度（PMF）的定义是：客户主动向你靠拢，而非你去推动客户。
留存指标：
  • 第1周的用户中，有40%以上在第4周返回使用
  • 用户使用频率随时间提升
  • 客户无需销售推动就主动续费
自然增长指标：
  • 出现口碑推荐
  • 客户询问“我可以邀请我的团队使用吗？”
  • 无需付费营销就有潜在客户主动咨询
销售效率指标：
  • 销售周期缩短
  • 试用用户的转化率超过30%
  • 客户表示“我们现在就需要这个产品”
定性指标：
  • 超过40%的用户表示如果产品下架会非常失望（Sean Ellis测试）
  • 客户能清晰表述产品的用途（明确的使用场景）
  • 客户主动公开推荐你的产品
如果以上指标未达成，说明你尚未实现PMF。此时不要规模化营销或销售投入。

Decision Trees

决策树

Why Is Our Launch Stalling?

为什么我们的发布陷入停滞？

Do prospects understand what you are?
├─ No → Layer 1: Positioning problem
│         Fix: Test new messaging before changing product
└─ Yes → Continue...
    │
    Do users activate after signing up?
    ├─ No → Layer 2: Experience problem
    │         Fix: Restrict onboarding to 2-3 use cases, guide to aha moment
    └─ Yes → Continue...
        │
        Is the team aligned on what matters?
        ├─ No → Layer 3: Alignment problem
        │         Fix: Single north star, weekly visibility, cut non-essential
        └─ Yes → Keep iterating, you're on the right track
Do prospects understand what you are?
├─ No → Layer 1: Positioning problem
│         Fix: Test new messaging before changing product
└─ Yes → Continue...
    │
    Do users activate after signing up?
    ├─ No → Layer 2: Experience problem
    │         Fix: Restrict onboarding to 2-3 use cases, guide to aha moment
    └─ Yes → Continue...
        │
        Is the team aligned on what matters?
        ├─ No → Layer 3: Alignment problem
        │         Fix: Single north star, weekly visibility, cut non-essential
        └─ Yes → Keep iterating, you're on the right track

Press Launch or Direct Outreach?

选择媒体发布还是直接触达？

Self-serve ready? (Users get value in <10 min)
├─ No → Direct outreach only (press won't convert)
└─ Yes → Do you have >$1M funding to announce?
    ├─ Yes → Both (press for awareness, outreach for conversion)
    └─ No → Direct outreach first, press later
Self-serve ready? (Users get value in <10 min)
├─ No → Direct outreach only (press won't convert)
└─ Yes → Do you have >$1M funding to announce?
    ├─ Yes → Both (press for awareness, outreach for conversion)
    └─ No → Direct outreach first, press later

Common Mistakes

常见误区

1. Optimizing for headlines instead of activation 50K impressions and 12 signups. Press ≠ growth.
2. No target customer list before launch Spray-and-pray doesn't work at 0-to-1. Build the list of 100 accounts first.
3. Flexibility without defaults Giving users every option paralyzes them. Pick 2-3 undeniable use cases and guide hard.
4. Giving product away for free Free users give polite feedback. Paying users give honest feedback.
5. Scaling before learning First 10 customers are for learning, not revenue. Document everything.
6. Over-planning, under-testing 2-week experiments with clear kill criteria. Move fast, document learnings.
7. Diagnosing the wrong layer Positioning fix when the problem is experience = wasted marketing. Experience fix when the problem is positioning = wasted engineering.
1. 过度优化头条曝光而非用户激活 5万次曝光却仅12人注册。媒体报道≠用户增长。
2. 发布前没有目标客户列表 广撒网的策略在从0到1阶段无效。先构建包含100个目标客户的列表。
3. 只提供灵活性却没有预设最优路径 给用户太多选择会导致决策瘫痪。选定2-3个不可替代的使用场景并强力引导用户。
4. 免费赠送产品 免费用户只会给出客气的反馈，付费用户才会给出真实的反馈。
5. 在学习前就规模化 首批10位客户的价值是学习，而非收入。记录所有学习内容。
6. 过度规划，测试不足 采用两周实验周期并设定清晰的终止标准。快速行动，记录学习内容。
7. 诊断错误的问题层面 如果问题是体验却去优化定位=浪费营销预算。如果问题是定位却去优化体验=浪费工程资源。

Quick Reference

快速参考

Three-layer diagnosis: Layer 1: Positioning (messaging sounds like competitors) → Test new messaging Layer 2: Experience (awareness but no activation) → Guide to aha moment Layer 3: Alignment (team scattered) → Single north star, weekly visibility
First 10 customers: Personal network (2-3) → Direct outreach (3-20) → Ceiling moment targeting (highest intent) → Community (developer products)
2-week experiment cycle: Hypothesis → Success criteria → Test (2 weeks max) → Kill or 3x → Document playbook
PMF signals: 40%+ Week 1→4 retention + word-of-mouth + shortening sales cycles + >40% very disappointed
Partner-led entry: Customer problem first → Narrow pilot → Reference customers together → Leverage their GTM
三层诊断模型： 第一层：定位问题（messaging与竞品同质化）→ 测试新的messaging 第二层：体验问题（有曝光但无激活）→ 引导用户至aha时刻 第三层：对齐问题（团队精力分散）→ 设定唯一北极星指标，每周同步进度
首批10位客户获取路径： 个人人脉（2-3位）→ 直接触达（3-20位）→ 天花板时刻定位（最高意向）→ 社区（开发者产品）
两周实验周期： 假设 → 成功标准 → 测试（最长两周）→ 终止或投入3倍资源 → 记录为行动手册
PMF信号： 第1周到第4周留存率≥40% + 口碑推荐 + 销售周期缩短 + 超过40%用户表示产品下架会非常失望
合作伙伴驱动的市场进入： 先聚焦客户问题 → 窄范围试点 → 共同打造参考客户 → 利用他们的GTM渠道

Related Skills

相关技能

  • product-led-growth: Scaling after initial traction
  • positioning-strategy: Positioning for launch
  • partnership-architecture: Partner-led market entry
Based on launching features that optimized for press and got 12 signups from 50K impressions, diagnosing launch stalls across three companies using the three-layer model, and building the 2-week experiment cycle that turned ad hoc testing into a repeatable machine. Also draws on partner-led market entry across multiple geographies and segments. Not theory — lessons from mistaking vanity metrics for growth and learning to diagnose the actual problem.
  • product-led-growth: 初始用户增长后的规模化策略
  • positioning-strategy: 发布阶段的定位策略
  • partnership-architecture: 合作伙伴驱动的市场进入
基于以下实践经验总结：曾主导一场过度优化媒体曝光的功能发布，获得5万曝光却仅12人注册；用三层诊断模型在三家公司诊断发布停滞问题；打造两周实验周期将零散测试转化为可复用机制；在多个地区和细分领域实践合作伙伴驱动的市场进入策略。这不是理论——是从将虚荣指标误认为增长的错误中，以及学习诊断真实问题的过程中总结的经验。