This page is for the VP Marketing or founder being sold an AI SDR this quarter, with a sales team already saying the leads are bad. Do not buy one until you have written down who your outbound should reach, why they should care now, and what a reply has to do before it goes out.
An AI SDR, the software that does a sales development rep’s outreach, follows what it is given. With nothing written, you have no standard to reject its work against, so the dashboard becomes the only judge.
That holds for a team that has had real sales conversations by hand. If you have never booked a meeting from a cold email, you have nothing to write down yet, so send twenty by hand first. A playbook also does not explain every failed rollout: some of those teams were selling something nobody wanted.
.png)
Read this knowing who wrote it. Empact Partners is a go-to-market consultancy, and since 2020 we have worked from inside the marketing teams of B2B software companies. We now also build the agents those teams run, and that work is called marketing engineering.
Outbound belongs to our RevOps workstream, so this is an order of work we sell. It also costs us: a team that already has the document should buy the tool and may not need us.
An AI SDR Can Only Be Wrong Against Something You Wrote Down
A draft can only be wrong if somebody decided in advance what right looks like. Without that, it can be sent and it can be counted. The dashboard reports what the tool controls, how many went out and how many came back, and those numbers rise whether or not anyone should have received the email. In practice you have hired a rep who writes their own performance review every night, with a chart.
We have been on the wrong end of this. In March 2026 we scaled a cold outreach build to 3,303 contacts, and to save on model costs the pipeline used templates and find-and-replace in places where a model had been reading. It ran. Then we read what it had made.
One generic product noun, “technology platform,” appeared hundreds of times. The same few Reddit threads were offered to more than 40 companies. A find-and-replace pass had wrecked 1,247 descriptions with no way back. We tore it down that day with no email sent, and rebuilt it the next.
We had judged those drafts against a standard we had never given the pipeline. That standard is written down now: before any send, read ten at random and five rendered previews, and one that reads generic or broken stops the send.
The Fast Wins Would Have Taught An Agent The Wrong Rule
It is tempting to write the playbook from your memory of what works. Ours would have been wrong.
Before we built a system to draft replies to our own prospects, Empact Partners read every conversation we had ever had with 259 companies, including the 4,351 emails our team had written to them by hand. Agents did the reading, which is the part you can hand over. What the record meant, and which rules came out of it, stayed ours.
Read the fast wins alone and the story is speed. They closed in under two weeks, and every one of them had the proposal out within hours of the first call. Write that down and you have an instruction an agent would follow beautifully. Then put it next to the whole record:
| What we checked | Partners we won (59) | Deals still open (142) |
|---|---|---|
| Proposal within a day of the call, where both dates are on record | 26 of 45 | 49 of 55 |
| Held a call | 53 of 59 | 72 of 142 |
| No email from us after their last message | Not comparable | 57 of 142 |
Deals that stalled got the fast proposal more often, so speed is not the difference. The call is the clearest line in the record, and the silence was on our side. An agent trained on our wins would have learned speed, which we already had, and nothing in those deals would have shown it the silence in the rest.
Thirteen companies had also been written to by two to four of us within days. Nobody here had those numbers before we read them, and no sales meeting would have produced them.
What we wrote down from that came to the same three decisions:
None of that is a reference shelf for people. The system we built the next day loads those documents for every draft it writes.
The First Run Came Back As Questions
On the afternoon of 23 October 2026 we pointed the drafting agent at our open deals, with those documents loaded and one instruction for when it was unsure: say so. On 33 drafts that afternoon it asked 111 questions.
Only 17 of them asked whether a fact was still true. The other 94 asked somebody to make a decision, and the hardest of them pointed at faults in our own setup:
We had written both sides of the first two, and nobody had noticed, because a person reading two rules quietly applies the sensible one.
The other three are the plumbing our RevOps workstream exists for: the routing, the data that says which leads deserve a call, and the workflows that carry a lead from first touch to closed. A sales team saying the leads are bad is often looking at the same kind of fault: a field that means something different to everyone who reads it.
Those five mark places where a tool with nothing written has no reason to stop. It picks a sender, picks a price and writes to the bounce mailbox, and the dashboard counts one more email sent.
.png)
Most of the answers took hours, because a specific question is easy to rule on. That night we wrote the price rule, what a follow-up must carry and how attachments work. By the small hours the routing rule was in. A follow-up goes to whomever our last email went to, an answer goes from the inbox their message reached, and when the record cannot say who, the draft waits rather than guessing.
The sign-off took until 28 October, and the consultant’s own word won. Not every question deserved asking, either. The CRM record already answered some of the who-sends-it ones, so we told the agent to look first and to ask at most one thing per draft.
A Person Approving Needs The Same Document
The usual answer to all this is a human in the loop, and we run one. Since that first run, every reply and follow-up our agents have written has gone out only because a named person on our team asked for it or approved it. A suggestion lands in the company’s thread in Slack, and whoever is on it answers in plain words: send it, change this line, hold it, or I will take this one.
We did not plan it that way. On the morning of 23 October the plan was to let the agent answer on its own until a meeting was booked. That same day we found a prospect had got two emails from us, a day after we had written “one sender per company” into the playbook. A rule nobody can check does not hold. That afternoon I took sending away from the agent, and the rules we could check became code that blocks a send.
On the first run that code refused 14 drafts, 8 of them claiming an attachment that was not there and 5 quoting a price nobody had asked for. There are now five written levels of what the agent may do alone. We are on the first, and I am the only person who can raise it.
Our corrections go back into the document. On 26 October I ruled that a price question gets answered straight away, even with a report still being built. By the 27th that was a line in the reply guide the agent reads.
This costs time. Somebody reads every draft. The system started in late October 2026, and as I write we have no before-and-after number for hours or pipeline. What we can show is what it stopped.
Working with us on this starts with an audit of your stack and data flows, plus the outreach and replies your team already repeats, and we write the document from those conversations. Then one agent gets one job, a named consultant owns what it produces, and we agree the measure before anything is built: hours returned, pipeline moved, or a number your team already reports.
The Vendor’s Pipeline Numbers Are Real, So Why Wait?
Those numbers may well be real. A tool can book real meetings within weeks, your competitor may already have one switched on, and two weeks spent on a document is two weeks with no pipeline from it. Some tools earn their seat, and I would rather you heard that from me than found it out in a board meeting.
What a multiplier leaves out is what it multiplies. One exchange on Reddit in May 2026, from someone running AI outbound at a B2B SaaS company, shows the gap.
What a buyer said on Reddit
“I’ve benchmarked tools and they all promise x3 higher reply rate and all but i didn’t manage to achieve that.” — u/tchakchouka, r/sales, May 2026
“What was your reply rate before? 3x of 0 is still 0...” — u/CyberStartupGuy, r/sales, May 2026
“Before, we had qualitative reply rate around 5%, with the AI outbound its mearly a 1%...” — u/tchakchouka, r/sales, May 2026
The exchange is one person’s report, and it says nothing about what that tool could have done with better inputs. It does show the thing a promise cannot supply: a baseline you wrote down yourself.
Our own record shows how far a pipeline count flatters. When we read it, cold outreach was the source of 116 of the 142 open deals and 18 of the 59 partners we have won. Part of that gap is age, since the open deals started about 16 months later at the median, and a pipeline count cannot tell you how much.
We have been wrong about our own number too, in good faith. Nothing in our stack had ever recorded where a partner came from. When we rebuilt that from the evidence in August 2026, the largest win our April ledger had credited to cold email turned out to be a warm referral, and a message from the time said so.
| The number | What it shows | What it cannot show |
|---|---|---|
| Reply rate | People answered | Whether you wanted that answer, or what it multiplies |
| Meetings booked and show rate | Calendar activity | Whether your team can close them |
| Pipeline created | What entered the CRM | Whether a stage means the same to everyone, or where it came from |
| Deals closed, by source | The one that settles it | Nothing, but it takes a full sales cycle and a source someone recorded |
A team with nothing written down would prove me wrong if its AI SDR meetings closed at the rate of the meetings its people book, measured through to signed deals over a full sales cycle. If that is you, keep going.
Buy The Tool When You Can Reject Its Work
None of this says never buy. It says when: the day you can look at a draft, say no, and say why. You do not need 259 companies for that. One segment is enough, with three answers written before the contract:
If you can write those, buy the tool. It has something to be wrong against, its first run will read as a list of decisions, and you may not need us at all. If you cannot, no tool will write them for you, and signing only sets how fast the guesses go out.
If your team is being sold an AI SDR and nobody can yet say which of this month’s leads deserved a call, book a call with me to find out whether this is work we should do together.
