# Sales velocity in Pipedrive: calculate it, then find the lever

https://salesbond.app/blog/sales-velocity-pipedrive/
Published: 2026-10-01 · Updated: 2026-10-26

Sales velocity is the revenue your pipeline produces per day: number of opportunities times average deal value times win rate, divided by the length of the sales cycle in days. With 20 deals at $5,000, a 40% win rate and a 60-day cycle, that is about $667 a day (hypothetical).

The average deal value in that formula is only as useful as [what goes into the value field](https://salesbond.app/blog/acv-vs-deal-value-pipedrive/).

The formula is printed on nearly every page that ranks for the term, [HubSpot’s guide](https://blog.hubspot.com/sales/sales-velocity) among them, and it is not the hard part. The hard part is the week after you calculate it. Which Pipedrive deals count as opportunities? Whose average? What do you say at Monday’s meeting when the number comes out lower than last quarter? This piece is about those questions, for a team of about five reps who run their deals in Pipedrive.

## The sales velocity formula, with one worked example

Sales velocity = (opportunities × average deal value × win rate) ÷ sales cycle length in days

Here is the arithmetic for a hypothetical team, one step at a time: 20 × $5,000 = $100,000; × 0.40 = $40,000; ÷ 60 days = $666.67 a day.

Read it as “this pipeline turns into roughly $667 of won revenue for every day it runs.” That’s a rate, not a forecast for any particular month. You’ll also see it called pipeline velocity. Same calculation, other name; the guides that use that term print the same formula.

On its own the number says nothing about whether the team is doing well. A team at $667 a day is doing $667 a day. It starts to mean something the second time you calculate it with the same definitions, because now there is something to compare. On Salesforce the inputs come from different reports, which we walk through in [sales velocity in Salesforce](https://salesbond.app/blog/sales-velocity-salesforce/).

## The four inputs and where each lives in a Pipedrive deal

You don’t need a custom field to start. Every input comes from things a Pipedrive deal already carries: its status (open, won or lost), its value, the date it was created and the date it was marked won or lost. What you do need is to define each input once, write the definition next to the number, and never change it quietly.

Opportunities can mean two things: deals created during the period, or deals open at its start. We count deals created in the period. A snapshot of open deals drags in everything nobody has bothered to mark as lost, and velocity built on that treats old, silent deals as live pipeline. If your stages are loose enough that “open” means very different things from rep to rep, fix [the stage definitions](https://salesbond.app/blog/sales-pipeline-stages/) first.

For average deal value use the deals won in the period. Values on open deals are estimates a rep typed in on day one. Values on won deals are what the customer agreed to pay, and if your reps routinely correct the value at closing, that correction is the reason to trust won deals over open ones.

Win rate is won deals divided by won plus lost, counted on deals decided in the period. Open deals stay out of the denominator. HubSpot’s guide divides wins by all opportunities; when you pull the number from a live CRM we prefer decided deals only, because the open ones haven’t had their chance to lose yet. Win rate has [more traps than fit in one paragraph](https://salesbond.app/blog/sales-win-rate-pipedrive/), and the biggest of them opens the list below.

Sales cycle length is usually defined as close date minus first contact, averaged across deals. In Pipedrive, the closest honest version is the number of days from a deal’s creation to the date it was marked won, averaged over the deals won in the period. Leave lost deals out. You are measuring how long a sale takes, and a rejection is a different clock.

Pipedrive already does most of this work for you. In Insights, a deal duration report (+ Create > Report > Deal > Duration) shows an average sales cycle in days: the total time the filtered deals spent in all stages, divided by the number of deals. Filter it to won deals closed in your period and that figure is your cycle length. One detail from [Pipedrive’s own documentation](https://support.pipedrive.com/en/article/insights-reports-deal-duration): time spent in stages you have since deleted isn’t counted, so a pipeline that was rebuilt mid-quarter will show a shorter cycle than the buyers lived through.

![Diagram of the sales velocity formula with the Pipedrive deal data behind each of its four inputs](https://salesbond.app/wp-content/uploads/2026/10/sales-velocity-pipedrive-2.png)

## Four ways the number lies

The formula is honest. The data under it often isn’t, and each of these traps moves velocity in a way that looks like news when it isn’t.

1. Open deals in the win-rate denominator. Divide wins by every deal from the period and the win rate drops whenever prospecting goes well, since young deals haven’t been won yet. A good month of pipeline building then shows up as a fall in velocity.
2. Close dates edited by reps. If cycle length is measured to a date someone types in, it records what the rep hoped and then what they settled for. The date a deal was marked won is harder to bend, although a deal marked won two weeks after the contract was signed still stretches the cycle. We looked at [what pushed close dates tell you](https://salesbond.app/blog/pushed-close-dates-pipedrive/) separately.
3. Deal creation date isn’t first contact. Many small teams create the deal in Pipedrive only after a few emails and a call, once the lead feels real, so the cycle looks shorter than what the buyer went through. That’s fine as long as everyone does it the same way. It stops being fine when one rep creates deals at first touch and another at proposal, and the team average blends two habits into a number that describes neither. Segments do the same thing: small and large deals averaged together give a cycle that fits no real deal.
4. One mega-deal in the average. Say ten deals were won this quarter, nine at about $4,000 and one at $40,000. The average is $7,600 and the median is $4,000, so velocity built on the average describes a pipeline almost twice as valuable as the one you’ll have when the big deal doesn’t repeat. Put the median next to the average every time. If they are far apart, show velocity both ways or set the outlier aside and say so. How to read both numbers from the same list of won deals is in [average vs median deal size in Pipedrive](https://salesbond.app/blog/average-deal-size-median-pipedrive/).

If two or more of these show up at once, the problem is data quality rather than velocity. [These CRM data quality metrics](https://salesbond.app/blog/crm-data-quality-metrics/) or a [Pipedrive audit](https://salesbond.app/blog/pipedrive-audit/) will tell you more than recalculating.

## How to increase sales velocity: pick one lever first

Say the same hypothetical team calculates velocity again a quarter later. Last quarter: 20 opportunities, $5,000 average, 40% win rate, 60 days, so $667 a day. This quarter: 24 opportunities, $5,000, 30%, 60 days. That comes to $600 a day, 10% lower.

A team that looks only at the headline says “we slowed down” and starts pushing for more deals. A team that looks at the inputs sees something else: opportunities went up by a fifth, and the win rate fell from 40% to 30%. More deals came in and fewer of them were the right deals, or the reps spread themselves thinner. Either way, the lever is win rate, and the first place to look is how deals get qualified at the top of the pipeline. Adding more opportunities would push the the same leak harder.

So compare the number with last period, then find which of the four inputs moved against you. The weakest input is where the week’s attention goes. There is no universal “good” velocity to aim for, because it depends on what you sell and how long buying takes; your own last quarter is the benchmark that means something.

When nothing has obviously broken and you simply want velocity higher, the arithmetic is less helpful than it looks. Move opportunities, deal value or win rate up by 10% and velocity rises to $733 a day; cut the cycle by 10%, to 54 days, and it reaches $741. Cycle length has a small edge because it is the divisor, but the math doesn’t pick your lever for you. What your team can actually change does.

Velocity also tells you nothing about whether there’s enough pipeline to hit the plan, [coverage ratio](https://salesbond.app/blog/pipeline-coverage-ratio/) answers that one, and a [weighted forecast](https://salesbond.app/blog/weighted-pipeline-forecast/) turns win rates into an expected number for the quarter.

## Calculate it the same day each month

A velocity number you calculate once is decoration. It goes into a board slide, looks precise, and nobody can say whether it’s good. The value is in the series, which means the same definitions, the same filters and the same day every month, say the first working day, over the same trailing window. We’d use the last full quarter rather than the last month, because a small team closes few enough deals that a single month can swing the win rate on one or two outcomes.

Keep the four inputs next to the result every time you report it. Velocity alone can fall for opposite reasons, and a manager who sees only the total can’t tell a qualification problem from a slow month of prospecting. It is a lagging measure; the inputs that feed it, especially new opportunities, move earlier, which is why it belongs alongside [leading metrics](https://salesbond.app/blog/leading-vs-lagging-sales-metrics/) and not instead of them.

At the monthly meeting, that comes down to one sentence: “Velocity is $600 a day, down from $667. Opportunities are up, win rate is down, so this month we’re looking at qualification.”

## What a team of five can move in a quarter

Our view: in one quarter, a small team can realistically move the win rate and the cycle length, because both respond to how reps work deals they already have. Qualifying out poor-fit deals earlier and keeping a clear next step on every open deal are habits, and habits can change in twelve weeks. Average deal value tends to follow pricing and packaging decisions, and opportunity volume follows marketing and hiring, which take longer to show up in closed deals. So pick one of the first two, agree on the definition, and check the same four inputs on the same day next month. If you sell subscriptions, see [how SaaS metrics read differently](https://salesbond.app/blog/saas-sales/).