The Simple Guide to SDR Capacity and Pipeline Planning

How to figure out how many SDRs you really need, what they must produce, and what it costs to support them

Most teams guess when it comes to SDR capacity.

They hire one more SDR because pipeline feels light.
They push activity because meetings dipped.
They blame tools, markets, or effort when targets are missed.

The problem is not effort.
The problem is math that never gets written down.

This guide shows you how to plan SDR capacity step by step, using simple inputs you already know or can estimate. By the end, you will know:

• How much pipeline you want to create
• How many deals that means
• How many meetings are required
• How many SDRs it takes to book those meetings
• How many emails must be sent to support that work
• How many domains and mailboxes are needed to send safely
• Rough monthly costs for tools and infrastructure

Nothing here is theory. This is a working model you can use to hire, plan, and adjust without guessing.

What “SDR Capacity” Really Means

SDR capacity is not how busy your team feels.

It is the maximum number of meetings your team can book in a month without burning out people or breaking email deliverability.

Capacity depends on five things:

1. Your pipeline goal
2. Your average deal size
3. How often meetings turn into real opportunities
4. How many meetings one SDR can realistically book
5. How many emails it takes to book one meeting

When you connect these five numbers, everything else becomes clear.

Step 1: Set Your Monthly Pipeline Target

Start with one number:
How much pipeline do you want to create this month?

This is not revenue.
This is not bookings.
This is the dollar value of open opportunities you want sales to work.

Examples:

• $100,000 in new pipeline
• $300,000 in new pipeline
• $1,000,000 in new pipeline

Pick one number. Write it down.

This number becomes the anchor for every decision that follows. If this target is wrong or fuzzy, the rest of the plan will be too.

Tip:
Use a monthly number, not quarterly. Monthly keeps planning grounded and easier to adjust.

Step 2: Add Your Average Deal Size

Now ask a simple question:

When a deal closes, how big is it on average?

Use real data if you have it. If not, take your last 10–20 closed deals and find the middle value.

Examples:

• $10,000 per deal
• $20,000 per deal
• $50,000 per deal

Once you have this number, divide your pipeline target by your deal size.

Example:

• Pipeline target: $300,000
• Average deal size: $20,000

$300,000 ÷ $20,000 = 15 opportunities

This means sales needs 15 real opportunities, not meetings, not replies. Actual deals in the pipeline.

This step is critical. Many teams skip it and jump straight to activity. That’s how you end up with busy SDRs and empty forecasts.

Step 3: Enter Your Meeting-to-Opportunity Rate

Not every meeting turns into an opportunity.

Some prospects are curious but not serious.
Some are too small.
Some were never a fit.

Your meeting-to-opportunity rate shows how many meetings it takes to create one real deal.

Common ranges:

• 30 percent (3 meetings = 1 opportunity)
• 50 percent (2 meetings = 1 opportunity)
• 70 percent (strong qualification and targeting)

If you don’t know your rate, start with 50 percent. It is a fair baseline for most B2B teams.

Example:

You need 15 opportunities.
Your meeting-to-opportunity rate is 50 percent.

15 opportunities × 2 meetings = 30 meetings

Now you know how many meetings SDRs must book this month.

This is where planning gets real.

Step 4: Set Meetings per SDR per Month

Now we move from goals to people.

Ask this question honestly:

How many meetings can one SDR book in a month without rushing, spamming, or burning out?

For most teams:

• Low end: 15 meetings
• Average: 20–30 meetings
• High end: 35–40 meetings (rare and hard to sustain)

Do not use best-month numbers.
Use what an SDR can hit most months.

Example:

• Total meetings needed: 30
• Meetings per SDR per month: 15

30 ÷ 15 = 2 SDRs

This means two SDRs, performing at a realistic level, can support your pipeline goal.

If your math says you need 2.4 SDRs, you really need 3. People are not spreadsheets.

Step 5: Estimate Emails Needed per Meeting

Meetings do not appear by magic.

They come from volume, follow-up, and patience.

Ask your team or look at data:

How many emails does it usually take to book one meeting?

Typical ranges:

• Strong targeting: 30–40 emails
• Average outbound: 40–60 emails
• Cold or broad lists: 60–80 emails

This includes:

• First emails
• Follow-ups
• Light personalization
• Polite nudges

Example:

• Meetings needed: 30
• Emails per meeting: 50

30 × 50 = 1,500 emails per month

This is total team volume, not per SDR.

Step 6: Break Email Volume Down per SDR

Now divide the total email volume by the number of SDRs.

Example:

• Total emails needed: 1,500
• SDRs: 2

1,500 ÷ 2 = 750 emails per SDR per month

That equals:

• About 37 emails per day (over 20 working days)

This is reasonable, safe, and sustainable.

If your math says each SDR needs to send 200 emails per day, your plan is broken somewhere upstream.

Step 7: Plan Domains and Mailboxes the Right Way

Email deliverability matters. Sending too much from one inbox will hurt results fast.

A safe rule:

• 150–200 emails per mailbox per day
• Spread across multiple domains

Example:

An SDR sends 750 emails per month.
That’s about 38 emails per day.

One mailbox can technically handle this, but it leaves no room for warm-up, replies, or growth.

A safer setup:

• 2–3 mailboxes per SDR
• 1 domain per 2–3 mailboxes

This protects deliverability and gives you flexibility.

Step 8: Estimate Monthly Tool and Infrastructure Costs

Now that you know:

• Number of SDRs
• Number of mailboxes
• Number of domains

You can estimate costs.

Typical monthly costs per SDR:

• Email tool: $50–$100
• Mailboxes: $5–$10 each
• Domains: $10–$15 each

Example: 

Per SDR:

• 3 mailboxes × $8 = $24
• 1 domain = $12
• Outreach tool = $75

Total per SDR: ~$110 per month

Multiply by headcount and you now have a real budget, not a guess.

Step 9: Test Scenarios Before You Hire

This is where the planner becomes powerful.

Change one input at a time and watch the impact.

Try:

• Increasing deal size
• Improving meeting quality
• Raising meetings per SDR
• Lowering emails per meeting

Example:

If deal size goes from $20k to $30k:

• Opportunities drop
• Meetings drop
• SDR need drops

Or if meetings per SDR fall:

• Headcount increases
• Costs rise
• Hiring becomes urgent

This lets you plan ahead instead of reacting late.

Common Mistakes to Avoid

Planning from activity instead of outcomes

Emails do not matter. Meetings that turn into deals do.

Using best-case numbers

Plan for normal months, not lucky ones.

Overloading inboxes

More volume does not mean more meetings.

Hiring before fixing math

If conversion is weak, adding SDRs just multiplies waste.

Why This Approach Works

This planning method removes emotion and guesswork.

You are no longer asking:

• “Should we hire?”
• “Are SDRs working hard enough?”

Instead, you are asking:

• “Do we have enough meetings to support our pipeline goal?”
• “Is our activity level realistic?”

You see exactly:

• How many SDRs you need
• What each one must produce
• How much volume supports that output
• What it costs to run the system

When numbers are clear, decisions become calm.

Final Thought

Pipeline problems are rarely effort problems.

They are planning problems.

When you map pipeline goals to meetings, meetings to SDRs, and SDRs to volume, the system becomes predictable. You stop guessing, stop over-hiring, and stop pushing people past healthy limits.

Use this guide as a living model. Revisit it monthly. Adjust assumptions as your data improves.

Clarity beats hustle every time.