sales-ops-analyst

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sales Ops Analyst

销售运营分析师

Strategic sales operations expertise for revenue teams — from CRM architecture and pipeline analytics to territory design and commission automation.
为营收团队提供战略性销售运营专业支持——从CRM架构、销售漏斗分析到销售区域设计与佣金自动化。

Philosophy

核心理念

Great sales ops isn't about more data. It's about actionable insights that accelerate revenue.
The best sales operations teams:
  1. Enable, don't police — Make it easier for reps to do the right thing
  2. Measure what matters — Vanity metrics create vanity pipeline
  3. Automate the mundane — Free reps to sell, not update fields
  4. Build for scale — Today's workaround is tomorrow's technical debt
优秀的销售运营不在于拥有更多数据,而在于提供可落地的洞见以加速营收增长。
顶尖的销售运营团队具备以下特质:
  1. 赋能而非管控——让销售代表更易于做正确的事
  2. 聚焦关键指标——虚荣指标只会催生虚假的销售漏斗
  3. 自动化繁琐工作——解放销售代表的时间,让他们专注于销售而非更新字段
  4. 为规模化而构建——今日的临时解决方案会成为明日的技术债务

How This Skill Works

本Skill的工作方式

When invoked, apply the guidelines in
rules/
organized by:
  • crm-*
    — CRM architecture, data models, hygiene practices
  • pipeline-*
    — Pipeline analytics, stage definitions, velocity metrics
  • dashboard-*
    — Sales reporting, metrics, visualizations
  • process-*
    — Automation, workflows, approval chains
  • routing-*
    — Lead routing, assignment rules, territory design
  • commission-*
    — Comp plans, calculation logic, tracking
  • data-*
    — Data quality, deduplication, enrichment
  • forecast-*
    — Forecasting methodologies, models, accuracy
调用本Skill时,将应用
rules/
目录下按以下类别组织的指导原则:
  • crm-*
    — CRM架构、数据模型、数据卫生规范
  • pipeline-*
    — 销售漏斗分析、阶段定义、流转速度指标
  • dashboard-*
    — 销售报表、指标、可视化
  • process-*
    — 自动化、工作流、审批链
  • routing-*
    — 线索分配、规则设定、销售区域设计
  • commission-*
    — 薪酬方案、计算逻辑、追踪管理
  • data-*
    — 数据质量、去重、数据 enrichment
  • forecast-*
    — 预测方法论、模型、准确性

Core Frameworks

核心框架

The RevOps Data Hierarchy

RevOps数据层级

LevelWhat It MeasuresUsed ByUpdate Frequency
ActivityCalls, emails, meetingsReps, managersReal-time
OpportunityDeal progress, valueReps, managersDaily
PipelineForecast, velocityDirectors, execsWeekly
RevenueBookings, ARR, churnC-suite, boardMonthly/Quarterly
层级衡量内容使用人群更新频率
活动层通话、邮件、会议销售代表、经理实时
机会层交易进展、金额销售代表、经理每日
漏斗层预测、流转速度总监、高管每周
营收层签约额、ARR、客户流失高管层、董事会每月/每季度

Pipeline Velocity Formula

销售漏斗流转速度公式

Pipeline Velocity = (# Opportunities × Win Rate × Avg Deal Size) / Sales Cycle Length

Example:
(100 opps × 25% × $50K) / 90 days = $13,889/day potential revenue
Pipeline Velocity = (# Opportunities × Win Rate × Avg Deal Size) / Sales Cycle Length

Example:
(100 opps × 25% × $50K) / 90 days = $13,889/day potential revenue

The Sales Tech Stack

销售技术栈架构

┌─────────────────────────────────────────────────────────────┐
│                      ANALYTICS LAYER                         │
│   (BI Tools: Tableau, Looker, Power BI, Salesforce Reports) │
├─────────────────────────────────────────────────────────────┤
│                      CRM LAYER                               │
│           (Salesforce, HubSpot, Dynamics 365)               │
├──────────────────┬──────────────────┬───────────────────────┤
│   ENGAGEMENT     │   INTELLIGENCE    │     ENRICHMENT       │
│ Outreach, Salesloft│  Gong, Chorus   │   ZoomInfo, Clearbit │
├──────────────────┴──────────────────┴───────────────────────┤
│                      DATA LAYER                              │
│     (Integrations, ETL, Data Warehouse, CDP)                │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│                      分析层                                 │
│   (BI Tools: Tableau, Looker, Power BI, Salesforce Reports) │
├─────────────────────────────────────────────────────────────┤
│                      CRM层                                 │
│           (Salesforce, HubSpot, Dynamics 365)               │
├──────────────────┬──────────────────┬───────────────────────┤
│   客户互动工具     │   智能分析工具    │     数据 enrichment       │
│ Outreach, Salesloft│  Gong, Chorus   │   ZoomInfo, Clearbit │
├──────────────────┴──────────────────┴───────────────────────┤
│                      数据层                                 │
│     (Integrations, ETL, Data Warehouse, CDP)                │
└─────────────────────────────────────────────────────────────┘

Lead Scoring Matrix

线索评分矩阵

Signal TypeExamplesWeight
Fit (firmographic)Industry, company size, tech stack40%
Engagement (behavioral)Website visits, content downloads, email opens35%
Intent (buying signals)Pricing page views, demo requests, competitor research25%
信号类型示例权重
匹配度(企业属性)行业、公司规模、技术栈40%
参与度(行为数据)网站访问、内容下载、邮件打开35%
购买意向(购买信号)定价页浏览、演示请求、竞品调研25%

Territory Design Principles

销售区域设计原则

                    ┌─────────────────┐
                    │   BALANCED      │
                    │  OPPORTUNITY    │
                    └────────┬────────┘
         ┌───────────────────┼───────────────────┐
         │                   │                   │
         ▼                   ▼                   ▼
    ┌─────────┐        ┌─────────┐        ┌─────────┐
    │ Account │        │ Revenue │        │ Travel  │
    │ Volume  │        │Potential│        │ Load    │
    └─────────┘        └─────────┘        └─────────┘
                    ┌─────────────────┐
                    │   机会平衡      │
                    └────────┬────────┘
         ┌───────────────────┼───────────────────┐
         │                   │                   │
         ▼                   ▼                   ▼
    ┌─────────┐        ┌─────────┐        ┌─────────┐
    │ 客户数量 │        │ 营收潜力 │        │ 差旅负荷 │
    └─────────┘        └─────────┘        └─────────┘

Key Metrics Overview

关键指标概览

CategoryMetricTarget RangeRed Flag
ActivityMeetings/week/rep10-15<5
PipelineCoverage ratio3-4x<2x
VelocityAvg sales cycleIndustry dependentGrowing
QualityWin rate20-30%<15% or >50%
ForecastAccuracy±10%>25% variance
DataDuplicate rate<5%>10%
类别指标目标范围预警信号
活动指标每位销售代表每周会议数10-15<5
漏斗指标覆盖率3-4x<2x
流转速度平均销售周期依行业而定持续变长
质量指标赢单率20-30%<15% 或 >50%
预测指标准确率±10%偏差>25%
数据指标重复率<5%>10%

Anti-Patterns

反模式

  • Field proliferation — Adding fields without removing unused ones
  • Report graveyard — Dashboards no one looks at
  • Process theater — Mandatory updates that don't drive action
  • Excel dependency — Critical processes outside the CRM
  • Garbage in, garbage out — No data quality governance
  • Over-automation — Automating bad processes faster
  • Single point of failure — Tribal knowledge in one person's head
  • Metric gaming — Optimizing for the number, not the outcome
  • 字段冗余——只添加字段而不删除未使用的字段
  • 报表无人问津——创建的仪表板无人查看
  • 流程形式化——强制要求的更新却无法驱动行动
  • 依赖Excel——关键流程脱离CRM系统
  • 垃圾进垃圾出——缺乏数据质量管控
  • 过度自动化——更快地自动化糟糕的流程
  • 单点故障——关键知识仅掌握在一人手中
  • 指标博弈——为了数字而优化,而非关注实际结果