Demand Spring

Velocity Reporting

Velocity Reporting is a reporting approach that tracks the speed at which leads and opportunities move through the funnel over time.

Also known as: cycle time reporting, stage velocity tracking, funnel velocity

Velocity Reporting focuses on time as the central dimension, measuring how long leads and deals spend at each stage and how quickly they progress from entry to close. It treats speed as a performance signal in its own right, separate from volume and conversion, and it functions as an early-warning system for funnel health.

What Velocity Reporting Means

Velocity Reporting captures timestamps as records enter and leave each funnel stage, then reports averages and trends such as days-in-stage and total cycle time. Revenue teams use it to spot slowdowns early, since rising stage durations often precede a drop in closed revenue by one to two quarters. Velocity is a leading indicator where conversion is lagging. The discipline differs from pipeline velocity, which is a single calculated metric combining deals, win rate, value, and cycle length into one number; Velocity Reporting is the broader practice of monitoring time-based movement across stages and trends over periods.

How Velocity Reporting Works

The mechanics require accurate stage-entry and stage-exit timestamps in the CRM. If reps move deals between stages inconsistently, in bulk at month-end, or retroactively after the fact, the timing data becomes unreliable and the reporting misleads. CRM automation that timestamps stage changes automatically is the practical solution. Once data is clean, the reports typically show median and percentile dwell times per stage, total cycle time from entry to close, and trends versus trailing 12-month baselines. A Velocity Reporting baseline is the trailing average velocity for a specific segment over a meaningful window, typically 12 months.

Common Pitfalls and Misconceptions

The nuance is that faster is not automatically better. Compressed cycle times can indicate strong demand and good fit, but they can also reflect smaller deals, skipped diligence, or rushed evaluations that win at the expense of long-term retention. Velocity Reporting should be read alongside deal size and win rate, since speeding up small low-quality deals can produce flattering velocity reports that hide underlying problems. The second pitfall is using a blended velocity number that hides segment-specific deterioration: enterprise slowing while SMB accelerates can show flat blended velocity while masking a meaningful problem.

Velocity Reporting in Practice

The practitioner discipline is segmenting velocity by deal size, segment, and acquisition source, then watching each segment against its own historical baseline rather than a blended average. Enterprise deals naturally move slower than SMB; that is not a problem unless enterprise velocity has slowed against its own historical norm. The cleanest Velocity Reporting programs flag any segment that drifts more than 20 percent from its trailing 12-month average, which catches sales-process, qualification, or competitive-pressure shifts before they show up in revenue. Most teams have one or two segments whose velocity is deteriorating quietly, masked by overall metrics that look fine.

Back to the Glossary

Common questions.

What does velocity reporting actually track?
It tracks time-based metrics: how long records sit in each stage, total time from lead creation to close, and how those durations trend. The emphasis is on the pace of movement, not just volume or conversion. Velocity exposes momentum changes that pure volume or conversion reporting can miss.
Why is funnel speed worth measuring?
Slowing velocity often signals trouble before it shows up in revenue. Deals lingering longer in a stage can indicate qualification problems, competitive friction, or capacity issues, giving teams an early warning one to two quarters before the impact lands in closed revenue. It is a leading indicator where conversion is lagging.
Is faster funnel velocity always good?
Not necessarily. Quicker cycles can mean healthy demand, but they may also reflect smaller, simpler deals or rushed evaluations that win at the expense of retention. Velocity should be interpreted together with deal value and win rate, since speeding up small low-quality deals can flatter velocity while masking problems.
How is velocity reporting different from pipeline velocity?
Pipeline velocity is a single calculated metric combining deals, win rate, value, and cycle length into one number. Velocity reporting is the broader practice of monitoring time-based movement across stages and trends over periods. Pipeline velocity is the index; velocity reporting is the full discipline.
What data does velocity reporting require?
It needs accurate stage-entry and stage-exit timestamps in the CRM. If reps move deals between stages inconsistently, in bulk at month-end, or retroactively after the fact, the timing data becomes unreliable and the reporting misleads. CRM automation that timestamps stage changes automatically is the practical solution.
How do you segment velocity reporting?
Segment by deal size, ICP fit, acquisition channel, and product line. Enterprise versus SMB velocity differs enormously; inbound versus outbound differs; experienced versus new reps differ. Blended velocity hides important variation, so segment-specific views with each compared to its own historical baseline are far more informative than aggregate reporting.
What is a velocity baseline?
A velocity baseline is the trailing average velocity for a specific segment over a meaningful window, typically 12 months. It is the reference point against which current velocity is compared. The right benchmark is your own segment baseline, not a universal industry number. Drift of 20 percent or more from baseline is the most common alerting threshold for velocity reporting.

Related Terms

More from Measurement.

  • Algorithmic Attribution

    Algorithmic Attribution is a data-driven approach that uses statistical or machine learning models to assign conversion credit based on each touchpoint's measured contribution rather than a fixed rule.

  • Annual Recurring Revenue (ARR)

    Annual Recurring Revenue (ARR) is the value of the recurring components of a subscription business normalized to a one-year period, excluding one-time fees.

  • Attribution Window

    Attribution Window is the defined time period during which a marketing touchpoint can be credited for a resulting conversion in an attribution model.

  • Benchmarking

    Benchmarking is the practice of comparing performance metrics against past results, competitors, or industry standards to assess how performance compares to a reference point.

  • Bottom-Up Forecasting

    Bottom-Up Forecasting is a forecasting method that builds revenue projections by summing individual deals, accounts, or program estimates from the ground up rather than dividing a top-line target downward.

  • Bounce Rate

    Bounce Rate is the percentage of website sessions in which a visitor views a single page and leaves without further interaction or navigating to another page.

Back to the Glossary Talk to a Strategist

Let’s Talk

Let’s talk about what your next quarter could look like.

Tell us what you’re working on. A senior practitioner reads it, not an SDR queue, and replies, usually within one business day.

  • Reviewed personally, not routed through a queue.
  • A conversation about what you’re actually working on, not a generic pitch.
  • No pressure, just a chance to talk it through.

Book a conversation