Built for teams that measure sales velocity weekly

Sales velocity visible on the pipeline, not buried in a quarterly deck.

Sales velocity is the four-variable formula every RevOps team quotes in a QBR and almost nobody computes live in the CRM. Strkr runs the number on every pipeline view, segments by rep and segment and source, and shows which of the four inputs moved the needle this week. One Slack message instead of a Sunday-night spreadsheet.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

Pipedrive lists sales velocity in a report builder behind three menu layers. Salesforce computes it in a dashboard component that nobody opens between QBRs. HubSpot ships a formula calculator in Operations Hub Enterprise, which is the tier most buyers do not sit on. The result is the same every quarter at every revenue org: a VP of sales recites the four variables (number of opportunities, average deal size, win rate, sales cycle length) in a slide and nobody on the floor can tell you yesterday's number without pulling a report. Four symptoms show up on buyer calls. Velocity treated as a trailing report instead of a live operating metric. Variable-level attribution missing when the number drops. Rep-level segmentation only in the data warehouse, which Finance owns. And formula definitions that disagree between the pipeline view and the forecast call.

Velocity as a trailing report

Nobody checks the number between QBRs.

Classic CRM dashboards treat sales velocity as a slide artifact rather than a live operating metric. The QBR deck lands with a chart. The chart gets a nod. The team goes back to running the week on gut feel. Strkr renders velocity as a live header on the pipeline view, refreshed on every record change, so a sales manager can tell at 9 AM Tuesday whether the week is tracking against the trailing-30 baseline. The metric earns its keep by being visible every day.

Which variable moved

The number drops and nobody can say why.

Velocity dropped 14 percent this month. Was it win rate, cycle length, deal size, or opportunity count? Most tools give you the composite without the breakdown, so the diagnosis is a two-day RevOps project. Strkr decomposes velocity on the same card: four variables, week-over-week delta on each, click to drill into the records driving the swing. Diagnosis in five minutes.

Rep-level segmentation

The team metric hides the two reps dragging it down.

An org-wide velocity number smooths over the fact that two reps are running 60-day cycles while the top five run 28. The composite looks fine. Strkr segments velocity by rep, by segment, by lead source, by product, so the manager can spot the dispersion that the single number conceals. The two slow reps get coaching before quarter end instead of a surprise at the QBR.

Definition drift across surfaces

The pipeline view and the exec deck disagree on the formula.

A common pain pattern at a 50-rep org: the pipeline dashboard counts qualified opportunities, the exec deck counts stage-2-plus, the forecast call counts everything commit-and-above. Each produces a different velocity number. Strkr pins the velocity formula at the workspace level with an admin-visible config so every surface in the product computes the same way. One number, one definition, no drift.

Cycle length missing on half the deals

The CRM never captured when the deal actually opened.

Sales velocity depends on a clean cycle-length value, and cycle length depends on a clean deal-created-date and a clean deal-closed-date. Teams that imported from a legacy CRM or ran a lazy stage history miss these timestamps on 20 to 40 percent of deals, which quietly breaks the velocity math. Strkr enforces stage-history capture on write with a backfill helper for existing records, so the cycle-length denominator is actually computable.

Forecast vs velocity disconnect

The forecast says one thing, velocity math says another.

A forecast call commits 2.1 million and the velocity math predicts 1.6 million. One of the two numbers is wrong. Classic tools surface the forecast but not the velocity reconciliation, so the gap goes unexamined until the quarter closes short. Strkr runs a weekly velocity-vs-forecast reconciliation and surfaces the gap on the Friday forecast card, which is when a VP of sales can still do something about it.

How Strkr computes velocity

The four variables, live on every pipeline view.

The classic sales velocity formula multiplies opportunity count by average deal size by win rate, then divides by sales cycle length in days. The output is a dollar-per-day number that tells the team how fast money moves through the pipeline. Strkr renders this on every pipeline view and lets you decompose by any dimension the team cares about.

Live header on pipeline

Velocity number refreshes on every record change.

The pipeline view in Strkr carries a velocity header that recomputes on every opportunity write. A rep moves a deal to stage 3 and the number ticks up in real time. The visible-every-day quality is what makes velocity actually operational instead of a report artifact. Managers watching the dispersion get a signal when the number drifts outside the trailing-30 band.

Four-variable breakdown

Opportunity count, deal size, win rate, cycle length on one card.

Click the velocity header and the four inputs expand: current period value, trailing-30 baseline, week-over-week delta, which direction improved vs regressed. The card tells the manager within 60 seconds whether the velocity dip is a deal-size problem (deal mix shifted smaller), a win-rate problem (quality dropped), a cycle problem (deals stuck), or a count problem (top-of-funnel softer).

Rep-level dispersion

Who is 2x the median and who is half.

Strkr segments velocity by rep with a dispersion view that shows the median, the top quartile, the bottom quartile. The manager who sees the top rep running 3,400 dollars-per-day and the bottom rep running 900 can start the coaching conversation with specifics. The dispersion also feeds the quota-attainment projection on the forecast card.

Segment and source cuts

Enterprise velocity vs mid-market velocity vs SMB.

The composite number hides that enterprise deals move at 180-day cycles while SMB deals close in 21. Strkr lets a manager segment velocity by deal segment, lead source, product line, region. The result is four or five sub-numbers that each tell a different operating story, which is the level a VP of sales can actually act on.

Weekly forecast reconciliation

Velocity math meets the Friday commit.

Strkr reconciles the committed forecast against the velocity-implied number every Friday. When the two disagree by more than 15 percent the forecast card flags it for the VP of sales. The reconciliation closes the common gap between what managers commit on the Friday call and what the math actually supports.

Stage-friction detection

Which stage is where deals stall.

Cycle length is a composite of time-in-stage across every stage. Strkr breaks cycle time by stage so a RevOps lead can see that stage 3 (technical validation) averages 14 days when stage 4 (procurement) averages 42. The friction map tells the team which stage transition is the actual bottleneck, not just the overall cycle number.

Win-rate quality guard

The win-rate denominator excludes stage-0 noise.

Win rate math breaks when stage 0 (unqualified) deals get counted in the denominator, because the win rate drops to single digits and the velocity number collapses. Strkr lets the admin set a qualification floor (default stage 2) and the win-rate math respects it. Teams running MEDDIC can set the floor at MEDDIC-complete; teams running a simpler model can keep the default.

Historical replay

Velocity trend across every quarter back to go-live.

The historical view plots velocity week by week back to the first day of CRM data. The quarter-over-quarter chart highlights the seasonal pattern (Q4 ramps, January dips, back-to-school) so the manager comparing this week against last week has the right baseline. The replay is also the input to the capacity planning that Finance runs ahead of hiring cycles.

Alert on dispersion drift

When the gap between top and bottom widens, somebody gets a Slack ping.

Strkr watches the inter-quartile range on rep-level velocity and pings the sales manager when the IQR widens past a trailing baseline. A widening dispersion usually means two or three reps are losing the thread while the top performers compensate for the team. Catching it in week two is cheaper than catching it at QBR.

Which lever to pull

The playbook when velocity drops.

A velocity drop is diagnosable in four directions. Opportunity count dropped (top-of-funnel issue). Average deal size dropped (deal mix shifted smaller). Win rate dropped (qualification softened or competitive pressure spiked). Cycle length grew (deals stuck mid-funnel). The cards below are the operating responses Strkr customers run against each.

Opportunity count soft

Top-of-funnel is the lever.

When velocity drops because opportunity count softened, the response is marketing-ops, SDR activity, or outbound sequence throughput. Strkr surfaces the sources that fed opportunity count last period and flags which ones underdelivered this period. The manager fixes attribution first, then diagnoses the sources, then adjusts the SDR day-plan or the paid-media budget.

Average deal size shrinking

The mix moved toward smaller deals.

A shrinking average deal size usually means the deal mix shifted (more SMB, less enterprise) or discounting crept up on existing deals. Strkr tracks both and surfaces the one that moved. The manager either pulls levers on ICP targeting (push the SDR team toward enterprise) or tightens the discounting policy at the workflow level.

Win rate dropping

Qualification got lazy or a competitor got sharper.

Win rate drops have two usual causes: unqualified deals slipping into the forecast (fix at qualification criteria), or a specific competitor winning more deals (fix at competitive enablement). Strkr tags lost-deal reasons with a required dropdown so the data to diagnose is there. The weekly loss-reason summary feeds the Monday review.

Cycle length growing

Deals are stuck and nobody is pushing.

A growing cycle usually means deals are stalling in a specific stage. Strkr's stage-friction map tells the manager where. Common culprits: procurement delays (fix at MSA-template process), security review (fix with a pre-built security packet), executive sign-off missing (fix at MEDDIC champion criteria). The friction map tells you which fix matters.

Composite looks fine, dispersion widening

The team metric hides two reps in trouble.

When composite velocity holds steady but the rep-level dispersion widens, the top performers are compensating for the bottom. The manager intervenes before the top quits or the bottom gets fired. Strkr's dispersion alert catches this pattern before it shows up in the composite drop that triggers a QBR panic.

Velocity vs forecast gap

The commit disagrees with the math.

When the committed forecast exceeds velocity-implied revenue by more than 15 percent, the gap is usually optimism bias or a specific whale deal the manager is backing without the pipeline math to support it. Strkr flags the gap on the Friday forecast card and lets the VP of sales ask the right question (what gives) on the Monday call instead of discovering the gap at quarter close.

What the formula will not tell you

The honest limits of velocity as a metric.

Sales velocity is a useful operating metric but it is not a silver bullet. The limitations below show up in every mature RevOps shop, and they are the reason the metric should be one data point in a dashboard, not the single number the team manages against.

Backward-looking by nature

Velocity measures the past, not the future.

The formula computes against closed-deal history. A velocity number of 4,500 dollars-per-day tells you how the pipeline performed last period, not how it will perform next. For forward-looking pacing use Strkr's forecast module, which combines velocity-implied revenue with rep commits, deal-level AI risk flags, and seasonal baselines. Velocity feeds the forecast, it does not replace it.

Noisy on small samples

A 6-rep team gets choppy velocity week to week.

Small teams (6 reps and under) get velocity numbers that swing by 20 percent week to week because a single big deal moves the composite. Strkr suppresses the week-over-week alert threshold on small-team configurations and recommends trailing-30 or trailing-90 as the baseline instead of week-over-week. The number is still useful; the volatility threshold just has to match the sample size.

Hides product-mix changes

Average deal size blurs when the catalog shifts.

If the team launches a lower-ticket product in Q2, average deal size will drop and velocity will look like it fell even though the business is actually healthier. Strkr lets the admin segment velocity by product line, so the composite shift decomposes into "the new product is working" rather than "velocity is dying." Admins who skip this cut get misdiagnoses.

Does not capture customer health

Velocity treats a 90-day deal and a 30-day deal the same if they close.

A fast-closing deal that churns in 90 days contributes to velocity the same as a long-cycle deal that becomes a reference customer. Velocity is a sales-math metric, not a lifetime-value metric. Pair it with Strkr's customer-health scoring in the account module to see which closed deals were actually good deals.

Methodology-sensitive

MEDDIC teams and BANT teams compute different numbers.

A MEDDIC team setting the qualification floor at MEDDIC-complete gets a higher win rate (and higher velocity) than a BANT team counting from first discovery. Neither is wrong but they are not comparable across orgs. Strkr documents the methodology on the velocity card so a new VP of sales reading last quarter's number knows which qualification floor the number ran against.

Over-indexing drives bad behavior

Reps start closing fast cheap deals to pump the number.

If the comp plan or the Monday review optimizes against velocity alone, reps will chase short cycles and small deals because the math rewards both. Strkr lets managers pair velocity with ACV and gross-margin cuts so the composite view does not reward the wrong motion. Velocity is a diagnostic, not a KPI you should bonus against directly.

Head-to-head

Strkr vs Pipedrive on sales velocity specifically.

Pipedrive is the common comparison for teams that use sales velocity as a weekly operating metric. The vendor has shipped a velocity feature in their reporting module since 2019 and it is the most-cited competitor in buyer calls on this topic.

Feature Strkr Pipedrive (Professional + Insights add-on)
Live velocity on pipeline Header on every pipeline view, refreshes per record change Report builder, run on demand
Variable decomposition Four-variable breakdown on one card with deltas Multi-chart report, not a single card
Rep-level dispersion IQR view, alert when dispersion widens Rep report, no alerting layer
Segment and source cuts Any dimension including custom fields Fixed cuts in Insights, custom cuts via Pro plan report
Forecast reconciliation Weekly velocity-vs-commit gap on forecast card Not integrated between modules
Stage-friction map Time-in-stage by stage with friction heatmap Available in Insights, separate view
Historical replay Weekly velocity back to go-live, seasonal overlay Rolling 12 months in Insights
Admin-defined formula Workspace config pins the definition everywhere Report-level formula, drift risk across saved views
Qualification floor Admin sets the stage floor, win-rate math respects it Report filter, per-report
Price for the capability Included on every paid tier Insights add-on on Pro and above
How teams use Strkr

How velocity-literate teams run Strkr today.

The teams that get the most out of velocity treat the number as a weekly operating signal, not a quarterly reporting artifact. The playbooks below show how customers run the metric in Monday reviews, Friday forecast calls, and QBR prep.

Series C SaaS, 48 reps

Monday review opens with the velocity card.

A 48-rep SaaS team starts every Monday review by projecting the Strkr velocity card on the TV. The four-variable breakdown shows which input moved. The manager spends the first 10 minutes on the specific lever (cycle, win rate, deal size, count) instead of a round-robin "what are you working on" that ate 40 minutes of the old meeting. The review got sharper and 20 minutes shorter, which gave the manager time to actually coach a deal in the back half.

Mid-market B2B, 72 reps across 4 teams

Rep-dispersion alert surfaced a struggling pod before the manager noticed.

A 72-rep B2B org runs four pod structures with 18 reps per pod. The Strkr dispersion alert fired on pod 3 in week 6 of the quarter: the IQR on velocity widened past the trailing-30 baseline. The pod manager pulled rep-level data, found two reps running 70-day cycles against the team average of 32, and ran targeted stage-friction coaching for three weeks. The pod recovered by end of quarter instead of showing up as an underperformer at the QBR.

Enterprise B2B, 24 AE org

Velocity-vs-forecast gap caught a 400K miss three weeks early.

A 24-AE enterprise team committed 3.1 million on the Friday forecast call. Strkr's reconciliation flagged a 400K gap vs the velocity-implied number. The VP of sales dug into the stage-3-plus pipeline and found one AE had three deals he was commit-above on with no procurement engagement. The VP flagged the deals, pulled in a procurement-ops specialist, and recovered 280K of the 400K in the back three weeks instead of discovering the miss at close.

High-velocity SMB, 14 reps

Weekly stage-friction coaching replaced the Thursday pipeline call.

A 14-rep SMB team used to run a Thursday pipeline review that ate 90 minutes. They replaced it with a 20-minute conversation anchored on the Strkr stage-friction map: which stage transition is slow this week. The map pointed at stage 2-to-3 (demo-to-proposal) in weeks 3 and 4 of the quarter, so the manager ran a one-hour clinic on proposal mechanics. Average cycle dropped from 23 days to 19 over the next month without changing the comp plan.

Marketplace agency, 11 account executives

Average deal size segment cut diagnosed a mix shift in week two.

An 11-AE agency saw velocity drop 12 percent in month 2. The composite deal size shrank. Strkr's product-line segmentation showed the agency was closing more small retainer deals and fewer custom-build engagements. The sales manager redirected two reps to the custom-build pipeline the same week. Average deal size recovered inside the quarter and nobody had to call it a velocity emergency.

Make sales velocity a live operating metric instead of a quarterly chart.

Start a 14-day trial. Velocity renders on every pipeline view, decomposes the four inputs on one card, and reconciles weekly against the forecast. Watch the Monday review get sharper and the quarter-close surprise get smaller.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

What is the sales velocity formula and how does Strkr compute it?

Sales velocity equals opportunity count multiplied by average deal size multiplied by win rate, divided by sales cycle length in days. The output is a dollar-per-day number. Strkr computes it live on every pipeline view, with the four inputs pulled from the underlying deal records. Opportunity count is deals at or above a configurable qualification floor. Average deal size is the mean closed-won amount over the trailing period. Win rate is closed-won divided by closed-won plus closed-lost at the qualification floor. Cycle length is mean days from stage-floor entry to closed-won. The admin pins the definitions at the workspace level so every surface in Strkr computes the same number.

Can we segment velocity by rep, by segment, by lead source?

Yes, by any dimension including custom fields. The sales velocity view in Strkr lets you cut by rep, by segment (enterprise, mid-market, SMB), by lead source, by product line, by region, by any custom field defined on the deal object. The dispersion view shows the median, top quartile, bottom quartile for the chosen cut. Managers who diagnose with the segment cuts first instead of the composite number usually find the actual operating issue in minutes rather than days.

How does Strkr handle the velocity-vs-forecast gap?

Strkr reconciles committed forecast against velocity-implied revenue every Friday. When the two disagree by more than 15 percent the forecast card flags the gap for the VP of sales, with a drill-down into the specific deals contributing to the delta. The reconciliation is the piece most CRMs miss, because velocity lives in the reporting module and forecast lives in the forecast module and the two never meet on one surface. The gap signal has caught 7-figure forecast misses three weeks ahead of close in multiple customer deployments.

Does velocity work for teams with long enterprise cycles and teams with short SMB cycles in the same workspace?

Yes, with segmentation. A 180-day enterprise cycle and a 21-day SMB cycle produce very different velocity numbers, which is why the composite view hides more than it reveals in a mixed-segment business. The right posture is to segment velocity by deal segment and read the three sub-numbers separately. Strkr makes the segmentation one-click on the velocity card and lets a RevOps lead pin segment-specific baselines for alerting, so the trailing-30 band for enterprise does not false-alarm on a normal 180-day cycle while the SMB band stays sensitive to a 3-day slip.

How is this different from the velocity report in Pipedrive or the Breeze dashboard in HubSpot?

Three structural differences. First, velocity in Strkr is a live header on every pipeline view, not a report that someone runs on demand, which changes the metric from a trailing artifact to a daily operating signal. Second, Strkr decomposes the four variables on one card with week-over-week deltas, so a manager diagnoses the drop in 60 seconds instead of pulling four separate reports. Third, Strkr reconciles velocity against the forecast weekly, which catches commit-vs-math gaps before quarter close. Pipedrive's Insights velocity report and HubSpot's Operations Hub velocity component both compute the same formula; the difference is where the number lives in the workflow and whether it is wired to the forecast call.

What is the honest limit of sales velocity as a metric?

Three real limits. Velocity is backward-looking, so it tells you how last period performed, not how next period will perform. It is sample-size-sensitive, so a 6-rep team gets choppy week-over-week numbers that need a trailing-30 or trailing-90 baseline instead of a weekly alert. And it can drive bad behavior if the comp plan optimizes against the composite alone, because reps will chase short cycles and small deals to pump the number. Strkr handles the first by pairing velocity with the forecast module, the second by suppressing weekly alerts on small-team configurations, and the third by letting managers pair velocity with ACV and margin cuts in the same dashboard view. The metric is a strong diagnostic; it is not a KPI you should bonus against alone.

Also built for

Related audiences.

Sales Tracker For RevOps For VP of Sales Sales Intelligence Challenger Sales Methodology Strkr vs Pipedrive

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing