“Who approved that email?”
An AI draft reached a key account with the wrong price. Nobody checked it before it left.
ConvOps runs your sales playbook as governed AI agent workflows. Research lands as structure. Outreach waits for your approval before anything leaves. Follow-ups start from the meeting.
chatgpt · claude · nothing sends without approval · one motion for every rep
new chat
Northwind Logistics
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.
A real account, run through the Sales Outreach pack from ChatGPT. Every rep, the same motion.
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.
Company, contacts and buying signals become fields on the task, deduplicated. The next step and the next rep read the same record.
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.
askintro to a logistics ops lead
The draft waits at the approval gate. You read it, edit it or send it back. Outbound leaves only when a person releases it.
Send the intro to Dana Ruiz?
Subject: On-time rates at Northwind · 92 words
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.
Thanks for the time today, Dana
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.
Pilot proposal: Lisbon dispatch
Five steps from first look to proposal. Nothing leaves the building until a person releases it.
Companies and contacts land as structured, deduplicated tasks.
Written against your positioning, inside the process.
Every outbound message waits until a person releases it.
needs a personNotes, commitments and next steps on the same thread.
Inherits the research, the call and the decisions.
The next rep and the next agent start with every lesson the team already paid for.
Logistics buyers care about on-time rates. Lead with that.
what wins
No pricing in a first email. Decided once, recalled before every draft.
decided once
Research, calls and decisions on one thread per account.
one thread
Case studies and pricing sheets, so no draft starts with a search.
where it lives
The send sits behind a requires_approval gate. The run does not advance until it is met.
Prospect Research, Outreach Message, Meeting Follow-Up and Proposal. Inspect every step and gate before you install.
Change a step in the template and the next run, for every rep, uses it. Runs already in progress keep going.
Follow-ups and proposals run in the same task lineage, and decisions recorded on steps become memories the next run recalls.
Connect the AI tool your team already uses, install the workflows, and run one real piece of work through them.
Install the Sales Outreach pack
Point Prospect Research at your segment: it lands as structured tasks, not a doc
Draft outreach with the approval gate on: nothing sends until you release it
After the first meeting, the follow-up workflow already has the context
ConvOps is the operations layer for AI agents: an MCP server that holds your team's process as workflows, with approval gates, a shared memory and an audit trail. It runs no AI models.
Not past an approval gate. Outbound sits behind requires_approval; the workflow drafts, the run stops, and nothing leaves until a human releases it. Remove the gate only when you decide to.
The Sales Outreach pack: Prospect Research, Outreach Message, Meeting Follow-Up, and Proposal, each a real workflow with steps and gates you can inspect on this site before installing.
The motion is the template. Edit a step once and every subsequent run, for every rep, inherits it. The playbook stops being a doc people half-remember.
In the thread of work: follow-ups and proposals run inside the same task lineage, and decisions recorded on steps become memories the next run recalls.