Something Inc.LoginSchedule a free consultation
STRATEGY

Your AI SDR Reply Rate Has No Denominator

SaaStr says its AI agents sent 19,847 messages in six months at a 6.7 percent response rate. Atlassian's own reps say no AI-written email reaches a customer unreviewed. Both are true, and the AI SDR reply rate is the number hiding the disagreement.

STRATEGYOUTBOUNDNOV 2026

An AI SDR reply rate is the easiest number in outbound to quote and the hardest to compare, because almost nobody publishing one says what sits underneath the division line. Two prominent accounts from the last few weeks make the problem concrete, and one of them contradicts itself.

Start with the bullish case, because it is the better documented of the two. Jason Lemkin, writing at SaaStr on six months of running AI sales development agents, reports an outbound agent that sent 19,847 messages over the period at a 6.7 percent overall response rate and a 4 percent positive response rate, against the roughly 3 percent the same write-up cites as an industry average. Monthly volume ran near 3,000 messages, where the human reps it replaced had managed 75 to 285 each.

That is a real result from a named operator with the figures attached, and it deserves to be taken seriously rather than waved off. It is also not the claim most people repeat from it. The repeated claim is the multiple, the ten times more email. Lemkin's own assessment of the rate is considerably more modest: he writes that response rates have not changed materially in six months, and that the agents are not materially better than the humans on that measure, just basically the same.

Read those two statements together and the actual finding appears. The agents did not improve the rate. They multiplied the volume while holding the rate roughly flat, which is a volume win, not a quality win. Whether a volume win is a win at all depends entirely on what the rate is a rate of, and that is where the published numbers stop cooperating.

TL;DR · 60 SECONDSThe bullish data: Jason Lemkin at SaaStr reports an outbound AI agent sending 19,847 messages over six months at a 6.7 percent overall and 4 percent positive response rate, roughly 3,000 messages a month against 75 to 285 a month per human rep, at 50,000 to 100,000 dollars a year per platform plus 15 to 20 hours a week of operator time. His own read is that response rates did not change materially, so the gain is volume, not rate. The problem: the three campaign breakdowns he publishes state rates that match neither replies per message nor replies per lead, and the gap between the stated figure and each candidate denominator is different in every campaign. The counterweight: Atlassian's Teamwork Lab, publishing November 9, 2026 on interviews with eight sales development reps, reports that no AI-written communication reaches a customer or an account executive without human review, and one rep who dropped AI from outbound email and booked ten meetings in a week. Our verdict: hold your program to positive replies per account reached, not replies per message sent. Volume inflates the message denominator while the account denominator stays flat, so a rate that looks stable can hide both worse coverage and a growing reputation bill.

What The AI SDR Reply Rate Numbers Actually Say

SaaStr publishes three campaign breakdowns with leads, messages, responses and a stated rate for each, and in all three the stated rate sits between replies per message sent and replies per lead contacted without equalling either one. The gap is not consistent across the three.

REPORTED CAMPAIGNLEADSMESSAGESRESPONSESSTATED RATEREPLIES PER MESSAGEREPLIES PER LEAD
Europa prior-year attendees8002,17513712.13%6.3%17.1%
London known website visitors2657353311.70%4.5%12.5%
Europa earlier attendees, batches 1 and 2about 880about 2,490785.54% to 5.66%3.1%8.9%

The two right-hand columns are arithmetic on the figures as published, not a competing measurement. Work the first row and the issue is plain. One hundred and thirty-seven responses from 2,175 messages is 6.3 percent. The same responses against 800 leads is 17.1 percent. The stated 12.13 percent is neither, and no definition in the write-up reconciles it. The London row lands close to its lead denominator, and the third row sits in the middle of its two. Three campaigns, three different relationships between the published rate and the published inputs.

None of that makes the program a failure or the author careless. Sequencers report several reply metrics side by side, deduplication across a multi-message sequence is genuinely fiddly, and an operator writing up his own results is not running an audit. It does mean the headline rate cannot be compared to your rate, or to a vendor benchmark, or to the roughly 3 percent industry figure quoted next to it, because those are very unlikely to share a denominator. We made the wider version of this argument when we traced how outbound benchmarks get laundered through citation, and this is the same failure at the level of a single honest write-up.

Replies per lead contacted: 17.1 percent100%
Rate as stated in the write-up: 12.13 percent71%
Replies per message sent: 6.3 percent37%

SaaStr's reported Europa campaign (800 leads, 2,175 messages, 137 responses, stated rate 12.13 percent), with each candidate denominator shown against the highest reading. Bar length is indexed to that highest reading, so it is not itself a percentage.

The spread between the top and bottom bar is the whole commercial question. At 17.1 percent an outbound program is excellent and should be funded harder. At 6.3 percent it is ordinary and the sequence length is doing a lot of the work. Same campaign, same responses, same week, and the number a buyer would act on moves by a factor of nearly three depending on a definition nobody wrote down.

19,847
messages SaaStr reports its outbound agent sent across six months, against the 75 to 285 a month its human reps had been sending
6.7%
overall response rate reported for that six-month window, with a 4 percent positive response rate, against the roughly 3 percent the same write-up cites as the industry average
$50K to $100K
annual cost per AI sales development platform in SaaStr's account, plus 15 to 20 hours a week of human operator time across its agents
8 REPS
sales development representatives interviewed by Atlassian's Teamwork Lab across three regions in August and September 2026, in the write-up published November 9

Why The Denominator Decides The Whole Argument

Replies per message sent and replies per account reached move in opposite directions when volume rises on a fixed list, so a program can hold one steady while the other degrades, and only one of the two is connected to pipeline. Choosing between them is a strategy decision, not a reporting preference.

Here is the mechanism. Your total addressable account list is finite and it does not grow because you bought a sending tool. Adding volume on top of a fixed list means more messages per account: longer sequences, more personas per company, more follow-ups before you give up. Each extra touch is worth less than the one before it, so replies per message sent falls by construction. Replies per account reached, meanwhile, keeps climbing, because you are extracting more response from the same universe.

Both of those are real and neither is a trick. The problem is that they justify opposite decisions. A falling rate per message reads as deteriorating creative and invites a rewrite. A rising rate per account reads as a working channel and invites more budget. A team watching only the first metric cuts a program that is growing pipeline. A team watching only the second adds volume right up until the sending infrastructure gives out, which is a separate ceiling with no warning light on this dashboard at all.

Lemkin is specific about what the agents are and are not, and the sentence that travels furthest is the one about amplification.

“AI SDRs scale what's already working. They can't create something from nothing.”

Take that literally and it is a constraint, not a slogan. Scaling what works also scales what does not, and the thing most reliably scaled by a tenfold volume increase is your complaint rate. We have argued before that sending volume is the deliverability variable teams mismanage first, and an agent that writes 3,000 messages a month on infrastructure sized for 300 is the fastest route to finding out. The reply rate denominator and the reputation ceiling are the same conversation, which is why the volume case has to be argued on both at once.

Lemkin's other framing is worth keeping too, because it sets the honest expectation for autonomy. He writes that the agents do not fail catastrophically without him, they just perform at a B-plus level instead of an A-plus level, on 15 to 20 hours a week of operator attention across five of them. That is a managed system with a person in it, not a replacement for one, and it is roughly what the stop rules an outbound agent needs are designed to formalise.

What Atlassian's Own Reps Did Instead

Atlassian's Teamwork Lab interviewed eight sales development representatives across three regions in August and September 2026 and found a hard internal boundary: no AI-written communication or artifact reaches a customer or an account executive without human review first. The AI is used on preparation, not on sending.

Beth Klawitter, Atlassian's global head of enterprise development representatives, published the findings on November 9, 2026, with contributions from regional manager Toni Cadden and Lora Kassanchuk, who leads its mid-market reps. The detail that matters most for anyone reading reply rate claims is a single rep's experiment: they stopped using AI for outbound email altogether, wrote in a casual register closer to texting a friend, and booked ten meetings in a week.

One rep for one week is an anecdote and should be labelled as one. It is a useful anecdote because it is the opposite experiment from SaaStr's, run inside a large enterprise, and reported by the people who manage the function rather than by anyone selling software. Where AI clearly did help was upstream of the message: one rep went from five or six calls a week to twenty once preparation was automated. Patrick Konadu, a rep quoted in the write-up, put the limit at the thing a tool cannot do, the ability to make the customer laugh.

Notice that Atlassian publishes no reply rate at all, and that this is a defensible choice rather than an omission. A function that reviews every outbound message by hand has a volume ceiling set by reviewer hours, so its binding constraint is review capacity, and replies per message is the number it should optimise. SaaStr's constraint is list exhaustion and deliverability, so replies per account is its number. The two organisations are not disagreeing about AI. They are operating under different binding constraints and reporting the metric that matches.

How To Read An AI SDR Reply Rate Before You Buy One

Any reply rate quoted to you by a vendor, a case study or a peer is uninterpretable until you know four things: the denominator, the reply definition, the deduplication rule, and the list quality underneath it. Ask for all four before the number enters a business case.

DENOMINATORWHAT IT MEASURESWHAT ADDED VOLUME DOES TO ITWHEN IT IS THE RIGHT NUMBER
Replies per message sentEfficiency of each individual sendFalls, by construction, on a fixed listJudging creative, targeting and sequence length
Replies per account reachedCoverage of your addressable listRises until the list is exhaustedJudging whether the channel is still growing pipeline
Positive replies per account reachedQuality of the demand createdRoughly flat, it tracks fit rather than effortThe only one tied to revenue, and the one to commit to
Replies per sending domain per dayLoad on your infrastructureRises toward the reputation ceilingJudging whether more volume is safe to add at all
Negative and unqualified replies per 1,000 sendsCost of the volume you addedRises faster than positive replies doJudging when to stop adding volume

The third row is the one to commit to, and it is deliberately the least flattering. Positive replies per account reached cannot be improved by sending more, which is exactly why it is the honest measure of an outbound program. A tool that triples your sends will move every other row in this table and leave that one roughly where it was, and a vendor conversation that avoids it is telling you something.

1Make the denominator explicit in your own reporting this weekRename every reply metric in your dashboard to carry its denominator in the label: replies per message sent, replies per account reached, positive replies per account reached. The renaming alone ends most internal arguments about whether outbound is working, because it reveals that the two sides were quoting different numbers.
2Define a positive reply once, in writing, and freeze itA reply that says stop is a reply. An out-of-office is a reply. Agree that a positive reply means an expression of interest from a person in the buying group, write it down, and apply it to historical data before you compare periods. Most reported improvements in reply rate are definition drift.
3Deduplicate to the account before you compute anythingFour personas at one company replying to a five-message sequence can be counted as anything from one reply to twenty. Pick account-level deduplication, because that matches how the deal actually works, and recompute your baseline on it.
4Report replies per sending domain per day alongside the rateThis is the metric that catches the volume ceiling before your bounce data does. If it is climbing while your reply rate holds flat, you are buying the same results with more reputation risk, and the bill arrives later as filtering rather than as bounces.
5Separate list growth from volume growth in every reviewAdding 2,000 new accounts and sending 2,000 more messages to existing accounts look identical in a monthly send total and mean completely different things. Track new accounts touched as its own line, because it is the only one of the two that raises the ceiling.
6Price the operator time into any agent business caseSaaStr's figures include 15 to 20 hours a week of human attention across its agents and 50,000 to 100,000 dollars a year per platform. An agent evaluated as software rather than as a managed system will look cheaper than it is by most of a salary.
7Run the Atlassian experiment as a control armHold one segment back for a human writing in their own register, reviewed by nobody, and compare positive replies per account against the automated arm on the same list for a month. It is a cheap control, and the one result worth having is the one where the control wins.

Pick The Denominator Before You Pick The Volume

The decision in front of most outbound teams right now is not whether to use AI agents, which is close to settled, but which number they are going to be held to once they do, and that choice has to be made before volume rises rather than after.

Make it afterwards and the data no longer supports the argument. Once sends have tripled, replies per message has fallen for reasons that have nothing to do with the quality of the work, and nobody in the room can separate the mechanical dilution from a genuine decline in performance. The baseline you needed was the one from before the volume change, computed on a denominator you had already agreed on. That is a fifteen-minute job this week and an unanswerable question next quarter.

The two accounts in front of us are not actually in conflict, and reading them as a debate is the mistake. SaaStr ran a volume play on a list it was exhausting, measured it against messages, and got a defensible result it slightly over-claimed in the headline. Atlassian ran a quality play against a reviewer-hours ceiling, measured nothing publicly, and got a defensible result too. The failure mode is importing one organisation's metric into the other's constraint, which is what happens every time a reply rate crosses a slide boundary without its denominator attached.

For B2B programs the practical consequence is narrower than the discourse suggests. Volume is worth buying when your addressable list is genuinely larger than your current coverage, your infrastructure has headroom measured per domain rather than in aggregate, and your positive reply definition is strict enough that the extra sends cannot flatter it. Fail any of those three and added volume is a cost dressed as growth, and it will show up first in your deliverability and only later in your pipeline.

DO THIS NEXTToday, add the denominator to the label of every reply metric in your outbound reporting and write down a single definition of a positive reply. This week, recompute the last two quarters as positive replies per account reached, deduplicated to the account, and put replies per sending domain per day on the same chart so the reputation ceiling is visible next to the rate. Before you buy or expand an agent, demand the vendor's rate with its denominator, its reply definition and its deduplication rule, and refuse the number without all three. If you would rather hand the per-domain ceiling and the account-level baseline to someone who maintains them as standard, that work sits inside our cold email lead generation engagements, and it is the first thing any competent cold email agency should put in front of you instead of a reply rate with no denominator. Our view on what to ask an outbound partner before signing covers the rest of that conversation.
What is an AI SDR reply rate?It is the share of outbound messages or contacted accounts that produce a reply when an AI agent does the sending. The term is used for both, which is the problem: the same program can report roughly 6 percent or roughly 17 percent depending on which denominator is used.
Which denominator should we report?Positive replies per account reached, deduplicated to the account. It is the only common reply metric that added sending volume cannot inflate, which makes it the one connected to pipeline rather than to effort.
What did SaaStr actually report?Jason Lemkin's six-month write-up reports an outbound agent sending 19,847 messages at a 6.7 percent overall and 4 percent positive response rate, roughly 3,000 a month against 75 to 285 a month per human rep, at 50,000 to 100,000 dollars a year per platform.
Why do the SaaStr campaign numbers not add up?Each of the three published campaigns states a rate that matches neither replies per message nor replies per lead. The Europa campaign's 137 responses are 6.3 percent of 2,175 messages and 17.1 percent of 800 leads, while the stated figure is 12.13 percent.
Does that mean the result is not real?No. Sequencers report several reply metrics at once and sequence-level deduplication is genuinely awkward, so an operator's own write-up is not an audit. It means the figure cannot be compared against your numbers or a vendor benchmark, because they almost certainly use different denominators.
What did Atlassian find?Its Teamwork Lab interviewed eight sales development reps across three regions in August and September 2026 and reported that no AI-written message reaches a customer or an account executive without human review. One rep dropped AI from outbound email and booked ten meetings in a week.
Do AI agents improve reply rates?On the published evidence, no. Lemkin writes that response rates did not change materially over six months and that the agents were basically the same as the humans on that measure. The reported gain is volume at a roughly flat rate, which is a different claim.
When is more sending volume worth buying?When your addressable account list is genuinely bigger than your current coverage, your per-domain sending has headroom, and your positive reply definition is strict enough that extra sends cannot flatter it. Fail any of the three and volume is a cost, not growth.
What breaks first when volume rises?Sender reputation, usually before the reply rate moves enough to notice. Replies per sending domain per day is the early indicator, and it should sit on the same chart as the reply rate so the ceiling is visible before filtering starts.
How should we evaluate an AI SDR vendor's numbers?Ask for the denominator, the definition of a reply, the deduplication rule, and the list quality underneath the test. A rate quoted without those four is not a benchmark, and a vendor that cannot supply them is quoting a number it has not interrogated either.

See where you are cited today

A free snapshot audit of your rankings and AI citations before we ever talk.

TT
Tyler TruffiMANAGING PARTNER, SOMETHING INC.

Tyler leads work at the intersection of SEO and generative engines at Something Inc., helping B2B brands get ranked and cited across every major AI engine.

Keep reading

All insights →
STRATEGYYour November Bounce Data Is ContaminatedOn November 5, 2026, senders began getting hard rejections from Outlook.com, Hotmail, Live and MSN addresses, carrying the error 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records. Plenty of those senders had passing SPF and DKIM. Plenty were nowhere near the 5,000 messages a day that Microsoft's published bulk sender rule actually covers. On November 10 Microsoft's incident report said a spam enforcement rule update had caused messages to be incorrectly marked and blocked, and by November 11 a spokesperson said the bug was fixed. No postmaster notice went out while it was happening, and the bounce text pointed at SPF when a missing DMARC record was the trigger. For outbound teams the damage is not the week of blocked sends. It is that six days of Microsoft bounce data is now unusable as a reputation signal, and the standard response to a bounce spike, cut volume and rebuild domains, is the wrong move if the spike was never yours. Here is how to read those bounces, what to quarantine, and why the botched rollout still points one direction.TYLER TRUFFI · 11 MINSTRATEGYReverse DNS Is The Cold Email Gate You Do Not ControlSpamhaus updated its Sender Guidelines in October 2026 and says that starting in November 2026 it is gradually rolling out a requirement for every sending IP to have a valid HELO, a reverse DNS (PTR) record and a matching A record. Nothing in that sentence is new advice. What is new is enforcement, and the listing zones behind it are CSS and XBL, which are the ones that take an IP out of the inbox rather than into the spam folder. The awkward part for outbound teams is ownership: SPF, DKIM and DMARC are published in DNS you control, while a PTR record can only be set by whoever controls the IP. Most cold email programmes spent 2026 moving onto private and dedicated sending infrastructure to escape bulk-sender limits, and in doing so handed the one record they cannot publish themselves to a vendor they have never audited. Here is how to find out whose problem it is, by sending setup, and what to fix this week.JOSH BERNSTEIN · 11 MINSTRATEGYThe Plan You Approve Is The Only Brake You GetSalesforce announced a long-horizon runtime at Dreamforce 2026 and made Hunter, its outbound sales agent, the first thing to run on it. The runtime is built from memory, durable execution and dynamic steering, and Salesforce describes it as letting an agent pursue a goal across days and weeks rather than finishing a single task. Salesforce also built a gate: when Hunter wants to do something that deviates from the approved plan, it stops and asks. That gate is better governance than most outbound tooling has ever shipped, and it is also the whole story, because a gate that fires on deviation makes the plan you approve on day one the only real control you exercise. Approve a vague goal and you have authorized six weeks of autonomous sending on a domain you have to keep alive afterwards.TYLER TRUFFI · 11 MIN
Free consultation

Let us be the last SEO agency you ever work with

A 30 minute call and a free audit of your SEO and GEO position. You keep the findings either way.