AI agents for sales development reps: what works, what doesn't.

Q: What does an SDR’s day actually look like?

Six hours of repetition: research the prospect (LinkedIn, company news, recent triggers), draft a personalised outbound email, log activity in CRM, follow up at the right cadence, repeat 30-50 times [cite: https://en.wikipedia.org/wiki/Sales_development · 2026-04-10 · medium].

The other two hours are calls with the people who responded. That’s the high-value work. The first six hours is the bottleneck.

Agents can absorb most of the six hours. The trick is which parts.

Q: What can an agent reliably do?

Three concrete tasks, in order of confidence:

1. Research synthesis (high confidence)

Agent reads LinkedIn profile, company website, recent news, and the prospect’s last 10 social posts. Outputs a 5-line summary the SDR can use to personalise the email.

This is the highest-leverage agent task in SDR work. The research time drops from ~10 minutes per prospect to ~30 seconds. Quality is consistently higher than what an SDR pulls together at 3pm on Friday.

Tools: Apollo or ZoomInfo for the firmographic data [cite: https://en.wikipedia.org/wiki/Sales_intelligence · 2026-03-25 · medium], Claude with web search for the news + social.

2. Email drafting (medium confidence — needs review)

Agent takes the research summary plus the SDR’s outbound template and produces a personalised email draft. The SDR reviews, edits, sends.

The agent doesn’t send. That’s the discipline. The cost of one bad outbound email at scale is sender reputation damage that takes weeks to recover from [cite: https://reddit.com/r/sales/comments/1sxj6s3/ · 2026-04-15 · medium].

3. CRM data entry (high confidence)

After the SDR sends the email, the agent logs the activity in Salesforce / HubSpot, updates the prospect status, schedules the follow-up reminder. This is glue work. Agents are good at it.

Tools: the CRM’s REST API, structured JSON output from Claude to populate the fields [cite: https://docs.anthropic.com/en/docs/build-with-claude/structured-outputs · 2026-04-15 · high].

Q: What can’t an agent do?

Three failure modes:

1. Autonomous outbound sending

The “AI SDR” SaaS tools that send without human review fail in production. Reddit threads document repeated cases where:

• The agent personalises with stale data and looks dumb (offers congratulations on a 3-year-old promotion)
• The agent uses sender domains that get flagged for spam at scale
• The agent’s “personalisation” patterns are similar enough across emails that recipients realise they’re templated [cite: https://reddit.com/r/sales/comments/1sxj6s3/ · 2026-04-15 · medium]

The pattern that wins: agent drafts, human approves, tool sends.

2. Reading social signals

Agents are bad at the soft intel SDRs use to time outreach. “She just got back from maternity leave; don’t pitch this week” is the kind of judgement humans make from cues that don’t surface in structured data.

This is fixable over time as agents get better at multi-modal context. As of 2026, it’s still a human edge.

3. Negotiation

Anything past the booked-meeting stage is human. Discovery calls, pricing conversations, contract negotiation — these aren’t SDR work, but the line gets blurry. Agents are tools for high-volume top-of-funnel; they shouldn’t be in the closing conversation.

Q: What’s the practical agent stack?

Apollo (data)
    │
    ▼
Claude Sonnet 4.5 (research synthesis, email drafting)
    │
    ▼
Human SDR (review, send, calls)
    │
    ▼
HubSpot / Salesforce API (CRM logging via structured Claude output)

Total tooling cost (small team): ~£300-£500/month for Apollo data + ~£20-£40/month for Claude API at typical SDR volume.

That replaces the manual research / drafting / logging cycle. The SDR spends their time on calls and edge cases instead of typing.

Q: How do you measure if it’s working?

Track the SDR-level metrics, not the agent-level metrics:

• Meetings booked per week (the actual outcome)
• Reply rate on outbound (quality signal)
• Spam complaint rate (don’t blow up the domain)
• SDR time-on-calls vs time-on-research (the time you saved)

Don’t track “agent calls per day” or “tokens used” as your primary metric. Those are inputs. Track the outputs.

Q: What about “AI SDR” SaaS?

Be sceptical. The category has a credibility problem in 2026 [cite: https://reddit.com/r/sales/comments/1sxj6s3/ · 2026-04-15 · medium]. Issues:

• Many of them are GPT-4 + an outbound sender behind a fancy dashboard
• The “personalisation” is templated in ways recipients can pattern-match
• They burn sender reputation across customers

If you’re going to use one, evaluate the actual emails it generates against blind email-from-human samples. Most fail this test.

The DIY stack with Claude API + your own approval gate beats most “AI SDR” products on quality.

Q: Where does this go from here?

The next 12 months will likely see:

• Better integration between LinkedIn-style social signals and outbound timing
• More structured “researcher agents” that build prospect profiles and feed the SDR
• Continued failure of “fully autonomous” SDR products (the trust-cost economics don’t work)

The job of the SDR doesn’t disappear. The job becomes “operator of an agent stack” — fewer hours typing, more hours on calls, similar comp.

Sources

• Wikipedia: Sales development
• Wikipedia: Sales intelligence
• Anthropic structured outputs documentation
• HubSpot API documentation
• Salesforce API documentation
• r/sales: AI SDR product war stories
• r/SaaS: practical agent stacks for sales