AI agents for sales outreach

Research and first emails, approved before they send.

Agents that research prospects, draft the first email and classify the replies, with every send waiting for a person. Each run shows who was found, why, and what was written.

The job

Writing to prospects is repetitive. Choosing them is not.

Outbound looks like a perfect job for agents: research a company, write a first email, follow up, sort the replies. The writing and the bookkeeping repeat. Deciding who is worth writing to, and what goes out under your name, still needs a person.

How it runs

A pipeline of agents, with one gate.

One agent researches, another drafts, a third sorts the replies. Agents hand work to each other inside a pipeline, and the step that sends email waits for an approval, so nothing reaches a prospect that a person has not read.

  • Research with sources. Web search and page reading, with the pages it used kept on the run.
  • Drafts, not sends. The send step requires approval; approvers see the email as the prospect will.
  • Replies sorted. Interested, not interested, needs a follow-up, out of office: classified, so a person answers the ones that matter.
  • Cost per run. Token spend per agent, so a pipeline that grows does not grow its bill unnoticed.
The drafted emails wait for a person, as the prospect will read them.

What we learned

We ran our own outreach this way.

Agents are good at the writing and the bookkeeping; deciding who is worth writing to needed a person.

Case studyWhat we learned from letting agents do our cold outreach

Step by step

A pipeline you can read end to end.

  1. Research

    An agent finds the facts on each company, with its sources.
  2. Draft

    Another writes the first email from them.
  3. Approve

    The send waits; a person reads each email as the prospect will.
  4. Sort replies

    Replies are classified so a person answers the ones that matter.

Questions

What teams ask first.

Can it send email without anyone reading it?
Only if you let it. The send tool can require an approval, and the approver sees the email as it will go out.
Who picks the prospects?
You do, or an agent from the list you give it. In our own outreach, the best results came from a person choosing who to write to.

Pilot

Try it on one real workflow.

We build the agent with you, with an approval gate on the risky step, and report what it did.

Integrations

18 apps, your models, your APIs.

Connect GitHub, Gmail, Slack and more once, describe any HTTP API as a tool, and choose the model per agent.

Give one job to an agent this week.

Start from a template, gate the sensitive step behind your approval, and read the first run end to end.