AI SDR or do it yourself? A solo founder’s guide

What an AI SDR does

An AI SDR (sales development representative) is software that does the work of an outbound rep: finds prospects that match your criteria, enriches them with data, writes personalized emails, sends them, follows up, and sometimes books meetings.

What founders actually report

The promise is pipeline on autopilot. The reports are mixed. In one r/sales thread on which AI SDR tools people are happy with, a commenter described switching to automation and then spending the saved time managing sequences and sorting poor-quality data. Others praise specific tools. Treat both as anecdotes, not benchmarks.

The common thread: AI SDRs amplify what you give them. A clear target and a proven message get amplified. A vague target gets amplified too.

When to start manual

Do outreach yourself first if:

• You have fewer than about 20 replies to learn from.
• You can’t yet say in one sentence why the right person should reply.
• Your sending domain is new.

Manual outreach at this stage is research. Every reply tells you which words work.

When an AI SDR helps

• You have a message that gets replies.
• You can describe your ideal customer precisely enough to filter a database.
• Your sending setup is healthy: separate domains, authentication, warm-up. See the guide on cold email deliverability.
• Replies flow into a CRM where someone follows up.

Your options compared

Prices change often, so check each vendor’s current pricing page before you decide. The cost column below describes the type of cost, not a quoted price.

Guardrails that keep it safe

• Approve the first sends of every new sequence yourself.
• Watch sender health: bounces and spam complaints. Pause on warning signs.
• Hand replies to a human fast, with the full context in the CRM.
• Keep a log of what was sent, to whom and why.

Your first 100 emails by hand: a two-week plan

Manual outreach sounds slow. But the first hundred emails are not about volume; they are about finding the one message that gets replies. So treat these two weeks as research with a send button.

Days 1–2: build the list. Pick 100 people who match your ideal customer closely. For each, write down one specific reason to contact them now: a job post, a launch, a public question, a tool they use.

Day 3: write three versions. Same offer, three different angles. For example: one leads with the problem, one with a result, one with a question.

Days 4–8: send in small batches. About 20 a day, split across the three versions. Personalize the first line of every email.

Days 9–12: follow up. One or two follow-ups each, every one adding something new.

Days 13–14: read the replies. Which version got replies? Which words did people repeat back to you? Which objections came up?

At the end you have a message, a list profile and a set of objections. That is exactly what an AI SDR needs to work well.

What to measure before you automate

Don’t chase someone else’s benchmark. Compare your own batches against each other.

How to evaluate an AI SDR tool: ten questions

1. Where does the prospect data come from, and how fresh is it?
2. Can I approve the first sends of every sequence?
3. Can I edit the prompts and the guardrails, not just the template?
4. Does it warm up inboxes and watch sender health?
5. Will it pause automatically when bounces or complaints rise?
6. How does it hand a reply to a human, and how fast?
7. Does it write replies to my CRM, with the full thread?
8. What happens to my data and my domains if I leave?
9. How is pricing counted: seats, contacts, emails or credits?
10. Can I see a log of every email it sent and why?

If a vendor can’t answer questions 2, 5 and 10 clearly, keep looking.

The hybrid setup most founders end up with

Fully manual outreach doesn’t scale. But fully autonomous outreach tends to drift toward generic messages. So most founders who make outbound work settle on a hybrid:

• You write the core message, choose the target list and answer every real reply.
• The agent researches prospects, personalizes first lines, sends on schedule, follows up and logs everything.
• The rules stop sending on warning signs and route any reply about price or scope to you.

This is how Marco works inside Growth Control: research, sequences and sender health checks run under approval rules, and replies land on the customer record in the CRM.

Common mistakes with AI SDRs

1. Scaling an unproven message. Volume multiplies whatever you give it, good or bad.
2. Sending from your main domain. One bad week can affect the inbox your customers use.
3. Buying a big list and hoping. Broad lists produce broad, ignorable emails.
4. Letting the agent negotiate. Replies about price, scope or timing need a person.
5. No CRM handoff. Replies that sit in a sending tool’s inbox go cold.
6. Judging after a week. Outbound needs several batches before the numbers mean anything.

Cost lines to plan for

• The tool or platform: a subscription or credits. Check current pricing on each vendor’s page.
• Prospect data: sometimes included, often extra.
• Sending infrastructure: separate domains and inboxes.
• Your time: approving sends and answering replies.

Compare the total against what a booked meeting is worth to you, not against the price of a human SDR alone.

A first-email teardown: weak vs strong

The same offer can be written in a way that gets ignored or in a way that gets a reply. Here is an illustrative pair for a founder selling a quoting tool to event rental companies.

Weak version

Subject: Revolutionize your business with AI. Hi {first_name}, I hope this email finds you well! I’m reaching out because our cutting-edge AI platform helps businesses like yours streamline operations and boost revenue. We’d love to show you a quick demo. Do you have 30 minutes this week?

Strong version

Subject: quotes during wedding season. Hi Maria, saw Coastal Rentals is booking weddings through October. Most rental owners I talk to lose bookings in peak season because quotes go out a day late. I built a tool that turns an inquiry into a priced quote in a few minutes. Is quote speed a problem for you right now, or not really?

What changed:

An AI SDR can produce either version. But it will only produce the strong one if you give it a real reason to write and a clear problem. So write the first 20 strong emails yourself and use them as the examples the agent copies.

A reply-handling playbook

Replies are where outbound turns into revenue, and where most automated setups break. Decide in advance who handles each type.

The two automatic rows are safe to hand off. Everything that sounds like a conversation should reach a person with the full thread attached.

The handoff checklist: from agent to human

When an AI SDR passes a warm reply to you, check that the handoff includes:

• The full email thread, not a summary alone
• Why this prospect was chosen (the signal or trigger)
• The company and role, with a source link
• Any earlier contact: forms, calls, past emails
• A suggested next step you can accept or change

If any item is missing, fix the setup before you add volume. A great reply lost in a bad handoff is the most expensive failure in outbound.

What to do this week

• Write one sentence: who you email and why they should care now.
• Hand-pick 25 prospects and find one real reason to write to each.
• Write and send 25 emails yourself from a separate, warmed-up domain.
• Track every reply in the CRM with its type from the playbook above.
• At the end of the week, pick your two best emails. They become the examples for any tool you test next.

Questions and answers