Guides

How to choose an SDR agent for an early-stage startup

How to choose an AI SDR for an early-stage startup: who approves sends, mailbox and domain setup, pricing models and a two-week test plan.

Short answer: Choose the AI SDR where a person approves what goes out, where mailbox and domain setup is spelled out, and where the price can be modeled before you commit. Outlevo, our own product, sends nothing outside a policy a person approved [[1]](#sources), and a new managed mailbox sends nothing until it is warm, which takes at least 14 days [[2]](#sources).

Who this is for

This guide is for a founder who is doing outbound alone or with one other person. There is no sales team, no sales operations person and nobody to review drafts before they go out. You are looking at an AI SDR: software that does part of the work of a sales development rep (SDR). You need to know what it will do without you watching it. If the term is new, the AI SDR glossary entry covers it.

It is not a ranking. Tools in this space sell in different shapes, and the right one depends on how much you want to hand over. We name Outlevo as one option and say plainly that it is ours. Everything about other vendors comes from what they publish on their own pages. The linked tool pages show each quote with the date it was read [[3]](#sources) [[4]](#sources) [[5]](#sources).

If you want the wider context first, read outbound for early-stage B2B SaaS. For the choice between software, a sales engagement platform and an agency, see SDR software vs sales engagement vs outbound agency.

Four shapes of tool, by what they publish

An agent that runs outbound

Artisan describes Ava as an AI BDR that "finds leads, enriches them, sends personalized messages, and books meetings on behalf of your reps" [[6]](#sources). Its homepage line is "Put your outbound on autopilot" [[7]](#sources). Its pricing page scopes the Team plan at about 2,500 leads contacted a month and the Scale plan at about 6,000 [[8]](#sources) [[9]](#sources). An AI dialer is sold as an add-on per seat [[10]](#sources). Current plans are on Outlevo's Artisan page.

An email-writing tool with an agent on top

Lavender calls itself the "email intelligence company" and offers an AI email coach and an AI sales agent called Ora [[11]](#sources). Ora is listed at $500 per agent per month at launch, free to build, with no annual commitments [[12]](#sources). Lavender's Starter plan is $29 a month for individual Gmail or Outlook users [[13]](#sources), and its Pro plan is $49 a month [[14]](#sources). Lavender Teams starts at $8,500 [[15]](#sources). More on Outlevo's Lavender page.

A prospecting platform priced by seat and credit

Regie.ai describes itself as an AI sales prospecting platform that goes from ICP to pipeline: it finds buyers, enriches contacts, drafts emails and call scripts, and dials [[16]](#sources). Its Free plan is $0 with 250 one-time credits per person [[17]](#sources). Pro is $49 a month with 5,000 credits [[18]](#sources). Team is $150 per seat a month with 15,000 credits per seat and a two-seat minimum [[19]](#sources). A prospecting search costs one credit for every hundred results [[20]](#sources). See Outlevo's Regie.ai page.

Other tools publish similar mixes of seats and credits. Unify's Base plan is $20 per seat a month with 1 mailbox and 800 credits per seat [[21]](#sources). Causo charges one token per completed action and sells top-ups at $0.30 a token on two of its plans [[22]](#sources). Amplemarket's Startup plan includes 13,500 email address credits and 600 phone number credits per user a year [[23]](#sources).

Credit-based, no seats

Outlevo does not price by seat. The plans are Free at USD 0 a month, Builder at USD 29 with 320 credits, Growth at USD 149 with 3000 credits, Self-Serve at USD 199 with 1600 credits, and Managed from USD 999 a month on a contract [[24]](#sources). Credits are spent per action. Qualification costs 3, contact discovery 4, email verification 1 and deep research 30 [[24]](#sources). Sending, follow-ups and the mailboxes your plan includes use no credits [[25]](#sources).

For a side-by-side of everything published in the category, see the AI SDR tools page [[26]](#sources).

Steps

1. Write down who you sell to before you pick a tool

An agent can only work as well as the target you give it. If you have no written ideal customer profile (ICP), start there.

Outlevo's free assessment reads up to 5 public pages of your website. It returns facts labelled as verified observations or AI inferences, plus up to 5 experimental segment hypotheses [[27]](#sources). It asks which countries you sell into and never proposes markets [[28]](#sources). Run it, or do the same exercise by hand, and keep the output as your test brief.

If you have past deals, expect thin data. Outlevo counts companies, not deals, and treats fewer than 10 won companies as very low confidence [[28]](#sources). AI-proposed segments stay experimental until a person approves them [[28]](#sources). Whatever tool you pick, ask how it labels guesses.

2. Decide who approves what is sent

With no sales team, you are the reviewer, and you will not read every email. So the question is what the tool is allowed to do when you are not looking.

Ask for three things:

  • A way to set limits before anything runs.
  • A record of what ran.
  • A way to stop everything at once.

In Outlevo, policies set who can be contacted, on which channels, how often and with what budget [[1]](#sources). Every external action is checked against the approved policy before it runs and recorded in a ledger [[1]](#sources). Kill switches pause a campaign, a channel or the whole workspace at once [[1]](#sources).

Replies need the same decision. When someone answers with interest, Outlevo can reply with your Calendly or Cal.com link. On autopilot that answer goes at once. Otherwise it waits in Replies for you to send [[29]](#sources) [[30]](#sources). Pick one on purpose. A founder in the first month will usually want the second.

3. Settle mailboxes and domains

Three standards matter:

  • DKIM. It "permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message" [[31]](#sources).
  • SPF. Implementations "MUST limit the total number of those terms to 10 during SPF evaluation" [[32]](#sources). If you add sending tools to your main domain's SPF record, count the lookups.
  • DMARC. It lets "a mail-originating organization ... express domain-level policies and preferences for message validation, disposition, and reporting" [[33]](#sources). Yahoo's guidance is to "Publish a valid DMARC policy with at least p=none" [[34]](#sources).

Google's rule applies to "email senders who send more than 5,000 messages per day to Gmail accounts", who must set up SPF and DKIM [[35]](#sources). In our judgment, a startup is unlikely to reach that volume early. A tool that checks all three records before it sends still saves you a failure you would otherwise find out about late.

Here is what Outlevo does. Outlevo buys sending domains, creates the mailboxes through Zapmail, sets up DNS and warms them up, so you never touch your main domain [[2]](#sources). You choose from the domains it proposes and set the sender names [[2]](#sources). Self-Serve includes 2 domains and 4 mailboxes [[2]](#sources). A new mailbox sends nothing until it is warm, at least 14 days and usually about 3 weeks [[2]](#sources).

If you use Smartlead for sending, Outlevo builds each campaign in Smartlead and sends from the mailboxes in your Smartlead account [[25]](#sources). Before a campaign sends, every mailbox must be connected and warmed up. Its domain must have SPF, DKIM and DMARC checked in the last 7 days [[25]](#sources).

Check mailbox support in any tool too. AgentSDR sends from Google Workspace mailboxes only, and Microsoft 365 is not supported yet [[36]](#sources). If your company runs on Microsoft 365, that decides the question.

4. Model the price for your own volume

Work out what you would pay for a month of the work you want done. Use the pricing models these tools publish:

  • Per seat. Regie.ai's Team plan and Unify's Base plan are priced this way [[19]](#sources) [[21]](#sources). Check the seat minimum. For a one-person team it can decide the choice.
  • Per agent. Lavender's Ora is listed per agent per month [[12]](#sources).
  • By volume of leads contacted. Artisan scopes plans this way [[8]](#sources) [[9]](#sources).
  • By credit or token. Outlevo, Regie.ai and Causo meter actions [[24]](#sources) [[20]](#sources) [[22]](#sources).

Ask each vendor whether it offers per-meeting pricing. If one does, ask for it in writing and check how it defines a meeting.

For a credit model, count the steps for one contact. In Outlevo, one account takes 3 credits to qualify, 4 to find a contact and 1 to verify the email [[24]](#sources). That is 8 credits before a single email goes out. Multiply by the accounts you want in a month and compare against the plan's credits. Deep research at 30 credits is a different order of cost, so decide where you want it [[24]](#sources).

Also check which side items are metered. In Outlevo, webhooks cost 1 credit per delivered event; failed attempts and test pings are free [[37]](#sources). Website visitor identification costs 1 credit per company identified per day [[38]](#sources). Read the fine print on every tool for items like these.

5. Connect what you already have

If you have a CRM, check what the tool reads and where it writes.

Outlevo's HubSpot integration reads companies, deals and owners, and writes only to fields it owns. Your standard HubSpot fields are never edited, and nothing is written until an owner or admin approves the field mapping [[39]](#sources). Connecting and syncing a CRM uses no credits [[39]](#sources). The Salesforce integration runs through the Outlevo package, which Outlevo installs with you [[40]](#sources). Salesforce is a pilot with no AppExchange listing [[40]](#sources).

If you have no CRM, a CSV import takes companies and won or lost deals, up to 200,000 rows, and costs no credits [[41]](#sources). If you want to wire in your own tools, everything in the Outlevo app is available in the REST API, with a TypeScript SDK and an MCP server [[42]](#sources).

6. Run a two-week test

If you choose a managed mailbox setup, plan around warm-up. A new Outlevo mailbox sends nothing for at least 14 days [[2]](#sources). On that path the two weeks therefore contain no sending. Use the time like this.

Days 1 to 3: set up and approve.

  • Run your ICP brief through the tool and read the segments it proposes. Approve or reject each one; in Outlevo, AI-proposed segments stay experimental until a person approves them [[28]](#sources).
  • Set the limits: who can be contacted, on which channels, how often, at what budget [[1]](#sources). Find the kill switch and use it once, so you know it works [[1]](#sources).

Days 4 to 14: build without sending.

  • Test keys in Outlevo run against a sandbox with 100 fake companies. They are never charged, so you can build without sending anything [[43]](#sources).
  • Check what the tool shows for each account. A Readiness Card in Outlevo needs at least three observations with a source and a date [[44]](#sources). Facts read from a website are kept only when their quote is found on the page [[44]](#sources). Guesses are labelled as hypotheses [[44]](#sources). For any tool, open ten accounts and check whether each claim can be traced to a page.
  • Confirm your domain records and mailbox state.

Day 15 or later, once the mailboxes are warm: a small first send.

  • Day 15 is the earliest, and warm-up usually takes about 3 weeks [[2]](#sources).
  • Send a small batch, with every message approved by you before it goes.
  • Read the replies yourself. Judge the process, not the count. Few replies is normal at small volume. Smartlead's State of Cold Email 2026, covering more than 850 million emails sent from January to June 2026, puts the median cold email reply rate at 0.74% per contact, the top quarter at 1.43% and the top tenth at 2.63% [[45]](#sources). That rate counts a person once, however many emails they were sent [[45]](#sources).

If a tool can send from day one, move the first send into days 11 to 14 and keep the rest of the list.

What to check

Use this list on any tool, including ours.

Control

  • Can you set limits on who is contacted, on which channels, how often and at what budget before anything runs?
  • Is there a record of every external action?
  • Can you stop one campaign, one channel and the whole account separately?
  • What happens to replies: sent at once, or held for you?

Setup

  • Who buys the domains and sets up the DNS: you or the vendor?
  • How long until the first email can go out?
  • Which mailbox providers are supported?
  • Does the tool check SPF, DKIM and DMARC before sending, and how recently?

Evidence

  • Does each fact about a company carry a source and a date?
  • Are guesses labelled as guesses?
  • Do segments stay experimental until a person approves them?

Price

  • Is the price per seat, per agent, per volume or per credit?
  • What is the minimum seat count?
  • What does one contact cost end to end?
  • Which actions are free, and which are charged even when they fail?

Fit with your stack

  • Does it write to your CRM only in fields it owns, and does someone approve the mapping?
  • Can you export your lists as CSV or Excel? In Outlevo, exports of up to 5,000 rows download at once, and larger ones, up to 100,000 rows, are prepared in the background [[41]](#sources).
  • Is access by the vendor's staff limited and visible? In Outlevo, staff support access is time-limited and shown in your activity feed, with the reason and the number of changes made [[46]](#sources).

Data handling

  • Is personal data protected at the field level? In Outlevo, every customer table has row-level security in the database, and personal data such as email addresses is encrypted at the field level [[46]](#sources).

Some of these answers are on pricing pages. Others you will have to ask for in a sales call. Write down what each vendor says and compare the notes after the test.

Where a founder should be cautious

Autonomous means different things on different pages. Artisan's page says "autopilot" [[7]](#sources). That tells you what the vendor aims for, not what you can control. Read the settings, not the slogan.

Free is not the same as low-cost. Regie.ai's Free plan gives 250 one-time credits per person [[17]](#sources). That works for a trial. Work out what you would pay once the credits run out.

Finally, keep your main domain out of the experiment. The setup described under step 3 is one way to do it [[2]](#sources). Whatever tool you pick, ask where the sending domain lives.

Next step

Start with the part that costs nothing. Run the free ICP assessment on your site and read the segments it proposes. It reads up to 5 public pages and labels what it observed and what it inferred [[27]](#sources).

Then read how Outlevo works for the approval policy and kill switches, and pricing for the credit costs. If you are comparing a sales engagement platform instead, see the Reply.io alternative page. If your target buyers are other founders, cold email to startup founders covers that audience.

Whichever tool you try, run the two-week test and keep your notes. A tool that is clear about what it will do without you watching is the one to keep.

Sources

  1. How Outlevo works
  2. Managed mailboxes integration
  3. Artisan pricing
  4. Lavender pricing
  5. Regie.ai pricing
  6. Artisan: positioning
  7. Artisan: positioning
  8. Artisan: pricing
  9. Artisan: pricing
  10. Artisan: pricing
  11. Lavender: positioning
  12. Lavender: pricing
  13. Lavender: pricing
  14. Lavender: pricing
  15. Lavender: pricing
  16. Regie.ai: positioning
  17. Regie.ai: pricing
  18. Regie.ai: pricing
  19. Regie.ai: pricing
  20. Regie.ai: pricing
  21. Unify pricing
  22. Causo pricing
  23. Amplemarket pricing
  24. Outlevo pricing
  25. Smartlead integration
  26. ai sdr tools
  27. Free ICP assessment
  28. ICP from evidence
  29. Calendly integration
  30. Cal.com integration
  31. RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
  32. RFC 7208: Sender Policy Framework (SPF)
  33. RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)
  34. Yahoo: Sender best practices
  35. Google: Email sender guidelines
  36. AgentSDR on GitHub
  37. Webhooks integration
  38. Website visitors integration
  39. HubSpot integration
  40. Salesforce integration
  41. CSV and Excel integration
  42. Developer hub
  43. REST API and SDK integration
  44. Readiness Cards
  45. Smartlead, The State of Cold Email 2026: reply rate per contact (top quartile; January to June 2026, more than 850 million emails)
  46. Security

Related

See what Outlevo finds on your own website

Free, no sign-up, about a minute.