The agents worth building first, and how our favourite works
Start with a job that comes round every day, has a number on it and fails safely. Ours is the reply reader – every reply to an outreach email read, sorted and acted on, which is the job no sales team ever gets round to by hand.

How to pick the first one
We'd ask three questions. Does the job happen every day, so the agent actually gets used and its faults show up quickly? Is there a number on it, so you can say afterwards what changed? And does it fail safely – if the agent gets it wrong, does someone on your team catch it before a customer does? A drafting agent fails safely. One that sends on its own doesn't, and we don't think it should be anyone's first.
Three that suit most sales teams
| Agent | Trigger | Reads | Writes | Fails safely because |
|---|---|---|---|---|
| Meeting notes | A call ends, or a recording lands | The recording or the rep's notes | The agreed fields and a summary on the CRM record, as a draft for the rep to confirm | The rep confirms before anything gets saved |
| Company check | A new company appears, or a rep asks | Public sources and your written profile | A fit score with the reasons and sources, and a flag on anything it couldn't confirm | It recommends, the rep decides whether to call |
| Reply reader | A reply lands in a rep's mailbox | The reply and the thread | What kind of reply it was, the facts in it, a draft response, updates to the record | The draft waits for the rep, only the record-keeping is automatic |
How the reply reader works
A reply to an outreach email lands in the rep's own mailbox. The agent reads it and works out what it is: a yes, a not now, a referral to someone else, a person who's left, an out-of-office, or a request to stop. Then it looks for facts – a direct number in a signature, a new job title, a colleague's name, a date to call back.
Each kind gets its own action. A yes becomes a deal and a task on the account, with a draft answer sitting in the rep's drafts folder, flagged until someone sends it. A referral becomes a new contact, found and checked against the persona, added to the account and linked to the person who referred them. A leaver's record gets updated so they stop getting email. An out-of-office gets recognised as automatic, so it doesn't count as a response and the follow-ups carry on. A request to stop unsubscribes that person, and only that person. All of it gets written to the CRM with a line in the log.
What the rep sees is a flagged yes with a draft ready, and an account whose record is already right. In our own outreach roughly one reply in three comes from someone other than the person we wrote to – a referral, a leaver or an absence – and before the agent existed, that was exactly the work nobody did.
Why it's our favourite
It isn't the clever one. It's the one doing something nobody was doing. Sales teams have always written the first email and chased the yes. What they've never done reliably is update the CRM when a reply said the contact had left, create the colleague who was copied in, or stop emailing the person who asked them to. The inbox is the richest source of fresh information a sales team has, and the reply reader turns it into something that keeps the CRM right instead of letting it rot.
What not to build first
Anything that sends to a customer without a person involved, anything that changes a price or a quote, anything that deletes, and anything whose mistakes a customer would see before you do. Those are second-year agents, for once your team trusts the first-year ones and the three tiers are in place.