Outsourced SDR Meetings Per Month: What SLA to Expect

A fair meetings-per-month SLA for an outsourced SDR provider is a number built from your deal size, your market size and how narrow your list is, not a number from a price sheet. It counts only held meetings, counts a no-show against the provider, and takes the count from your calendar. Blesso, a done-for-you B2B go-to-market service, works this way.

Build the target from ACV, market size and list narrowness

Three inputs set a sensible monthly target. Each one moves the number in a different direction.

• ACV (annual contract value). A higher ACV needs fewer meetings to hit your revenue goal, so it supports a lower target.
• Market size. The number of accounts that fit your ideal customer profile (ICP) sets how many meetings exist at all.
• List narrowness. A narrow list has few accounts and few buyers at each account. You can message each person only so many times, so the monthly ceiling is lower.

The first input comes from your own sales math. The two others come from the list. Start with the sales math.

Worked estimate: work back from ACV

This is an estimate with made-up inputs, not a measured result. Assume you want the same $240,000 in new annual contract value from outbound. Assume 1 in 10 held meetings becomes a customer. Change that rate to your own close rate.

Both rows start from the same revenue goal. The lower ACV needs about three and a half times as many meetings. That is why a provider that quotes one number for every client has not done this sum.

Worked estimate: check it against your list

Now test whether your list can supply that number. Again, these are assumptions, not benchmarks. Assume 1,000 ICP accounts and 2.5 buyers per account, so 2,500 contacts. Assume each contact gets one outbound sequence in a four-week pass. Assume 1% of contacts book a meeting, and 3 in 4 booked meetings are held.

1. 2,500 contacts × 1% booked = 25 booked meetings in the pass.
2. 25 booked × 75% held = about 19 held meetings in the pass.
3. A second pass to the same people, after a pause, yields fewer, because the contacts who wanted a meeting already booked one.

In this example the list supports about 19 held meetings in the first month and fewer after that. A target of 25 held meetings a month is not a realistic target for that list, whatever the provider's sales page says. Either the list must get larger, or the target must come down before month one. Fix this gap on day one, not in month three.

For the contact rate, public data gives a range, not a single answer. Belkins reported an average cold email reply rate of 5.8% in 2024, down from 6.8% in 2023, across 16.5 million cold emails it sent. A Mailshake survey of 508 senders found 1% to 4% reply rates are the norm. A reply is not a meeting, so the meeting rate per contact is lower. Treat the 1% above as a starting assumption to test, and ask the provider what rate it assumed.

Fix the counting rules before month one

The number is only half of the SLA. The counting rules decide whether the number means anything. Write them into the contract before the first sequence goes out. Blesso agrees its targets before month one for the same reason.

Only held meetings count

A booking is a calendar invite. A held meeting is a conversation that took place. The two differ by the no-show rate, and that rate changes month to month. If the SLA counts bookings, the provider can meet the number while your closers sit in empty calendar slots.

Several providers already publish this rule. Appointment Setters says its no-shows do not count and are replaced. DemandNexus says no-shows are replaced within five business days. BizDev Labs says its meetings are held, not just booked. Use these pages as examples of what to ask for. Check each provider's own contract, because a web page is not an agreement.

A no-show counts against the number

State it as an arithmetic rule. If the target is 10 held meetings and 12 were booked, and 3 did not attend, the count is 9. The provider has missed. At Blesso, a no-show counts against the number: only held meetings count, not bookings.

A replacement clause is a good addition. It lets the provider make up the gap with a new meeting. It does not replace the count rule, because the replacement arrives late and may land in the next month.

Count from the buyer's calendar, not the provider's dashboard

A dashboard shows what the provider chose to log. Your calendar shows what happened. When the two disagree, the calendar wins. Blesso counts demos from the customer's calendar, not from its own dashboard.

A counted meeting should meet five tests. These come from the demo rules published on the Blesso how-we-work page.

1. A human attended it.
2. It took place on a date that has already passed.
3. The account is on the approved account list.
4. The attendee's title matches the agreed ICP titles.
5. The call ended with agreed next steps.

Add a monthly cap. Without a cap, a provider can push low-fit meetings to reach a larger count. With a cap, extra volume does not hide a quality problem.

Questions that expose a soft meetings SLA

Some provider promises sound firm and are not. Send these questions before you sign and keep the answers.

The market has no single standard. DemandNexus publishes tiers with a guaranteed monthly meeting count. Managed Outbound says it does not guarantee a meeting count and commits instead to operating work, such as accounts researched and reply handling times. Both positions are honest. The risk is a provider that says "guaranteed" in marketing and "forecast" in the contract. Ask which one you are buying.

What a provider should do after missing twice

Plan for a miss before it happens. A provider that misses the target once has a data point. A provider that misses twice has a method problem. The right response to a second miss is to change what the provider does, not to lower the number.

Blesso states the rule this way: miss the target twice and it changes something, such as more channels or different signals, not a lower target. Put the same rule in your contract. Name the changes the provider may make:

• Channels. Add LinkedIn to email, or add calls, so the same accounts are reached in more than one place.
• Signals. Change what triggers outreach, for example a hiring signal, a funding event or a technology change at the account.
• List. Widen the account list, if the earlier check showed it was too narrow for the target.

Do not accept "the market is harder than we expected" as the only answer. That sentence moves the risk to you. A provider that cannot name a change after two misses has no second plan.

One exception is fair. If the list check at the start showed that the list cannot support the target, change the target once, at the start, with the evidence in front of both sides. Do not change it after a miss.

How Blesso handles it

Blesso runs outbound for B2B teams as a monthly retainer, from $2k a month with a three-month minimum. It sets the monthly meeting target from the customer's ACV, market and list narrowness. Weekly reports come in three fixed tiers, always in the same order: activity Blesso controls, market response such as meeting attendance, and business outcomes. Blesso's own wording for the first tier is that if activity slips, that is an operator failure.

For one example of the pace, HappierHire, an AI hiring platform, published first meetings inside three weeks of kickoff. That is one customer's result, not an average and not a promise. Read the others on the case studies page, and see what each service line includes on the services page.

Set the number, then set the rules

Do the sales math, check it against your list, and write down the three counting rules. Then ask what happens after two misses. If you want to run this with Blesso, book a call and bring your ACV and your account list.

Book a call