What an AI SDR actually has to do
Strip the hype and an AI SDR is a pipeline with seven stages:
Every stage has to work — the pipeline is only as good as its weakest link.
The stages are not equally hard. Finding and sending are commodity problems with mature tools. Research quality, reply handling, and deliverability discipline are where builds live or die — keep that in mind as we walk the DIY route.
The DIY stack, piece by piece
| Component | Tool | Monthly cost |
|---|---|---|
| List building & enrichment | Clay | $149–800 (Growth: $495 for 6,000 credits) |
| Sending & inbox rotation | Instantly | $30–47 entry |
| Sending (alternative) | Smartlead | $39–379 |
| Drafting | LLM API (Claude or GPT) | ~$20–100 in usage |
| Automation glue | n8n or Make | ~$20+ |
| Extras | Separate domain, email validator, CRM | Varies |
| Your time | You | The biggest line item — see below |
List building and enrichment: Clay is the default choice — spreadsheet-style workflows over dozens of data providers, with waterfall enrichment so you only pay for hits. Plans run $149–800 per month; the popular Growth tier is $495 for 6,000 credits. Credits go faster than you expect once you chain enrichment, validation, and research columns.
Sending: Instantly ($30–47 per month entry) or Smartlead ($39–379 per month) handle inbox rotation, warmup, and scheduling. Drafting: an LLM API — Claude or GPT — called with your ICP context, the prospect's research, and a tight style prompt. Budget real prompt-engineering time here; the default output of any model is recognizably AI and will get ignored.
Glue: n8n or Make to wire it together — webhooks from your site or Clay into the LLM, drafts into the sender, replies back into Slack or your CRM. Plus a separate sending domain (never your main one), an email validator, and a CRM to keep state. Total subscription cost lands roughly $250–1,400 per month depending on volume, before your time.
The real cost is the build and the babysitting
Expect one to three weeks of focused work to get a first version live: designing the Clay tables, writing and testing prompts, wiring the automations, configuring DNS and warmup on the new domain. That is the fun part, and if you are a GTM engineer at heart you will enjoy it.
The recurring cost is maintenance. Providers change APIs, Clay columns silently error, a prompt that worked on one segment writes nonsense on another, warmup schedules need adjusting, and reply handling needs constant tuning. Realistic steady-state is several hours per week of operating time. That is fine if this is your craft; it is a hidden full cost if you just wanted meetings.
Where DIY builds break
Deliverability discipline is the number-one killer. The glue-stack happily lets you send 500 emails a day to unverified addresses from a two-day-old domain, and nothing stops you until reply rates crater and you discover your domain is on a blocklist.
Reply handling is the second failure point. Most DIY builds automate sending well and then dump replies into an inbox where they age for days — which forfeits the entire timing advantage. Correctly classifying "interested, but can you explain pricing?" versus a polite brush-off, and answering with real product context, is genuinely hard to build.
Research quality is the third. At demo scale you handcraft great research columns; at production scale the long tail of prospects gets thin, generic inputs, and the LLM writes thin, generic emails from them. Garbage research in, spam-shaped email out — reply rates converge back toward cold-list numbers.
Deliverability guardrails every build needs
These are non-negotiable regardless of what you build or buy:
- 1Send from a separate domain, not your primary — a suspension or blocklisting must never touch your transactional and team email.
- 2Configure SPF, DKIM, and DMARC before the first send.
- 3Warm the domain up over roughly ten days, ramping volume gradually from a small floor rather than starting at full speed.
- 4Cap volume at around 200 emails per day per sending domain, across all campaigns combined — not per campaign, which is how teams accidentally stack five campaigns into 1,000 daily sends.
- 5Send only to verified valid addresses; hold catch-all and unknown results for review, because bounces are the fastest way to burn a domain.
- 6Suppress hard bounces and complaints automatically and permanently.
- 7Include a working unsubscribe and your sender identity on every message — the law under CAN-SPAM and the honest-legitimate-interest bar under GDPR, and it keeps complaint rates down.
Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher.
The legal floor is documented in the FTC's CAN-SPAM compliance guide and, for European contacts, at GDPR.eu; Google's bulk sender guidelines set the practical deliverability bar. We cover the full setup in our deliverability guide. BusinessMCP enforces every item on this list mechanically: verified-only autonomous sending, the 200-per-day domain cap, a ~10-day warmup ramp, automatic bounce and complaint suppression, and unsubscribe plus sender identity appended to every email.
The one-click route
The alternative to assembling the stack is buying the outcome. BusinessMCP's AI SDR starts at $199 per month on the Scale plan, month-to-month: you describe your ideal customer in plain English — who you sell to, who to avoid, your dream accounts — and it runs the whole pipeline: discovery, waterfall enrichment through Hunter, Findymail, LeadMagic, and Prospeo preferring verified emails, per-prospect research, human-sounding multi-channel sequences, reply classification with an auto-sent booking link, and the CRM and analytics underneath.
The structural difference from the DIY stack is that it is warm-first: because the same platform runs your website analytics, it starts outreach from companies already visiting your site — the highest-precision signal there is — before spending anything on colder discovery. A Clay-plus-sender stack has no native view of your traffic.
Modes matter for trust:
- Manual — drafts only; nothing sends without you.
- Assisted — you approve each send.
- Autonomous — it sends within the guardrails.
Most teams start assisted for a couple of weeks, audit the drafts, then graduate campaigns to autonomous.
Build or buy: a straight answer
Build if outbound tooling is genuinely your craft — you enjoy operating Clay tables and prompts, you need exotic workflows a product will not support, and the weekly maintenance hours are a feature of your job rather than a tax on it. GTM engineers at later-stage companies with unusual data needs are the honest build case.
Buy if what you want is meetings. If the sentence "a provider changed their API and my enrichment column has been silently failing for nine days" fills you with dread rather than interest, you want the packaged outcome. At $199 per month against $250–1,400 in DIY subscriptions plus hours of weekly operation, the buy case is usually cheaper in total cost, not just easier.
Frequently asked questions
How much does it cost to build an AI SDR yourself?
Subscriptions land roughly $250–1,400 per month: Clay at $149–800, a sender like Instantly ($30–47 entry) or Smartlead ($39–379), LLM API usage, an automation tool, an email validator, and a separate domain. The bigger cost is time — one to three weeks to build and several hours a week to operate.
Can an AI SDR fully replace a human SDR?
It replaces the repetitive 80% — list building, enrichment, research, drafting, sequencing, and first-pass reply handling. Humans stay essential for live conversations, complex objections, and strategy. Given a human SDR runs $60k–90k fully loaded, the economics of automating the mechanical layer are hard to argue with.
What is the single most common way DIY AI SDR builds fail?
Deliverability. Homemade stacks let you send unlimited volume to unverified addresses from a fresh domain, and nothing intervenes until you are blocklisted. Verified-only sending, a ~200 per day per domain cap, a warmup ramp, and automatic bounce suppression have to be enforced mechanically, not by good intentions.
Do I need a separate sending domain for an AI SDR?
Yes, always. Outreach carries inherent reputation risk, and a suspension or blocklisting on your primary domain takes down transactional email, password resets, and your team's deliverability with it. Use a sibling domain, configure SPF, DKIM, and DMARC, and warm it up before real volume.
What should an AI SDR do with replies?
Classify them (interested, question, objection, not-now), answer questions with real product context, send interested prospects a booking link within minutes, and suppress opt-outs permanently. Reply handling is where the meeting actually gets won — a build that automates sending but leaves replies aging in an inbox forfeits the point.
Sources
Richard Hopp
Founder of BusinessMCP. Every guide is written from running BusinessMCP on its own platform — the match rates, reply rates, and deliverability lessons are from our own data, not recycled blog folklore. About Richard
Turn your business into one AI-ready MCP server
Connect your tools, install one tracking script, and expose your unified data to any AI agent through a single secure endpoint.
Get started free