Work Back from a New-Logo Bookings Target to the Ramped SDRs You Need
The problem
Headcount plans start from "how many SDRs do we have" instead of the quarterly new-logo bookings target, so finance and sales argue about reqs without a shared funnel from ACV, win rate, show rate, and meetings booked per ramped SDR.
Run it in your LLM
One prompt for Claude or ChatGPT that turns a new-logo bookings target into the ramped SDR count a headcount review asks for: deals, SQOs, meetings booked, and the round-up, with ramping SDRs left on the ramp plan. Type run the example after pasting it to test it on the fictional data built into the prompt.
# SDR headcount from a new-logo pipeline target
You are a RevOps and finance lead reporting to the CRO and the CFO. From a quarterly new-logo bookings target, work backwards through ACV, SQO-to-won, meeting-held-to-SQO, show rate, and meetings booked per ramped SDR per month to the number of ramped SDRs the target needs, with every number traceable to the extract.
This count is ramped SDRs only. Ramping SDRs contribute partial capacity; do not convert them 1:1 here. Point the user at a ramp-capacity plan for that math.
## Rules
- Use only the data in this conversation. Do not invent win-rate, show-rate, or meetings-per-SDR 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.
- Show the formula next to every headline number.
- Round the SDR count up to a whole person. Show the unrounded figure next to it.
- The +5 point show-rate and win-rate levers are example input changes, not a forecast of a coaching or process program.
- Read only. Do not change CRM records, reqs, or quotas. Report what the numbers imply and leave the hiring decision to the user.
- Format: money to the nearest dollar, funnel counts to one decimal if not whole, SDRs unrounded to one decimal, rounded SDRs as a whole number.
## Definitions
- Bookings target is quarterly new-logo bookings, not expansion, not NRR, not a full-year number unless the user says so and you relabel the period.
- ACV is average contracted value of a new-logo win in the same currency as the target.
- SQO-to-won win rate is won new-logo deals / SQOs, in percent.
- Meeting-held-to-SQO is SQOs / meetings held, in percent.
- Show rate is meetings held / meetings booked, in percent.
- Meetings booked per ramped SDR per month is an input from the calendar or the SDR scorecard. Times 3 for a quarter.
- SDRs needed = meetings booked needed / (meetings per ramped SDR per month x 3), then round up.
- Do not divide by zero. If ACV, a rate, or meetings per SDR is 0 or missing, stop and say which input is unusable.
## 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 scenarios, one row per plan, with these columns (ask the user to map theirs):
- scenario (id, for example 2026-Q4), bookings_target, acv, win_rate_pct, meeting_to_sqo_pct, show_rate_pct, meetings_booked_per_sdr_per_month
Where to get it: finance or the CRO for the new-logo bookings target; CRM for ACV, SQO-to-won, and meeting-to-SQO; calendar or the SDR scorecard for show rate and meetings booked per ramped SDR. Rates are percents (25 means 25%).
2. Which scenario to score. Default: the last kept row.
Then report a data check: rows read; rows left out and why (duplicate scenario, no scenario id, inputs not numbers, a rate or ACV that cannot be used); scenarios kept. Ask the user to confirm before going on, unless they said "run the example".
## Step 1. Funnel
For the scored scenario:
- Deals needed = bookings target / ACV.
- SQOs needed = deals / (win_rate_pct / 100).
- Meetings held needed = SQOs / (meeting_to_sqo_pct / 100).
- Meetings booked needed = held / (show_rate_pct / 100).
- Meetings per ramped SDR per quarter = meetings_booked_per_sdr_per_month x 3.
- Unrounded SDRs = meetings booked / meetings per SDR per quarter.
- SDRs needed = round that up to a whole person.
## Step 2. Levers
Recompute the same funnel twice, each holding every other input fixed:
- Show rate +5 points (capped at 100).
- Win rate +5 points (capped at 100).
Report the new rounded SDR count and how many ramped SDRs that saves versus the base. Label both as example lifts, not as a forecast.
## Step 3. Output
Start with a five-line summary:
- Headline: "{sdrsNeeded} ramped SDRs for {target} new-logo bookings at {acv} ACV ({sdrsExact} before rounding up)."
- Funnel: "{deals} deals, {sqos} SQOs, {held} meetings held, {booked} meetings booked."
- Productivity: "{perMonth} meetings booked per ramped SDR per month x 3 = {perQuarter} per quarter."
- Levers: "+5 pts show rate -> {showSdrs} SDRs; +5 pts win rate -> {winSdrs} SDRs. Example lifts, not a forecast."
- One line: "Ramped SDRs only. Ramping SDRs count at partial capacity on the ramp-capacity plan. {excluded} rows were left out."
Then these tables:
1. Data check
2. Scored scenario (inputs, funnel, unrounded SDRs, rounded SDRs)
3. Levers (+5 show, +5 win)
4. Assumptions, each labeled as an assumption, including: rates are history not a forecast; 12 meetings a month in the example is an input not a benchmark; ramping SDRs are out of this count; rounding up is a staffing choice so you do not plan a fraction of a person.
If you can create files, offer the scored row as a CSV download.
## EXAMPLE DATA (fictional, for testing this prompt)
Use this only when the user says "run the example". The company and scenarios are made up.
- Score 2026-Q4
- Quarterly new-logo bookings target $1,200,000
- Average new-logo ACV $30,000
- SQO-to-won 25%, meeting-held-to-SQO 50%, show rate 80%
- 12 meetings booked per ramped SDR per month (example input, not a benchmark)
Scenarios:
```csv
scenario,bookings_target,acv,win_rate_pct,meeting_to_sqo_pct,show_rate_pct,meetings_booked_per_sdr_per_month
2026-Q3,900000,30000,22,45,75,10
2026-Q4,1200000,30000,25,50,80,12
2026-Q4,1200000,30000,25,50,80,12
BAD-1,1200000,0,25,50,80,12
,1200000,30000,25,50,80,12
```
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 scenarios with bookings target, ACV, win rate, meeting-to-SQO, show rate, and meetings booked per ramped SDR per month, and give the prompt which scenario to score. The prompt lists the columns.
- Read the data check first, then take the funnel and the rounded ramped-SDR count to the headcount review. Keep the +5 point levers labeled as example lifts.
Before you paste funnel data
Targets, win rates, and SDR productivity are commercially sensitive. Check your company's AI and data policy, prefer a business or enterprise plan, and drop names: the prompt only needs scenario ids and amounts. It reads the extract and changes nothing in the 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
- 5 rows; scored 2026-Q4; left out: 2026-Q4 (duplicate scenario), BAD-1 (Enter average new-logo ACV above zero.), (blank scenario) (no scenario id)
- Funnel
- $1,200,000 / $30,000 = 40 deals; 160 SQOs; 320 held; 400 booked
- Ramped SDRs
- 400 / 36 = 11.1, round up to 12
- Example levers
- +5 pts show (85%) -> 11 SDRs; +5 pts win (30%) -> 10 SDRs
| Scenario | Deals | SQOs | Held | Booked | Unrounded | SDRs |
|---|---|---|---|---|---|---|
| 2026-Q4 | 40 | 160 | 320 | 400 | 11.1 | 12 |
Q4 target $1,200,000 at $30,000 ACV is 40 deals, 160 SQOs, 320 meetings held, 400 meetings booked. 12 meetings per ramped SDR per month is 36 a quarter, 400 / 36 = 11.1, round up to 12 ramped SDRs. +5 pts show rate goes to 11; +5 pts win rate goes to 10. Those lifts are example input changes, not a forecast. Ramping SDRs are not in this count.
SDR headcount from a new-logo target
Work backwards from quarterly new-logo bookings to ramped SDRs. Rates and meetings per SDR are your inputs, not benchmarks. Prefilled with the fictional example.
- Deals needed
- 40
- $1,200,000 / $30,000
- SQOs needed
- 160
- 40 / 25% win rate
- Meetings held needed
- 320
- 160 / 50% meeting-to-SQO
- Meetings booked needed
- 400
- 320 / 80% show rate
- Meetings per ramped SDR per quarter
- 36
- 12 per month x 3
- Ramped SDRs needed
- 12
- 11.1 before rounding up. Ramped SDRs only.
Example levers, holding everything else fixed
+5 points is an example lift so you can see the SDR count move. It is not a forecast of a show-rate or win-rate program.
| Change | Meetings booked | SDRs | Vs base |
|---|---|---|---|
| Base (80% show, 25% win) | 400 | 12 | - |
| +5 pts show rate (85%) | 376.5 | 11 | 1 fewer |
| +5 pts win rate (30%) | 333.3 | 10 | 2 fewer |
New-logo bookings only. Ramping SDRs count at partial capacity on the ramp-capacity plan; this page does not convert them 1:1. Coverage of existing pipeline is a different question, on the pipeline coverage check. A headcount figure is not a forecast of what more SDRs would book.
Implementation steps
- 1
Write the definitions down with finance and the SDR leader before pulling data: the target is quarterly new-logo bookings, not expansion and not a full-year number; ACV is average new-logo contracted value; SQO-to-won, meeting-held-to-SQO, and show rate (booked to held) are percents; meetings booked per ramped SDR per month comes from the calendar or the scorecard. Ramping SDRs are out of this count; they contribute partial capacity on the ramp-capacity plan
- 2
Export last quarter's rates and productivity as the starting inputs, labeled as history, not as a forecast. Drop rows with a missing scenario id, duplicate scenarios, ACV of zero, or a rate of zero, and list each dropped row
- 3
Deals needed = bookings target / ACV. In the fictional example $1,200,000 / $30,000 = 40 deals. If ACV is a mix of segments, split the target by segment and add the SDR counts; a blended ACV hides the heavier segment
- 4
Work backwards: SQOs needed = deals / (win rate / 100); meetings held needed = SQOs / (meeting-held-to-SQO / 100); meetings booked needed = held / (show rate / 100). Do not divide by zero. In the fictional example 25% win, 50% meeting-to-SQO, and 80% show rate give 160 SQOs, 320 meetings held, and 400 meetings booked
- 5
Meetings booked per ramped SDR per quarter = monthly meetings x 3. SDRs needed = meetings booked / that number, then round up to a whole person so you do not plan a fraction of a head. In the fictional example 12 meetings a month (an example input, not a benchmark) is 36 a quarter, 400 / 36 = 11.1, round up to 12 ramped SDRs
- 6
Recompute two example levers, holding everything else fixed: show rate +5 points, and win rate +5 points. Those lifts are sizing devices, not a forecast of a coaching program. Compare the rounded SDR counts. Keep pipeline coverage of already-created deals on the coverage playbook; this page is the outbound engine to create the meetings
- 7
Run it with the copy-paste prompt on this page in Claude or ChatGPT, or with formulas in the template, and use the calculator on this page to test other targets and rates. Share the funnel and the rounded ramped-SDR count with finance; this is a staffing size, not a req-open date and not a bookings forecast
- 8
Rerun each quarter on the same definitions and store the six inputs so a mix shift, a show-rate drop, or a target change shows up before the next headcount review
Template outline
The structure to recreate in your own workspace. Field names and thresholds are starting points.
Google Sheet: SDR headcount from new-logo target FYxx (RevOps owns the funnel; finance owns the target)
Tab inputs: score_scenario
Tab scenarios (one row per plan):
scenario, bookings_target, acv, win_rate_pct, meeting_to_sqo_pct, show_rate_pct, meetings_booked_per_sdr_per_month
kept = unique scenario AND all fields are numbers AND acv > 0 AND every rate is in (0, 100] AND meetings per SDR > 0
Tab funnel:
deals = bookings_target / acv
sqos = deals / (win_rate_pct / 100)
held = sqos / (meeting_to_sqo_pct / 100)
booked = held / (show_rate_pct / 100)
per_quarter = meetings_booked_per_sdr_per_month * 3
sdrs_exact = booked / per_quarter
sdrs_needed = CEILING(sdrs_exact)
Tab levers (same formulas, one input changed):
show_plus_5 = MIN(100, show_rate_pct + 5)
win_plus_5 = MIN(100, win_rate_pct + 5)
Worked example (example data, fictional): score 2026-Q4
5 rows read, 2 kept (Q3 and Q4). Left out: 2026-Q4 listed twice; BAD-1 ACV 0; blank scenario.
Target $1,200,000 / ACV $30,000 = 40 deals.
Win 25% -> 160 SQOs. Meeting-to-SQO 50% -> 320 meetings held. Show 80% -> 400 meetings booked.
12 meetings booked per ramped SDR per month x 3 = 36 per quarter.
400 / 36 = 11.1, round up to 12 ramped SDRs.
+5 pts show (85%): 11 ramped SDRs. +5 pts win (30%): 10 ramped SDRs. Example lifts, not a forecast.
Calculator on this page, prefilled: target $1,200,000, ACV $30,000, win 25%, meeting-to-SQO 50%, show 80%, 12 meetings per month. Every money line above matches.
Slack to #sales-leadership before the headcount review:
"Ramped SDRs for {{scenario}}: {{sdrs}} for {{target}} new-logo bookings ({{exact}} before rounding up).
Funnel {{deals}} deals, {{sqos}} SQOs, {{held}} held, {{booked}} booked.
+5 pts show -> {{show_sdrs}}; +5 pts win -> {{win_sdrs}}. Ramping SDRs are on the ramp plan. Sheet: {{sheet_url}}"
Tab history: scenario, target, acv, win, to_sqo, show, meetings_per_month, sdrs_neededCost, 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. Hours saved are estimates, not measured results.
Inputs (all assumptions)
Replace each value with your own figure.
- THours a quarter to pull new-logo target, ACV, funnel rates, and meetings per SDR and size headcount by hand5AssumptionTime the next quarterly SDR headcount review.
- VHours a quarter with the prompt or template (export, review the data check and the results)1AssumptionTime the first two quarterly runs.
- RLoaded hourly cost of the RevOps or FP&A 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 (estimate)
T - V - 5 - 1 = 4 hours
- Time saved per week (estimate)
(T - V) / 13 - 4 / 13 = 0.3 hours
- Value of time saved per quarter (estimate)
(T - V) x R - 4 x $75 = $300
- 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
- Ramped SDRs (fictional example data)
CEILING(meetings booked / (meetings per SDR per month x 3)) - CEILING(400 / 36) = 12 ramped SDRs
- The time math counts analyst time only and is an estimate. Opening or closing reqs is a much larger number, but that decision is yours, so it is not added to the time savings.
- A rounded SDR count is not a forecast of bookings. Recheck each quarter on the same six inputs.
- Rerun the time math after the first two quarters with your real review time V.
Common questions
- How do you work back from a bookings target to SDR headcount?
- Deals = target / ACV. SQOs = deals / win rate. Meetings held = SQOs / meeting-held-to-SQO. Meetings booked = held / show rate. Divide booked meetings by meetings booked per ramped SDR per month x 3, then round up. In the fictional example $1,200,000 / $30,000 = 40 deals, 160 SQOs, 320 held, 400 booked, 11.1 unrounded, 12 ramped SDRs.
- Why round the SDR count up?
- You cannot staff a fraction of a person. 400 / 36 = 11.1 in the fictional example, so the plan uses 12. The unrounded figure stays on the slide so finance can see the slack. Rounding up is a staffing choice, not a forecast that 12 SDRs will book $1,200,000.
- Do ramping SDRs count in this number?
- No. This page counts ramped SDRs only. A ramping SDR contributes partial capacity; that math is on the ramp-capacity plan. Adding rampers 1:1 here overstates how many fully productive people you have.
- Is 12 meetings booked per SDR per month a benchmark?
- No. It is an example input in the fictional example so the 11.1 to 12 rounding is visible. Use the meetings your ramped SDRs actually book. Any range you hear as a rule of thumb is illustrative until you replace it with your scorecard.
- What does a +5 point show rate or win rate change do?
- It is an example lever, holding every other input fixed, not a forecast of a program. In the fictional example, show rate 80% to 85% takes the rounded count from 12 to 11 ramped SDRs; win rate 25% to 30% takes it to 10. Use the calculator to test your own lifts.
Keep going
Related playbooks
- Finance/FP&AIntermediate
Plan Sales Capacity with Ramp and Attrition, Not Headcount
Bookings targets are usually funded as headcount times quota, which assumes every rep is fully ramped all year and nobody leaves, so a plan can look covered on paper while new hires are still ramping, leavers' seats sit empty for months, and the shortfall shows up mid-year, too late to hire into.
HubSpot or SalesforceBambooHR, Rippling, or WorkdayGoogle Sheets or Clay+2Estimate: 1 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 - 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
Need help implementing a playbook?
Our team builds custom Clay workflows and AI automations for revenue teams.
Get it built for you