10 Things to Know Before Your First AI SDR Rollout

SaaStr’s 10-Point Operational Playbook for AI SDR Deployment

SaaStr’s Amelia (Head of GTM Operations) and Jason Lemkin (Founder & CEO) distill 10 months of running AI SDR agents across Artisan, Qualified, Agent Force, and Monaco into a concrete deployment checklist. This isn’t theory — it’s the operational manual from a team that has sent 200,000+ messages across four AI SDR platforms simultaneously.

Use what already works. “It does not need to be the best email on planet Earth. Consistency beats brilliance.” SaaStr’s first rule: feed your AI SDR the exact copy, subject lines, and messaging that already converts with humans. Don’t reinvent — replicate what’s proven, then let the agent run it at scale. 40,000 messages via Artisan, 100,000 via Qualified, 200,000 via Salesforce Agent Force — none of those started from scratch.

Start with low-risk, high-value leads. The smartest first deployment isn’t your hottest pipeline — it’s the leads nobody is working. Old leads, lapsed customers, sponsors who haven’t logged in. Amelia describes building a micro-agent for their SaaStr sponsor portal that checks who hasn’t logged in and sends automated nudges. “It’s unglamorous work, but the sponsors are happier with more regular check-ins. They get a response faster.” The result: less than a tenth of the agency hours compared to the previous year.

Segment ruthlessly — then segment again. SaaStr runs approximately nine segments per campaign with around a thousand contacts each. Amelia updates segments literally every day: website visitors, email openers, lapsed customers, current sponsors. The key insight: even their inbound Qualified agent, which started as “one big brain,” was eventually split into sub-segments — brand new visitors, ad-driven traffic, former sponsors, current customers. Tighter context produces dramatically better conversations.

You need two humans, not zero. Every AI SDR requires daily check-ins of 10 minutes to an hour. Multiply by 4+ agents and the human manager becomes the bottleneck. SaaStr’s mandate: minimum two people managing agents, because if one leaves, all institutional knowledge walks out the door. When Amelia’s time got split during SaaStr Annual production, agent performance visibly degraded.

Read everything your agent says — especially in the first 30 days. Amelia still reads agent output daily after 10 months. Early catches included: misspelling “SaaStr” with lowercase S’s, using outdated event dates scraped from the web, and missing subject line rules. She now filters for escalations and frustrated users rather than positive interactions: “I actually only care now if they say something bad or if they need an escalation.”

Most people prefer chat over voice/video. SaaStr’s multimodal agent (Amelia AI with video avatar via Tavus on Qualified) shows an 85/15 split — 85% choose chat, 15% use video. Voice and video require more guardrails because users ask personal questions, try prompt injection, and go off-topic. Jason’s advice: get chat working first, add video later once you have a quarter of data on what people actually ask.

10 Deployment Rules from 200,000+ AI SDR Messages

• Use proven copy — feed the agent messaging that already works with humans, don’t start from scratch
• Start with neglected leads — old leads, lapsed customers, and low-risk re-engagement are the ideal first deployment
• Segment ruthlessly — ~1,000 contacts per campaign, update segments daily, split even inbound into sub-segments
• Consistency beats brilliance — “pretty good” at 24/7 scale outperforms perfect-but-inconsistent human output
• Two humans minimum — one person managing all agents is existential risk; agents idle without daily feeding
• Read everything for 30 days — then do a daily 10-minute speedrun checking for errors and escalations
• Budget 2 weeks ramp — nothing is instant; domain warmup, segmentation, and calibration take real time
• Chat first, voice later — 85% prefer chat; video adds fun but needs more guardrails and isn’t day-one priority
• Avoid person-dependent deployments — what happens to your AI avatar agent if that person leaves?
• Your data must work first — 10-20K monthly visitors for inbound; 1,000+ contacts minimum for outbound

What Operators Need to Know About AI SDR Economics

The threshold is higher than most expect: 10,000-20,000 monthly website visitors minimum for inbound AI SDR to be worthwhile, and a continuously replenishable list of 1,000+ contacts for outbound. SaaStr’s 1.5 million sessions on Qualified in six months shows the scale these agents reach once deployed — and why the human management layer can’t be an afterthought. The operators who invest in segmentation, daily reading, and two-person coverage are the ones getting 70% open rates on ghosted leads and 15% of event revenue from AI.