AI sales outreach workflows: Every rep runs the same motion.

ConvOps runs your sales playbook as governed AI agent workflows. Research lands as structure. A gate holds every send until it is approved. Follow-ups start from the meeting.

chatgpt · claude · nothing sends without approval · one motion for every rep

example · ChatGPTconnected
Research Northwind Logistics and draft an intro.
task created · Prospect Research attached
Researching first. Findings land on the task.
approval · nothing sends yet
Intro drafted for their ops lead. Approve the send?
Approved. Send it.
sent · follow-up waits for the meeting
ConvOps · task · exampleSales Outreach
task

Northwind Logistics

step 1 of 5
research draft approve send approvalfollow-up proposal
in short

What is an AI sales workflow with approval?

A ConvOps workflow every rep's AI agent follows: research, scoring, a drafted message, then a gate that holds the send until it is approved.

ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.

key facts · october 2026

  • A gate holds the step until an explicit approval is given, recorded with the account that gave it.
  • ConvOps does not send email. The agent sends through the tools its environment provides, or hands the message to the rep.
  • Prospect Research marks each account keep, drop or uncertain, with a source for every match.
  • Edit a step once and every run that starts afterwards follows the new version, for every rep.
  • Define the numbers each outreach run must report, such as replies or meetings booked, and bind them at the step that produces them. Every recorded value carries who recorded it and at which step.
  • ConvOps also records the cost, duration, tokens and outcome of every run by itself. Agents cannot write these numbers.

best for

  • Founders and small sales teams doing researched, one-to-one outreach
  • Account teams where every send and every price needs a read first
  • Sales leaders who want every rep on the same playbook

not for

  • High-volume sequences to large lists
  • Teams looking for a CRM

updated

the problem

Ten reps. Ten playbooks.

AI writes outreach in seconds. Whether it is on message, accurate or checked depends on the rep.

“Who approved that email?”

An AI draft reached a key account with the wrong price. Nobody checked it before it left.

“Where did that decision go?”

The pilot scope agreed on the call lives in one rep's notes. The proposal never saw it.

“What happens when someone leaves?”

Their accounts, their context and their way of selling leave with them.

watch it work

One prospect, research to proposal.

A real account, run through the Sales Outreach pack from ChatGPT. Every rep, the same motion.

01you, in ChatGPT

Name the account.

You name the prospect and ask for an intro. ConvOps creates the task and attaches Prospect Research. The motion starts the same way for every rep.

example
example · ChatGPTconnected to ConvOps
Research Northwind Logistics and draft an intro to their ops lead.
task created · Prospect Research attached
Researching first. Findings land on the task, not in this chat.
02the AI · research

Research lands as structure.

Company, contacts and buying signals become fields on the task, deduplicated. The next step and the next rep read the same record.

example
example · Northwind Logisticsprospect
industry
Freight and logistics
size
About 800 people
contact
Dana Ruiz · Head of Operations
signal
Hiring three dispatch coordinators
fit
Strong · manual handoffs between teams
structureddeduplicated
03the AI

It remembers what works.

Before drafting, the AI recalls the team's rulings: what logistics buyers respond to, and what never to say. Every draft starts from the same lessons.

example
example · ConvOps · recallbefore acting

askintro to a logistics ops lead

memoryLogistics buyers care about on-time rates. Lead with that.
memoryNo pricing in a first email. Decided in the Q2 review.
routeCase studies: sales/case-studies/logistics/
04you approve

Nothing sends until it is approved.

The draft waits at the approval gate. You read it, edit it or send it back. Outbound leaves only once the send is approved.

example
waiting for approval

Send the intro to Dana Ruiz?

Subject: On-time rates at Northwind · 92 words

EditApprove send
approvedSend step unlockedThe follow-up waits for the meeting.
05the AI · follow-up

The meeting writes the follow-up.

After the call, notes, commitments and next steps land on the same thread of work. The follow-up is drafted from what was actually agreed.

example
example · follow-up · Northwinddraft

Thanks for the time today, Dana

drafted from the meeting notes

agreedA pilot with the Lisbon dispatch team
nextSecurity review by the 14th
ownerDana shares this quarter's on-time data
commitments capturedsame thread as the research
06the AI · proposal

The proposal inherits everything.

The proposal runs in the same line of work. It starts from the research, the call and the decisions that led here. Nobody types the account again.

example
example · proposal · Northwinddraft

Pilot proposal: Lisbon dispatch

built from one thread of work

from researchThree coordinators hired for manual handoffs
from the callPilot scope agreed with Dana
from memoryLead with on-time rates
researchmeetingmemory
example
example · ChatGPTconnected to ConvOps
Research Northwind Logistics and draft an intro to their ops lead.
task created · Prospect Research attached
Researching first. Findings land on the task, not in this chat.
the workflow

The outreach motion, running.

Five steps from first look to proposal. A gate holds every send until it is approved.

workflow · Sales Outreachrunning · step 1 of 5
  1. 01

    Prospect research

    Companies and contacts land as structured, deduplicated tasks.

  2. 02

    Outreach drafted

    Written against your positioning, inside the process.

  3. 03

    You approve the send

    Every outbound message waits at the gate until it is approved.

    needs approval
  4. 04

    Meeting follow-up

    Notes, commitments and next steps on the same thread.

  5. 05

    Proposal

    Inherits the research, the call and the decisions.

what teams run it for

What sales teams run on it

Labelled examples from different kinds of selling.

example · SaaS sales development

First touch on a researched hook

An SDR's agent finds one specific reason to write, such as a new job post, drafts 80 words with one ask, and waits at the send gate. The rep approves or sends it back.

Outreach Message send gate

example · enterprise key accountsenterprise

A monthly account plan for a bank

A key account team runs a monthly plan for one banking client. Any message that mentions pricing or terms waits at a legal gate before the account lead approves the send.

Monthly schedule, two approval gates

example · channel partners

A partner pack per reseller

Each reseller gets its own task on the same workflow: research, a tailored pitch outline and a cover note. The partner manager approves each pack before it goes out.

One workflow, one task per partner

example · bid teamenterprise

An insurer's RFP answered as child tasks

A bid team splits an insurer's 120-question RFP into child tasks by section. The parent bid waits until every section is completed, and the bid lead approves the final response.

Child tasks and a final approval

example · account research

Call prep before every first meeting

Before each discovery call, the agent pulls the account's recent news, open roles and likely priorities into a one-page brief. There is no approval gate: the rep reads it before the call.

Research step, no approval

example · meeting follow-up

The recap, sent the same day

The rep pastes the call notes. Meeting Follow-Up drafts the recap with each agreed action, owner and date, and Send Review catches a wrong name before the rep approves.

Send Review approval

example · freight salesenterprise

Tender proposals at the approved rate

A freight forwarder's sales lead approves lanes and rates for a tender. The proposal draft is checked line by line against that approval before it reaches the client-ready gate.

Scope & Pricing approval

example · sales leadership

A monthly win-loss review

On the first weekday of each month, a schedule starts a review of the month's closed deals and writes the patterns into a short report. There is no approval gate: the sales lead reads it in the next team meeting.

Monthly schedule, no approval

what it remembers

What wins stays with the team.

The next rep and the next agent start with every lesson the team already paid for.

What works

Logistics buyers care about on-time rates. Lead with that.

what wins

What never to say

No pricing in a first email. Decided once, recalled before every draft.

decided once

Account history

Research, calls and decisions on one thread per account.

one thread

Where the proof lives

Case studies and pricing sheets, so no draft starts with a search.

where it lives

recurring work

Run it every week

Prospecting is weekly work. ConvOps keeps it on a rhythm and shows when it slips.

Put research on a schedule: one segment every Monday, in your time zone, with a preview of the next five runs. Group the schedules into a program with an owner, and its verdict turns late or silent when a week is missed.

Plan follow-ups and proposals on Plan. A planned task can auto-run on its day at a set time in the task's time zone, and the send still waits at its gate.

Define the numbers outreach must report in Metrics, such as replies and meetings booked, and bind them at the step that logs the outcome. Every value carries who recorded it and at which step, and ConvOps records the cost and outcome of each run by itself.

schedule firesMondays, in its time zone
researchkeep, drop or uncertain
list reviewapproval
draftone researched hook
sendapproval
repliesmetric required
program verdicthealthy
the difference

Ten playbooks vs one motion.

  • Each rep prompts their own way
  • AI drafts go out unchecked
  • Call notes stay in one rep's head
  • Proposals start from a blank page
  • One workflow for every rep
  • Every send waits for approval
  • Commitments land on the account thread
  • Proposals inherit the research and the call

Approval before send

A gate holds the send until an explicit approval is given, recorded with the account that gave it.

One pack, four workflows

Prospect Research, Outreach Message, Meeting Follow-Up and Proposal. Inspect every step and gate before you install.

Edit once, every rep inherits

Change a step in the template and the next run, for every rep, uses it. Runs already in progress keep going.

Context on the thread

Follow-ups and proposals run in the same task lineage, and decisions recorded on steps become memories the next run recalls.

next to what you use

ConvOps next to what you already use

Keep the sequencer and the CRM. ConvOps runs the researched work in between.

ConvOps next to the sales tools teams already weigh
ConvOpsA sequencerAn n8n or Zapier flowA chat prompt
What it doesRuns researched, one-to-one work as stepsSends cadences to listsMoves data between apps on a triggerWrites one message on request
Before a sendA gate holds it until it is approvedOptional manual tasksAn approval step where the tool offers oneYou copy and send it yourself
Same playbook for every repOne stored workflow, edited onceShared sequence templatesOne flow per useEach rep's own prompt
Research behind each nameA source for every matchImported listsWhatever the connected app holdsWhatever the model recalls
RecordEvery step and approval on the taskActivity log per contactExecution logsThe chat history
start this week

Four moves to your first run.

Connect the AI tool your team already uses, install the workflows, and run one real piece of work through them.

  1. move 1

    Install the Sales Outreach pack

  2. move 2

    Point Prospect Research at your segment: it lands as structured tasks, not a doc

  3. move 3

    Draft outreach with the approval gate on: nothing sends until the send is approved

  4. move 4

    After the first meeting, the follow-up workflow already has the context

install these

built on

The parts doing the work.

ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.

questions

What teams ask.

What is the sales use case in ConvOps?

In ConvOps, the sales use case runs prospect research, outreach, meeting follow-ups and proposals as workflows every rep's AI agent follows. Research lands as a qualified list with a source for each account, messages are drafted on a researched hook, and a gate holds every send and every price until it is approved. What one step learns becomes the next step's input.

Can a person approve every message before it is sent?

Yes. In ConvOps, the Outreach Message and Meeting Follow-Up templates put an approval gate on the send. A gate holds the step until an explicit approval is given, recorded with the account that gave it, so the agent drafts and the run waits. Remove the gate only when you decide the drafts no longer need a read before they go out.

Which numbers does ConvOps record for outreach, and who records them?

The ones you define, then the run numbers. In ConvOps you define the metrics outreach must report, such as replies or meetings booked, and bind them at the step that logs the outcome, where the agent or a rep records them. Every value carries who recorded it and at which step, with evidence as a link or a note. ConvOps also records the cost, duration, tokens and outcome of every run by itself.

How does every rep's agent follow the same playbook?

The playbook is the workflow. In ConvOps, every rep's AI agent receives the same steps from the same stored workflow, one at a time, with the same gates. Edit a step once, in conversation, and every run that starts afterwards follows the new version, for every rep and every AI client. The playbook stops being a document people half remember.

Does ConvOps replace our sequencer or CRM?

No. ConvOps governs the work around them. One way to split the work: the sequencer sends high-volume cadences, the CRM holds the account record, and ConvOps runs the researched, one-to-one work with a gate before each send. ConvOps does not send email itself; the agent sends through the tools its environment provides, or hands you the message.

Can sales outreach run every week without someone starting it?

Yes. In ConvOps, a weekly schedule can start a Prospect Research run for a segment, and a program groups those schedules under one owner with a health verdict. Plan shows the week ahead, and a planned task can auto-run on its day at a set time in the task's time zone. Sends still wait at their gate until they are approved.