What an AI SDR Needs Before It Sends

What the job actually is
A human SDR researches accounts, writes first touches, qualifies replies, and hands a meeting to someone who closes. An AI SDR is that sequence run by software, with a person still responsible for the offer, the list rules, and the deals that are too specific to automate. The homepage that ranks first assumes you want its agent. A builder needs the split the homepage skips.
Three parts, and only one of them sends:
The record. Who the person is, whether the company is the one you mean, whether the address is real, and whether there is a reason this month. That is data.
The judgment. Which record is worth a message, what the first line should rest on, and when to stop. That is the agent.
The send. The sequencer, the dialer, the LinkedIn step, the CRM task. That is the tool the team already runs.
If you buy part three and call it an AI SDR, you have a mail merge with a new label. If you buy part two and feed it a guessed name, you have a faster way to burn a domain. The page that ranked will tell you its agent will not email a random list. That is a product promise. It is not a spec you can hand your own agent.
What that homepage states, and what it does not
Opened on 2 Oct 2026, aisdr.com says the agent finds people in real time, writes the message, qualifies replies, and books. It says it will not blast ten thousand emails, will not replace your SDRs, and will not send without a reason. In the objection section the page itself puts $900 a month next to a comparison with a $6,000 a month SDR and an $1,800 a month tool stack. Those are figures on that page that day. They are not a category price, and they are not a quote from Prospect Desk.
The same page claims results in the range of one to three qualified meetings per 100 leads, and a lead-to-demo rate, and meetings booked for clients in 2025. Treat every one of those as the vendor's claim. Do not put them in your plan until you have run your own accounts.
What the homepage does not do is tell a company that ships an agent how the record should look before the agent is allowed to write. That is the gap. The Salesforce explainer further down the results, dated 12 Feb 2026 on its own byline, describes AI prospecting as automation of outreach and qualification. It is useful as a map of tasks. It is still written to land on Agentforce. Neither page is a contract for the data underneath.
Named people, from records you own
Start with rows you already have a reason to hold. Customers, trials, inbound, and accounts a seller is working. An AI SDR that begins by inventing a fresh list of strangers is a list rental with a chat window. Identity resolution is the call that says these signals are one person at one company, or that they are not. The contract for that call is the identity resolution API. The person payload is the people data API. The company payload is the company data API. Enrichment of a row you already have is the data enrichment API.
A miss is a successful response. If the score is low, the agent does not get a name. Forcing a match is how the wrong person enters the tool that sends. Search that returns a population is not the same call as enrich that returns one person. Do not pour a search into a sequencer and call it development.
Verified reach
The address, if you hand one over, carries its own status. Deliverable, catch-all, invalid, or unknown are different facts. Catch-all is not a yes. Pattern-based guesses are a hypothesis, then a check, not a CRM field. Partner volume goes through the email verification API. A person checking one address uses the free email verifier. That tool is not the API and not an append service.
The ranked homepage talks about deliverability as something its team watches. Good. Your agent still should not be the thing that discovers a dead inbox by sending. Verification happens before the row is eligible.
Why now, on a record you hold
"Why now" is a signal attached to an account you already resolved. A job change, a hiring spike, a page visit, a topic the account is researching. It is not a reason to buy a new file this week. Intent audiences are a set of accounts that share a signal, handed to the tool that already advertises or sequences. They are not a blast list.
If the only signal your agent can see is "this title matches the ICP," you do not have a why-now. You have a filter. Filters are fine for who is allowed into the pool. They are a weak reason to write the first line. The B2B data provider page is the buy decision when someone is selling you a file instead of a call. This page is the agent that will consume the call.
Where the row has to land
The agent should write back into the system that already sends. A CRM, a sequencer, a dialer queue. If the only place the meeting can be booked is inside a new login, you bought a prospecting product. That can be the right buy for a team with no tool yet. It is the wrong buy for a partner whose users already live somewhere else.
Prospect Desk does not send the email. Verified reach means the address is worth handing over. It is not consent, and it is not a sequence.

Who this is for
Build it if you are the company shipping the agent, or the operator wiring one into a stack you already run. You need a record that can be refused, a status on the email, and a signal that is dated.
Buy a finished agent, the kind of homepage that ranked first, if you want someone else's judgment and someone else's send, and you have read their price on their page. Do not buy that seat because the query is "ai sdr" and the first result is a brand. The query is generic. The result is not.
Do not build it if success is "messages sent." The homepage that ranks is right about one thing: volume without a reason is noise. It is wrong if you hear that as "therefore use our agent." The test is whether your own twenty accounts come back as the right people, with emails you would let a human send.
A build order that survives the first week
Write the offer in one sentence. If you cannot, the agent will invent one.
Define the accounts you already hold. Twenty is enough. Run them through identity first, then email status, then a why-now you can point at. Count false fills. A column that is never empty is a smell.
Pick the tool that will send, and confirm the row can land there with the status attached. If it cannot, stop. Do not add a second sequencer to "use the data."
Only then let the agent draft. A human reads the first fifty. You are checking whether the draft rests on a field that exists, not on a vibe.
Measure replies that a person would take, bounces, and meetings that show. Ignore a vendor's per-hundred claim until your twenty look like your market.
Automated prospecting is the rules version of this, triggers without an agent. AI sales prospecting is the wider workflow, including tools that are not an SDR at all. Keep the three URLs separate.

FAQ
What is an AI SDR?
Software that researches a person, writes the first touches, follows up, and books a meeting. The record underneath it is a separate product. The tool that sends is a third.
Is an AI SDR the same as a prospecting database?
No. A database returns people. An AI SDR decides and writes. If the database is wrong, the writing is confident and useless.
Does this replace a human SDR?
Not by itself. It takes the repetitive first pass. A person still owns the offer, the edge cases, and the conversation that is no longer a template. The brand page that ranks says it will not replace your SDRs. That is their positioning. Your design should assume a human can stop a send.
Can the data layer send the email?
No. It returns a named person or a miss, a verification status, and a why-now on a record you own. The partner's tool sends. Book a call when you are embedding that layer, not when you want a sequencer.
What should a low match do?
Return nobody. Do not let the agent invent a first name so the sequence can stay full.