Quick answer
Booking 100 meetings a month is a math problem before it is a hiring problem. Work backward from real reply-rate benchmarks to a per-rep output number (roughly 10 to 15 blended meetings a month per rep once you apply actual conversion rates), then discount for the fact that most reps do not hit their number every month. That lands most teams on a realistic range of 9 to 14 reps, or an equivalent blend of reps and AI-handled volume, not the round number teams tend to guess at.
Why "100 a month" breaks most plans
I'm Hlib Storchak. I build and run outbound systems for B2B founders and sales teams, 2000+ meetings booked for B2B clients so far, and the "100 meetings a month" target is one I get handed constantly, usually as a headcount question: "how many SDRs do I need to hit 100?" That is the wrong first question. The right first question is what your actual per-rep output looks like once you stop assuming and start calculating it from real numbers.
Most plans that miss 100 a month do not miss because the reps are bad. They miss because the plan was built on a guessed number, usually "each rep books about 15 to 20 meetings a month," pulled from a LinkedIn post rather than from the reply rates that number actually depends on. Guessed inputs produce a guessed headcount, and a guessed headcount misses its target roughly as often as it hits it.
Step 1: work backward, not toward
Start at 100 and work backward through the funnel, not forward from a hire plan. The chain looks like this: sends, per channel, times a conversion rate to a reply, times a discount from reply to an actual booked meeting, times how many of those meetings you get per rep once you account for ramp time and the fact that not every rep hits their number every month. Each of those four multipliers has a real, citable range. None of them should be a guess.
The rule. If you cannot point to where each number in your meetings-per-rep math came from, the plan built on top of it is not a plan, it is a hope with a spreadsheet attached.
Step 2: set a real volume assumption
Volume is the one input you actually control, so set it first and set it conservatively. Assume 20 working days a month. A rep sending 25 cold emails a day across properly warmed, dedicated domains lands at 500 emails a month, a volume that stays well inside the safe per-mailbox ranges I cover in the deliverability guide. On LinkedIn, 20 connection requests a day lands at 400 a month, inside the roughly 100 to 200 a week range that holds up as safe across multiple independent trackers, per my piece on LinkedIn's daily limits. These are assumptions, not facts. Swap in your own safe volume ceilings before you run this math for your own team.
Step 3: apply real conversion rates
This is where guessing stops and cited data starts. Instantly's 2026 Cold Email Benchmark Report puts the platform-wide average cold email reply rate at 3.43%, with an elite tier clearing 10%+. Applied to 500 sends a month, that is roughly 17 replies for an average sender and roughly 50 for an elite one. On LinkedIn, Expandi's 2026 benchmark, built on 13.2 million tracked connection requests, puts average acceptance at 28.5% and the reply rate on messages sent after acceptance at 10.4%. Applied to 400 requests a month, that is roughly 114 accepted connections and roughly 12 replies.
| Channel | Monthly volume (assumption) | Real benchmark applied | Replies a month |
|---|---|---|---|
| Cold email, average sender | 500 sends | 3.43% reply rate, Instantly 2026 | ~17 |
| Cold email, elite sender | 500 sends | 10%+ reply rate, Instantly 2026 | ~50 |
| 400 requests | 28.5% acceptance, 10.4% post-connect reply, Expandi 2026 | ~12 |
Step 4: discount replies to actual meetings
A reply is not a meeting. Some replies are objections, some are "not now," some are outright no's that still count as engagement but book nothing. In client campaigns I typically see somewhere between a third and half of substantive replies convert into a booked meeting once a rep or an SDR works the thread properly, the rest resolve into a real no or silence after the first back and forth. For this model, assume 40%, and treat that number as the one you should replace first with your own CRM data once you have a full quarter of it.
Run the math: an average blended rep gets roughly 17 email replies plus 12 LinkedIn replies, 29 total, times 40%, which is about 12 meetings a month. An elite-email rep with the same LinkedIn output gets roughly 50 plus 12, 62 total, times 40%, about 25 meetings a month. That 12-to-25 range is the real per-rep output band, not the 15-to-20 round number most plans start from.
Step 5: account for ramp and attainment
Two more numbers matter before you convert output into headcount. Ramp time: a new rep does not produce full output on day one. Bridge Group's most recent SDR benchmarking report, its 10th edition, published February 2025 and based on 351 B2B companies, puts average ramp time at 3.0 months, the lowest on record, and quota attainment at 60% at the 12-month mark, also the lowest on record. Read that second number carefully: even mature, fully ramped teams see roughly 4 in 10 reps miss their own monthly number in a typical month. If you staff to the raw output math with no buffer for that gap, you will hit 100 in your best months and miss it in most others.
Step 6: back into the headcount range
At the average blended output of 12 meetings a rep a month, hitting 100 on paper takes roughly 9 reps. Divide that by Bridge Group's 60% attainment rate to size for a typical month rather than a best month, and you land closer to 14 to 15 reps, or a mix of fewer reps running at a higher, elite-tier output plus some AI-handled volume covering the gap. At the elite-tier output of 25 meetings a rep a month, the raw math drops to 4 reps, and the attainment-adjusted number lands around 6 to 7. The honest range for most teams, not the best-case one, is 9 to 14 reps depending on how close to elite output your actual sending and targeting get.
Step 7: a worked example at four team sizes
Here is the same math laid out at four team sizes, using the average blended output of 12 meetings a rep a month and a fully loaded cost built from stated assumptions: a €55k base SDR salary, 30% on-costs, and €400 a month of tooling per seat, which works out to roughly €6,350 a month fully loaded per rep. Swap in your own local salary and tooling numbers, this is a shape to copy, not a number to trust blindly.
| Team size | Raw math, meetings/mo | Realistic, at 60% attainment | Fully loaded monthly cost (assumption) |
|---|---|---|---|
| 3 reps | 36 | ~22 | ~€19,000 |
| 6 reps | 72 | ~43 | ~€38,000 |
| 10 reps | 120 | ~72 | ~€64,000 |
| 14 reps | 168 | ~101 | ~€89,000 |
Read the gap between the raw math column and the realistic column as the whole point of this exercise. A 10-rep team that looks like it should clear 120 meetings a month on paper realistically clears closer to 72 once actual attainment is priced in. Plan against the realistic column, not the raw one.
Step 8: where AI changes the number
AI seats do not remove this math, they change which cells you fill with a human versus an agent. I cover the underlying cost data in more depth in my framework for how many AI SDRs per human rep, but the two numbers that matter here: a hybrid pod of one human plus AI seats has been benchmarked at a lower cost per qualified opportunity than either an all-human or an all-AI pod, and AI seats ramp to a first booked meeting in a matter of weeks against a human's 3.0-month average. That makes AI seats a good fit for absorbing the top-of-funnel volume, the 500 emails and 400 connection requests a month per seat, while a smaller number of human reps handle the judgment calls on ambiguous replies. The math above still applies, you are just filling more of the volume side with cheaper, faster-ramping seats and keeping the reply-quality side human.
The execution checklist behind the math
None of the math above survives a bad list or a slow reply desk. Before you staff to any number from this model, check five things: your list is verified and matched to a real ICP, not just large; every sending domain and LinkedIn account is warmed and inside safe volume ranges, not pushed past them to hit a target faster; replies are routed to one place and answered inside hours, not days; each rep's individual quota is set from this math, not from a round number handed down; and you are tracking reply rate and meetings-held, not just meetings-booked, since a booked meeting that no-shows is not the 100 you were counting.
Where teams miss the number anyway
The mistake I see most often when I take over an account that is missing its number is that the original headcount plan skipped the attainment discount entirely, staffed to the raw math column, and then treated every missed month as a performance problem with the reps rather than a math problem with the plan. The second most common mistake is pushing per-rep volume past the safe ranges in step 2 to try to close the gap, which burns domains and LinkedIn accounts and makes next month's number worse, not better. The third is counting every reply as progress toward the 100, which hides a real problem in the reply-to-meeting conversion step until a whole quarter has gone by.
When 100 a month is the wrong target
A flat meetings number is a fine planning input, but it is a poor optimization target on its own. I go deeper on this in my piece on what to optimize for instead of raw counts: 100 meetings with a loose ICP and a weak show rate can produce less pipeline than 60 meetings with a tight one. Use this model to size your team and budget honestly, then hold the team to opportunity and pipeline conversion, not to the raw meeting count, once the engine is running.
Key takeaways
- Work backward from 100 through real conversion rates, not forward from a guessed per-rep number.
- Cited benchmarks: 3.43% average and 10%+ elite cold email reply rate (Instantly 2026), 28.5% LinkedIn acceptance and 10.4% post-connect reply rate (Expandi 2026).
- A realistic blended rep books roughly 12 meetings a month, an elite one roughly 25, once you discount replies to actual bookings.
- Bridge Group's 2025 data puts SDR ramp at 3.0 months and 12-month quota attainment at 60%, both the lowest on record, meaning most teams need to staff above the raw math to hit a target consistently.
- Most teams land in a realistic range of 9 to 14 reps, or an equivalent AI-plus-human blend, not a round guessed number.
- Plan against the realistic, attainment-adjusted number, not the optimistic raw math.
FAQ
How many SDRs do I need to book 100 meetings a month?
Working backward from real reply-rate benchmarks and Bridge Group's 60% quota attainment figure, most teams land in a realistic range of 9 to 14 reps, depending on how close to elite output your list and copy actually get, and how much of the volume you shift onto AI seats.
What is a realistic number of meetings per SDR per month?
Applying Instantly's 3.43% average cold email reply rate and Expandi's 28.5% LinkedIn acceptance and 10.4% post-connect reply rate to a conservative sending volume, then discounting replies to bookings, lands an average rep around 12 meetings a month and an elite one around 25.
Does adding AI seats change how many reps I need?
It changes the mix more than the math. AI seats ramp faster and cost less per qualified opportunity for top-of-funnel volume, per the benchmark data in my AI-SDR cost framework, so a hybrid team can hit the same number with fewer human seats, keeping people on the judgment calls.
How long before a new SDR is producing meetings?
Bridge Group's most recent report, based on 351 B2B companies, puts average ramp time at 3.0 months, the lowest on record. Budget for that gap in any headcount plan rather than assuming full output from day one.
Is 100 meetings a month always the right target?
Not on its own. A high meeting count with a loose ICP or a weak show rate can produce less real pipeline than a lower count with a tight one. Use the math here to size the team and budget, then hold the team to opportunity conversion, not the raw meeting count.