Back to Details

product-led-sales

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Product-Led Sales

产品导向型销售（PLS）

Scope

适用范围

Covers
  • Designing a product-led sales (PLS) motion: converting self-serve usage into a sales opportunity that can close larger contracts
  • Defining product-qualified entities (PQL/PQA), signals, thresholds, scoring, and routing rules
  • Designing the sales handoff workflow (alerts, SLAs, dispositions) and a Product↔Sales feedback loop
  • Creating a usage-triggered outreach kit (helpful, compliant, not “creepy”)
  • Planning instrumentation, reporting, and a pilot-to-scale rollout
When to use
  • “We’re PLG/self-serve, but we want to add sales without breaking the low-touch funnel.”
  • “Define PQLs/PQAs and the product signals that should trigger outreach.”
  • “Create a product-led sales playbook for sales to act on usage signals.”
  • “Sales says MQLs are low quality—build a product-qualified pipeline instead.”
  • “Design a PLS pilot (routing + SLAs + measurement) before scaling.”
When NOT to use
  • You don’t have meaningful activation or self-serve usage yet (fix onboarding/activation first)
  • You want a purely enterprise, relationship-led motion with minimal product usage signals (use 
    enterprise-sales
    )
  • You need ICP/positioning or pricing/packaging from scratch (do that first, then return)
  • You want spammy outreach, deception, or dark patterns (not supported)
  • You need legal/privacy/security advice or production data/CRM implementation (coordinate with qualified experts)
涵盖内容
  • 设计**产品导向型销售（PLS）**动作：将自助式使用转化为可促成更大合同的销售机会
  • 定义产品合格实体（PQL/PQA）、信号、阈值、评分及路由规则
  • 设计销售交接工作流（告警、SLA、处理结果）以及产品↔销售反馈闭环
  • 创建基于使用行为触发的触达工具包（实用、合规，而非“令人反感”）
  • 规划埋点、报告以及从试点到规模化的推广方案
适用场景
  • “我们采用PLG/自助式模式，但希望在不破坏低接触漏斗的前提下增加销售介入。”
  • “定义PQL/PQA以及应触发销售触达的产品信号。”
  • “为销售团队创建一套基于使用信号的产品导向型销售手册。”
  • “销售团队表示MQL质量低下——转而构建产品合格的销售线索管道。”
  • “在规模化之前设计PLS试点方案（路由+SLA+衡量指标）。”
不适用场景
  • 尚未获得有意义的用户激活或自助式使用数据（先优化用户引导/激活流程）
  • 想要纯企业级、关系导向的动作模式，且几乎不使用产品使用信号（请使用
    enterprise-sales
    ）
  • 需要从零开始定义理想客户画像（ICP）/定位或定价/包装（先完成这些工作，再回来使用本工具）
  • 想要垃圾式触达、欺骗性手段或暗黑模式（不支持此类需求）
  • 需要法律/隐私/安全建议或生产数据/CRM实施支持（请与合格专家协作）

Inputs

输入信息

Minimum required
  • Product + model: freemium/trial, typical onboarding path, who uses vs who buys
  • ICP/segments: target roles + company types + ACV bands (and which segment is in scope for PLS)
  • Objective: conversion to paid, expansion, ACV lift, pipeline creation (pick 1 primary)
  • Current funnel baseline: activation rate, trial-to-paid, expansion rate (even rough)
  • Usage data reality: what events/attributes exist, and whether you can map users → accounts
  • Sales capacity + workflow: SDR/AE/CS roles, SLAs, and where activity is logged (CRM)
  • Constraints: regions/compliance, “don’t use these signals,” messaging tone/brand rules
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md.
  • If answers aren’t available, proceed with explicit assumptions and label unknowns in Assumptions & unknowns plus a short Validation plan.
最低要求
  • 产品+模式：免费增值/试用版、典型用户引导路径、使用者与决策者的区分
  • ICP/细分群体：目标角色+公司类型+客户平均生命周期价值（ACV）区间（以及哪些细分群体属于PLS的适用范围）
  • 目标：转化为付费用户、用户拓展、ACV提升、线索管道创建（选择1个核心目标）
  • 当前漏斗基准数据：激活率、试用转付费率、拓展率（即使是粗略数据也可）
  • 使用数据现状：已有的事件/属性，以及是否能将用户映射到对应企业账户
  • 销售能力+工作流：SDR/AE/CS角色、SLA，以及活动记录位置（CRM）
  • 约束条件：区域/合规要求、“禁止使用这些信号”、沟通语气/品牌规则
缺失信息处理策略
  • 从references/INTAKE.md中最多提出5个问题。
  • 如果无法获取答案，基于明确假设继续推进，并在假设与未知项部分标注未知内容，同时附上简短的验证计划。

Outputs (deliverables)

输出成果（交付物）

Produce a Product-Led Sales Motion Pack in Markdown (in-chat; or as files if requested):
  1. Context + goal snapshot (segment, objective, success metrics, constraints)
  2. PLS funnel + ownership map (stages, intervention points, RACI, SLAs)
  3. PQL/PQA definition + signal spec (signals table, thresholds/scoring, false-positive controls)
  4. Routing + workflow spec (alerts, assignment rules, CRM fields, dispositions, feedback loop)
  5. Usage-triggered outreach kit (email templates + call opener + follow-up rules)
  6. Instrumentation + reporting plan (tracking plan, dashboards, leading indicators)
  7. Pilot + scale plan (timeline, experiment design, rollout guardrails)
  8. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
生成一套Markdown格式的产品导向型销售动作包（可在对话中直接输出；若有需求也可作为文件交付）：
  1. 背景+目标快照（细分群体、目标、成功指标、约束条件）
  2. PLS漏斗+权责地图（阶段、介入点、RACI矩阵、SLA）
  3. PQL/PQA定义+信号规范（信号表格、阈值/评分、误判防控措施）
  4. 路由+工作流规范（告警、分配规则、CRM字段、处理结果、反馈闭环）
  5. 基于使用行为触发的触达工具包（邮件模板+开场白+跟进规则）
  6. 埋点+报告计划（追踪计划、仪表盘、领先指标）
  7. 试点+规模化计划（时间线、实验设计、推广管控规则）
  8. 风险/待解决问题/下一步行动（必须包含）
模板参考：references/TEMPLATES.md

Workflow (7 steps)

工作流（7个步骤）

1) Intake + readiness gate (PLS is a layer, not a substitute)

1) 信息收集+就绪检查（PLS是补充层，而非替代方案）

  • Inputs: User context; references/INTAKE.md.
  • Actions: Confirm the primary objective and target segment(s). Run a readiness gate: do you have activation/usage depth + identity/account mapping to create reliable signals? Capture constraints (sales capacity, SLA expectations, privacy/compliance).
  • Outputs: Context snapshot + readiness verdict (Ready / Needs prerequisites) + assumptions/unknowns.
  • Checks: Objective is measurable; segment is explicit; prerequisites and constraints are documented.
  • 输入：用户提供的背景信息；references/INTAKE.md
  • 动作：确认核心目标和目标细分群体。执行就绪检查：是否具备足够的用户激活/使用深度，以及身份/账户映射能力来创建可靠信号？记录约束条件（销售能力、SLA预期、隐私/合规要求）。
  • 输出：背景快照+就绪判定（就绪/需先完成前置工作）+假设与未知项。
  • 检查项：目标可衡量；细分群体明确；前置条件和约束条件已记录。

2) Map the PLS funnel and decide where sales intervenes

2) 绘制PLS漏斗并确定销售介入节点

  • Inputs: Current PLG funnel, user journey, pricing/packaging, sales coverage model.
  • Actions: Map stages from first value → sustained usage → qualification → sales assist → purchase/expansion → onboarding. Pick intervention points where a human can increase deal size or reduce time-to-value, and define guardrails to keep a low-touch path intact.
  • Outputs: PLS funnel + intervention points + guardrails + ownership map (RACI).
  • Checks: Low-touch conversion path remains viable; ownership is explicit at every stage.
  • 输入：当前PLG漏斗、用户旅程、定价/包装、销售覆盖模型。
  • 动作：绘制从首次获得到持续使用，再到资格认定、销售支持、购买/拓展、用户引导的全阶段漏斗。选择人工介入可提升交易规模或缩短价值交付时间的节点，并定义管控规则以保留低接触路径的完整性。
  • 输出：PLS漏斗+介入节点+管控规则+权责地图（RACI矩阵）。
  • 检查项：低接触转化路径仍可行；每个阶段的权责明确。

3) Choose the qualified unit (PQL vs PQA) and write the definition

3) 选择合格单元（PQL vs PQA）并撰写定义

  • Inputs: Buyer/user model, account structure, pricing driver (seats/usage).
  • Actions: Decide the qualified unit:
    • PQL for user-led buying (a user’s intent/need)
    • PQA for account-led expansion (account adoption/coordination) Write a crisp definition: required signals + thresholds + exclusions.
  • Outputs: PQL/PQA definition (inclusion/exclusion + examples).
  • Checks: Definition is computable from data, not vibes; includes anti-gaming/false-positive controls.
  • 输入：购买者/使用者模型、账户结构、定价驱动因素（席位/使用量）。
  • 动作：确定合格单元：
    • PQL适用于用户主导的购买场景（用户的意向/需求）
    • PQA适用于账户主导的拓展场景（账户的采用/协作情况） 撰写清晰的定义：所需信号+阈值+排除项。
  • 输出：PQL/PQA定义（包含纳入/排除规则+示例）。
  • 检查项：定义可通过数据计算得出，而非主观判断；包含反作弊/误判防控措施。

4) Build the signal spec, scoring, and routing/SLA rules

4) 构建信号规范、评分模型及路由/SLA规则

  • Inputs: Available events/properties, identity graph, sales capacity, CRM workflow.
  • Actions: Create a signal catalog (activation/aha, depth, breadth, integrations, invites, admin actions, billing intent). Set thresholds and scoring, define routing (who gets alerted, when), and specify a triage/holdout path for ambiguous signals.
  • Outputs: Signal spec table + scoring model + routing + SLA + disposition taxonomy.
  • Checks: Signals map to intent and value potential; routing matches capacity; false positives are addressed.
  • 输入：可用事件/属性、身份图谱、销售能力、CRM工作流。
  • 动作：创建信号目录（激活/aha时刻、使用深度、使用广度、集成、邀请、管理员操作、付费意向）。设置阈值和评分，定义路由规则（谁会收到告警、何时收到），并为模糊信号定义分类/暂存路径。
  • 输出：信号规范表格+评分模型+路由规则+SLA+处理结果分类体系。
  • 检查项：信号与用户意向及价值潜力匹配；路由规则与销售能力匹配；已处理误判问题。

5) Design the sales workflow and Product↔Sales feedback loop

5) 设计销售工作流及产品↔销售反馈闭环

  • Inputs: Sales roles, CRM fields, enablement constraints.
  • Actions: Define the operational workflow: alert delivery, assignment rules, what context reps see, required actions, logging, dispositions, and a weekly tuning loop with Product/RevOps to improve signals and messaging.
  • Outputs: Workflow spec + RACI + weekly review agenda.
  • Checks: Every alert has a next best action; outcomes are measurable and feed back into tuning.
  • 输入：销售角色、CRM字段、赋能约束条件。
  • 动作：定义运营工作流：告警交付、分配规则、销售代表可见的上下文信息、必填动作、记录要求、处理结果，以及每周与产品/营收运营团队的调优闭环，以优化信号和沟通内容。
  • 输出：工作流规范+RACI矩阵+每周复盘议程。
  • 检查项：每个告警都有明确的下一步最佳动作；结果可衡量并能反馈到调优环节。

6) Create the usage-triggered outreach kit (helpful, not creepy)

6) 创建基于使用行为触发的触达工具包（实用，而非令人反感）

  • Inputs: Use case narrative, common objections, signal context.
  • Actions: Write email templates that reference helpful context (“noticed you’re setting up X”) without surveillance language. Provide variants for early vs high intent. Add a call opener + discovery prompts anchored to the user’s likely goal.
  • Outputs: Outreach kit (emails + call opener + follow-up rules).
  • Checks: One clear ask per message; tone is respectful/compliant; personalization uses only approved signals.
  • 输入：用例场景、常见异议、信号上下文。
  • 动作：撰写邮件模板，参考实用的上下文信息（如“注意到您正在设置X功能”），避免使用监控式语言。为早期意向和高意向场景提供不同版本。添加开场白+基于用户可能目标的探索式问题。
  • 输出：触达工具包（邮件+开场白+跟进规则）。
  • 检查项：每条信息仅有一个明确诉求；语气尊重/合规；个性化内容仅使用经批准的信号。

7) Pilot, measure, iterate, and scale

7) 试点、衡量、迭代、规模化

  • Inputs: Draft pack; baseline metrics; pilot constraints.
  • Actions: Propose a pilot (segment + duration + sample size), define success metrics and leading indicators (time-to-first-touch, meeting rate, conversion, expansion, retention). Run references/CHECKLISTS.md and score with references/RUBRIC.md. Finalize with Risks / Open questions / Next steps and a rollout plan.
  • Outputs: Final Product-Led Sales Motion Pack + pilot/measurement plan.
  • Checks: Pilot is bounded; dashboards are specified; iteration cadence is scheduled and owned.
  • 输入：草稿动作包；基准指标；试点约束条件。
  • 动作：提出试点方案（细分群体+时长+样本量），定义成功指标和领先指标（首次触达时间、会议转化率、用户转化、拓展、留存）。执行references/CHECKLISTS.md并通过references/RUBRIC.md进行评分。最终补充风险/待解决问题/下一步行动及推广计划。
  • 输出：最终版产品导向型销售动作包+试点/衡量计划。
  • 检查项：试点范围明确；仪表盘已指定；迭代节奏已规划并明确负责人。

Quality gate (required)

质量检查门（必填）

  • Use references/CHECKLISTS.md and references/RUBRIC.md.
  • Always include: Risks, Open questions, Next steps.
  • 使用references/CHECKLISTS.md和references/RUBRIC.md进行检查。
  • 必须包含：风险、待解决问题、下一步行动。

Examples

示例

Example 1 (trial → sales assist):
“Use 
product-led-sales
. We’re a B2B analytics tool with a 14-day trial. We get lots of signups but low trial-to-paid. We have usage events and can map users to companies via email domain. Sales: 2 SDRs + 2 AEs. Output: a Product-Led Sales Motion Pack with a PQL definition, routing rules, outreach emails, and a 4-week pilot plan.”
Example 2 (expansion via PQA):
“Use 
product-led-sales
. We’re seat-based SaaS. Teams start self-serve at $20/seat but we want to land-and-expand into 100+ seat contracts. We can detect invites, admin setup, and integration activation. Output: a Motion Pack that defines PQAs, scoring, and a sales workflow + outreach kit for expansion.”
Boundary example:
“Write a generic cold outbound sequence for any product and send it to 50,000 people.”
Response: explain this skill is usage-signal-driven and must be targeted and compliant; request product + ICP + available signals and produce a small, testable sequence and pilot instead.
示例1（试用→销售支持）：
“使用
product-led-sales
。我们是一款B2B分析工具，提供14天试用版。我们有大量注册用户，但试用转付费率很低。我们有使用事件数据，且可通过邮箱域名将用户映射到企业账户。销售团队：2名SDR + 2名AE。输出：一套包含PQL定义、路由规则、触达邮件以及4周试点计划的产品导向型销售动作包。”
示例2（通过PQA进行用户拓展）：
“使用
product-led-sales
。我们是基于席位收费的SaaS产品。团队以20美元/席位的价格开始自助式使用，但我们希望通过‘落地并拓展’策略达成100+席位的合同。我们可检测邀请、管理员设置和集成激活行为。输出：一套定义PQA、评分模型、销售工作流及拓展触达工具包的动作包。”
边界示例：
“为任意产品编写通用的冷启动触达序列，并发送给50,000人。”
回复：说明本工具基于使用信号驱动，必须具备针对性且合规；请提供产品+ICP+可用信号，我们将生成一个小型、可测试的触达序列及试点方案。