What Is Sales Velocity?什么是 Sales Velocity？
Sales velocity estimates how much revenue value a defined group of qualified opportunities generates per unit of time. The common formula multiplies opportunity count, average deal value, and win rate, then divides by average sales cycle length.
Sales Velocity 用于估计一组定义明确的合格商机在单位时间内产生多少收入价值。常见公式把商机数量、平均交易金额和赢率相乘，再除以平均销售周期。
The metric compresses four parts of the revenue system into one rate. It helps Sales Ops, RevOps, sales leaders, and finance compare how efficiently comparable sales motions turn qualified pipeline into won value. It can reveal whether performance changed because the team had more opportunities, captured more value per win, converted a higher share, or completed decisions faster.
该指标把收入系统的四个部分压缩成一个速率，帮助 Sales Ops、RevOps、销售管理者和财务团队比较可比销售模式把合格 Pipeline 转化为赢单价值的效率。它可以揭示变化来自更多商机、更高单笔价值、更高转化比例，还是更快完成决策。
Sales velocity is a diagnostic summary, not a guaranteed forecast, seller score, or universal benchmark. A higher value can be encouraging, but it can also result from inconsistent qualification, a changed cohort, currency movement, an unusually large deal, or an incomplete sales-cycle sample. Preserve the four inputs and their definitions so the headline number can be explained.
Sales Velocity 是诊断性汇总，而不是确定预测、销售人员评分或通用基准。更高数值可能是积极信号，也可能来自资格口径不一致、Cohort 改变、汇率变化、异常大额交易或销售周期样本尚未成熟。必须保留四项输入及其定义，才能解释最终数字。
| Related concept相关概念 | What it measures衡量内容 | How it differs区别 |
|---|---|---|
| Sales cycle length销售周期长度 | Elapsed time from a defined start event to a defined close event.从明确开始事件到明确结束事件的经过时间。 | It is one denominator input, not the complete velocity metric.它只是分母输入之一，并非完整速度指标。 |
| Pipeline velocityPipeline Velocity | Often used as a synonym for sales velocity; sometimes scoped to pipeline movement.通常是 Sales Velocity 的同义表达，有时仅指 Pipeline 移动速度。 | Document the chosen definition rather than assuming every dashboard uses identical math.应记录采用的定义，不能假设所有 Dashboard 使用相同算法。 |
| Lead velocityLead Velocity | Usually tracks growth or movement of leads before qualified opportunity creation.通常跟踪合格商机创建之前的线索增长或移动。 | It answers an earlier-funnel question and should not be silently substituted.它回答更早漏斗阶段的问题，不能直接替代。 |
| Revenue run rateRevenue Run Rate | Annualizes or projects realized revenue from a recent period.根据近期期间对已实现收入进行年化或推算。 | It uses realized accounting or operating results rather than the four pipeline drivers.它使用已实现的会计或运营结果，而非四项 Pipeline 驱动因素。 |
Sales Velocity Formula and UnitsSales Velocity 公式与单位
Sales velocity = (qualified opportunities × average deal value × win rate) ÷ average sales cycle length.
Sales Velocity =（合格商机数量 × 平均交易金额 × 赢率）÷ 平均销售周期。
Use win rate as a decimal in the calculation: 25% becomes 0.25. If deal value is measured in dollars and cycle length in days, the output is dollars per day. A weekly or monthly result is possible only when every time input is converted consistently. Do not calculate in days and relabel the result as monthly without a documented conversion.
计算时应把赢率写成小数，例如 25% 写为 0.25。如果交易金额使用美元、周期使用天，结果单位就是美元/天。只有在所有时间输入一致转换时，才可以得到每周或每月结果。不能使用天数计算后直接把结果标记为月度指标。
The numerator represents expected won value from the selected opportunity population: opportunity count multiplied by average value and the expected share won. Dividing by cycle time expresses that expected value as a rate. This interpretation is most defensible when the inputs represent comparable populations and stable definitions. Mixing current open opportunities with last year’s company-wide deal value, a different segment’s win rate, and won-only cycle length creates a mathematically valid number with weak business meaning.
分子表示所选商机群体的预期赢单价值：商机数量乘以平均金额，再乘以预计赢单比例。除以周期后，预期价值被表达为速率。当输入来自可比群体且定义稳定时，这种解释最可靠。如果把当前未结商机、去年全公司的平均交易金额、其他分群赢率和仅赢单周期混合，虽然数学计算成立，业务含义却很弱。
Place this formula within the broader sales analytics framework, where pipeline composition, stage conversion, forecasting, quota, and realized revenue provide the context required for a decision.
应把该公式放入更完整的销售分析体系中，由 Pipeline 构成、阶段转化、预测、Quota 和实际收入提供决策所需背景。
Define the Four Sales Velocity Drivers定义 Sales Velocity 的四个驱动因素
Count opportunities that meet an explicit eligibility rule for the selected motion and window. State stage, status, source, duplicate, reopening, renewal, and expansion treatment.
统计满足所选销售模式和窗口明确资格规则的商机，并说明阶段、状态、来源、重复、重新开启、续约与扩展的处理方式。
Choose a value basis such as bookings, annual contract value, total contract value, or another approved measure. Define discounts, credits, splits, products, term, and currency conversion.
选择 Bookings、年度合同价值、合同总价值或其他批准口径，并定义折扣、抵扣、拆分、产品、期限和汇率转换。
A common opportunity-count version is closed-won ÷ eligible closed opportunities. State whether the denominator is won plus lost, how no-decisions are handled, and whether value weighting is used.
常见数量口径为赢单商机 ÷ 合格已结商机。应说明分母是否为赢单加输单、无决策如何处理，以及是否采用金额加权。
Measure elapsed time between explicit events, such as qualified opportunity creation and terminal close. State whether won and lost deals are included and use distributions when the mean is skewed.
衡量明确事件之间的经过时间，例如合格商机创建到最终关闭。说明是否包含赢单与输单，并在均值受偏态影响时使用分布。
The four drivers interact. Adding weak opportunities may increase opportunity count while reducing win rate and lengthening the cycle. Increasing average deal value may introduce more stakeholders and approvals. Aggressively closing old deals can shorten the measured cycle while changing the population. Optimize the system rather than maximizing one field in isolation.
四项驱动因素相互影响。加入低质量商机可能提高数量，却降低赢率并延长周期；提高平均交易金额可能引入更多利益相关者和审批；激进关闭旧交易可能缩短测得周期，却改变分析群体。因此应优化完整系统，而不是孤立最大化某个字段。
Create a Sales Velocity Measurement Contract建立 Sales Velocity 衡量契约
Before calculating, write one metric contract that binds all inputs to the same business question. Include owner, sales motion, population, observation window, cohort rule, value basis, currency date, start and end events, closed-status mapping, exclusions, refresh cutoff, formula version, and intended decision.
计算前应建立一份指标契约，把全部输入绑定到同一业务问题。契约应包括负责人、销售模式、群体、观察窗口、Cohort 规则、金额口径、汇率日期、开始与结束事件、关闭状态映射、排除项、刷新截止时间、公式版本和目标决策。
| Decision决策 | Recommended scope建议范围 | Primary caution主要注意事项 |
|---|---|---|
| Trend a sales motion跟踪销售模式趋势 | Stable cohort, value basis, currency, and formula version over comparable periods.在可比期间保持 Cohort、金额口径、币种和公式版本稳定。 | Mix shifts can move the metric even if every segment is unchanged.即使每个分群不变，结构变化也会移动整体指标。 |
| Compare teams比较团队 | Teams with similar territory, product, maturity, capacity, and opportunity definitions.区域、产品、成熟度、产能和商机定义相似的团队。 | Uncontrolled assignments make a seller ranking misleading.未控制的任务分配会让销售排名产生误导。 |
| Plan an improvement规划改进 | Baseline driver values, constraint hypothesis, target cohort, intervention, and validation date.基线驱动值、瓶颈假设、目标 Cohort、干预和验证日期。 | A modeled uplift is not a realized result until later outcomes are reconciled.模型提升在与后续结果对账前不等于实际结果。 |
Data Requirements and Quality Checks数据要求与质量检查
A reproducible calculation normally needs more than a current CRM opportunity export. Prepare stable opportunity IDs, created and qualified timestamps, stage history, terminal status and close time, original and revised amounts, currency, product, sales motion, owner history, account and territory dimensions, and the evidence used for qualification. Preserve orders, contracts, or billing outcomes when the chosen value must reconcile to a downstream financial result.
可复现计算通常不能只依赖当前 CRM 商机导出。应准备稳定的商机 ID、创建和合格时间戳、阶段历史、最终状态与关闭时间、原始及修订金额、币种、产品、销售模式、归属历史、客户与区域维度，以及用于资格判断的证据。当所选金额需要与下游财务结果对账时，还应保留订单、合同或 Billing 结果。
Confirm that stage, amount, close-date, owner, and status changes are preserved with effective timestamps. Current fields cannot reconstruct the population visible at an earlier review or explain whether a shorter cycle came from genuine progress, backfilled dates, or deleted old opportunities.
确认阶段、金额、成交日期、负责人和状态变化均带生效时间戳保存。当前字段无法重建过去复盘时可见的群体，也无法说明周期缩短来自真实推进、补录日期还是删除旧商机。
Test duplicate IDs, merged accounts, reopened deals, split opportunities, renewals recorded as new business, internal tests, and records that skip required qualification stages. Count each business event according to the metric contract, not according to how many rows a join produces.
检查重复 ID、合并客户、重新开启交易、拆分商机、被记录为新增的续约、内部测试，以及跳过必要资格阶段的记录。应按照指标契约统计业务事件，而不是按照 Join 产生的行数统计。
Reject impossible sequences such as close before creation, qualification after terminal close, or negative stage duration. Decide how weekends, time zones, missing timestamps, backdated updates, and reopened opportunities affect elapsed time before comparing teams or periods.
排除成交早于创建、合格晚于最终关闭或阶段时长为负等不可能顺序。比较团队或期间前，应确定周末、时区、缺失时间戳、回填更新和重新开启交易如何影响经过时间。
Validate currency codes, exchange-rate dates, amount basis, discounts, credits, product splits, ownership credit, and cancellations. Reconcile aggregate won value to the approved downstream source within a documented tolerance and explain every material difference.
验证币种代码、汇率日期、金额口径、折扣、抵扣、产品拆分、归属信用和取消。按照记录的容差把汇总赢单金额与批准的下游来源对账，并解释所有重大差异。
Run quality checks before calculating and publish their result beside the metric. At minimum, report eligible record count, missing required fields, duplicates, invalid dates, unconverted currencies, unmatched downstream outcomes, and cohort maturity. If a material quality threshold fails, label the velocity as provisional or withhold comparison instead of presenting a precise but unsupported rate. Keep the rejected-record list and rule version so another analyst can reproduce the result.
应在计算前运行质量检查，并把结果与指标一起发布。至少报告合格记录数、必要字段缺失、重复、无效日期、未转换币种、无法匹配的下游结果和 Cohort 成熟度。如果重大质量阈值失败，应把 Velocity 标记为暂定或暂停比较，而不是展示精确但缺乏支持的速率。保留被拒记录清单和规则版本，使其他分析人员可以复现结果。
How to Calculate Sales Velocity Correctly如何正确计算 Sales Velocity
-
Choose one sales motion and question.选择一种销售模式和一个问题。
Do not blend new business, expansion, renewal, partner, SMB, and enterprise motions unless the decision truly concerns the combined portfolio.
除非决策确实关注组合整体，否则不要混合新增、扩展、续约、渠道、SMB 和企业销售。
-
Set the observation window and cohort rule.设定观察窗口与 Cohort 规则。
Choose created-date, qualified-date, or closed-date cohorts and allow enough maturity to observe wins, losses, and cycle length.
选择按创建日、合格日或关闭日形成 Cohort，并留出足够时间观察赢单、输单和周期。
-
Validate opportunity eligibility.验证商机资格。
Remove duplicates, tests, invalid stages, unsupported records, and out-of-scope motions according to documented rules, not manual preference.
按照记录规则排除重复、测试、无效阶段、缺乏支持的记录和范围外模式，而不是依赖人工偏好。
-
Calculate each input separately.分别计算每项输入。
Retain numerator, denominator, sample size, mean, median, percentiles, and missing-data counts. A single final rate cannot reveal which input is unstable.
保留分子、分母、样本量、均值、中位数、百分位和缺失数据数量。单一最终速率无法说明哪项输入不稳定。
-
Standardize value and time units.统一金额与时间单位。
Apply approved currency conversion and use one time unit. Document whether calendar days, business days, weeks, or months are used.
应用批准的汇率转换并使用统一时间单位，记录使用自然日、工作日、周还是月。
-
Apply the formula and test sensitivity.应用公式并测试敏感度。
Calculate the baseline, then change one input at a time to understand leverage. Do not present scenarios as commitments.
先计算基线，再逐项改变输入以理解杠杆作用，不能把情景模拟描述成承诺。
-
Reconcile and version the result.对账并记录版本。
Compare won value with orders or finance outcomes where appropriate, preserve source lineage, and publish the formula version and refresh time.
在适用时把赢单金额与订单或财务结果对账，保留数据血缘，并发布公式版本和刷新时间。
Sales Velocity Calculation ExampleSales Velocity 计算示例
Hypothetical example: a defined mid-market new-business motion has 120 qualified opportunities, an average deal value of $30,000, a 25% win rate, and a 60-day average sales cycle.
假设示例：某项定义明确的中端市场新增销售模式拥有 120 个合格商机，平均交易金额为 30,000 美元，赢率为 25%，平均销售周期为 60 天。
(120 × $30,000 × 0.25) ÷ 60 = $15,000 per day.
（120 × 30,000 美元 × 0.25）÷ 60 = 15,000 美元/天。
This is a modeled rate for that defined population, not proof that exactly $15,000 will book every day. Deals close unevenly, and the input statistics summarize populations. The value becomes useful when compared with a consistently calculated prior period or a controlled scenario.
这是该定义群体的模型速率，并不证明每天一定产生 15,000 美元 Bookings。交易关闭并不均匀，各项输入是群体统计。只有与口径一致的上一期间或受控情景比较时，该数值才更有意义。
| Single-driver scenario单驱动情景 | New input新输入 | Modeled velocity模型速度 | Interpretation解释 |
|---|---|---|---|
| 10% more qualified opportunities合格商机增加 10% | 132 | $16,500/day | A 10% modeled lift if the other drivers truly remain stable.如果其他驱动因素真正保持稳定，模型提升 10%。 |
| 10% higher average deal value平均交易金额提高 10% | $33,000 | $16,500/day | Check whether larger deals also change win rate or cycle length.检查更大交易是否同时改变赢率或周期。 |
| Win rate rises to 27.5%赢率提高到 27.5% | 0.275 | $16,500/day | Validate with a mature comparable cohort, not open opportunities.使用成熟且可比的 Cohort 验证，不能使用未结商机。 |
| Cycle falls by 10%周期缩短 10% | 54 days | $16,667/day | Because time is the divisor, a 10% reduction produces about an 11.1% modeled lift.由于时间位于分母，缩短 10% 产生约 11.1% 的模型提升。 |
Sensitivity analysis isolates arithmetic leverage; it does not prove causality or feasibility. If a proposed change affects multiple drivers, model those dependencies and validate the realized cohort later.
敏感度分析只隔离算术杠杆，并不证明因果关系或可行性。如果某项变化会影响多个驱动因素，应对依赖关系建模，并在后续使用实际 Cohort 验证。
Interpret Sales Velocity Without Hiding the Drivers解释 Sales Velocity 时不要隐藏驱动因素
Always display the headline rate beside the four inputs, sample sizes, period, segment, currency, and formula version. If velocity changes, decompose the difference before assigning a cause. A higher rate with fewer opportunities may be driven by one unusually large win. A lower rate may reflect a strategic shift toward enterprise accounts rather than process deterioration.
最终速率应与四项输入、样本量、期间、分群、币种和公式版本同时展示。指标变化时，应先拆解差异再判断原因。商机减少但速度提高，可能来自一笔异常大额赢单；速度下降也可能源于战略转向企业客户，而不是流程恶化。
- Segment by sales motion. New business, expansion, renewal, partner, SMB, mid-market, and enterprise usually have different economics and timing.按销售模式分群。新增、扩展、续约、渠道、SMB、中端市场和企业销售通常具有不同经济特征与时间。
- Show distributions. Report median and percentiles for deal value and cycle length when outliers distort the mean.展示分布。当异常值扭曲均值时，应报告交易金额和周期的中位数与百分位。
- Distinguish cohort and snapshot views. A current pipeline count and a historical closed cohort answer different questions.区分 Cohort 与快照。当前 Pipeline 数量和历史已结 Cohort 回答不同问题。
- Avoid incomplete-period bias. Do not compare a partially observed cohort with a mature cohort without adjustment.避免未完整期间偏差。未经调整，不能把观察尚未完成的 Cohort 与成熟 Cohort 比较。
Compare both level and change. A team can have a lower absolute velocity than another team yet improve faster against its own stable baseline, while the apparently stronger team deteriorates. Use an input bridge that attributes the modeled difference to opportunity count, deal value, win rate, cycle length, and any interaction or mix effect. Then inspect the records responsible for the largest movement. Record whether the explanation is a verified data fact, a calculation, or an operating hypothesis. This prevents a convenient story from being presented as a proven cause and makes the next review testable.
应同时比较绝对水平和变化。某团队的绝对 Velocity 可能低于另一团队，却相对自身稳定基线改善更快；看似更强的团队反而可能正在恶化。使用输入桥接把模型差异归因到商机数量、交易金额、赢率、周期以及交互或结构效应，再检查造成最大移动的底层记录。记录解释属于已验证数据事实、计算结果还是运营假设，防止把方便的故事描述成已证明原因，并使下次复盘可以检验。
How to Improve Sales Velocity Responsibly如何负责任地提高 Sales Velocity
Start with the constrained driver and protect the others. More activity is not automatically better, and faster is not automatically healthier. Define the intervention, target cohort, expected mechanism, guardrail metrics, owner, and review date before changing the process.
应从受约束的驱动因素开始，同时保护其他指标。更多活动不一定更好，更快也不一定更健康。改变流程前，应定义干预、目标 Cohort、预期机制、护栏指标、负责人和复核日期。
Improve targeting, source quality, handoff criteria, qualification evidence, and capacity alignment. Guard against adding low-intent records that later reduce win rate and extend cycle time.
改善目标选择、来源质量、交接标准、资格证据和产能匹配，防止加入低意向记录后降低赢率并延长周期。
Clarify value, packaging, scope, expansion paths, and discount governance. Track margin, approval time, and win rate so larger proposals do not create hidden deterioration.
明确价值、组合、范围、扩展路径和折扣治理，同时跟踪利润、审批时间和赢率，避免更大报价带来隐性恶化。
Strengthen qualification, stakeholder coverage, problem evidence, solution fit, competitive learning, mutual plans, and loss review. Do not improve the metric by redefining losses out of the denominator.
加强资格判断、利益相关者覆盖、问题证据、方案匹配、竞争学习、双方计划和输单复盘，不能通过把输单移出分母来改善指标。
Locate stage delays, unclear ownership, repeated discovery, scheduling friction, approval queues, legal rework, and missing next events. Preserve necessary buyer evaluation and control steps.
定位阶段延迟、归属不清、重复需求发现、排期摩擦、审批排队、法务返工和下一事件缺失，同时保留必要的买方评估与控制步骤。
Use a balanced experiment. For example, if legal review appears to extend cycle time, define eligible deals, capture submission completeness, measure queue and rework time, introduce a standardized intake, and compare a later cohort. Monitor win rate, discount, contract risk, and customer experience so a shorter cycle is not achieved by bypassing essential review.
应使用平衡实验。例如，如果法务审查似乎延长周期，可定义合格交易、记录提交完整度、衡量排队与返工时间、引入标准化入口，并比较后续 Cohort。同时监测赢率、折扣、合同风险和客户体验，避免通过绕过必要审查来缩短周期。
Connect Sales Velocity to Pipeline and Forecasting将 Sales Velocity 与 Pipeline 和预测连接
Sales velocity complements sales pipeline management. Pipeline management preserves stage evidence, movement, aging, coverage, and data quality; velocity summarizes four selected drivers as a rate. A healthy pipeline can still have a lower velocity when it intentionally serves larger, slower segments.
Sales Velocity 是销售 Pipeline 管理的补充。Pipeline 管理保留阶段证据、移动、老化、覆盖和数据质量，Velocity 则把四项驱动因素汇总为速率。当团队有意服务更大、更慢的分群时，健康 Pipeline 也可能具有较低速度。
It also informs, but does not replace, sales forecasting. Forecasts answer what is likely to close in a defined future period and incorporate timing, forecast categories, judgment, seasonality, concentration, and uncertainty. Velocity is better used as a driver trend or scenario input than as a direct daily bookings promise.
它也可以支持但不能替代销售预测。预测回答特定未来期间内可能成交什么，并结合时间、预测类别、判断、季节性、集中度和不确定性。Velocity 更适合作为驱动趋势或情景输入，而不是每天 Bookings 的直接承诺。
Common Sales Velocity Errors and ControlsSales Velocity 常见错误与控制
| Error错误 | Why it misleads为何误导 | Control控制方法 |
|---|---|---|
| Mixing open and closed populations混合未结与已结群体 | Opportunity count, win rate, value, and cycle may describe different underlying deals.商机数、赢率、金额和周期可能描述不同交易群体。 | Publish cohort and snapshot rules for every input.为每项输入发布 Cohort 和快照规则。 |
| Using unqualified volume使用未合格数量 | It initially raises opportunity count but often weakens later conversion and time.它最初提高商机数，却常常削弱后续转化与时间。 | Require auditable qualification evidence and monitor downstream outcomes.要求可审计的资格证据，并监测下游结果。 |
| Ignoring outliers忽略异常值 | One large deal or long cycle can dominate the mean and headline rate.一笔大额交易或超长周期可能主导均值和最终速率。 | Show median, percentiles, trimmed sensitivity, and record-level context.展示中位数、百分位、截尾敏感度和记录级背景。 |
| Treating scenarios as forecasts把情景当作预测 | Arithmetic sensitivity does not prove that a change is feasible or independent.算术敏感度不能证明变化可行或相互独立。 | Label assumptions and validate later realized outcomes.标记假设，并验证后续实际结果。 |
| Ranking sellers without controls缺乏控制的销售排名 | Territory, product, tenure, assignment, and segment mix affect every driver.区域、产品、任职时间、任务分配和分群结构影响全部驱动因素。 | Use comparable cohorts and support coaching rather than simplistic ranking.使用可比 Cohort，并用于辅导而非简单排名。 |
For consistent denominator, cohort, currency, ownership, and snapshot rules, use the related sales metrics guide. Governance matters because a small definition change can move several velocity inputs simultaneously.
如需统一分母、Cohort、币种、归属和快照规则，可参考相关的销售指标指南。治理非常重要，因为一个小的定义变化可能同时移动多项 Velocity 输入。
Analyze Sales Velocity Across Connected Data跨连接数据分析 Sales Velocity
Prepare CRM opportunity and stage history, qualified-status rules, closed outcomes, amount history, currency conversion, owner history, product and segment dimensions, orders or billing actuals, the metric contract, and one decision-focused question. Useful questions include: Which driver explains the quarter-over-quarter change? Did velocity fall within every segment or only because the mix changed? Is a shorter cycle associated with stable win rate and deal quality?
应准备 CRM 商机与阶段历史、合格状态规则、关闭结果、金额历史、汇率转换、归属历史、产品和分群维度、订单或 Billing 实际值、指标契约和一个面向决策的问题。例如：哪项驱动因素解释环比变化？每个分群的速度都下降了，还是仅由结构改变导致？更短周期是否同时保持赢率和交易质量？
InfiniSynapse can support connected analysis by helping users examine available evidence across CRM, warehouse, target, and finance data; compare metric definitions; segment results; inspect records; and document conclusions for human review. It does not replace CRM execution, approve finance actuals, or prove that an observed relationship is causal.
InfiniSynapse 可以帮助用户跨 CRM、Warehouse、目标和财务数据检查可用证据、比较指标定义、分群结果、查看记录并记录供人工复核的结论，从而支持连接分析。它不会替代 CRM 执行、审批财务实际值，也不能证明观察关系具有因果性。
Prepare the four driver tables, definitions, history, segment dimensions, quality checks, and one focused question. Then use InfiniSynapse to examine connected evidence and record a reproducible interpretation.
准备四项驱动表、定义、历史、分群维度、质量检查和一个明确问题，然后使用 InfiniSynapse 检查连接证据并记录可复现解释。
Try InfiniSynapse Online在线体验 InfiniSynapseSales Velocity Calculation ChecklistSales Velocity 计算检查清单
- Define one sales motion, business question, observation window, and output unit.定义一种销售模式、业务问题、观察窗口和输出单位。
- Use explicit qualified-opportunity, closed-status, value, and cycle rules.使用明确的合格商机、关闭状态、金额和周期规则。
- Keep cohorts, segments, currencies, and time units comparable.保持 Cohort、分群、币种和时间单位可比。
- Retain all four inputs, sample sizes, distributions, filters, and formula version.保留四项输入、样本量、分布、筛选条件和公式版本。
- Label hypothetical scenarios and validate later realized outcomes.标记假设情景，并验证后续实际结果。
- Monitor guardrails when improving one driver.改进某项驱动时监测护栏指标。
Sales Velocity FAQSales Velocity 常见问题
Sales velocity estimates the revenue value a defined opportunity population generates per unit of time by combining qualified opportunity count, average deal value, win rate, and sales cycle length.
Sales Velocity 通过组合合格商机数、平均交易金额、赢率和销售周期，估计定义明确的商机群体在单位时间内产生的收入价值。
Multiply qualified opportunities by average deal value and win rate, then divide by average sales cycle length. Currency divided by days produces currency per day.
合格商机数乘以平均交易金额和赢率，再除以平均销售周期。金额除以天数后，结果单位为金额/天。
Define one motion and window, use qualified opportunities, calculate value and win rate from comparable cohorts, define cycle start and end events, and keep currency and time units consistent.
定义一种销售模式和窗口，使用合格商机，从可比 Cohort 计算金额与赢率，定义周期开始和结束事件，并保持币种和时间单位一致。
There is no universal good value because markets, prices, motions, qualification, and cycles differ. Compare a consistently defined metric over time and across genuinely comparable segments.
没有通用的好数值，因为市场、价格、销售模式、资格标准和周期不同。应按一致口径进行时间趋势和真正可比分群的比较。
Improve the constrained input without damaging the others: create more qualified opportunities, improve value capture, raise win rate, or remove avoidable cycle delay. Validate by cohort and outcome.
在不损害其他输入的情况下改进瓶颈：增加合格商机、提高价值获取、提升赢率或消除可避免的周期延迟，并使用 Cohort 与结果验证。
No. Cycle length measures elapsed time and is one denominator input. Sales velocity combines it with opportunity count, average deal value, and win rate to estimate value per time unit.
不同。销售周期衡量经过时间，是分母输入之一。Sales Velocity 还组合商机数量、平均交易金额和赢率，以估计单位时间价值。