Measure Pipeline Velocity by Segment and the Create Volume Remaining Quota Needs
The problem
Open pipeline is counted in dollars of coverage, but nobody measures how fast each segment actually turns opportunities into bookings, so a long-cycle enterprise book can look covered while it cannot produce the remaining quota in the days left, and a cycle that stretched by two weeks never shows up as a dollars-per-day problem.
Run it in your LLM
One prompt for Claude or ChatGPT that turns an opportunity export into the number a CRO asks for in week 8: how fast each segment actually produces bookings, and whether that engine covers remaining quota in the days left. Type run the example after pasting it to test it on the fictional data built into the prompt.
# Pipeline Velocity by Segment
You are a RevOps and FP&A lead reporting to the CRO. From a CRM export of open opportunities plus closed-won and closed-lost deals, measure how fast each segment turns pipeline into bookings (dollars per day), whether that engine covers remaining quota in the days left, how many more open opportunities would close the gap, and what shortening the cycle is worth, with every number traceable to the export.
## Rules
- Use only the data in this conversation. Do not invent deals, win rates, cycle lengths, or industry benchmarks. If something is missing, ask for it, or use the fallback this prompt defines and label it as an assumption.
- Run the calculations in code if you can. If you cannot run code, say so at the top and show the working by segment.
- Show the formula next to every headline number.
- Win rate, ACV, and cycle days come from this team's closed history, not from a rule of thumb. Remaining quota and days left come from the user.
- Read only. Do not change anything in the CRM. Report what the numbers imply and leave the hiring, sourcing, and stage-coaching decisions to the user.
- Format: money to the nearest dollar, rates with one decimal, days as whole numbers unless the median is a half day.
## Step 0. Inputs
If the user says "run the example", use the EXAMPLE DATA section at the end of this prompt, do not ask any questions, and label every output "Example data (fictional)".
Otherwise ask for everything below in one message, skipping anything the user already gave:
1. A CSV of opportunities, one row per deal, with these columns (ask the user to map theirs):
- deal_id, segment, amount, created_date (YYYY-MM-DD), close_date (YYYY-MM-DD, blank when open), status (open, won, or lost)
Where to get it: CRM opportunities, including open deals with no close date and closed deals for the lookback period.
2. Remaining quota for the period (quota minus closed won to date).
3. Days left in the period, including today.
4. The closed lookback: by default the last two quarters of close dates (an assumption you can change).
5. Days of cycle the user wants to test cutting, by default 0; suggest rerunning at 10 days as a planning case.
Then report a data check: rows read; rows left out and why (duplicate deal ID, no created date, no amount, closed outside the period, close date before created date, status not open/won/lost); open, won, and lost counts kept. Ask the user to confirm before going on, unless they said "run the example".
## Step 1. History by segment
For each segment, from won and lost deals in the lookback:
- ACV = average won amount (won dollars / won deals).
- Win rate = won dollars / (won dollars + lost dollars). Dollar-weighted, not deal-weighted. Show both the dollar rate and the deal count.
- Cycle days = median of (close date - created date) on won deals, in whole days. If you also have stage-entered dates, report median days in each stage and say whether they add up close to this cycle; the longest stage is the one a cut would most likely have to come from. If you do not have stage dates, say so and use created-to-close only.
- Open opportunities = count of open deals (not their face-value pipeline). Pipeline velocity uses the count times historical ACV, because open amounts can be padded. Show open pipeline dollars next to the count so the user can see the difference.
Skip a segment for velocity when it has no open deals, no won deals (so no ACV or cycle), or no decided dollars (so no win rate). List those segments and why.
## Step 2. Velocity
Pipeline velocity, dollars per day, for each segment:
V = (open opportunities x ACV x win rate) / cycle days
That is expected won dollars per day if today's open book turns at this segment's own history. Sum the segments for the team.
Required velocity = remaining quota / days left.
Gap per day = required - V. Gap dollars = gap per day x days left. A negative gap is a surplus.
Contribution of one more open opportunity in a segment = ACV x win rate / cycle days. Extra open opportunities to close a positive gap = gap per day / the highest contribution among segments, rounded up. Say which segment that is, and that putting every extra deal into one segment is a sizing device, not a sourcing plan.
## Step 3. Cycle cut
Rerun V with every segment's cycle reduced by the days the user chose to cut (skip a segment whose cycle would drop to 0 or below). New gap = required - V after the cut. The dollars the cut is worth this period = (V after - V before) x days left. Do not claim the team can actually cut that many days; that is a process question.
## Step 4. Output
Start with a five-line summary:
- Headline: "Team velocity {V}/day against {required}/day required; {gap} per day, {gap dollars} over the days left."
- Where it sits: each segment's V, cycle, and win rate, without ranking people.
- Extra opportunities: the count at the fastest segment's contribution, labeled as a sizing device.
- Cycle cut: V and the gap after the cut, and what that is worth in this period.
- One line: "Period {start} to {end} for closed history; {excluded} rows left out; remaining quota {quota}; {days} days left."
Then these tables:
1. Data check
2. By segment (open opps, open pipeline, won, lost, ACV, win rate, cycle days, V per day, contribution per extra opp)
3. Team velocity vs required, extra opps, cycle-cut case
4. Assumptions, each labeled as an assumption, including: count x historical ACV rather than open pipeline face value; win rate dollar-weighted on this lookback; median cycle; a cycle cut is a what-if, not a forecast; extra opps in the fastest segment is a sizing device; history is not a forecast.
If you can create files, offer the segment table as a CSV download.
## EXAMPLE DATA (fictional, for testing this prompt)
Use this only when the user says "run the example". The company, segments, and deals are made up.
- Remaining quota $900,000, 45 days left, cycle cut 10 days (all example inputs)
- Closed lookback: 2025-10-01 to 2026-03-31
```csv
deal_id,segment,amount,created_date,close_date,status
W-E1,Enterprise,50000,2025-08-12,2025-10-21,won
W-E2,Enterprise,50000,2025-09-01,2025-11-20,won
W-E3,Enterprise,50000,2025-09-15,2025-12-04,won
W-E4,Enterprise,50000,2025-10-01,2025-12-30,won
L-E1,Enterprise,100000,2025-07-01,2025-11-01,lost
L-E2,Enterprise,100000,2025-07-15,2025-11-20,lost
L-E3,Enterprise,100000,2025-08-01,2025-12-10,lost
L-E4,Enterprise,100000,2025-08-20,2026-01-15,lost
L-E5,Enterprise,100000,2025-09-10,2026-02-01,lost
L-E6,Enterprise,100000,2025-10-05,2026-02-20,lost
W-M1,Mid-market,18000,2025-10-12,2025-11-11,won
W-M2,Mid-market,18000,2025-10-20,2025-11-24,won
W-M3,Mid-market,18000,2025-11-01,2025-12-11,won
W-M4,Mid-market,18000,2025-11-10,2025-12-20,won
W-M5,Mid-market,18000,2025-12-01,2026-01-15,won
W-M6,Mid-market,18000,2025-12-10,2026-01-29,won
L-M1,Mid-market,36000,2025-10-01,2025-11-20,lost
L-M2,Mid-market,36000,2025-10-15,2025-12-01,lost
L-M3,Mid-market,36000,2025-11-01,2025-12-20,lost
L-M4,Mid-market,36000,2025-11-15,2026-01-10,lost
L-M5,Mid-market,36000,2025-12-01,2026-01-25,lost
L-M6,Mid-market,36000,2025-12-10,2026-02-05,lost
L-M7,Mid-market,36000,2026-01-05,2026-02-20,lost
W-S1,SMB,6000,2025-11-01,2025-11-15,won
W-S2,SMB,6000,2025-11-10,2025-11-26,won
W-S3,SMB,6000,2025-11-20,2025-12-08,won
W-S4,SMB,6000,2025-12-01,2025-12-21,won
W-S5,SMB,6000,2025-12-10,2025-12-30,won
W-S6,SMB,6000,2026-01-05,2026-01-27,won
W-S7,SMB,6000,2026-01-12,2026-02-05,won
W-S8,SMB,6000,2026-01-20,2026-02-15,won
L-S1,SMB,9000,2025-11-05,2025-11-25,lost
L-S2,SMB,9000,2025-11-15,2025-12-05,lost
L-S3,SMB,9000,2025-12-01,2025-12-20,lost
L-S4,SMB,9000,2025-12-10,2026-01-05,lost
L-S5,SMB,9000,2026-01-05,2026-01-25,lost
L-S6,SMB,9000,2026-01-12,2026-02-01,lost
L-S7,SMB,9000,2026-01-20,2026-02-10,lost
L-S8,SMB,9000,2026-02-01,2026-02-22,lost
O-E1,Enterprise,50000,2026-01-15,,open
O-E2,Enterprise,50000,2026-01-15,,open
O-E3,Enterprise,50000,2026-01-15,,open
O-E4,Enterprise,50000,2026-01-15,,open
O-E5,Enterprise,50000,2026-01-15,,open
O-E6,Enterprise,50000,2026-01-15,,open
O-E7,Enterprise,50000,2026-01-15,,open
O-E8,Enterprise,50000,2026-01-15,,open
O-E9,Enterprise,50000,2026-01-15,,open
O-E10,Enterprise,50000,2026-01-15,,open
O-E11,Enterprise,50000,2026-01-15,,open
O-E12,Enterprise,50000,2026-01-15,,open
O-E13,Enterprise,50000,2026-01-15,,open
O-E14,Enterprise,50000,2026-01-15,,open
O-E15,Enterprise,50000,2026-01-15,,open
O-E16,Enterprise,50000,2026-01-15,,open
O-E17,Enterprise,50000,2026-01-15,,open
O-E18,Enterprise,50000,2026-01-15,,open
O-E19,Enterprise,50000,2026-01-15,,open
O-E20,Enterprise,50000,2026-01-15,,open
O-E21,Enterprise,50000,2026-01-15,,open
O-E22,Enterprise,50000,2026-01-15,,open
O-E23,Enterprise,50000,2026-01-15,,open
O-E24,Enterprise,50000,2026-01-15,,open
O-M1,Mid-market,18000,2026-02-01,,open
O-M2,Mid-market,18000,2026-02-01,,open
O-M3,Mid-market,18000,2026-02-01,,open
O-M4,Mid-market,18000,2026-02-01,,open
O-M5,Mid-market,18000,2026-02-01,,open
O-M6,Mid-market,18000,2026-02-01,,open
O-M7,Mid-market,18000,2026-02-01,,open
O-M8,Mid-market,18000,2026-02-01,,open
O-M9,Mid-market,18000,2026-02-01,,open
O-M10,Mid-market,18000,2026-02-01,,open
O-M11,Mid-market,18000,2026-02-01,,open
O-M12,Mid-market,18000,2026-02-01,,open
O-M13,Mid-market,18000,2026-02-01,,open
O-M14,Mid-market,18000,2026-02-01,,open
O-M15,Mid-market,18000,2026-02-01,,open
O-M16,Mid-market,18000,2026-02-01,,open
O-M17,Mid-market,18000,2026-02-01,,open
O-M18,Mid-market,18000,2026-02-01,,open
O-M19,Mid-market,18000,2026-02-01,,open
O-M20,Mid-market,18000,2026-02-01,,open
O-M21,Mid-market,18000,2026-02-01,,open
O-M22,Mid-market,18000,2026-02-01,,open
O-M23,Mid-market,18000,2026-02-01,,open
O-M24,Mid-market,18000,2026-02-01,,open
O-M25,Mid-market,18000,2026-02-01,,open
O-M26,Mid-market,18000,2026-02-01,,open
O-M27,Mid-market,18000,2026-02-01,,open
O-M28,Mid-market,18000,2026-02-01,,open
O-M29,Mid-market,18000,2026-02-01,,open
O-M30,Mid-market,18000,2026-02-01,,open
O-M31,Mid-market,18000,2026-02-01,,open
O-M32,Mid-market,18000,2026-02-01,,open
O-M33,Mid-market,18000,2026-02-01,,open
O-M34,Mid-market,18000,2026-02-01,,open
O-M35,Mid-market,18000,2026-02-01,,open
O-M36,Mid-market,18000,2026-02-01,,open
O-M37,Mid-market,18000,2026-02-01,,open
O-M38,Mid-market,18000,2026-02-01,,open
O-M39,Mid-market,18000,2026-02-01,,open
O-M40,Mid-market,18000,2026-02-01,,open
O-M41,Mid-market,18000,2026-02-01,,open
O-M42,Mid-market,18000,2026-02-01,,open
O-M43,Mid-market,18000,2026-02-01,,open
O-M44,Mid-market,18000,2026-02-01,,open
O-M45,Mid-market,18000,2026-02-01,,open
O-M46,Mid-market,18000,2026-02-01,,open
O-M47,Mid-market,18000,2026-02-01,,open
O-M48,Mid-market,18000,2026-02-01,,open
O-M49,Mid-market,18000,2026-02-01,,open
O-M50,Mid-market,18000,2026-02-01,,open
O-S1,SMB,6000,2026-02-20,,open
O-S2,SMB,6000,2026-02-20,,open
O-S3,SMB,6000,2026-02-20,,open
O-S4,SMB,6000,2026-02-20,,open
O-S5,SMB,6000,2026-02-20,,open
O-S6,SMB,6000,2026-02-20,,open
O-S7,SMB,6000,2026-02-20,,open
O-S8,SMB,6000,2026-02-20,,open
O-S9,SMB,6000,2026-02-20,,open
O-S10,SMB,6000,2026-02-20,,open
O-S11,SMB,6000,2026-02-20,,open
O-S12,SMB,6000,2026-02-20,,open
O-S13,SMB,6000,2026-02-20,,open
O-S14,SMB,6000,2026-02-20,,open
O-S15,SMB,6000,2026-02-20,,open
O-S16,SMB,6000,2026-02-20,,open
O-S17,SMB,6000,2026-02-20,,open
O-S18,SMB,6000,2026-02-20,,open
O-S19,SMB,6000,2026-02-20,,open
O-S20,SMB,6000,2026-02-20,,open
O-S21,SMB,6000,2026-02-20,,open
O-S22,SMB,6000,2026-02-20,,open
O-S23,SMB,6000,2026-02-20,,open
O-S24,SMB,6000,2026-02-20,,open
O-S25,SMB,6000,2026-02-20,,open
O-S26,SMB,6000,2026-02-20,,open
O-S27,SMB,6000,2026-02-20,,open
O-S28,SMB,6000,2026-02-20,,open
O-S29,SMB,6000,2026-02-20,,open
O-S30,SMB,6000,2026-02-20,,open
O-S31,SMB,6000,2026-02-20,,open
O-S32,SMB,6000,2026-02-20,,open
O-S33,SMB,6000,2026-02-20,,open
O-S34,SMB,6000,2026-02-20,,open
O-S35,SMB,6000,2026-02-20,,open
O-S36,SMB,6000,2026-02-20,,open
O-S37,SMB,6000,2026-02-20,,open
O-S38,SMB,6000,2026-02-20,,open
O-S39,SMB,6000,2026-02-20,,open
O-S40,SMB,6000,2026-02-20,,open
O-E1,Enterprise,50000,2026-01-15,,open
B-01,Enterprise,80000,2025-01-01,2025-04-01,won
B-02,SMB,,2026-02-01,,open
B-03,Mid-market,18000,2026-02-01,,stalled
```
How to run it
- Open Claude or ChatGPT with code execution on (Claude's analysis tool, ChatGPT data analysis). Without it the model does arithmetic by hand, and you should check every number.
- Paste the prompt. To test it first, send "run the example" and compare with the expected results below.
- Attach a CSV of opportunities with deal ID, segment, amount, created date, close date, and status (open, won, or lost), and give the prompt remaining quota and days left. The prompt lists the columns and where to find them.
- Read the data check first, then take team velocity vs required velocity to the weekly pipeline meeting. Extra open opportunities are a sizing device, not a sourcing plan.
Before you paste pipeline data
Open pipeline and win rates by segment are commercially sensitive. Check your company's AI and data policy, prefer a business or enterprise plan, and drop account names and contacts: the prompt only needs deal IDs, segments, dates, amounts, and status. It reads the export and changes nothing in your CRM.
Expected results on the example data
A correct run of "run the example" should match these, give or take rounding. They are computed from the prompt's definitions by a reference implementation that is tested against hand-worked numbers. The data is fictional.
- Data check
- 157 rows; left out: O-E1 (duplicate deal ID), B-01 (closed outside the period), B-02 (no amount), B-03 (status is not open, won, or lost)
- Team velocity
- Enterprise $3,750/day; Mid-market $6,750/day; SMB $4,800/day; total $15,300/day
- Required vs gap
- $20,000/day required; gap $4,700/day, $211,500 over 45 days
- Extra open opportunities
- 31 Enterprise opportunities (30.1 before rounding up)
- After a 10-day cycle cut
- $22,886/day, surplus $2,886/day
| Segment | Open opps | ACV | Win rate | Cycle days | Velocity / day | $/day per extra opp |
|---|---|---|---|---|---|---|
| Enterprise | 24 | $50,000 | 25.0% | 80 | $3,750 | $156 |
| Mid-market | 50 | $18,000 | 30.0% | 40 | $6,750 | $135 |
| SMB | 40 | $6,000 | 40.0% | 20 | $4,800 | $120 |
Coverage in dollars can hide a clock problem: the open book turns at $15,300/day and remaining quota needs $20,000/day, a $211,500 hole over 45 days. Sizing that hole at Enterprise economics is 31 extra open opportunities. Cutting 10 days off every cycle flips the gap to a surplus; whether those days can actually come out is a process question, not a forecast.
Pipeline velocity vs remaining quota
Enter remaining quota, days left, and each segment's open opportunities, average won deal size, win rate, and median cycle days. Velocity = (open opps x ACV x win rate) / cycle days. Prefilled with the fictional example.
Open book and history by segment
- Team velocity
- $15,300/day
- Sum of each segment's open opps x ACV x win rate / cycle days
- Required velocity
- $20,000/day
- $900,000 / 45 days left
- Gap per day
- $4,700/day
- $211,500 over the days left
- Extra Enterprise open opps
- 31
- 30.1 at $156/day each, rounded up. Sizing device, not a sourcing plan.
- Velocity after a 10-day cycle cut
- $22,886/day
- Surplus $2,886/day
- What the cut is worth this period
- $341,357
- (velocity after - velocity now) x days left
| Segment | Open opps | Expected $/opp | $/day per opp | Velocity / day |
|---|---|---|---|---|
| Enterprise | 24 | $12,500 | $156/day | $3,750/day |
| Mid-market | 50 | $5,400 | $135/day | $6,750/day |
| SMB | 40 | $2,400 | $120/day | $4,800/day |
Velocity uses the count of open opportunities times historical ACV, not the face value of open pipeline, because open amounts can be padded. Extra opportunities are sized on the segment with the highest dollars per day per opportunity; that is a sizing device, not a plan to source only that segment. A cycle cut is a what-if, not a forecast of how many days you can actually take out.
Implementation steps
- 1
Write the definitions down before pulling data: pipeline velocity = (open opportunities x average won deal size x win rate) / cycle days, in dollars per day; required velocity = remaining quota / days left; cycle days = median of close date minus created date on won deals in the lookback; win rate = won dollars / (won + lost dollars) in the same lookback, dollar-weighted. Use the count of open opportunities times historical ACV, not the face value of open pipeline, because open amounts can be padded
- 2
Export open opportunities plus closed-won and closed-lost deals for the last two quarters (an assumption you can change) with deal ID, segment, amount, created date, close date, and status. Drop duplicates, deals with no created date or amount, closed deals outside the lookback, close dates before created dates, and statuses that are not open, won, or lost, and list each dropped row
- 3
For each segment compute ACV, dollar-weighted win rate, median cycle days, and the open opportunity count. If you have stage-entered dates, report median days in each stage next to the cycle and say whether they add up close to it; the longest stage is where a cycle cut would have to come from. Skip a segment for velocity when it has no open deals, no won deals, or no decided dollars, and say why
- 4
Compute velocity per segment and the team total, required velocity from remaining quota and days left, and the gap per day. A negative gap is a surplus. Extra open opportunities to close a positive gap = gap per day / the highest dollars-per-day contribution of one more opportunity among segments, rounded up, and labeled as a sizing device rather than a sourcing plan
- 5
Rerun velocity with every segment's cycle cut by a number of days the CRO is willing to test (10 days in the fictional example, an input, not a benchmark). The dollars the cut is worth this period = (velocity after - velocity now) x days left. Do not claim the team can actually take those days out
- 6
Take the gap and the extra-opportunity line to the weekly pipeline meeting before new sourcing targets go out: a segment that is slow in dollars per day needs either more opportunities created inside its own cycle window, a real cycle cut, or an honest cut to the commit, not more coverage on the same clock
- 7
Run it with the copy-paste prompt on this page in Claude or ChatGPT, or with formulas in the template, check the open counts against the CRM, and use the calculator on this page to test other remaining quotas, days left, and cycle cuts
- 8
Rerun every week as days left shrinks, and after each quarter closes refresh ACV, win rate, and cycle so the velocity uses current history
Template outline
The structure to recreate in your own workspace. Field names and thresholds are starting points.
Google Sheet: Pipeline velocity FYxx (RevOps owns it)
Tab inputs: remaining_quota, days_left, lookback_start, lookback_end, cycle_cut_days (default 0; example uses 10)
Tab deals (one row per opportunity): deal_id, segment, amount, created_date, close_date, status (open, won, lost)
won_in_lookback = status = "won" AND close_date in lookback AND not a duplicate
cycle_days = close_date - created_date on won_in_lookback
win_rate = SUMIFS(amount, won) / (SUMIFS(won) + SUMIFS(lost))
acv = AVERAGEIFS(amount, won)
open_opps = COUNTIFS(status, "open")
Tab by_segment:
V = open_opps x acv x win_rate / cycle_days
contribution = acv x win_rate / cycle_days
V_after_cut = open_opps x acv x win_rate / (cycle_days - cycle_cut_days)
Tab team:
required = remaining_quota / days_left
gap = required - SUM(V)
extra_opps = IF(gap > 0, CEILING(gap / MAX(contribution)), 0)
cut_worth = (SUM(V_after_cut) - SUM(V)) x days_left
Worked example (example data, fictional): remaining quota $900,000, 45 days left, 10-day cycle cut
159 rows read. Left out: O-E1 listed twice; B-01 closed 2025-04-01, before the lookback;
B-02 has no amount; B-03 status "stalled".
Enterprise: 4 won x $50,000 = $200,000, 6 lost x $100,000 = $600,000, win rate 25%,
days 70, 80, 80, 90 median 80, 24 open
V = 24 x $50,000 x 25% / 80 = $3,750/day; contribution $156.25/day per extra opp
Mid-market: 6 won x $18,000 = $108,000, 7 lost x $36,000 = $252,000, win rate 30%,
days 30, 35, 40, 40, 45, 50 median 40, 50 open
V = 50 x $18,000 x 30% / 40 = $6,750/day; contribution $135/day
SMB: 8 won x $6,000 = $48,000, 8 lost x $9,000 = $72,000, win rate 40%,
days 14, 16, 18, 20, 20, 22, 24, 26 median 20, 40 open
V = 40 x $6,000 x 40% / 20 = $4,800/day; contribution $120/day
Team V $15,300/day; required $900,000 / 45 = $20,000/day; gap $4,700/day x 45 = $211,500
Extra open opps at Enterprise $156.25/day: 4,700 / 156.25 = 30.08, round up 31
After a 10-day cut: Enterprise $4,286/day, Mid-market $9,000, SMB $9,600, team $22,886/day,
surplus $2,886/day; the cut is worth ($22,886 - $15,300) x 45 = $341,357 this period
Slack to #revenue-leadership before the weekly pipeline meeting:
"Velocity check: {{velocity}}/day against {{required}}/day required, {{gap}}/day
({{gap_dollars}} over {{days_left}} days). Extra open opps to close it at {{fastest_segment}}
economics: {{extra_opps}}. A {{cut}}-day cycle cut would move velocity to {{velocity_after}}.
Sheet: {{sheet_url}}"
Tab history: week, days left, team V, required, gap, extra opps, V after cutCost, time saved, and break-even
Tool cost here is your share of an LLM plan, which depends on your vendor, so it is an input. Every number below is an example input; replace each with your own figure.
Inputs (all assumptions)
Replace each value with your own figure.
- THours a quarter to measure pipeline velocity by hand (weekly export of open and closed deals, clean them, compute ACV, win rate, and cycle by segment, compare with remaining quota, write it up)6AssumptionTime the next quarter of weekly pipeline reviews.
- VHours a quarter with the prompt or template (export, review the data check and the results)1AssumptionTime the first two weekly runs and multiply by 13.
- RLoaded hourly cost of the RevOps analyst$75AssumptionSalary plus benefits, divided by working hours.
- KMonthly tool cost for the LLM plan$20AssumptionYour share of the Claude or ChatGPT plan, from current vendor pricing and your invoices; the CRM, Google Sheets, and Slack are usually already paid for.
Formulas
- Time saved per quarter
T - V - 6 - 1 = 5 hours
- Time saved per week
(T - V) / 13 - 5 / 13 = 0.4 hours
- Value of time saved per quarter
(T - V) x R - 5 x $75 = $375
- Tool cost per quarter
K x 3 - $20 x 3 = $60
- Break-even hours per quarter
K x 3 / R - $60 / $75 = 0.8 hours, so the run covers its tool cost once it saves 48 minutes a quarter
- Gap this period (fictional example data)
remaining quota / days left - sum of (open opps x ACV x win rate / cycle days) - $20,000/day required - $15,300/day velocity = $4,700/day, $211,500 over 45 days
- The time math counts analyst time only. Closing the $211,500 gap depends on sourcing, cycle time, and the commit, so it is not added to the time savings.
- History is not a forecast: a mix shift, a new segment, or a pricing change can move ACV, win rate, and cycle. Recheck them when the quarter closes.
- Rerun the time math after the first two weeks with your real review time V.
Common questions
- How do you calculate pipeline velocity?
- Pipeline velocity in dollars per day is (open opportunities x average won deal size x win rate) / median cycle days, using each segment's own history. In the fictional example Enterprise has 24 open opportunities, a $50,000 ACV, a 25% win rate, and an 80-day cycle, so 24 x $50,000 x 25% / 80 = $3,750/day.
- Why not use the face value of open pipeline?
- Open amounts can be padded, so the velocity formula uses the count of open opportunities times historical ACV. In the fictional example that is the same as face value because every open Enterprise deal is $50,000, but it will not be if reps inflate amounts. Show both numbers and act on the count x ACV one.
- How many more opportunities does remaining quota need?
- Divide the dollars-per-day gap by the highest contribution of one extra open opportunity among segments, then round up. In the fictional example the team is $4,700/day short and one more Enterprise opportunity is worth $156.25/day, so 4,700 / 156.25 = 30.08, which rounds up to 31. That sizes the hole; it is not a plan to source only Enterprise.
- How does a longer sales cycle change pipeline velocity?
- Cycle days sit in the denominator, so stretching the cycle lowers dollars per day even when open opportunity count stays the same. In the fictional example cutting 10 days off every cycle lifts team velocity from $15,300/day to $22,886/day and turns a $4,700/day gap into a surplus. Whether those days can actually come out is a process question this playbook does not answer.
- How is pipeline velocity different from pipeline coverage?
- Coverage asks whether the current book, at a win rate, is large enough for remaining quota. Velocity asks how fast that book turns, in dollars per day, which is what days left actually constrain. A 4x coverage ratio on an 80-day Enterprise cycle cannot produce the same throughput as 4x on a 20-day SMB cycle. Run both: coverage for the snapshot, velocity for the clock.
Keep going
Related playbooks
- RevOpsIntermediate
Measure Sales Cycle Length by Segment and Set When Pipeline Must Be Created
Most teams plan pipeline with one blended sales cycle, so segments that close in a month and segments that take half a year get the same creation deadline, and the long-cycle segment finds out in the last month of the quarter that the pipeline it needed should have existed a quarter earlier.
HubSpot or SalesforceGoogle SheetsClaude or ChatGPT+1Estimate: 0.4 hrs/week - RevOpsIntermediate
Stage-to-Stage Conversion Rates From Your CRM, by Cohort and Segment
Most pipeline plans use one conversion rate per stage, often from a dashboard that counts open deals as losses or from a number nobody can trace, so the stage where one segment loses its deals is hidden in the average, deals that stopped moving weeks ago stay in the forecast, and the pipeline target behind the bookings number cannot be checked.
HubSpot or SalesforceGoogle SheetsClaude or ChatGPT+1Estimate: 0.5 hrs/week - Finance/FP&AIntermediate
Check Pipeline Coverage with Historical Conversion, Not Rep Probability
Pipeline coverage is usually reported as open pipeline over quota, or weighted by the probability reps enter in the CRM, so a quarter can look covered at 3x while the deals, at the rates they have actually closed in the past, fall well short of the number, and finance finds out late in the quarter.
HubSpot or SalesforceGoogle SheetsZapier or n8n+1Estimate: 2 hrs/week - Finance/FP&AIntermediate
Check Whether Quota Is Realistic From the Distribution of Rep Attainment
Quota and headcount plans usually assume every ramped rep hits 100%, and the check afterwards is one average attainment number, so nobody sees that most reps landed below quota, that a few top performers carried the average, or that the plan needed more from the typical rep than the team has delivered.
HubSpot or SalesforceGoogle SheetsClaude or ChatGPT+1Estimate: 0.4 hrs/week
Need help implementing a playbook?
Our team builds custom Clay workflows and AI automations for revenue teams.
Get it built for you