prd-v09-gtm-strategy
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseGTM Strategy
GTM策略
Position in workflow: v0.8 Monitoring Setup → v0.9 GTM Strategy → v0.9 Launch Metrics
在工作流中的位置:v0.8 监控设置 → v0.9 GTM策略 → v0.9 发布指标
Purpose
目的
Define how the product reaches its target users—the channels, messaging, timing, and coordination required for a successful launch.
定义产品触达目标用户的方式——包括成功发布所需的渠道、信息传递、时间安排和协作机制。
Core Concept: Launch as Campaign
核心概念:发布即营销活动
A launch is not "making the product available." It is a coordinated campaign that creates awareness, drives activation, and captures feedback. Every touchpoint should move users toward value.
发布不是“让产品可用”,而是一场协调一致的营销活动,用于打造认知度、推动用户激活并收集反馈。每个触点都应引导用户获取价值。
GTM Components
GTM组件
| Component | Purpose | Output |
|---|---|---|
| Messaging | What we say | GTM- (value props, headlines) |
| Channels | Where we say it | GTM- (channel strategy) |
| Timing | When we launch | GTM- (timeline, phases) |
| Coordination | Who does what | GTM- (RACI, tasks) |
| 组件 | 目的 | 输出 |
|---|---|---|
| 信息传递 | 我们传递的内容 | GTM-(价值主张、标题) |
| 渠道 | 我们的发布渠道 | GTM-(渠道策略) |
| 时间安排 | 我们的发布时机 | GTM-(时间线、阶段) |
| 协作机制 | 分工与职责 | GTM-(RACI矩阵、任务) |
Execution
执行步骤
-
Review target personas
- Pull PER- from v0.4
- Understand where they spend time
- Know what messages resonate
-
Define core messaging
- Value proposition (from CFD- value hypotheses)
- Positioning (from BR- product type)
- Key differentiators (from v0.2 competitive landscape)
-
Select launch channels
- Match channels to personas
- Prioritize by reach and conversion potential
- Consider owned, earned, and paid media
-
Plan launch timeline
- Pre-launch: Build anticipation
- Launch day: Maximum impact
- Post-launch: Sustain momentum
-
Assign ownership
- Who creates content?
- Who monitors channels?
- Who handles support surge?
-
Create GTM- entries with full traceability
-
回顾目标用户画像
- 调取v0.4中的PER-条目
- 了解他们活跃的平台
- 明确能引起他们共鸣的信息
-
定义核心信息
- 价值主张(来自CFD-价值假设)
- 市场定位(来自BR-产品类型)
- 核心差异化优势(来自v0.2竞争格局分析)
-
选择发布渠道
- 匹配渠道与用户画像
- 根据覆盖范围和转化潜力优先排序
- 考虑自有媒体、 earned媒体和付费媒体
-
制定发布时间线
- 预热期:打造用户期待
- 发布日:实现最大曝光
- 发布后:维持热度
-
分配职责
- 谁负责内容创作?
- 谁负责监控渠道?
- 谁负责应对支持请求激增?
-
创建具备完整可追溯性的GTM-条目
GTM- Output Template
GTM-输出模板
GTM-XXX: [GTM Item Title]
Type: [Messaging | Channel | Timeline | Task | Asset]
Owner: [Person or team responsible]
Status: [Planned | In Progress | Ready | Live]
For Messaging Type:
Audience: [PER-XXX targeted]
Format: [Headline | Value Prop | Tagline | Elevator Pitch]
Message: [The actual copy]
Supporting Evidence: [CFD-XXX value hypothesis it's based on]
Where Used: [GTM-YYY channels, assets]
For Channel Type:
Channel: [Specific platform or medium]
Audience Fit: [Why this channel reaches PER-XXX]
Strategy: [How we'll use this channel]
Content Plan: [What content goes here]
Success Metric: [How we measure effectiveness]
Linked Assets: [GTM-YYY assets for this channel]
For Timeline Type:
Phase: [Pre-launch | Launch Day | Week 1 | Month 1]
Date: [Specific date or relative timing]
Activities: [What happens in this phase]
Dependencies: [What must be ready]
Milestones: [Key checkpoints]
For Task Type:
Task: [What needs to be done]
Owner: [Who is responsible]
Due: [When it's due]
Dependency: [What it depends on]
Deliverable: [What's produced]
For Asset Type:
Asset: [What this is — landing page, email, video]
Purpose: [What it accomplishes]
Channel: [GTM-YYY where it's used]
Copy: [GTM-YYY messaging used]
Status: [Draft | Review | Approved | Live]
Linked IDs: [PER-XXX, CFD-XXX, KPI-XXX related]Example GTM- entries:
GTM-001: Primary Value Proposition
Type: Messaging
Owner: Product Marketing
Status: Ready
Audience: PER-001 (Startup Founder)
Format: Value Prop
Message: "Ship faster with AI that understands your codebase.
Context-aware coding assistance that reduces debugging
time by 40%."
Supporting Evidence: CFD-010 (time savings validated in interviews)
Where Used: GTM-005 (Landing Page), GTM-010 (Product Hunt)
Linked IDs: PER-001, CFD-010, KPI-001GTM-002: Product Hunt Launch
Type: Channel
Owner: Growth Team
Status: Planned
Channel: Product Hunt
Audience Fit: PER-001 (Startup Founder) frequents PH for tools
Strategy:
- Launch on Tuesday 12:01 AM PT
- Engage with comments first 24 hours
- Share maker story
- Prepare demo video
Content Plan:
- Tagline: GTM-001 (Primary Value Prop)
- Maker comment: GTM-003 (Founder Story)
- Demo video: GTM-006 (Product Demo)
Success Metric: Top 5 product of the day, 500+ upvotes
Linked IDs: PER-001, GTM-001, GTM-003, GTM-006, KPI-005GTM-003: Launch Week Timeline
Type: Timeline
Owner: Launch Coordinator
Status: Planned
Phase: Launch Week
Day -7 (Pre-launch):
- [ ] Email list teaser
- [ ] Social media hints
- [ ] Press outreach
Day -1:
- [ ] Final staging verification
- [ ] Launch assets approved
- [ ] Team roles confirmed
Day 0 (Launch):
- [ ] Product Hunt live at 12:01 AM PT
- [ ] Social media posts scheduled
- [ ] Email to waitlist
- [ ] Monitor and engage
Day 1-3:
- [ ] Respond to all feedback
- [ ] Fix any critical issues
- [ ] Share early wins
Day 4-7:
- [ ] Publish case study
- [ ] Analyze metrics
- [ ] Plan iteration
Dependencies: DEP- release criteria met, MON- monitoring active
Milestones: 1000 signups (Day 3), First paying customer (Day 7)
Linked IDs: DEP-002, MON-005, KPI-001GTM-004: Landing Page Hero Section
Type: Asset
Owner: Design + Marketing
Status: In Progress
Asset: Landing page hero section
Purpose: Convert visitors to signups
Channel: GTM-007 (Website), GTM-002 (Product Hunt referrals)
Copy: GTM-001 (Primary Value Prop)
Status: Review
Components:
- Headline: "Ship faster with AI that understands your codebase"
- Subhead: "Context-aware coding assistance that reduces
debugging time by 40%"
- CTA: "Start Free Trial" → /signup
- Social proof: "Trusted by 500+ developers"
- Demo video thumbnail: GTM-006
Linked IDs: GTM-001, GTM-006, SCR-001GTM-XXX: [GTM Item Title]
Type: [Messaging | Channel | Timeline | Task | Asset]
Owner: [Person or team responsible]
Status: [Planned | In Progress | Ready | Live]
For Messaging Type:
Audience: [PER-XXX targeted]
Format: [Headline | Value Prop | Tagline | Elevator Pitch]
Message: [The actual copy]
Supporting Evidence: [CFD-XXX value hypothesis it's based on]
Where Used: [GTM-YYY channels, assets]
For Channel Type:
Channel: [Specific platform or medium]
Audience Fit: [Why this channel reaches PER-XXX]
Strategy: [How we'll use this channel]
Content Plan: [What content goes here]
Success Metric: [How we measure effectiveness]
Linked Assets: [GTM-YYY assets for this channel]
For Timeline Type:
Phase: [Pre-launch | Launch Day | Week 1 | Month 1]
Date: [Specific date or relative timing]
Activities: [What happens in this phase]
Dependencies: [What must be ready]
Milestones: [Key checkpoints]
For Task Type:
Task: [What needs to be done]
Owner: [Who is responsible]
Due: [When it's due]
Dependency: [What it depends on]
Deliverable: [What's produced]
For Asset Type:
Asset: [What this is — landing page, email, video]
Purpose: [What it accomplishes]
Channel: [GTM-YYY where it's used]
Copy: [GTM-YYY messaging used]
Status: [Draft | Review | Approved | Live]
Linked IDs: [PER-XXX, CFD-XXX, KPI-XXX related]GTM-条目示例:
GTM-001: Primary Value Proposition
Type: Messaging
Owner: Product Marketing
Status: Ready
Audience: PER-001 (Startup Founder)
Format: Value Prop
Message: "Ship faster with AI that understands your codebase.
Context-aware coding assistance that reduces debugging
time by 40%."
Supporting Evidence: CFD-010 (time savings validated in interviews)
Where Used: GTM-005 (Landing Page), GTM-010 (Product Hunt)
Linked IDs: PER-001, CFD-010, KPI-001GTM-002: Product Hunt Launch
Type: Channel
Owner: Growth Team
Status: Planned
Channel: Product Hunt
Audience Fit: PER-001 (Startup Founder) frequents PH for tools
Strategy:
- Launch on Tuesday 12:01 AM PT
- Engage with comments first 24 hours
- Share maker story
- Prepare demo video
Content Plan:
- Tagline: GTM-001 (Primary Value Prop)
- Maker comment: GTM-003 (Founder Story)
- Demo video: GTM-006 (Product Demo)
Success Metric: Top 5 product of the day, 500+ upvotes
Linked IDs: PER-001, GTM-001, GTM-003, GTM-006, KPI-005GTM-003: Launch Week Timeline
Type: Timeline
Owner: Launch Coordinator
Status: Planned
Phase: Launch Week
Day -7 (Pre-launch):
- [ ] Email list teaser
- [ ] Social media hints
- [ ] Press outreach
Day -1:
- [ ] Final staging verification
- [ ] Launch assets approved
- [ ] Team roles confirmed
Day 0 (Launch):
- [ ] Product Hunt live at 12:01 AM PT
- [ ] Social media posts scheduled
- [ ] Email to waitlist
- [ ] Monitor and engage
Day 1-3:
- [ ] Respond to all feedback
- [ ] Fix any critical issues
- [ ] Share early wins
Day 4-7:
- [ ] Publish case study
- [ ] Analyze metrics
- [ ] Plan iteration
Dependencies: DEP- release criteria met, MON- monitoring active
Milestones: 1000 signups (Day 3), First paying customer (Day 7)
Linked IDs: DEP-002, MON-005, KPI-001GTM-004: Landing Page Hero Section
Type: Asset
Owner: Design + Marketing
Status: In Progress
Asset: Landing page hero section
Purpose: Convert visitors to signups
Channel: GTM-007 (Website), GTM-002 (Product Hunt referrals)
Copy: GTM-001 (Primary Value Prop)
Status: Review
Components:
- Headline: "Ship faster with AI that understands your codebase"
- Subhead: "Context-aware coding assistance that reduces
debugging time by 40%"
- CTA: "Start Free Trial" → /signup
- Social proof: "Trusted by 500+ developers"
- Demo video thumbnail: GTM-006
Linked IDs: GTM-001, GTM-006, SCR-001Channel Selection Framework
渠道选择框架
Match channels to product type (from v0.2 BR-):
| Product Type | Primary Channels | Strategy |
|---|---|---|
| Fast Follow | SEO, Paid, Aggregators | "We're the better [competitor]" |
| Slice | Community, Integrations, Partnerships | "Best [thing] for [ecosystem]" |
| Innovation | Content, PR, Events | "Here's why this matters" |
根据v0.2中的BR-产品类型匹配渠道:
| 产品类型 | 核心渠道 | 策略 |
|---|---|---|
| 快速跟进型 | SEO、付费广告、聚合平台 | "我们是比[竞品]更好的选择" |
| 细分场景型 | 社区、集成、合作伙伴 | "[生态系统]中最佳的[产品]" |
| 创新型 | 内容营销、公关、活动 | "这一产品的价值所在" |
Channel Categories
渠道分类
| Category | Examples | Best For |
|---|---|---|
| Owned | Website, Blog, Email, Product | Control message, build audience |
| Earned | PR, Reviews, Word-of-mouth | Credibility, reach |
| Paid | Ads, Sponsorships, Influencers | Scale, targeting |
| Community | Forums, Discord, Twitter | Engagement, feedback |
| 类别 | 示例 | 适用场景 |
|---|---|---|
| 自有媒体 | 官网、博客、邮件、产品内渠道 | 掌控信息传递,打造自有受众 |
| ** earned媒体** | 公关报道、评测、口碑传播 | 提升可信度,扩大覆盖 |
| 付费媒体 | 广告、赞助、网红合作 | 快速规模化,精准触达 |
| 社区渠道 | 论坛、Discord、Twitter | 用户互动,收集反馈 |
Messaging Hierarchy
信息传递层级
| Level | Purpose | Example |
|---|---|---|
| Mission | Why we exist | "Make developers 10x more productive" |
| Value Prop | What we offer | "AI that understands your codebase" |
| Differentiator | Why us vs others | "Context-aware, not just autocomplete" |
| Proof Point | Why believe us | "40% reduction in debugging time" |
| CTA | What to do next | "Start your free trial" |
| 层级 | 目的 | 示例 |
|---|---|---|
| 使命 | 我们存在的意义 | "让开发者效率提升10倍" |
| 价值主张 | 我们提供的价值 | "能理解你代码库的AI" |
| 差异化优势 | 为何选择我们 | "基于上下文,而非仅自动补全" |
| 佐证点 | 为何值得信赖 | "调试时间减少40%" |
| 行动号召(CTA) | 用户下一步操作 | "开始免费试用" |
Launch Phases
发布阶段
| Phase | Duration | Focus | Success Metric |
|---|---|---|---|
| Teaser | 2 weeks pre | Build anticipation | Waitlist signups |
| Launch | Day 0-3 | Maximum impact | Traffic, signups |
| Momentum | Week 1-4 | Sustain interest | Activation, feedback |
| Steady State | Month 2+ | Optimize funnel | Conversion, retention |
| 阶段 | 时长 | 核心重点 | 成功指标 |
|---|---|---|---|
| 预热期 | 发布前2周 | 打造用户期待 | 等待列表注册量 |
| 发布期 | 第0-3天 | 实现最大曝光 | 流量、注册量 |
| 热度维持期 | 第1-4周 | 持续吸引关注 | 用户激活、反馈量 |
| 稳定运营期 | 第2个月及以后 | 优化转化漏斗 | 转化率、留存率 |
Anti-Patterns
反模式
| Pattern | Signal | Fix |
|---|---|---|
| Launch and leave | Big launch day, then silence | Plan 30 days of post-launch activity |
| Everything everywhere | All channels, no focus | Pick 2-3 channels, do them well |
| Features not benefits | "We have X, Y, Z" | "You can achieve X, Y, Z" |
| No measurement | "The launch went well (I think)" | Define KPI- before launch |
| Ignoring personas | Generic messaging for everyone | Tailor by PER- |
| Over-promising | "Revolutionary AI" without proof | Ground in CFD- evidence |
| 模式 | 信号 | 解决方案 |
|---|---|---|
| 发布即结束 | 发布日声势浩大,随后悄无声息 | 规划30天的发布后活动 |
| 全面撒网 | 覆盖所有渠道,无重点 | 选择2-3个核心渠道,深耕运营 |
| 只讲功能不讲价值 | "我们有X、Y、Z功能" | "你可以通过我们实现X、Y、Z目标" |
| 无数据衡量 | "我觉得发布很成功" | 发布前定义KPI-指标 |
| 忽略用户画像 | 面向所有人的通用信息 | 根据PER-画像定制内容 |
| 过度承诺 | "革命性AI"却无实证 | 基于CFD-的证据传递信息 |
Quality Gates
质量门槛
Before proceeding to Launch Metrics:
- Core messaging defined (GTM- Messaging type)
- Primary channels selected (GTM- Channel type)
- Launch timeline created (GTM- Timeline type)
- All tasks assigned owners (GTM- Task type)
- Key assets identified (GTM- Asset type)
- Messaging traces to CFD- evidence
- Channel selection matches PER- personas
进入发布指标阶段前需满足:
- 已定义核心信息(GTM- 信息传递类型条目)
- 已选定核心渠道(GTM- 渠道类型条目)
- 已创建发布时间线(GTM- 时间线类型条目)
- 所有任务已分配负责人(GTM- 任务类型条目)
- 已确定关键资产(GTM- 资产类型条目)
- 信息传递可追溯至CFD-证据
- 渠道选择与PER-用户画像匹配
Downstream Connections
下游关联
| Consumer | What It Uses | Example |
|---|---|---|
| Launch Metrics | GTM- channels inform tracking | GTM-002 (PH) → KPI-005 (PH upvotes) |
| Feedback Loop Setup | GTM- channels become feedback sources | GTM-002 comments → CFD-100 |
| Content Creation | GTM- messaging guides content | GTM-001 → blog post theme |
| Sales | GTM- messaging for outreach | GTM-001 → sales email template |
| 关联环节 | 使用内容 | 示例 |
|---|---|---|
| 发布指标 | GTM-渠道用于制定追踪方案 | GTM-002(Product Hunt)→ KPI-005(PH点赞数) |
| 反馈循环搭建 | GTM-渠道作为反馈来源 | GTM-002的评论 → CFD-100 |
| 内容创作 | GTM-信息指导内容方向 | GTM-001 → 博客主题 |
| 销售 | GTM-信息用于客户触达 | GTM-001 → 销售邮件模板 |
Detailed References
详细参考
- Messaging framework examples: See
references/messaging-examples.md - GTM- entry template: See
assets/gtm-template.md - Channel evaluation guide: See
references/channel-guide.md - Launch timeline template: See
references/timeline-template.md
- 信息传递框架示例:参见
references/messaging-examples.md - GTM-条目模板:参见
assets/gtm-template.md - 渠道评估指南:参见
references/channel-guide.md - 发布时间线模板:参见
references/timeline-template.md