关于 crm-sales-momentum
crm-sales-momentum 是分析 HubSpot CRM 销售管线动能的技能,适用于销售团队。它衡量成交速度、阶段转化与停留时间,并按细分维度分析输赢模式和识别停滞交易。
主要功能
- 01计算整体及阶段成交速度
- 02比较各销售阶段的转化率
- 03识别超时停滞的交易
- 04按金额、来源、负责人等分析输赢
- 05总结管线动能并记录可行动发现
适用场景
- 01找出销售流程中流失率较高的阶段
- 02筛选需要跟进的停滞交易
- 03比较不同客群或来源的成交表现
MCP 相关
通过 Cogny 的 MCP 服务读取 HubSpot CRM 联系人、公司和交易数据,并可将可执行洞察记录为 finding。
安装
复制下面的命令,在终端中运行。
npx skills add https:/ / github.com/ cognyai/ claude-code-marketing-skills --skill crm-sales-momentum安装后在 Claude Code 中输入/crm-sales-momentum确认已加载。
详细介绍
CRM 销售势头驱动因素
分析 HubSpot CRM 中推动或拖慢销售管道势头的因素。衡量成交速度、阶段转化率、阶段停留时间,以及各细分群体的赢单/输单模式。揭示能够预测赢单或输单的交易特征,并识别停滞的交易。
需要: Cogny Agent 订阅(每月 $9)— 注册
提示: 先运行 /crm-icp-analysis 建立 ICP 基准,然后使用此技能查看符合 ICP 的交易与不符合 ICP 的交易在销售管道中的推进情况有何差异。
用法
/crm-sales-momentum — 全面分析销售势头
/crm-sales-momentum velocity — 仅分析成交速度和阶段用时
/crm-sales-momentum stalls — 仅检测停滞的交易
/crm-sales-momentum segments — 仅分析各细分群体的赢单/输单模式
前提条件检查
调用 mcp__cogny__hubspot__get_user_details 以验证 CRM 访问权限。确认具有 contacts、companies 和 deals 的读取权限。如果缺少访问权限:
This skill requires HubSpot CRM access via Cogny's MCP server.
Sign up at https://cogny.com/agent and connect your HubSpot account.
步骤
1. 了解销售管道结构
获取交易阶段属性,以了解销售管道:
hubspot__get_properties(objectType: "deals", propertyNames: ["dealstage", "pipeline"])
识别:
- 所有销售管道阶段及其顺序(来自
dealstage属性的枚举值) - 销售管道名称(如果有多个销售管道)
- 与细分相关的自定义交易属性
使用 search_properties 查找阶段计时属性:
hubspot__search_properties(objectType: "deals", keywords: ["hs_date_entered", "hs_time_in"])
同时获取所有者列表,以便按销售代表进行分析:
hubspot__search_owners()
2. 获取所有阶段的交易数据
获取过去 90 天创建的交易以及近期已关闭的交易:
hubspot__search_crm_objects(
objectType: "deals",
filterGroups: [{"filters": [{"propertyName": "createdate", "operator": "GTE", "value": "<90 days ago timestamp>"}]}],
properties: ["dealname", "dealstage", "amount", "createdate", "closedate", "pipeline", "hubspot_owner_id", "hs_analytics_source", "dealtype", <stage timing properties from step 1>],
sorts: [{"propertyName": "createdate", "direction": "DESCENDING"}],
limit: 200
)
检查 total 计数,并在需要时分页,以获取完整数据集。
3. 交易速度分析
计算整个销售管道的速度指标:
- 整体速度:从交易创建到关闭的平均天数(分别计算赢单和输单)
- 逐阶段速度:每个阶段的平均停留时间
- 阶段转化率:从每个阶段推进到下一阶段的交易百分比
- 流失阶段:流失率最高的阶段
- 速度趋势:比较最近 30 天与此前 30 天
构建销售管道流程可视化:
Pipeline Flow (last 90 days):
[Stage 1] ──85%──> [Stage 2] ──62%──> [Stage 3] ──48%──> [Stage 4] ──71%──> [Closed Won]
100 deals 85 deals 53 deals 25 deals 18 deals
avg 4 days avg 7 days avg 12 days avg 5 days
↓ 15% ↓ 38% ↓ 52% ↓ 29%
[Lost: 15] [Lost: 32] [Lost: 28] [Lost: 7]
标记:
- 超过 40% 的交易停滞或流失的阶段
- 平均停留时间超过阶段整体平均值 2 倍的阶段
- 与上一时期相比,转化率下降超过 10% 的阶段
4. 检测停滞的交易
根据阶段停留时间分析识别停滞的交易。
对每个销售管道阶段,计算:
- 最终成功推进的交易在该阶段的停留时间中位数
- 阶段停留时间的标准差
- 停滞阈值:中位数 + 1.5 倍标准差
标记当前停留时间超过停滞阈值的交易:
hubspot__search_crm_objects(
objectType: "deals",
filterGroups: [{"filters": [
{"propertyName": "dealstage", "operator": "EQ", "value": "<stage>"},
{"propertyName": "hs_date_entered_<stage>", "operator": "LT", "value": "<stall threshold date>"}
]}],
properties: ["dealname", "amount", "hubspot_owner_id", "hs_date_entered_<stage>"],
limit: 50
)
对于每笔停滞的交易,获取关联公司和联系人,以补充其可能停滞的原因背景。
5. 按细分群体分析赢单/输单模式
从多个维度对已关闭的交易进行细分,并比较赢单率:
按交易规模:
- 将交易按规模划分为多个层级,并比较各层级的赢单率
- 找出赢单率最高的交易规模范围
按潜在客户来源:
- 按
hs_analytics_source统计赢单率(自然流量、付费、推荐、直接访问等) - 按来源统计平均交易规模
- 按来源统计平均销售周期
按所有者(销售代表):
- 统计每位销售代表的赢单率
- 统计每位销售代表的平均成交速度
- 统计每位销售代表的平均交易规模
- 找出表现最佳者及其不同之处
按公司细分群体(获取关联公司):
- 按行业统计赢单率
- 按公司规模统计赢单率
- 按地理位置统计赢单率
按阶段停留时间:
- 统计每个阶段停留时间少于 X 天的交易的赢单率
- 统计停留时间超过 X 天的交易的赢单率
- 找出与赢单相关的阶段停留时间范围,即“黄金窗口”
6. 势头评分
评估销售管道整体势头:
Pipeline Momentum Score: X/100
Velocity: X/25
[FAST/NORMAL/SLOW] Average cycle [N] days
[UP/DOWN/FLAT] Velocity trend: [X]% change vs prior period
Flow Rate: X/25
[STRONG/MODERATE/WEAK] Stage conversion rates
[IMPROVING/DECLINING/STABLE] Conversion trend
Drop-off stage: [stage name] ([X]% loss rate)
Pipeline Health: X/25
[HEALTHY/AT_RISK/CRITICAL] [N] deals stuck ([X]% of active pipeline)
[GROWING/SHRINKING/STABLE] Pipeline value: $[X] ([X]% change)
Coverage ratio: [X]x ([pipeline value] / [target])
Predictability: X/25
[HIGH/MEDIUM/LOW] Win rate consistency: [X]% +/- [Y]%
[CLEAR/MIXED/UNCLEAR] Segment patterns identified
[STRONG/WEAK] Leading indicators reliability
7. 输出势头报告
CRM Sales Momentum Analysis
Period: Last 90 days
Deals analyzed: [N] ([N] won, [N] lost, [N] active)
Pipeline value: $[X]
═══════════════════════════════════════════════════
MOMENTUM SCORE: X/100
═══════════════════════════════════════════════════
Pipeline Flow:
[Stage-by-stage flow diagram from Step 3]
Key Velocity Metrics:
Average Sales Cycle (Won): [N] days
Average Sales Cycle (Lost): [N] days
Fastest Close: [N] days ([deal name])
Slowest Win: [N] days ([deal name])
Stage Health:
┌──────────────────┬──────────┬───────────┬──────────┬─────────────┐
│ Stage │ Deals In │ Avg Days │ Conv Rate│ Stuck Deals │
├──────────────────┼──────────┼───────────┼──────────┼─────────────┤
│ [Stage 1] │ [N] │ [N] │ [X]% │ [N] │
│ [Stage 2] │ [N] │ [N] │ [X]% │ [N] │
│ [Stage 3] │ [N] │ [N] │ [X]% │ [N] │
│ [Stage 4] │ [N] │ [N] │ [X]% │ [N] │
└──────────────────┴──────────┴───────────┴──────────┴─────────────┘
Win Predictors (what separates wins from losses):
1. [Predictor]: deals with [X] win at [Y]% vs [Z]% without
2. [Predictor]: deals with [X] win at [Y]% vs [Z]% without
3. [Predictor]: deals with [X] win at [Y]% vs [Z]% without
Stuck Deals Requiring Attention:
┌──────────────────┬──────────┬──────────┬──────────┬─────────────────┐
│ Deal │ Amount │ Stage │ Days In │ Owner │
├──────────────────┼──────────┼──────────┼──────────┼─────────────────┤
│ [Deal 1] │ $[X] │ [Stage] │ [N] │ [Rep] │
│ [Deal 2] │ $[X] │ [Stage] │ [N] │ [Rep] │
└──────────────────┴──────────┴──────────┴──────────┴─────────────────┘
Rep Performance:
┌──────────────────┬──────────┬───────────┬──────────┬─────────────┐
│ Rep │ Win Rate │ Avg Cycle │ Avg Deal │ Pipeline $ │
├──────────────────┼──────────┼───────────┼──────────┼─────────────┤
│ [Rep 1] │ [X]% │ [N] days │ $[X] │ $[X] │
│ [Rep 2] │ [X]% │ [N] days │ $[X] │ $[X] │
└──────────────────┴──────────┴───────────┴──────────┴─────────────┘
Top 3 Actions:
1. [Highest-impact momentum fix]
2. [Second highest]
3. [Third highest]
8. 记录发现
对于每项可执行的销售动能洞察,都要调用 mcp__cogny__create_finding:
{
"title": "38% of deals stall at Proposal stage — avg 18 days vs 7-day benchmark",
"body": "32 of 85 deals entering the Proposal stage in the last 90 days have stalled or been lost. Median time-in-stage for deals that advance is 7 days, but stalled deals average 18 days. Common pattern: deals without a second contact (single-threaded) stall at 2.1x the rate. 12 deals currently stuck in Proposal worth $340K total. Recommend: implement multi-threading requirement before Proposal stage, add 10-day stall alert.",
"action_type": "pipeline_optimization",
"expected_outcome": "Reduce Proposal stage stall rate from 38% to <20%",
"estimated_impact_usd": 8000,
"priority": "high"
}
销售动能的行动类型:
pipeline_optimization— 阶段流程调整、停滞干预deal_acceleration— 推进单笔交易的具体行动rep_coaching— 针对销售代表的绩效改进forecasting_improvement— 管道覆盖率、预测能力修正lead_source_optimization— 加大对能更快促成交易的线索来源的投入disqualification_rule— 预测失败的模式,及早筛选