The Business Ops kit gives your AI four workflows for the operational essentials: Meeting Notes, Weekly Report, SOP Documentation and Decision Memo. Each saves its work as task notes step by step, stops once for your approval before anything is shared or recorded, and keeps the final version on file.
4 templates · 16 steps · 4 approvals · 3 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 · 4 steps · 1 approval
Turn a meeting into clean, shareable notes. The AI drives Extract and Distribute, with a checkpoint on the structure.
02 · 4 steps · 1 approval
Produce a weekly status report from inputs to published. The AI drives Gather, Draft, and a review checkpoint.
03 · 4 steps · 1 approval
Document a repeatable process as a clear SOP. The AI drives through Draft and a walkthrough checkpoint.
04 · 4 steps · 1 approval
Make a decision you can defend later. The AI drives Options and a recommendation checkpoint, then records the call.
Each template runs on its own, and their outputs feed each other through the record they leave. Meeting notes and task updates are inputs for the weekly report. A decision memo records the why behind a call; an SOP records the how of a process. All four save every version as task notes.
| From | To | How the work moves |
|---|---|---|
| Meeting Notes | Weekly Report | Weekly Report Gather pulls from notes and task updates, including the notes Meeting Notes distributed. |
| Decision Memo | SOP Documentation | A recorded decision often changes a process; SOP Documentation captures the new way it runs. |
| Weekly Report | Decision Memo | Blockers raised in a report become decisions framed with explicit criteria. |
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 |
|---|---|---|
| Meeting Notes | Extract step 2 | no rejection path; approve to continue |
| Weekly Report | Review step 3 | back to Draft |
| SOP Documentation | Walkthrough step 3 | back to Draft SOP |
| Decision Memo | Recommendation step 3 | back to Options |
An illustrative run, labelled as an example. The step names are the templates' real steps.
Meeting Notes saves the raw record, extracts decisions and owners, and you confirm them before they go out.
Decision Memo frames the choice, lays out three options and recommends one. You make the call; it is recorded with the trade-off.
SOP Documentation captures the onboarding steps with the new vendor and walks the draft through before you publish it.
Weekly Report gathers the week, drafts, checks every number against its input, and publishes once you approve.
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
No. Each is its own workflow on its own task. They connect through what they leave on record: task notes, decisions and published documents.
Every step saves its output as a task note with task_notes_add and the next step reads it with task_notes_list, so a run can be resumed in a new session.
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.