Join the waitlist
Menu
Free guide

The AI SDR buyer's guide

Every post from the Dylan blog in one designed PDF: what survived the AI SDR hype, how to brief one, small markets, deliverability, AI disclosure, held meetings and how they are billed.

39 pagesPDF, 0.8 MBEdition of

Get the PDF.

The download starts on this page. We email you the link only if you ask.

We keep your email and copy it to the lead sheet the Belkins team reads. No marketing email unless you tick the box. Privacy

The first page. Every chapter is also on the blog.
Contents

What is inside

  1. Chapter 1: The AI SDR hype is over. Here is what actually survived

    AI SDRs promised to replace sales teams. Most early rollouts disappointed. What survived: proven playbooks, signals, people at decision points, inbound.

    4 min read
  2. Chapter 2: How to brief an AI SDR so it books the right meetings

    A brief decides who gets emailed, what they read and which meetings count. The seven inputs that matter, and why to edit a draft instead of writing one.

    4 min read
  3. Chapter 3: Enterprise outbound math: your market is a pond, not an ocean

    Only 1,138 US companies have 10,000+ employees. The outbound math for small markets, why precision beats volume, and what to do when the list runs out.

    4 min read
  4. Chapter 4: Cold email deliverability in 2026: the rules that matter for B2B

    Gmail's bulk sender rules get the headlines, but B2B cold email is decided by corporate gateways, Microsoft tenant limits and new-domain checks.

    4 min read
  5. Chapter 5: AI disclosure in cold email: why Dylan says he is an AI

    Every first email from Dylan says he is an AI agent and who he works for. Why we disclose, what the EU AI Act and CAN-SPAM say, and how to stop him.

    4 min read
  6. Chapter 6: What counts as a held meeting, and what never gets billed

    Booked, held and qualified are three different meetings. How Dylan defines a held meeting, what is never billed, and how disputes and the deposit work.

    4 min read
  7. Chapter 7: Pay per meeting: why Dylan charges only for meetings that happen

    Retainers, seats and per-lead pricing leave you holding the risk. Why Dylan charges per held meeting instead, and where outcome pricing can go wrong.

    5 min read
  8. Chapter 8: Agents judge, people approve, code protects: how Dylan is built

    How Dylan splits the work: AI agents make the judgment calls, people approve what goes out, and plain code enforces the rules that must never bend.

    4 min read

33 minutes of reading in all, across eight chapters.

Get on Dylan's calendar.

Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing.

Already know your definition? Send the full brief