Do AI SDRs work? What the public record says, and why we do not use them

We do not use AI SDRs on client work. The category was built for a volume problem, and account-based clients bring a precision problem. Digital Applied's 2026 benchmarks show one AI SDR seat sending 7,400 touches a month against 1,150 for a human SDR. The AI seat gets four times the replies and fewer qualified opportunities: 3.3 a month against 4.4.

The number the category sold on, and the number underneath it

The raw reply rate fell from 4.7% to 2.9%, but on that volume the AI seat still collects 215 replies a month to the human's 54. Anyone who says the category simply did not work is skipping that line. The loss comes after the reply: fewer replies are positive (0.9% against 1.3%), and 28% of the AI seat's meetings become opportunities, against 47% of the human's. Salesmotion, which repeats these figures, adds that about 1 in 6 emails now never reaches the inbox.

The hybrid pod, one person working with two AI seats, produced the most opportunities per seat: 7.5. That is the strongest case against our position, and it is still a volume result, at 5,260 touches per seat a month.

Six times the volume is not on the menu in account-based work

A program of 120 named accounts with six people worth contacting at each has 720 people in it. You cannot send 7,400 emails a month into that; you can only send the same people the same thing more often. Salesmotion's agency guide puts the working range for a team of two or three marketers at 50 to 200 target accounts. A throughput machine does not help a job with a throughput ceiling.

What the record says about the vendors

Refonte Learning's comparison of Clay, 11x and Artisan collects the reporting on 11x. TechCrunch reported in March 2025 that ZoomInfo ran a one-month trial and did not proceed, judging 11x below its own SDRs, and that Airtable's brief trial did not reach production. Sifted later reported sources alleging retention of roughly 20 to 30% during part of 2024. 11x disputed those allegations and said it had hundreds of customers receiving value.

What survives the dispute is two named pilots that did not convert.

The bill arrives at your domain

Digital Applied also found that 47% of attempted AI SDR deployments hit a domain-reputation problem within 90 days. If your buyers are on Microsoft 365, the 18.7% is the number that applies to you.

The vendor's reputation is not at stake in your sending. Your domain is, and it is also the address your invoices and renewal notices go out from. The checks are in the sender rules.

Clay is a different thing

Refonte calls Clay "unusually strong as a prospect-data, enrichment, research, and GTM-orchestration layer", and Salesmotion lists it as the build-your-own option. The line we care about is whether software decides who to contact and then presses send. Enrichment and research stop short of it. An autonomous SDR is defined by crossing it.

What we do instead

The machine reads and drafts, a person checks, and nothing is sent unread.

• The list is small and named, in the 50 to 200 range, with a written reason for each account. That method is its own post: how to build an account list you can defend.
• Research is generated, then checked. A model can read an annual report and a quarter of press coverage. A person checks every fact that will appear in the email against its source.
• A model drafts each email from the research, and a person edits and approves it, and that person is on the reply.
• The list caps the volume, so there is no throughput target to spend reputation on.
• The client owns the domain and the data, including the replies that say no.

Where we use AI, and where we stop, is in where AI helps in account-based marketing.

Where we stand

None of this says autonomous outbound never works. If your constraint is that you are not contacting enough people, a throughput tool is worth evaluating, and you should read the vendors' own defenses beside the reporting above. If the constraint is that the forty accounts that matter do not know who you are, more sending will not fix it, and it can cost you the domain you need for the fix. Tell us what you are trying to fix, or see how we run account-based outbound.