Work Backward from a Monthly Bookings Target to Meetings Booked
The problem
Monthly activity plans start from "how many meetings can we book" instead of the new-logo bookings target, so SDRs get a round number that does not trace to ACV, win rate, meeting-to-SQO, or show rate, and finance cannot see how many meetings the month actually needs.
Run it in your LLM
One prompt for Claude or ChatGPT that turns a monthly new-logo bookings target into the meetings booked the month needs, rounded up, with an optional split per SDR and a comparison at a 90% show rate. Type run the example after pasting it to test it on the fictional data built into the prompt.
# Monthly meetings target, working backward from bookings
You are a senior GTM and RevOps lead reporting to the CRO. From a monthly new-logo bookings target, work backwards through ACV, SQO-to-won, meeting-held-to-SQO, and show rate to the meetings booked the month needs, then optionally split that by SDR headcount into meetings booked per SDR per month and per week.
This page sizes the meeting engine for one month. Ramped SDR headcount from a quarterly target is a different question, on the SDR headcount playbook. Coverage of already-created pipeline is on the pipeline coverage check. Stage-to-stage conversion from closed cohorts is on stage conversion rates.
## 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 deal, SQO, and meeting counts up to whole numbers. Show the unrounded figure next to each so finance can see the slack. Rounding up is a planning choice so you do not under-book a fraction of a meeting.
- The 90% show-rate lever and the +5 point win-rate lever are example input changes, not a forecast of a coaching or process program.
- Read only. Do not change CRM records, calendars, or quotas. Report what the numbers imply and leave the staffing and activity decision to the user.
- Format: money to the nearest dollar, unrounded funnel counts to one decimal if not whole, rounded counts as whole numbers.
## Definitions
- Bookings target is monthly new-logo bookings, not expansion, not a quarterly 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.
- SDRs is an optional count of people who book the meetings. When it is missing or zero, skip per-SDR math.
- Deals needed = CEILING(target / ACV).
- SQOs needed = CEILING(deals / (win_rate_pct / 100)).
- Meetings held needed = CEILING(SQOs / (meeting_to_sqo_pct / 100)).
- Meetings booked needed = CEILING(held / (show_rate_pct / 100)).
- Meetings booked per SDR per month = booked / SDRs. Per week = that number / 4.
- Do not divide by zero. If ACV or a rate 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-11), monthly_bookings_target, acv, win_rate_pct, meeting_to_sqo_pct, show_rate_pct, sdrs (optional)
Where to get it: finance or the CRO for the monthly new-logo bookings target; CRM for ACV, SQO-to-won, and meeting-to-SQO; calendar or the SDR scorecard for show rate and the SDR count. 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 = CEILING(monthly bookings target / ACV).
- SQOs needed = CEILING(deals / (win_rate_pct / 100)).
- Meetings held needed = CEILING(SQOs / (meeting_to_sqo_pct / 100)).
- Meetings booked needed = CEILING(held / (show_rate_pct / 100)).
- If SDRs is above zero: per SDR per month = booked / SDRs; per week = per month / 4.
## Step 2. Levers
Recompute the same funnel twice, each holding every other input fixed:
- Show rate 90% (an example lift, capped at 100).
- Win rate +5 points (capped at 100).
Report the new rounded meetings-booked count versus the base. Label both as example lifts, not as a forecast.
## Step 3. Output
Start with a five-line summary:
- Headline: "{booked} meetings booked per month for {target} new-logo bookings at {acv} ACV."
- Funnel: "{deals} deals, {sqos} SQOs, {held} meetings held, {booked} meetings booked. Counts are rounded up."
- Per SDR (if SDRs given): "{sdrs} SDRs -> {perMonth} booked per SDR per month, about {perWeek} per week at 4 weeks."
- Levers: "Show rate 90% -> {show90Booked} booked; +5 pts win rate -> {winBooked} booked. Example lifts, not a forecast."
- One line: "This is a monthly meeting plan, not a quarterly SDR headcount and not a coverage check. {excluded} rows were left out."
Then these tables:
1. Data check
2. Scored scenario (inputs, unrounded funnel, rounded funnel, optional per-SDR)
3. Levers (show 90%, +5 win)
4. Assumptions, each labeled as an assumption, including: rates are history not a forecast; 4 weeks is a planning month, not a calendar; rounding up is a planning choice; SDR headcount from a quarterly target lives on the SDR headcount playbook.
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-11
- Monthly new-logo bookings target $300,000
- Average new-logo ACV $25,000
- SQO-to-won 25%, meeting-held-to-SQO 60%, show rate 80%
- 5 SDRs (optional; used only to split meetings per person)
Scenarios:
```csv
scenario,monthly_bookings_target,acv,win_rate_pct,meeting_to_sqo_pct,show_rate_pct,sdrs
2026-10,250000,25000,20,55,75,4
2026-11,300000,25000,25,60,80,5
2026-11,300000,25000,25,60,80,5
BAD-1,300000,0,25,60,80,5
,300000,25000,25,60,80,5
```
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 monthly bookings target, ACV, win rate, meeting-to-SQO, show rate, and optional SDRs. The prompt lists the columns.
- Read the data check first. Take the rounded meetings-booked number to the monthly plan. Keep the 90% show-rate lever labeled as an example lift, not a forecast. Quarterly ramped SDR count is on the SDR headcount playbook.
Before you paste target and funnel data
Bookings targets, win rates, and headcount 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; kept 2026-10, 2026-11; left out: 2026-11 (duplicate scenario), BAD-1 (Enter average new-logo ACV above zero.), (blank scenario) (no scenario id)
- Funnel
- 12 deals, 48 SQOs, 80 held, 100 booked
- Per SDR
- 5 SDRs, 20 booked per SDR per month, 5 per week
- Show 90%
- 89 meetings booked (88.9 before rounding up)
| Step | Unrounded | Rounded up |
|---|---|---|
| Deals | 12 | 12 |
| SQOs | 48 | 48 |
| Meetings held | 80 | 80 |
| Meetings booked | 100 | 100 |
$300,000 / $25,000 = 12 deals; 12 / 25% = 48 SQOs; 48 / 60% = 80 held; 80 / 80% = 100 booked. 5 SDRs is 20 per SDR per month, 5 per week at 4 weeks. Show rate 90% is 80 / 0.90 = 88.9, round up to 89 booked. Counts round up. This is a monthly meeting plan, not a quarterly SDR headcount.
Monthly meetings from a new-logo bookings target
Work backwards from monthly new-logo bookings to meetings booked. Deal, SQO, and meeting counts round up. Rates are your inputs, not benchmarks. Prefilled with the fictional example.
- Deals needed
- 12
- $300,000 / $25,000
- SQOs needed
- 48
- 12 / 25% win rate
- Meetings held needed
- 80
- 48 / 60% meeting-to-SQO
- Meetings booked needed
- 100
- 80 / 80% show rate, rounded up
- Booked per SDR per month
- 20
- 100 / 5 SDRs
- Booked per SDR per week
- 5
- 20 / 4 weeks
Example levers, holding everything else fixed
Show rate 90% and win rate +5 points are example lifts so you can see meetings booked move. They are not a forecast of a program.
| Change | Meetings booked | Vs base |
|---|---|---|
| Base (80% show, 25% win) | 100 | - |
| Show rate 90% (88.9 before rounding up) | 89 | 11 fewer |
| +5 pts win rate | 84 | 16 fewer |
Monthly meeting plan, not a quarterly headcount. Ramped SDR count from a quarterly target is on the SDR headcount playbook. Coverage of existing pipeline is on the pipeline coverage check; stage-to-stage conversion is on stage conversion rates.
Implementation steps
- 1
Write the definitions down with finance and the SDR leader before pulling data: the target is monthly new-logo bookings, not expansion and not a quarterly number; ACV is average new-logo contracted value; SQO-to-won, meeting-held-to-SQO, and show rate (booked to held) are percents. An SDR count is optional and only splits meetings per person. Quarterly ramped SDR headcount is a different question, on the SDR headcount playbook
- 2
Export last month's rates 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 = CEILING(target / ACV). In the fictional example $300,000 / $25,000 = 12 deals. Round deal, SQO, and meeting counts up to whole numbers so you do not plan a fraction of a meeting. Keep the unrounded figure next to it
- 4
Work backwards: SQOs needed = CEILING(deals / (win rate / 100)); meetings held needed = CEILING(SQOs / (meeting-held-to-SQO / 100)); meetings booked needed = CEILING(held / (show rate / 100)). Do not divide by zero. In the fictional example 25% win, 60% meeting-to-SQO, and 80% show rate give 48 SQOs, 80 meetings held, and 100 meetings booked
- 5
If you have an SDR count, meetings booked per SDR per month = booked / SDRs, and per week = that number / 4. In the fictional example 5 SDRs is 20 booked per SDR per month, about 5 per week. Four weeks is a planning month, not a calendar. Skip this split if the SDR count is blank
- 6
Recompute two example levers, holding everything else fixed: show rate 90%, and win rate +5 points. Those lifts are sizing devices, not a forecast of a coaching program. In the fictional example 80 held / 90% show = 88.9, round up to 89 meetings booked. Keep coverage of already-created deals on the coverage playbook and stage-to-stage conversion on the conversion playbook; this page is the monthly meeting engine
- 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 rounded meetings-booked number with the SDR leader; this is an activity plan, not a bookings forecast and not a req count
- 8
Rerun each month on the same definitions and store the five rates plus the optional SDR count so a mix shift, a show-rate drop, or a target change shows up before the next monthly plan
Template outline
The structure to recreate in your own workspace. Field names and thresholds are starting points.
Google Sheet: Monthly meetings from new-logo target FYxx (RevOps owns the funnel; finance owns the target)
Tab inputs: score_scenario
Tab scenarios (one row per plan):
scenario, monthly_bookings_target, acv, win_rate_pct, meeting_to_sqo_pct, show_rate_pct, sdrs
kept = unique scenario AND target, acv, and rates are numbers AND acv > 0 AND every rate is in (0, 100]
sdrs is optional; blank skips the per-SDR split
Tab funnel:
deals_exact = monthly_bookings_target / acv
deals = CEILING(deals_exact)
sqos_exact = deals / (win_rate_pct / 100)
sqos = CEILING(sqos_exact)
held_exact = sqos / (meeting_to_sqo_pct / 100)
held = CEILING(held_exact)
booked_exact = held / (show_rate_pct / 100)
booked = CEILING(booked_exact)
per_sdr_month = IF(sdrs > 0, booked / sdrs, "")
per_sdr_week = IF(sdrs > 0, per_sdr_month / 4, "")
Tab levers (same formulas, one input changed):
show_90 = 90
win_plus_5 = MIN(100, win_rate_pct + 5)
Worked example (example data, fictional): score 2026-11
5 rows read, 2 kept (2026-10 and 2026-11). Left out: 2026-11 listed twice; BAD-1 ACV 0; blank scenario.
Target $300,000 / ACV $25,000 = 12 deals.
Win 25% -> 48 SQOs. Meeting-to-SQO 60% -> 80 meetings held. Show 80% -> 100 meetings booked.
5 SDRs: 20 booked per SDR per month, 5 per week at 4 weeks.
Show 90%: 80 / 0.90 = 88.9, round up to 89 booked. +5 pts win (30%): 84 booked. Example lifts, not a forecast.
Calculator on this page, prefilled: target $300,000, ACV $25,000, win 25%, meeting-to-SQO 60%, show 80%, 5 SDRs. Every money line above matches.
Slack to #sales-leadership before the monthly plan:
"Meetings booked for {{scenario}}: {{booked}} for {{target}} new-logo bookings ({{exact}} before rounding up).
Funnel {{deals}} deals, {{sqos}} SQOs, {{held}} held, {{booked}} booked.
{{sdrs}} SDRs -> {{per_month}} / SDR / month, about {{per_week}} / week.
Show 90% -> {{show90_booked}} booked. Sheet: {{sheet_url}}"
Tab history: scenario, target, acv, win, to_sqo, show, sdrs, bookedCost, 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 the monthly new-logo target, ACV, funnel rates, and optional SDR count and size the meeting plan by hand4AssumptionTime the next three monthly meeting-plan reviews.
- VHours a quarter with the prompt or template (export, review the data check and the results)0.8AssumptionTime the first two monthly runs, then multiply by three for the quarter.
- RLoaded hourly cost of the RevOps or SDR-ops 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 - 4 - 0.8 = 3.2 hours
- Time saved per week (estimate)
(T - V) / 13 - 3.2 / 13 = 0.2 hours
- Value of time saved per quarter (estimate)
(T - V) x R - 3.2 x $75 = $240
- Tool cost per quarter
K x 3 - $20 x 3 = $60
- Break-even hours per quarter (estimate)
K x 3 / R - $60 / $75 = 0.8 hours, so the run covers its tool cost once it saves 48 minutes a quarter
- Meetings booked (fictional example data)
CEILING(meetings held / show rate) - CEILING(80 / 0.80) = 100 meetings booked; 5 SDRs is 20 per SDR per month
- The time math counts analyst time only and is an estimate. Changing activity targets or opening reqs is a much larger number, but that decision is yours, so it is not added to the time savings.
- A rounded meetings-booked count is not a forecast of bookings. Recheck each month on the same inputs.
- Rerun the time math after the first two months with your real review time V.
Common questions
- How do you work back from a monthly bookings target to meetings booked?
- Deals = CEILING(target / ACV). SQOs = CEILING(deals / win rate). Meetings held = CEILING(SQOs / meeting-held-to-SQO). Meetings booked = CEILING(held / show rate). In the fictional example $300,000 / $25,000 = 12 deals, 48 SQOs, 80 held, 100 booked. Counts round up to whole numbers.
- Why round deal and meeting counts up?
- You cannot book a fraction of a meeting. 80 / 0.90 = 88.9 in the 90% show-rate lever, so the plan uses 89. The unrounded figure stays on the slide so finance can see the slack. Rounding up is a planning choice, not a forecast that 100 meetings will book $300,000.
- How is this different from the SDR headcount playbook?
- This page sizes meetings booked for one month from a monthly target. The SDR headcount playbook sizes ramped SDRs for a quarter from a quarterly target and meetings booked per SDR as an input. Use this for the monthly activity plan; use that one for the req count.
- What does a 90% show 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 90% takes meetings booked from 100 to 89 (88.9 before rounding up). Use the calculator to test your own lifts.
- How much time does it save?
- With the example inputs, building the table by hand takes 4 hours a quarter and reviewing the prompt or template run takes 0.8, so 3.2 hours a quarter are saved, about 0.2 hours a week. That is an estimate, worth $240 a quarter at $75 an hour against an example $60 a quarter LLM plan share.
Keep going
Related playbooks
- RevOpsIntermediate
Work Back from a New-Logo Bookings Target to the Ramped SDRs You Need
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.
HubSpot or SalesforceGoogle SheetsClaude or ChatGPT+1Estimate: 0.3 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 - 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