Case study: how a mid market SaaS team ran outbound to booked meetings without more SDRs
A SaaS team was blasting a bought list and getting almost nothing. What changed when every account was researched before a word went out, and the whole motion ran itself to a booked meeting.
7 min readStallwart
Illustrative scenario. Written for VP of Sales at a 40 to 150 employee B2B SaaS company. This is pre launch, so it describes how the system addresses the situation rather than results from a named customer.
Where the work was breaking
On paper the team had an outbound motion. Buy a list, load a sequence, send. In practice it produced activity dashboards and almost no meetings. Reply rates sat below one percent, the sending domain was starting to land in spam, and the two SDRs spent their days loading contacts and pasting templates rather than talking to buyers. The instinct was to buy a bigger list and hire a third SDR, which would have scaled the exact thing that was not working.
The real problem sat upstream of the sequence. Nobody had time to research the accounts, so every message said the same generic thing. To a buyer, a message that could have been sent to any company reads as a message that was sent to every company, and it gets deleted accordingly. Volume was never the constraint. Relevance was, and relevance had been quietly cut to keep the volume up.
This is the trap mid market SaaS teams fall into. Outbound looks like a throughput problem, not enough sends, when it is actually a research problem, nothing worth sending. Throughput is easy to buy. Research is the expensive part, and it was the part being skipped every single day.
What the system does instead
Extrovert AI was pointed at the same target market, but the motion inverted. For each target company and website, it researches the account first: what the business does, what it clearly runs, what changed recently, and why now might be the moment. Then it writes outreach grounded in that specific research, in the team's voice, and sends it. Nothing goes out that could have been addressed to anyone else.
Follow up fires on the cadence each account's engagement justifies and adapts to replies, so no thread dies because a rep forgot the fourth touch. Responses are read and scored on real buying intent rather than politeness, and qualified conversations are booked straight onto the reps' calendars.
It also declines. Accounts that are plainly not a fit are skipped rather than blasted, which protects the sending domain the team had been slowly burning. The whole motion optimizes for a booked meeting, not for send count, which is the number that actually pays the team.
Why researched outbound protects the whole channel
Generic blasts do not merely underperform. They teach inbox providers to distrust the sending domain, which drags down the messages that would have worked. Deliverability is a reputation, and a reputation is spent every time a batch of irrelevant mail generates spam complaints instead of engagement.
By sending fewer, researched messages to accounts that actually fit, the domain's reputation recovers and the good messages start arriving again. Relevance and deliverability are the same lever seen from two sides: the outreach that earns a reply is also the outreach that keeps the channel alive.
What changed for the reps
The two SDRs stopped loading lists and pasting templates. Their day moved from assembling outbound to taking the conversations outbound produced. The work that genuinely needs a human, discovery and qualification on a live call, is the work they now spend their time on.
The administrative layer that used to eat the day, the research nobody had time for and the follow up nobody remembered, is carried by the system. Outbound volume can now grow without adding SDR headcount, because the part that used to require another person is no longer done by a person.
What actually changes
- Outbound stops being a volume game. Every account is researched before a message is sent, so relevance is the default rather than the exception.
- The sending domain recovers, because researched, well-targeted outreach is not what trains inbox providers to route a domain to spam.
- Rep time moves from assembling sequences to taking booked conversations, and outbound volume grows without adding SDR headcount.
We publish numbers once a customer has verified them. Nothing here yet, which is the honest answer.
Questions this raises
- How can a SaaS team improve outbound reply rates?
- By researching each account before sending rather than blasting a bought list. Reply rates collapse when every message is generic and recover when each references something specific and true about the account. An AI SDR does that research on every prospect, which is the step human reps skip under quota.
- What is account based outbound?
- Outreach built from research on the specific account rather than a template sent to a list. Each message references something true about that company, which is what earns a reply. AI makes it possible to run account based outbound at list scale, because the research no longer has to be done by hand.
- Does AI outbound hurt email deliverability?
- Done badly, any outbound hurts deliverability, because generic blasts get marked as spam and train inbox providers to bury the domain. Done well, researched outbound to accounts that fit protects deliverability, because it generates engagement instead of complaints. The differentiator is relevance, not volume.
- Does this replace our SaaS CRM?
- No. Extrovert AI connects to the CRM the team already keeps and runs the outbound motion on top of it, so reps keep their existing system of record while the research, outreach, follow up, and booking are automated.
Recognise this in your own operation?
Bring us the version of it happening in your business and we will tell you which part a system can take over.
Book a Call