The Sales Outreach kit gives your AI a full outreach motion in four workflows: Prospect Research builds a qualified list, Outreach Message sends a researched message and logs the outcome, Meeting Follow-Up recaps the call, and Proposal quotes the work. Each run's saved note is the next one's input, and nothing goes out unapproved.
4 templates · 20 steps · 6 approvals · 4 loops back
one chip per stored step · square chips wait for a person
Four workflow templates, installed together. Each one is a stored workflow your AI client receives one step at a time over MCP.
01 · 5 steps · 2 approvals
Build a qualified prospect list from ICP to review. The AI drives through Find, Qualify, and a list-review checkpoint.
02 · 5 steps · 1 approval
Send personalized outreach from prospect to logged outcome. The AI drives Research, Draft, and a send checkpoint.
03 · 5 steps · 1 approval
Turn a meeting into a sent follow-up. The AI drives through Extract, Draft, and a send-review checkpoint.
04 · 5 steps · 2 approvals
Build a client proposal from requirements to client-ready. The AI drives through Scope, Draft, and two checkpoints.
The templates chain by named inputs written into their steps. The approved prospect list is the input for outreach. The logged outreach outcome is the input for a meeting follow-up when the prospect responds. A discovery call's notes feed the proposal's requirements. Every send and every price stops for you.
| From | To | How the work moves |
|---|---|---|
| Prospect Research | Outreach Message | Prospect Research Complete names the approved list as the input for an Outreach Message; Prospect Intake pulls the entry from it. |
| Outreach Message | Meeting Follow-Up | Log Outcome is the named input for a Meeting Follow-Up if the prospect responds. |
| Meeting Follow-Up | Proposal | Proposal Requirements pulls from discovery call notes when they exist. |
Each template runs on its own task. They connect through what a finished run leaves on record, not through a shared run.
Every approval step in the kit, read from the stored workflows. The run holds at each one until you answer.
| Template | Approval step | If you reject |
|---|---|---|
| Prospect Research | Define ICP step 1 | no rejection path; approve to continue |
| List Review step 4 | back to Qualify & Enrich | |
| Outreach Message | Send Review step 4 | back to Draft |
| Meeting Follow-Up | Send Review step 4 | back to Draft Follow-Up |
| Proposal | Scope & Pricing step 2 | no rejection path; approve to continue |
| Client-Ready Review step 4 | back to Draft |
An illustrative run, labelled as an example. The step names are the templates' real steps.
You approve an ICP: dental clinics in Texas, 10 to 50 staff, hiring front-desk roles. The AI finds, qualifies and enriches 20; you approve the list.
For each account, Outreach Message researches one real hook and drafts a short email. You approve the send; the outcome is logged.
A clinic books a call. Meeting Follow-Up captures it, extracts the next step and drafts the recap. You approve the send.
Proposal captures requirements from the call, you approve scope and price, and you approve the client-ready version.
Connect your AI client first, then install the kit from the catalog in the ConvOps app. See how to connect a client
Installed templates are workflows in your workspace. Ask your AI to change one in plain words; the edit lands on the step that needs it.
new chat
more example prompts
Prospect Research stops twice (ICP and list), Outreach Message once (send), Meeting Follow-Up once (send) and Proposal twice (scope and price, then client-ready). Every irreversible send waits for you.
No. ConvOps holds the run and the record. Your AI client sends, or hands you the message, using the tools it is connected to.
The Free plan includes 3 workflow templates and this kit has 4, so the full kit needs Pro or above.
Any MCP client connected to ConvOps. Verified clients: Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode. None of its workflows needs a repository.