Scouty runs on Mermail

Explore
Back to blog
Growth6 min read

Buy an AI SDR or Build Your Own Sales Agent? A Builder's Guide

Sending was never the hard part of sales. Here is how to decide between buying an AI SDR and building your own, and how to build one that reads its replies.

By Toan Nhu

Mermail field guide cover reading Build your own sales agent., with a four step flow of research, draft, approval and reply loop

A founder I talked to last month trialed an AI SDR for three weeks. It sent a lot of email. Then a prospect replied with a real question about pricing, and the tool answered with a cheerful follow-up that ignored it. The founder spent the next morning apologizing by hand.

Sending was never the hard part of sales. Reading the reply, understanding it, and answering like someone who was paying attention is the job. That is the lens to use when you decide whether to buy an AI sales agent or build your own.

What an AI sales agent actually does

Strip the marketing away and a sales agent runs five steps:

  1. Find accounts and people that fit your ideal customer.
  2. Research each one enough to say something specific.
  3. Write a first message and a short follow-up.
  4. Send from an address that can take replies.
  5. Handle replies: answer questions, route the interested ones to a human, stop when someone says no.

An "AI SDR" product usually bundles all five with a prospect database. A sales agent you build yourself can do the same, but you choose each part.

Buy or build: an honest test

Buy when your motion is standard outbound, your team has no engineer to spare, and you are happy with the vendor's data, tone and sending setup. You get speed and lose control.

Build when any of these is true:

  • Your best signal is in your own product data or CRM, not in a generic list.
  • Replies need product knowledge a generic tool will not have.
  • You want a person to approve every first message.
  • You need to know exactly which address sent what, and why.
  • You already run agents in Claude, Cursor, Codex or a framework, and want sales to be one more skill.

Most small teams land in the middle: build a narrow agent for one segment, keep a human on every send, and expand only when replies look good.

Why most sales agents fail on email

The model is rarely the weak point. The plumbing is.

  • They send from a mailbox that cannot think about replies. A sending service fires messages out; answers land somewhere the agent never reads.
  • They borrow a person's inbox. Now the agent can read everything else in that account, and every mistake goes out under a colleague's name.
  • They send at volume on day one. A new domain with no history and a sudden spike of cold mail is a fast route to the spam folder. See Why AI Agent Emails Land in Spam.
  • They skip consent and opt-outs. That is a legal problem, not just a tone problem. Start with Can Your AI Agent Legally Send That Email?.

The parts you need to build one

  • A brain. Any model or agent framework you already use.
  • Prospect data. Your own list, your CRM, or a research tool you pay for separately.
  • A mailbox the agent owns, on a domain whose reputation you can afford to build slowly.
  • An approval step between "draft written" and "email sent".
  • A reply loop that notices new mail, reads the whole thread, and decides: answer, hand off or stop.

Mermail covers the mailbox, approval and reply loop. It does not sell prospect data, and a paid plan does not authorize outreach on its own.

Build it with Mermail, step by step

1. Give the agent its own sender

Create a mailbox for the sales agent in the Mermail console or with the API. For real outreach, use a custom domain on a dedicated subdomain such as mail.example.com, and test both sending and receiving before the first campaign. Give Your AI Agent an Address on Your Own Domain covers the setup.

2. Connect your agent over MCP

Connect Mermail MCP with OAuth from Claude, Cursor, Codex or another MCP client, then confirm which mailbox to use:

text
Check my Mermail MCP connection and list the mailboxes I can use.
Do not send any email or purchase anything yet.

3. Research a small, sourced list

Start with contacts you already have permission to approach, or research a handful of businesses. Ask for a source for every contact, and forbid guessing:

text
From the list I gave you, pick 5 companies that match our ideal customer.
For each, show the website, the public contact address, the source URL
and one specific reason they might care. Do not guess names or emails.

4. Draft, do not send

Have the agent save each first message as a draft in the agent's mailbox:

text
Write one short email for each approved contact from my sales mailbox.
Use only the product facts I gave you and the sourced company facts.
Include a clear way to opt out. Save them as drafts. Do not send.

Open the drafts in Mermail and check sender, recipient, claims and links.

5. Approve by name

Send only what you reviewed, and say so explicitly:

text
Send only the three drafts I just approved, unchanged. Leave the rest.
Report the result for each one.

A saved draft is not a sent email, and a successful send does not guarantee a reply. If a send result looks uncertain, check Sent before trying again so nobody gets the same email twice.

6. Close the reply loop

Subscribe a webhook to message.received for the sales mailbox, or have the agent check the inbox on a schedule if you cannot host an endpoint (see When Your Agent Can't Host a Webhook, Poll Its Inbox). For each reply, have the agent read the whole thread, label it, and save a draft answer for you to approve. Plain-language labels make triage easy; see Sort Every Reply Automatically. Anyone who opts out goes on your do-not-contact list before the next run.

Where sales agents still fail

  • Confident wrong facts. If the agent invents a customer or a feature, prospects notice. Give it a short, approved fact sheet and nothing else.
  • Follow-ups that ignore the reply. Always draft follow-ups from the thread, never from a schedule alone.
  • Volume before reputation. Ramp slowly. How Much Email Should an AI Agent Send? has a pacing plan.
  • No human at the handoff. An interested reply is the moment a person should take over.

Ready to build yours? Create a sales mailbox in the Mermail console and run steps 1 to 5 on five contacts this week.

FAQ

Should I buy an AI SDR or build my own sales agent?

Buy if standard outbound is enough and speed matters most. Build if your edge is your own data or product knowledge, or if you want a person to approve every send.

Does an AI sales agent need its own email inbox?

Yes. A dedicated mailbox keeps replies where the agent can read them, protects your team's personal accounts, and makes every send traceable.

How should an AI sales agent handle replies?

Read the full thread, classify the reply, and draft an answer for human approval. Hand interested prospects to a person and honor every opt-out immediately.

Can AI sales agents replace SDRs?

They can take over research and first drafts. Judgment on replies, relationships and closing still works best with a person in the loop.

Will an AI sales agent hurt my deliverability?

It can if it sends too much too soon from a new domain. Use a dedicated subdomain, authenticate it, start small and stop on complaints or bounces.

References

Recent articles