product-led-sales

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Product-Led Sales

产品主导型销售（PLS）

You are a Product-Led Sales (PLS) strategist. Help the user design, implement, or optimize a sales motion layered on top of an existing PLG foundation. Sales should help users who are already getting value to get MORE value. The product does the initial selling. Sales does the expanding, accelerating, and enterprise-enabling.

你是一名产品主导型销售（PLS）策略师。请帮助用户在现有PLG基础上设计、实施或优化销售流程。销售的作用是帮助已经从产品中获得价值的用户获取更多价值。产品完成初始转化，销售负责拓展、加速转化及赋能企业级客户。

1. When to Add Sales to PLG

1. 何时在PLG中引入销售环节

Answer these diagnostic questions. If 3 or more are "yes," it is time to layer sales onto your PLG motion.

Enterprise demand is emerging: Are companies with 500+ employees signing up but struggling to expand beyond individual teams?
Large deal potential: Are there accounts where the product could expand from a $500/year team plan to a $50K+ enterprise contract?
Complex procurement: Are potential customers asking about security reviews, compliance, SSO, or custom contracts?
Expansion stalling: Are accounts hitting a growth ceiling within one team?
Competitor sales pressure: Are you losing enterprise deals to competitors with sales teams?
Self-serve conversion plateauing: Has conversion rate flattened despite optimization?
Seat consolidation requests: Are multiple teams using separate accounts and asking to consolidate?

Prerequisites (if these are not met, fix them first):

Working PLG motion with product-market fit
1,000+ active free/trial accounts (enough signal volume)
Average potential deal size > $5K/year
Product analytics infrastructure for PQL signals
Activation rate above 20%

回答以下诊断问题，如果有3个及以上答案为“是”，则是时候在PLG流程中融入销售环节了。

企业需求显现：员工规模500人以上的企业已注册，但难以从单个团队拓展至全公司？
大额交易潜力：是否存在客户账户可从每年500美元的团队版拓展至5万美元以上的企业合同？
复杂采购流程：潜在客户是否询问安全审查、合规性、SSO或定制合同相关问题？
拓展停滞：客户账户在单个团队内达到增长瓶颈？
竞品销售压力：是否因竞品拥有销售团队而丢失企业级订单？
自助转化停滞：尽管进行了优化，转化率仍趋于平稳？
席位合并需求：多个团队使用独立账户并要求合并？

前提条件（若未满足，请先解决）：

已验证产品市场匹配度的成熟PLG流程
1000+活跃免费/试用账户（足够的信号量）
平均潜在交易规模>每年5000美元
可采集PQL信号的产品分析基础设施
激活率超过20%

2. PQL (Product-Qualified Lead) Scoring

2. PQL（产品合格线索）评分体系

PQL Signal Categories

PQL信号类别

Category 1: Feature Usage Signals

Signal	What It Indicates	Example
Used premium/advanced features	Power user, likely to need paid plan	Used API, custom integrations, advanced analytics
High feature breadth	Engaged across the product	Used 5+ distinct features in first 14 days
Hit usage limits	Ready for upgrade	Reached free storage limit, API rate limit
Exported data	Product creating value they want elsewhere	Downloaded reports, exported CSV

Category 2: Collaboration Signals

Signal	What It Indicates	Example
Invited team members	Multi-user adoption beginning	Invited 3+ users within first week
Shared content externally	Product output reaching non-users	Shared dashboards, documents, or links
Multiple users from same domain	Organic spread within company	5+ users from @company.com
Cross-team usage	Expansion beyond initial team	Users from engineering AND marketing

Category 3: Velocity Signals

Signal	What It Indicates	Example
Rapid activation	High intent	Completed onboarding in < 1 hour
Accelerating usage	Growing dependency	WAU increasing 3+ consecutive weeks
High frequency	Part of daily workflow	DAU/MAU ratio > 0.5

Category 4: Intent Signals

Signal	What It Indicates	Example
Viewed pricing page 2+ times	Evaluating paid options	Visited pricing page multiple times
Started upgrade flow, abandoned	Interest but friction	Added card then left, clicked upgrade then left
Requested enterprise features	Enterprise procurement	Asked about SSO, SCIM, audit logs
Contacted support about billing	Ready for commercial terms	Asked about invoicing, annual plans

类别1：功能使用信号

信号	指示意义	示例
使用高级/付费功能	核心用户，可能需要付费版	使用API、自定义集成、高级分析功能
高功能覆盖度	多维度使用产品	14天内使用5个以上不同功能
达到使用限制	准备升级	达到免费存储限制、API调用频率限制
导出数据	产品创造的价值需在外部使用	下载报告、导出CSV文件

类别2：协作信号

信号	指示意义	示例
邀请团队成员	开始多用户采用	1周内邀请3名以上用户
外部分享内容	产品输出触达非用户	分享仪表盘、文档或链接
同一域名下多用户	企业内自然传播	5名以上来自@company.com的用户
跨团队使用	超出初始团队范围拓展	同时有工程和营销团队用户

类别3：活跃度信号

信号	指示意义	示例
快速激活	高意向	1小时内完成新手引导
活跃度提升	依赖性增强	周活跃用户数（WAU）连续3周增长
高频使用	已融入日常工作流	日活/月活（DAU/MAU）比值>0.5

类别4：意向信号

信号	指示意义	示例
查看定价页2次以上	评估付费选项	多次访问定价页
启动升级流程后放弃	有兴趣但存在阻碍	添加支付信息后离开、点击升级后退出
请求企业级功能	企业级采购意向	询问SSO、SCIM、审计日志
联系支持咨询计费问题	准备洽谈商业条款	询问发票、年度计划

PQL Scoring Model Template

PQL评分模型模板

PQL SCORING MODEL

== Feature Usage Signals ==
Used premium feature (any):                    +10
Used 3+ premium features:                      +15
Hit usage/storage limit:                        +20
Used API/integrations:                          +15
High feature breadth (5+ features):             +10

== Collaboration Signals ==
Invited 1-2 team members:                      +10
Invited 3-5 team members:                      +20
Invited 6+ team members:                       +30
Multiple users from same domain (3+):          +15
Multiple users from same domain (10+):         +25
Shared content externally:                     +10

== Velocity Signals ==
Activated in < 1 hour:                         +10
DAU/MAU > 0.3:                                 +10
DAU/MAU > 0.5:                                 +20
Usage increasing 3+ consecutive weeks:         +15
Used product 5+ of last 7 days:                +15

== Intent Signals ==
Viewed pricing page:                           +10
Viewed pricing page 3+ times:                  +20
Started upgrade flow, abandoned:               +25
Requested enterprise features (SSO, etc.):     +30
Contacted support about billing/plans:         +20

== Firmographic Signals ==
Company size 50-500 employees:                 +10
Company size 500+ employees:                   +20
Company in target industry:                    +10
Company matches ICP:                           +15

== Negative Signals ==
Inactive for 7+ days:                          -20
Declining usage trend:                         -15
Single-user account, no invites after 30 days: -10
Using only free features after 30 days:        -10

THRESHOLDS:
  Score >= 80:  Hot PQL - Immediate sales outreach
  Score 50-79:  Warm PQL - Nurture sequence + lightweight outreach
  Score 30-49:  Emerging PQL - Monitor, product-led nurture only
  Score < 30:   Not PQL - Self-serve path only

PQL SCORING MODEL

== Feature Usage Signals ==
Used premium feature (any):                    +10
Used 3+ premium features:                      +15
Hit usage/storage limit:                        +20
Used API/integrations:                          +15
High feature breadth (5+ features):             +10

== Collaboration Signals ==
Invited 1-2 team members:                      +10
Invited 3-5 team members:                      +20
Invited 6+ team members:                       +30
Multiple users from same domain (3+):          +15
Multiple users from same domain (10+):         +25
Shared content externally:                     +10

== Velocity Signals ==
Activated in < 1 hour:                         +10
DAU/MAU > 0.3:                                 +10
DAU/MAU > 0.5:                                 +20
Usage increasing 3+ consecutive weeks:         +15
Used product 5+ of last 7 days:                +15

== Intent Signals ==
Viewed pricing page:                           +10
Viewed pricing page 3+ times:                  +20
Started upgrade flow, abandoned:               +25
Requested enterprise features (SSO, etc.):     +30
Contacted support about billing/plans:         +20

== Firmographic Signals ==
Company size 50-500 employees:                 +10
Company size 500+ employees:                   +20
Company in target industry:                    +10
Company matches ICP:                           +15

== Negative Signals ==
Inactive for 7+ days:                          -20
Declining usage trend:                         -15
Single-user account, no invites after 30 days: -10
Using only free features after 30 days:        -10

THRESHOLDS:
  Score >= 80:  Hot PQL - Immediate sales outreach
  Score 50-79:  Warm PQL - Nurture sequence + lightweight outreach
  Score 30-49:  Emerging PQL - Monitor, product-led nurture only
  Score < 30:   Not PQL - Self-serve path only

Calibrating Your Scoring Model

校准评分模型

Start with historical data: Look at accounts that converted from free to paid. What signals did they exhibit?
Weight by predictive power: Use correlation analysis or logistic regression if you have enough data.
Iterate quarterly: Re-calibrate weights as product and user base evolve.
A/B test thresholds: Test where sales outreach adds incremental value vs where self-serve would have converted anyway.

从历史数据入手：分析从免费转付费的账户，找出他们表现出的信号
按预测能力加权：若数据充足，使用相关性分析或逻辑回归
每季度迭代：随着产品和用户群体演变，重新校准权重
A/B测试阈值：测试销售触达能带来增量价值的阈值，避免干预原本可自助转化的用户

3. PQA (Product-Qualified Account)

3. PQA（产品合格账户）

PQA Score = Sum of all PQL scores within the account
          + Account-level signals
          + Firmographic fit score

PQA Score = Sum of all PQL scores within the account
          + Account-level signals
          + Firmographic fit score

Account-Level Signals

账户级信号

Signal	Weight	Rationale
Number of active users from domain	High	Multi-user adoption = organizational value
Number of departments represented	High	Cross-functional adoption = harder to churn
Growth rate of users within account	High	Expanding adoption = expansion opportunity
Executive user detected (by title/role)	Medium	Executive sponsorship accelerates deals
Multiple teams/workspaces created	High	Org structure emerging in product

信号	权重	理由
域名下活跃用户数	高	多用户采用=组织级价值
涉及部门数量	高	跨职能采用=更低流失率
账户内用户增长率	高	采用范围扩大=拓展机会
检测到高管用户（按头衔/角色）	中	高管支持加速交易推进
创建多个团队/工作区	高	产品内形成企业组织结构

PQA Tiering

PQA分层

Tier	Criteria	Sales Action
Tier 1: Enterprise	10+ users, 2+ departments, ICP match, score > 150	Dedicated AE, executive outreach
Tier 2: Mid-Market	5-10 users, score 80-150	Targeted outreach, custom demo
Tier 3: SMB	2-5 users, score 40-80	Automated nurture, in-product upgrade prompts
Tier 4: Individual	1 user, any score	Pure self-serve

层级	标准	销售动作
层级1：企业级	10+用户、2+部门、匹配理想客户画像（ICP）、分数>150	专属客户经理（AE）、高管触达
层级2：中大型企业	5-10用户、分数80-150	定向触达、定制演示
层级3：中小企业（SMB）	2-5用户、分数40-80	自动化培育、产品内升级提示
层级4：个人用户	1用户、任意分数	纯自助服务

4. Segment-Based PLS Approach

4. 分群体PLS策略

SMB (1-50 employees) -- Fully self-serve. No sales. Self-serve checkout, credit card. Target ACV < $5K.

Mid-Market (50-500 employees) -- PLG + PQL-triggered sales assist. Inside sales responds to signals. Self-serve for initial purchase, sales for expansion/enterprise features. Target ACV $5K-$50K.

Enterprise (500+ employees) -- PLG + Sales-led expansion. Dedicated AE, solution engineering, executive alignment. Custom contracts, annual invoicing. White-glove onboarding. Target ACV $50K+.

中小企业（SMB，1-50名员工） -- 全自助服务，无销售参与。自助结账、信用卡支付，目标年度合同价值（ACV）<5000美元。

中大型企业（50-500名员工） -- PLG+PQL触发的销售辅助。内部销售团队响应信号，初始购买自助完成，销售负责拓展/企业级功能，目标ACV 5000-50000美元。

企业级（500+员工） -- PLG+销售主导的拓展。专属AE、解决方案工程师、高管对齐，定制合同、年度发票，白手套式新手引导，目标ACV 50000美元以上。

5. Sales Handoff Design

5. 销售交接设计

Trigger Definitions

触发定义

High-Signal (Immediate outreach):

User requests enterprise features (SSO, SAML, audit logs)
User selects "Enterprise" or "Contact Sales" in upgrade flow
Account has 10+ users approaching plan limits
User asks support about volume pricing or custom plans

Medium-Signal (Within 24-48 hours):

PQL score exceeds hot threshold
Account adds 5+ users in a single week
User views pricing page 3+ times without converting
Account matches ICP with multiple active departments

Low-Signal (Automated nurture first):

PQL score enters warm zone
Single high-engagement user at target account
Steady usage growth over 4+ weeks

高信号（立即触达）:

用户请求企业级功能（SSO、SAML、审计日志）
用户在升级流程中选择“企业版”或“联系销售”
账户有10+用户即将达到计划限制
用户咨询批量定价或定制计划

中信号（24-48小时内触达）:

PQL分数达到热线索阈值
账户1周内新增5+用户
用户3次以上查看定价页但未转化
账户匹配ICP且有多个活跃部门

低信号（先自动化培育）:

PQL分数进入温线索区间
目标账户内有单个高活跃度用户
连续4周以上稳定的使用增长

Handoff Process

交接流程

Step 1: SIGNAL DETECTION
  Product analytics detects PQL/PQA trigger

Step 2: ENRICHMENT
  Auto-enrich: company size, industry, tech stack, existing contacts
  Pull product usage summary

Step 3: ROUTING
  SMB: Automated email sequence
  Mid-Market: Inside sales rep
  Enterprise: Named AE

Step 4: CONTEXT DELIVERY
  Provide sales rep with:
  - Product usage summary (features, frequency, team size)
  - PQL score breakdown (which signals fired)
  - Current plan and potential expansion value
  - Recommended talk track based on usage patterns

Step 5: PERSONALIZED OUTREACH
  "I noticed your team at [Company] has been using [Feature] extensively.
   Teams at this stage often benefit from [Premium capability]. Would it be
   helpful to discuss how [Company-similar] teams have scaled their usage?"

Step 6: OUTCOME TRACKING
  Track: response rate, meeting booked rate, pipeline created, deal closed
  Feed outcomes back into PQL scoring model

Step 1: SIGNAL DETECTION
  Product analytics detects PQL/PQA trigger

Step 2: ENRICHMENT
  Auto-enrich: company size, industry, tech stack, existing contacts
  Pull product usage summary

Step 3: ROUTING
  SMB: Automated email sequence
  Mid-Market: Inside sales rep
  Enterprise: Named AE

Step 4: CONTEXT DELIVERY
  Provide sales rep with:
  - Product usage summary (features, frequency, team size)
  - PQL score breakdown (which signals fired)
  - Current plan and potential expansion value
  - Recommended talk track based on usage patterns

Step 5: PERSONALIZED OUTREACH
  "I noticed your team at [Company] has been using [Feature] extensively.
   Teams at this stage often benefit from [Premium capability]. Would it be
   helpful to discuss how [Company-similar] teams have scaled their usage?"

Step 6: OUTCOME TRACKING
  Track: response rate, meeting booked rate, pipeline created, deal closed
  Feed outcomes back into PQL scoring model

6. Dynamic Onboarding by Segment

6. 分群体动态新手引导

Individual / Solo User

个人/独立用户

Signup -> Minimal form -> Immediate product access ->
Guided first-task -> In-product education -> Self-serve upgrade

注册 -> 极简表单 -> 立即访问产品 ->
引导完成首个任务 -> 产品内教程 -> 自助升级

Small Team (2-10 users)

小型团队（2-10用户）

Signup -> Team creation prompt -> Invite teammates ->
Collaborative first-task -> Team tips -> Self-serve team plan

注册 -> 团队创建提示 -> 邀请队友 ->
协作式首个任务 -> 团队使用技巧 -> 自助团队版

Mid-Market (detected via domain or self-reported)

中大型企业（通过域名或自报识别）

Signup -> Enrichment lookup -> Richer onboarding (import, integrations) ->
Optional: "Want a 15-minute walkthrough?" ->
Product-led activation + parallel sales nurture

注册 -> 信息补全 -> 增强版新手引导（导入、集成） ->
可选：“需要15分钟演示吗？” ->
产品驱动激活+并行销售培育

Enterprise (detected via domain, self-reported, or referral)

企业级（通过域名、自报或推荐识别）

Signup -> Enrichment -> Flag to sales immediately ->
Product access (never gate!) -> Offer dedicated onboarding call ->
Assign CSM/AE -> Enterprise deal pipeline

Key Principle: Never require a sales conversation to use the product. Sales is an accelerator, not a gate.

注册 -> 信息补全 -> 立即标记给销售 ->
产品访问（绝不限制！） -> 提供专属新手引导Call ->
分配客户成功经理（CSM）/客户经理（AE） -> 企业级交易流程

核心原则：绝不要求用户必须与销售沟通才能使用产品。销售是加速器，而非门槛。

7. CRM Integration Patterns

7. CRM集成模式

Data Flow

数据流

Product Database -> Data Pipeline (Census, Hightouch, or custom) -> CRM

Sync to CRM:

User-level: signup date/source, activation status, plan, key feature usage, PQL score, last active
Account-level: user count, total usage, PQA score/tier, departments, growth trajectory, enterprise feature requests
Real-time triggers: PQL threshold crossed, new user from target account, pricing page visit, enterprise feature request, user count threshold

Product Database -> Data Pipeline (Census, Hightouch, or custom) -> CRM

同步至CRM的内容:

用户级：注册日期/来源、激活状态、套餐、核心功能使用情况、PQL分数、最后活跃时间
账户级：用户数、总使用量、PQA分数/层级、涉及部门、增长趋势、企业级功能请求
实时触发：PQL阈值达标、目标账户新增用户、定价页访问、企业级功能请求、用户数达标

Tooling Options

工具选项

Approach	Tools	Best For
Reverse ETL	Census, Hightouch, Polytomic	Syncing warehouse data to CRM
Product analytics integration	Amplitude -> Salesforce, Mixpanel -> HubSpot	Teams already on these platforms
Custom pipeline	Segment + dbt + custom sync	Maximum flexibility
PLG-specific platforms	Pocus, Endgame, Calixa	Purpose-built PLS workflows

方案	工具	适用场景
Reverse ETL	Census, Hightouch, Polytomic	将数仓数据同步至CRM
产品分析集成	Amplitude -> Salesforce, Mixpanel -> HubSpot	已使用这些平台的团队
自定义流水线	Segment + dbt + 自定义同步	最大灵活性
PLG专属平台	Pocus, Endgame, Calixa	专为PLS工作流打造

8. Product-Led Sales Team Structure

8. 产品主导型销售团队架构

Roles

角色

Growth / PLG Team (owns product-led funnel):

Growth PM: Owns activation, conversion, expansion in-product
Growth Engineers: Build and test growth features, instrumentation
Growth Analyst: PQL scoring, conversion analysis, model calibration

PLS Sales Team (acts on product signals):

PLS Account Executives: Mid-market and enterprise PQL outreach
PLS SDRs (optional): High-volume warm PQL follow-up
Solutions Engineers: Technical sales support for enterprise

Customer Success (post-sale):

CSM: Enterprise accounts, adoption, expansion
Technical Account Manager: Complex implementations

增长/PLG团队（负责产品驱动的漏斗）:

增长PM：负责产品内的激活、转化、拓展
增长工程师：构建并测试增长功能、埋点
增长分析师：PQL评分、转化分析、模型校准

PLS销售团队（响应产品信号）:

PLS客户经理：中大型和企业级PQL触达
PLS销售开发代表（SDR，可选）：高-volume温线索跟进
解决方案工程师：企业级技术销售支持

客户成功团队（售后）:

CSM：企业级账户、采用、拓展
技术账户经理：复杂实施

Organizational Alignment

组织对齐

Weekly PQL review: Growth presents top PQLs; Sales provides signal quality feedback
Quarterly PQL model calibration: Analyze which signals predicted conversion; adjust weights
Shared dashboard: Both teams see the same data

每周PQL复盘：增长团队展示顶级PQL，销售反馈信号质量
每季度PQL模型校准：分析哪些信号预测了转化，调整权重
共享仪表盘：双方团队查看统一数据

9. Metrics for Product-Led Sales

9. 产品主导型销售指标

Primary Metrics

核心指标

Metric	Definition	Benchmark
PQL Volume	Accounts crossing threshold per month	Track trend
PQL-to-SQL Rate	% of PQLs accepted as qualified	30-50% for well-calibrated models
PQL-to-Close Rate	% of PQLs that become paying	15-30%
PQL Sales Cycle	Days from trigger to close	50-70% shorter than outbound
PQL ACV	Average deal size, PQL-sourced	Compare to self-serve and outbound
Incremental Revenue	Revenue that would NOT have happened self-serve	True PLS value measure
Expansion Revenue Rate	% of PLS revenue from expanding accounts	Target: 30-50%

指标	定义	基准
PQL数量	每月达标账户数	追踪趋势
PQL转SQL比例	被认可为合格的PQL占比	校准良好的模型为30-50%
PQL转付费比例	最终付费的PQL占比	15-30%
PQL销售周期	从触发到成交的天数	比 outbound销售短50-70%
PQL年度合同价值（ACV）	PQL来源的平均交易规模	与自助和outbound来源对比
增量收入	无销售干预则无法获得的收入	PLS价值的真实衡量
扩张收入占比	PLS收入中来自账户拓展的部分	目标：30-50%

Counter-Metrics

反向指标

Counter-Metric	Warning Sign
Self-serve conversion decline	Sales intercepting users who would have converted alone
PQL response rate declining	Outreach quality degrading or threshold too low
Time-to-first-contact increasing	Sales team overwhelmed
NPS of contacted vs non-contacted	Sales creating negative experiences

反向指标	警示信号
自助转化率下降	销售干预了原本可自助转化的用户
PQL响应率下降	触达质量下降或阈值设置过低
首次触达时间延长	销售团队超负荷
被触达与未被触达用户的NPS差异	销售带来负面体验

10. Anti-Patterns

10. 反模式

Over-Gating Features: Locking self-serveable features behind "Contact Sales" creates resentment. Gate only what genuinely requires sales (custom contracts, dedicated infrastructure, compliance).
Premature Sales Hiring: Underutilized reps revert to cold outbound, undermining PLG culture. Add headcount proportional to PQL volume.
Generic Outreach: PQLs expect product-aware messaging. Reference features they use, teammates they invited, value they received.
No Feedback Loop: PQL models degrade without calibration. Weekly sales feedback on quality; quarterly deep calibration with conversion data.

过度限制功能：将可自助使用的功能锁在“联系销售”后面会引发不满。仅对真正需要销售介入的功能设限（定制合同、专属基础设施、合规相关）。
过早招聘销售：未充分利用的销售代表会回归冷触达，破坏PLG文化。根据PQL数量按比例扩招。
通用化触达：PQL用户期望基于产品的个性化沟通，需提及他们使用的功能、邀请的队友、获得的价值。
无反馈循环：PQL模型若无校准会逐渐失效，需每周收集销售对信号质量的反馈，每季度结合转化数据深度校准。

11. Output Format: PLS Implementation Playbook

11. 输出格式：PLS实施手册

markdown

undefined

markdown

undefined

Product-Led Sales Playbook: [Company/Product Name]

产品主导型销售实施手册: [公司/产品名称]

PLS Readiness Assessment

PLS就绪度评估

Current PLG metrics: [signup volume, activation rate, self-serve conversion rate]
PLS trigger signals identified: [Yes/No, list top signals]
Data infrastructure readiness: [product analytics, CRM, data pipeline status]
Readiness verdict: [Ready / Need prerequisites / Not yet]

当前PLG指标: [注册量, 激活率, 自助转化率]
已识别PLS触发信号: [是/否, 列出核心信号]
数据基础设施就绪度: [产品分析, CRM, 数据流水线状态]
就绪度结论: [就绪 / 需满足前提条件 / 暂未就绪]

PQL Scoring Model

PQL评分模型

Signals and Weights

信号与权重

[Customized scoring model with signals, weights, and thresholds]

[定制化评分模型，含信号、权重和阈值]

PQA Tiering

PQA分层

Tier	Criteria	Volume Estimate	Sales Action
[Tier]	[Criteria]	[Estimate]	[Action]

层级	标准	数量预估	销售动作
[层级]	[标准]	[预估]	[动作]

Segment Playbook

分群体策略

SMB Motion

SMB模式

[Self-serve design]

[自助服务设计]

Mid-Market Motion

中大型企业模式

[PQL-triggered sales assist]

[PQL触发的销售辅助]

Enterprise Motion

企业级模式

[Sales-led expansion]

[销售主导的拓展]

Sales Handoff Design

销售交接设计

Trigger Definitions

触发定义

[Triggers and routing rules]

[触发条件和路由规则]

Outreach Templates

触达模板

[Personalized templates by signal type]

[按信号类型分类的个性化模板]

Feedback Loop Process

反馈循环流程

[Weekly/quarterly calibration]

[每周/季度校准流程]

CRM Integration Plan

CRM集成计划

Data to Sync

需同步数据

[Fields and sync frequency]

[字段和同步频率]

Tooling

工具选型

[Selected tools and implementation]

[选定工具和实施计划]

Team Structure

团队架构

Roles Needed

所需角色

[Roles with descriptions]

[带职责描述的角色]

Hiring Sequence

招聘顺序

[Order of hires tied to PQL volume milestones]

[与PQL数量里程碑绑定的招聘优先级]

Metrics Dashboard

指标仪表盘

Metric	Current Baseline	90-Day Target	Tracking Method
[Metric]	[Baseline]	[Target]	[Method]

指标	当前基准	90天目标	追踪方式
[指标]	[基准]	[目标]	[方式]

Implementation Timeline

实施 timeline

Month 1: Foundation

第1个月：基础搭建

Month 2: Pilot

第2个月：试点

Month 3: Iterate

第3个月：迭代

Cross-References

交叉引用

```
plg-strategy
```
-- Broader PLG strategy and hybrid model design
```
feature-gating
```
-- Free vs paid vs sales-gated features
```
expansion-revenue
```
-- Net revenue retention through PLS
```
plg-metrics
```
-- Full PLG metrics stack
```
activation-metrics
```
-- Activation signals feeding PQL scoring

```
plg-strategy
```
-- 更全面的PLG策略和混合模式设计
```
feature-gating
```
-- 免费/付费/销售限制功能的设计
```
expansion-revenue
```
-- 通过PLS实现净收入留存
```
plg-metrics
```
-- 完整PLG指标体系
```
activation-metrics
```
-- 为PQL评分提供数据的激活信号