go-to-market-strategy

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Go-to-Market Strategy

上市（GTM）策略

End-to-end GTM playbook: motion selection, positioning, channel strategy, phased launch execution, launch marketing, and technical product launches.

端到端GTM手册：涵盖运作模式选择、定位、渠道策略、分阶段发布执行、发布营销以及技术产品发布。

Core Philosophy

核心理念

A launch is a campaign, not an event. Build momentum before launch, peak at launch, sustain after. The best companies don't launch once — they launch again and again.

发布是一场持续的营销活动，而非单次事件。 在发布前积累势能，发布时达到峰值，发布后维持热度。顶尖企业不会只做一次发布——他们会持续进行多次发布。

GTM Motion Selection

GTM运作模式选择

Motion	Best For	Key Lever
PLG	SMB, developers, low ACV (<$5K)	Free → paid conversion
PLG + Sales-Assist	Mid-market, $5K-$25K ACV	PQL → SQL routing
Sales-Led	Enterprise, complex product, >$25K ACV	Relationship, champion
Community-Led	Developer tools, OSS	Community adoption
Partner-Led	Geographic expansion, enterprise	Partner incentives

Quick decision:

ACV < $5K and self-serve possible? → PLG
Buyer technical? → Developer/community-led
Everything else? → Sales-led

运作模式	适用场景	核心杠杆
PLG	中小企业、开发者、低ACV（<$5K）	免费转付费转化
PLG + 销售辅助	中大型企业、$5K-$25K ACV	PQL转SQL线索分配
销售驱动	大型企业、复杂产品、>$25K ACV	客户关系、内部支持者
社区驱动	开发者工具、开源软件	社区采纳
合作伙伴驱动	地域扩张、大型企业	合作伙伴激励

快速决策指南：

ACV < $5K且支持自助服务？→ PLG
买家为技术用户？→ 开发者/社区驱动
其他情况？→ 销售驱动

5-Phase GTM Strategy

五阶段GTM策略

Phase 1: Market Positioning

阶段1：市场定位

Define how your product fits in the market.

Positioning template:

For [target customer]
Who [need/problem]
[Product] is a [category]
That [key benefit]
Unlike [competitors]
Our product [unique differentiator]

Validate: target customer defined, differentiation identified, tested with 5+ customers.

定义产品在市场中的定位。

定位模板：

针对 [目标客户]
他们面临 [需求/问题]
[产品] 是一款 [品类]
能够 [核心价值]
与 [竞品] 不同
我们的产品 [独特差异化优势]

验证标准：明确目标客户、确定差异化优势、已与5位以上客户测试。

Phase 2: Messaging & Content

阶段2：信息传递与内容创作

Message hierarchy:

Headline — Core benefit in 5-10 words
Sub-headline — How it works or who it's for
3 Key Benefits — Feature → benefit
Social Proof — Testimonials, logos, metrics
CTA — Clear next step

Content to create: Launch blog post · Product demo video (2-3 min) · Landing page · Email announcement · 5-10 social posts

信息层级：

标题 — 5-10字概括核心价值
副标题 — 说明运作方式或目标用户
3个核心价值点 — 功能转化为价值
社交证明 — 客户证言、品牌logo、数据指标
行动召唤（CTA） — 清晰的下一步操作

需创建的内容： 发布博客文章 · 产品演示视频（2-3分钟） · 落地页 · 邮件公告 · 5-10条社交平台帖子

Phase 3: Channel Strategy (ORB)

阶段3：渠道策略（ORB模型）

Owned (highest ROI — build these first): Email list · Blog/SEO · Branded community

Rented (speed, not stability): Twitter/X · LinkedIn · YouTube · Reddit — use to drive to owned

Borrowed (shortcut to audiences): Guest posts · Podcast interviews · Influencer partnerships · Co-marketing

Strategy: Use rented/borrowed to drive traffic, capture into owned.

自有渠道（ROI最高 — 优先搭建）：邮件列表 · 博客/SEO · 品牌社区

租赁渠道（速度快，但稳定性弱）：Twitter/X · LinkedIn · YouTube · Reddit — 用于引流至自有渠道

借用渠道（快速触达精准受众）：客座文章 · 播客访谈 · 网红合作 · 联合营销

策略：利用租赁/借用渠道引流，将用户沉淀至自有渠道。

Phase 4: Launch Timeline

阶段4：发布时间线

6-Week Launch Timeline:

Week -6: Finalize messaging, create content, set metrics
Week -4: Build waitlist, draft emails, reach out to press/influencers
Week -2: Tease on social, send "coming soon" emails, final QA
Week 0 (Launch Day): Publish landing page + blog, post to Product Hunt 12:01 AM PT, send launch email, share on socials, monitor and respond
Week +1: Share testimonials, post case studies, analyze metrics
Week +2: Post-launch analysis, plan ongoing marketing

6周发布时间线：

第-6周： 敲定信息传递内容、创作物料、设定指标
第-4周： 搭建等待名单、撰写邮件草稿、联系媒体/网红
第-2周： 社交平台预热、发送“即将上线”邮件、最终QA测试
第0周（发布日）： 上线落地页+博客、PT时间凌晨12:01发布至Product Hunt、发送发布邮件、社交平台分享、监控并回复用户
第+1周： 分享客户证言、发布案例研究、分析数据指标
第+2周： 发布后复盘、规划后续营销活动

Phase 5: Metrics & Success Criteria

阶段5：指标与成功标准

Define BEFORE launch:

Awareness: Website visitors, social impressions
Acquisition: Signups, trial starts, purchases
Activation: Users completing core action
Revenue: MRR, conversion rate

发布前必须明确：

认知度： 网站访客量、社交平台曝光量
获客： 注册量、试用启动量、购买量
激活： 完成核心操作的用户数
收入： MRR、转化率

Multi-Phase Launch Approach

多阶段发布方法

Phase	Goal	Key Actions
Internal	Validate functionality	Test with friendly users, fix major issues
Alpha	First external validation	Landing page, waitlist, invite individually
Beta	Scale early access + buzz	Work through waitlist, tease problems you solve
Early Access	Validate at scale	Leak details, usage data, PMF survey
Full Launch	Maximum visibility	Open signups, start charging, all channels live

阶段	目标	核心动作
内部测试	验证功能可用性	友好用户测试、修复重大问题
Alpha测试	首次外部验证	落地页、等待名单、定向邀请用户
Beta测试	扩大提前访问范围+制造热度	处理等待名单用户、宣传解决的问题
提前访问	规模化验证	泄露细节、收集使用数据、PMF调研
正式发布	最大化曝光	开放注册、开始收费、全渠道启动

Product Hunt Launch

Product Hunt发布指南

Before launch day: Build relationships with supporters, optimize listing (tagline, visuals, demo video), engage in communities.

On launch day: Treat as all-day event. Respond to every comment. Drive traffic back to site to capture signups.

After: Follow up with all who engaged. Convert PH traffic into email signups.

Case study — Reform: studied successful launches, polished visuals, community engagement pre-launch → #1 Product of the Day.

发布前： 与支持者建立联系、优化列表信息（标语、视觉素材、演示视频）、参与社区互动

发布日： 当作全天活动对待。回复每一条评论。引流至官网以获取注册用户

发布后： 跟进所有互动用户。将Product Hunt流量转化为邮件订阅用户

案例研究 — Reform：研究成功发布案例、打磨视觉素材、发布前社区互动 → 获得当日最佳产品称号。

Launch Marketing Pack

发布营销包

For any major launch, produce these 7 deliverables:

Context snapshot — what's launching, who it's for, goal, date, constraints
Launch Marketing Brief — message, hook/sizzle, proof points, CTA, audience segments
Launch Motion + Channel Plan — sequencing, channel table, asset mapping
PR Outreach Kit — exclusive decision, target outlets, pitch + follow-up emails
Asset + Internal Readiness Kit — asset checklist, landing page outline, sales talk track, FAQ, objections
Measurement + Experiment Plan — metrics, instruments, experiments, what to double down on
Risks / Open questions / Next steps

For launch marketing templates: see

references/TEMPLATES.md

For intake questions to gather launch inputs: see

references/INTAKE.md

For full workflow guidance: see

references/WORKFLOW.md

针对重大发布，需产出以下7份交付物：

背景快照 — 发布内容、目标用户、目标、日期、约束条件
发布营销简报 — 核心信息、钩子、证明点、CTA、受众细分
发布运作模式+渠道计划 — 时间顺序、渠道表格、物料映射
媒体拓展工具包 — 独家内容决策、目标媒体、 pitch邮件+跟进邮件
物料+内部准备工具包 — 物料清单、落地页大纲、销售话术、FAQ、异议处理
度量+实验计划 — 指标、追踪工具、实验内容、重点投入方向
风险/待解决问题/下一步动作

发布营销模板：见

references/TEMPLATES.md

收集发布需求的问题清单：见

references/INTAKE.md

完整工作流指南：见

references/WORKFLOW.md

Technical Product Launches

技术产品发布

For developer tools, APIs, SDKs, and technical infrastructure:

适用于开发者工具、API、SDK以及技术基础设施：

Launch Tiers

发布层级

Tier	Type	Timeline	Investment
1 — Major	New product/GA	12-16 weeks	High
2 — Standard	New features/integrations	6-8 weeks	Medium
3 — Minor	Updates/patches	2-4 weeks	Low

层级	类型	时间线	投入资源
1 — 重大发布	新产品/正式版（GA）	12-16周	高
2 — 标准发布	新功能/集成	6-8周	中
3 — 小型发布	更新/补丁	2-4周	低

Developer-First Principles

开发者优先原则

Documentation is non-negotiable — Don't launch without a getting started guide + API reference + 3+ code samples
Show, don't tell — Actual code > marketing copy
Interactive > passive — Playground > demo video > screenshots
Community-first — Answer Stack Overflow, engage GitHub, respond on Hacker News

文档是硬性要求 — 发布前必须准备入门指南+API参考文档+3个以上代码示例
展示而非说教 — 实际代码优于营销文案
交互式优于被动式 — 在线调试环境 > 演示视频 > 截图
社区优先 — 回答Stack Overflow问题、参与GitHub讨论、回复Hacker News评论

Primary Developer Channels

核心开发者渠道

Dev docs · GitHub/GitLab · Developer blog · API changelog · Dev.to · Hacker News · Reddit · Discord/Slack · YouTube tutorials

For tier framework details: see

references/launch_tiers.md

For developer metrics: see

references/metrics_frameworks.md

开发者文档 · GitHub/GitLab · 开发者博客 · API更新日志 · Dev.to · Hacker News · Reddit · Discord/Slack · YouTube教程

层级框架细节：见

references/launch_tiers.md

开发者指标：见

references/metrics_frameworks.md

GTM Execution Checklist

GTM执行检查清单

Pre-Launch

发布前

Launch Day

发布日

Post-Launch

发布后

Common GTM Mistakes

常见GTM误区

Launching without audience — Build email list first
One-day launch, then silence — Plan 30 days of post-launch activity
Everything everywhere — Pick 2-3 channels, do them well
No success metrics — Define goals before launch
Features not benefits — "You can achieve X" beats "We have feature X"
Over-promising — Ground claims in real evidence

无受众基础就发布 — 先搭建邮件列表
仅做单日发布，之后无动作 — 规划30天的发布后活动
全面铺开所有渠道 — 选择2-3个渠道，深耕运营
未设定成功指标 — 发布前明确目标
只讲功能不讲价值 — “你可以实现X”优于“我们有功能X”
过度承诺 — 所有宣传需基于真实证据