Outbound prospecting
Your playbook, applied to every account.
Write the rules once. The operator checks each account against them, drafts the message with its sources, and waits for your rep's yes.
- ISO 27001
- GDPR
- Every run auditable
Corvane's outbound playbook
Illustrative runOB-0412
CRM check No record in HubSpot · net-new
Signal Opened a second distribution centre in Venlo Hallmark Freight newsroom, 3 Oct
Drafted, waiting for your yes · 3 follow-ups drafted
Two sites, one dock plan
Pieter, congratulations on opening the second Venlo distribution centreS. Running two sites side by side usually means two dock schedules that drift apart by midweek. Corvane plans dock slots for every site in one view. Would a short look at how that works for a two-site setup be useful?
Add 2 drafts to the outreach sheet and post them to #outbound-uk
Enterprises running operators on Alomana
- 2–5xmore positive replies than traditional outbound
- About 3xmore meetings booked
- 30–40 hourssaved per rep each month
What the operator does for each account
Generic outreach gets ignored. The operator does the research a good rep would do, for every account on the list.
- 01
Your CRM first
Checks HubSpot or Salesforce for customers, open deals, past touches and opt-outs
- 02
The people
Finds the buying group through your Apollo account
- 03
The reason to write now
Finds new sites, hiring, funding and leadership moves in public sources
- 04
The source
Links every personal line to the page it came from
- 05
The message
Drafts the first email, subject lines, follow-ups and a LinkedIn note in your playbook's voice
- 06
The handoff
Puts the drafts in a sheet, Slack or a review app for your rep to approve
How the operator prepares your outbound
Connect
Apollo, your CRM, your playbook.
Research and draft
Checks the CRM, finds the signal, cites the source.
Approve and send
Your rep says yes and sends from their own inbox.
Nothing goes out without your rep's yes.
- Your rep sends every message, from their own inbox
- Writes to sheets, Slack or your CRM wait for a person's yes
- A declined action is not retried
- Every run logged: input, output, tools, user
- Run record · OB-0412
- Input4 target accounts from Giulia's list, Corvane's outbound playbook
- Output2 drafts with 5 follow-ups, 1 note to a deal owner, 1 account skipped
- ToolsApollo, HubSpot, Salesforce, web search
- UserG. Ferri
- Measured on
- Qualified meetings heldCost per meetingResearch time per accountAccounts covered per rep
- Works with
- ApolloHubSpotSalesforceAttioGoogle SheetsSlackWeb searchOther systems via MCP
- Trusted for
- ISO 27001GDPRNever trains on your dataSingle-tenant for enterprise
A custom operator typically goes live in up to 4 weeks.
Questions sales leaders ask
What is an AI outbound research operator?
An AI agent that prepares your outbound end to end. For each target account it checks your CRM, finds the people and the reason to write now, cites where each fact came from, and drafts the first message and follow-ups for your rep to approve and send.
How is it different from an AI SDR?
Many AI SDR tools are built to send at volume from their own mailboxes. The operator does the research and the drafting, and your rep stays the sender: every message is approved and sent from the rep's own inbox, so your domain and your brand stay with your team.
Does it send emails or LinkedIn messages itself?
No. It drafts them, and your rep sends them from their own inbox and LinkedIn account. When the operator writes anywhere, such as adding drafts to a shared sheet, posting to Slack or updating your CRM, that action waits for a person's yes.
Where does the contact and signal data come from?
From the systems you connect: your Apollo account for people and companies, your CRM for history and opt-outs, and public web sources such as newsrooms, careers pages and reports for signals. It does not bring a contact database of its own.
Which systems does it connect to?
Alomana has 20+ connectors, including Apollo, HubSpot, Salesforce, Attio, Google Sheets, Google Drive, Slack and web search, activated per deployment. Systems outside the library connect through a remote MCP server.
Is our pipeline and customer data private?
Alomana is ISO 27001 certified and GDPR-compliant, and your data is never used to train AI models. Enterprise deployments run single-tenant, in a dedicated instance.
Bring five target accounts.
Talk it over with sales: what the operator needs from your systems, and how it goes live.
Alomana is a secure enterprise AI platform where autonomous agents, called operators, run business processes end to end. Every run is fully auditable.