Business Ops AI workflow kit: Notes, reports, SOPs and decisions, one way.

The ConvOps 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, holds once at a gate until an explicit approval is given before anything is shared or recorded, and keeps the final version on file.

4 templates · 16 steps · 4 approvals · 3 loops back

kit · 4 workflowsreal steps
  1. 01Meeting Notes4 steps · 1 approval
  2. 02Weekly Report4 steps · 1 approval
  3. 03SOP Documentation4 steps · 1 approval
  4. 04Decision Memo4 steps · 1 approval

one chip per stored step · square chips wait for an explicit approval

the set

What's in the Business Ops kit?

Four Business Ops templates, installed together, each received by your AI one step at a time.

Four separate workflows for notes, reports, SOPs and decisions that feed each other through the task notes they leave.

01 · 4 steps · 1 approval

Meeting Notes

For every Business Ops meeting: decisions and owners confirmed at Extract before the notes go out.

  1. Capture
  2. Extract
  3. Distribute
  4. Complete
  • Turn rough notes into a summary with decisions and action items
  • Write up a team standup into a shareable recap
every step of Meeting Notes →

02 · 4 steps · 1 approval

Weekly Report

The Business Ops Friday report, gathered from the week's notes with every number checked against its input.

  1. Gather
  2. Draft
  3. Review
  4. Publish
  • Write a weekly team status report from scattered updates
  • Turn the week's notes into a clear progress update for stakeholders
every step of Weekly Report →

03 · 4 steps · 1 approval

SOP Documentation

Business Ops reaches for it when a process lives in one person's head: drafted, walked through, then published.

  1. Capture Process
  2. Draft SOP
  3. Walkthrough
  4. Publish
  • Document a customer onboarding process as a step-by-step SOP
  • Write a standard operating procedure for handling refunds
every step of SOP Documentation →

04 · 4 steps · 1 approval

Decision Memo

The Business Ops record of why: criteria framed first, options weighed, the call recorded with the trade-off.

  1. Frame
  2. Options
  3. Recommendation
  4. Record
  • Decide build-versus-buy with the trade-offs laid out side by side
  • Choose between vendors with a clear recommendation and rationale
every step of Decision Memo →

reach for it when

  • For an operations lead who writes the same notes, reports and decisions every week.
  • The team needs one shape for each recurring document.
  • What was decided, and why, should sit beside how the work is done.

something else fits when

  • The agent should run a procedure, not write it down: build that SOP as a workflow.
  • Your recurring work is client-facing sales or content.
  • You need only one of the four: install that template on its own.
example · finance operationsenterprise

Month-end close at a retail group

Meeting Notes records the close meeting and confirms an owner for each open reconciliation. Weekly Report tracks them until they clear, and a Decision Memo records any write-off with the criteria it was judged on.

Extract, Review and Recommendation gates

how it fits

How do the Business Ops workflows connect?

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.

FromToHow the work moves
Meeting NotesWeekly ReportWeekly Report Gather pulls from notes and task updates, including the notes Meeting Notes distributed.
Decision MemoSOP DocumentationA recorded decision often changes a process; SOP Documentation captures the new way it runs.
Weekly ReportDecision MemoBlockers raised in a report become decisions framed with explicit criteria.

Each Business Ops template runs on its own task, and they connect through what a finished run leaves on record.

where approval is required

Where does the Business Ops kit wait for approval?

The four Business Ops approval gates, read from the stored workflows; each holds until an explicit approval is given.

TemplateStep with an approval gateIf you reject
Meeting NotesExtract step 2no rejection path; approve to continue
Weekly ReportReview step 3back to Draft
SOP DocumentationWalkthrough step 3back to Draft SOP
Decision MemoRecommendation step 3back to Options
example

What does a week with the Business Ops kit look like?

An illustrative Business Ops run, labelled as an example, using the real Business Ops step names.

  1. 01

    Monday: the ops sync

    Meeting Notes saves the raw record, extracts decisions and owners, and you confirm them before they go out.

  2. 02

    Wednesday: a vendor call

    Decision Memo frames the choice, lays out three options and recommends one. You make the call; it is recorded with the trade-off.

  3. 03

    Thursday: the new process

    SOP Documentation captures the onboarding steps with the new vendor and walks the draft through before you publish it.

  4. 04

    Friday: the report

    Weekly Report gathers the week, drafts, checks every number against its input, and publishes once you approve.

what you need

What do you need to run the Business Ops kit?

make it yours

How do you customize the Business Ops kit?

Once installed, each Business Ops template is a workflow in your workspace; ask your AI to change it in plain words.

ChatGPTexample

new chat

Schedule Weekly Report every Friday at 3 pm.
schedule_create · Business Ops
Done. Business Ops in your workspace now has the change, and every new run follows it.

more example prompts

  • "Schedule Weekly Report every Friday at 3 pm."
  • "In Meeting Notes, turn each action item into its own task."
  • "In Decision Memo, always include reversibility as a criterion."
questions

Business Ops kit FAQ

What is the ConvOps Business Ops kit?

The ConvOps 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, holds once at a gate until an explicit approval is given before anything is shared or recorded, and keeps the final version on file.

Do the four templates run as one workflow?

No. In ConvOps each Business Ops template is its own workflow on its own task: Meeting Notes, Weekly Report, SOP Documentation and Decision Memo. They connect through what they leave on record (task notes, confirmed decisions and published documents), so the next run starts from a saved record rather than from a chat history.

Where is the work saved?

In ConvOps task notes. Every step in the kit saves its output with task_notes_add and the next step reads it with task_notes_list, so a run can be resumed in a new session or a different AI client. Each template ends by saving the shared, published or recorded version as a task note, so the final text stays on file.

Does Business Ops fit on the Free plan?

Three of its four templates do. The ConvOps Free plan includes 3 workflow templates, so Meeting Notes, Weekly Report, SOP Documentation and Decision Memo together need Pro or above. None of them depends on another in the catalog, so on Free you can install the three your team runs most and add the fourth when you upgrade.

Where does each template stop for approval?

Once each. In ConvOps, Meeting Notes holds at Extract until the decisions and owners are confirmed, Weekly Report at Review, SOP Documentation at Walkthrough and Decision Memo at Recommendation. Each holds its step until an explicit approval is given, recorded with the account that gave it, and a rejection at Review, Walkthrough or Recommendation sends the run back one step.

Can the Business Ops templates run on a schedule?

Yes. In ConvOps, a schedule starts a task with a template attached, for example Weekly Report every Friday afternoon in the team's time zone, and you can preview the next runs before saving. The gate inside the template still holds, so a scheduled Business Ops report waits at Review until an explicit approval is given before it is published.