Most small sales teams have the same leak. Not the pitch, not the product. The follow-up. The prospect who asked for pricing and never heard back. The deal that sat in "proposal sent" for five weeks. The Monday pipeline review that nobody had time to prepare.
That is the work an AI sales team is good at: the research, the drafting and the checking that falls between real conversations. This post shows how to set one up in Murage, and where to keep a human hand on it.
A note before we start. An "AI SDR" that emails strangers on its own is a real product category. This is not that. On Full access, Murage bots stop before messaging anyone new, unless you have allowed it for that task (on Hermes and other ACP engines, only for what the engine asks Murage about). They prepare. You decide who hears from you.
The three jobs
A useful sales team covers three jobs, each with its own specialist.
1. Research. Who to talk to and why now. Given a target description, a researcher finds companies that fit, the likely buyer, and a reason to get in touch this month. It searches the web out of the box, and cites what it found.
2. Follow-ups. Who you owe a reply. A follow-up bot reads the threads, finds the conversations where your side promised the next step, and drafts a short, specific message for each one.
3. Pipeline review. Where deals are stuck. Once a week, an analyst goes through open deals, flags the ones that have stalled, and suggests a next step for each.
Start from the library
You don't have to design this from scratch. The team library has several sales teams:
- Sales Org: a sales lead, a researcher, an offer specialist and an analyst, with a Monday check-in routine that arrives switched off. Needs no apps.
- Lead-Gen Outbound Squad: defines your ideal customer, researches a prospect list and prepares a sequence for your review. Needs no apps.
- Recover Unanswered Sales Emails: finds conversations where your team owes a reply and drafts follow-ups without sending them. Uses Gmail, and HubSpot if you have it.
- Find Qualified Reddit Leads: searches communities you approve for people asking for what you sell.
Choose + in the sidebar, then New Team, type "run my sales pipeline", and pick from the matches. Or ask your Chief of Staff to build a custom one and show you the plan first.
Brief it once
Every sales team works better with a short brief. Give it the facts only you have:
We sell bookkeeping to independent design studios, 3 to 20 people, at $400 a month. Buyers are usually the founder. Our best customers came from referrals and from people complaining about month-end. Never discount more than 10%. Never mention competitors by name.
Put rules like the last two in the team instructions, so every bot on the team reads them first. The team keeps the rest in memory, which lives on your computer where you can open and correct it.
Job 1: prospect research
Find 15 design studios in Manchester and Leeds that match our customer. For each: who runs it, a sign they might need us now, and the source. Put it in a table. Don't contact anyone.
You get a table you can check. See prospect research.
Job 2: follow-ups
With Gmail connected, through a Flux Router account or your own connected-apps key, the follow-up bot can work from the real threads:
Every weekday at 8, find sales threads where we owe the next step. Skip anything closed, opted out or internal. Draft a short follow-up for each and leave it as a draft. Tell me which ones matter most.
The Chief proposes a routine, and nothing is scheduled until you choose Confirm. See follow-ups.
Job 3: the Monday pipeline review
Without a CRM connected, paste an export. With HubSpot connected, the analyst reads it.
Every Monday at 8: review open deals. Flag anything with no activity in 14 days. For each, suggest one next step and who should take it. One page. Decisions I need to make go first.
See pipeline review.
Where the human stays
This is the part that keeps you in charge of an AI sales team.
- New bots start on Ask. They check with you before they act.
- The stop line. On Full access, a bot stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about: shell commands and file edits. On every level short of No limits, a first email to a prospect waits for your yes.
- Replies can speed up. Once you trust the drafts, a bot on Auto or Full access can reply in conversations it is already in. New recipients still stop.
- Specific trust. On a stop-line card, Allow for this task covers a batch you have agreed, and Always allow is tied to one recipient.
Approvals from every bot collect in one inbox. Pair Telegram and they come to your phone with a tap. More in can I let AI send emails?
For a sales team with several people
Each rep runs Murage on their own computer. Build the team once, with your ideal customer, your rules and your routines, then export it and have each rep import the same file. They connect their own Gmail and CRM, and approve their own bots. Logins never travel with the file. See share a team with your staff.
What it costs
The app and the teams are free. Each bot runs on an engine you choose, such as your Claude or ChatGPT plan through Claude Code or Codex, a provider key or a local model. Connected apps like Gmail and HubSpot need a Flux Router account or your own connected-apps key.
Download Murage, import Sales Org, and give it your ideal customer. The sales teams page has more on how businesses like yours use it.