It can help you compare scenarios and investigate constraints. Its usefulness depends on the definitions and records behind the calculation.

At Collective, we read it alongside acquisition cost, margin and the actual movement of opportunities. The calculation supports a decision; it does not replace a revenue forecast or cash-flow schedule.

The formula

Pipeline velocity = opportunities × average deal value × opportunity win rate ÷ average sales-cycle days.

This is a widely used sales-velocity formula, also described by Salesforce. The four inputs connect volume, value, conversion and time.

Using days for the cycle length produces a result expressed as value per day. Enter a percentage as a decimal when calculating: 25% becomes 0.25.

Before running the numbers, define the sales process the calculation represents. Avoid combining a short-cycle service with a long-cycle project if their buying processes and values differ materially.

Define an opportunity

An opportunity should represent a prospect that has reached an agreed stage in the sales process. A raw enquiry does not automatically meet that definition.

Specify the requirements for entering the stage and make sure the team applies them consistently. Record when an opportunity closes or is no longer active.

The opportunity count is a stock of work in the pipeline at a point in time or an average across a defined period. The win rate and cycle length generally come from historical outcomes. Document how you select those inputs and why they are relevant to the current pipeline.

If the current mix differs from the history, calculate separate segments or show a range of assumptions. A single blended figure can conceal important differences.

Define value, win rate and time

Use average deal value on a consistent revenue basis. Do not mix total contract value, recurring monthly revenue and gross profit in one field.

Calculate opportunity win rate from a defined cohort or set of resolved opportunities, and state the approach. Open opportunities may still change the result if you are assessing a cohort that has not completed its cycle.

For cycle length, define the start and end events. The period from qualification to signed contract differs from enquiry to payment. Keep the boundary consistent when comparing periods.

Record whether the cycle statistic covers won deals only or all resolved opportunities. Check long-running open deals separately: they can be missed by a report built only from completed sales.

Work through an illustrative example

Suppose the model uses 50 active opportunities, an average deal value of $50,000, a 25% win rate and a 90-day cycle.

Illustrative pipeline inputs
InputValue
Opportunities50
Average deal value$50,000
Opportunity win rate25%
Average sales cycle90 days

The calculation is 50 × $50,000 × 0.25 ÷ 90, giving $6,944.44 per day.

This is an illustrative planning indicator. It does not mean $6,944.44 will arrive in the bank each day or that the business has booked that amount of revenue.

Multiplying the figure across a year introduces assumptions about replenishment, deal mix, capacity and the stability of the inputs. If you show that scenario, state those assumptions rather than presenting it as a settled annual yield.

Change one input first

Keep the other inputs fixed and increase the win rate from 25% to 27.5%. That is a 10% relative increase, or 2.5 percentage points. The modelled velocity rises by 10%.

Now consider reducing the cycle from 90 to 81 days while holding the other original inputs fixed. That is a 10% reduction in time, but the velocity increases by approximately 11.1%, because time is the divisor.

This is an inverse relationship. The same percentage movement in a numerator and denominator does not create the same percentage change in the result.

Use that distinction when reviewing targets. A faster cycle needs an operational explanation, such as removing a documented delay, rather than simply entering a smaller number in a calculator.

Understand the combined sensitivity

If opportunities, deal value and win rate each rise by 10%, while cycle length falls by 10%, the multiplier is:

1.1 × 1.1 × 1.1 ÷ 0.9 = 1.4789.

That represents approximately 47.9% higher modelled velocity. Applied to the illustrative baseline, the result is about $10,270.06 per day.

The calculation shows sensitivity, not the probability of achieving the changes. The inputs may influence one another. Increasing deal value could change win rate or cycle length. Increasing opportunity volume could place pressure on sales capacity.

When modelling opportunities, fractional counts can appear in percentage scenarios. Actual pipeline records are whole opportunities; make that distinction if turning the sensitivity into a practical target.

Check what the formula leaves out

Velocity does not include delivery cost, margin, payment terms or the timing of cash receipts. Faster sales at a lower margin may produce a different commercial result from the one the headline suggests.

It also does not show the distribution of deal sizes or cycle lengths. A few large opportunities can affect an average. Review the underlying records and segment the pipeline where useful.

For property, a signed contract and settlement are different events. For a construction business, winning the work and having capacity to deliver it are different decisions. Keep those realities in the wider commercial review.

Use the model to choose a question

If the cycle is lengthening, inspect the stage where opportunities are waiting. If win rate is changing, compare qualification criteria, deal mix and recorded outcomes. If value is rising, check whether margin and delivery requirements are changing too.

Connect the number to a practical investigation. Record the explanation, the action and the point at which the team will review the result.

Collective helps businesses make their marketing and sales performance more visible and useful. If your pipeline report raises questions it cannot answer, discuss the measurement with us.

Continue the conversationWhat does this mean for your business?