“Who approved that?”
Phase two started before anyone signed the plan off. Now finance is unwinding it.
ConvOps runs recurring operations as governed AI agent workflows. Plans wait for sign-off. Phases run strictly in order. Reports have one shape. SOPs run as steps instead of sitting in a wiki. Every recurring process has an owner and a health verdict.
claude · cowork · chatgpt · phases in order · sign-off before anything starts
Expense policy rollout
Agents that run recurring processes as ConvOps workflows: steps with judgement where rules run out, approvals at gates, and each process owned and checked by a program.
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
best for
not for
updated
The steps are in someone's head or a wiki nobody opens. AI makes it faster to skip them.
“Who approved that?”
Phase two started before anyone signed the plan off. Now finance is unwinding it.
“Where did that decision go?”
Why the approval limit is 500 lives in a meeting nobody wrote down.
“What happens when someone leaves?”
The person who knew the month-end close is gone. So is the process.
A real change, run as a plan from Claude. Then the weekly report, on a schedule.
You describe the change in plain words. ConvOps creates a plan and drafts its phases. The work has a shape before anyone starts.
Each phase is its own ordered chunk of work. Phase two stays locked until phase one lands. The engine checks that order, not etiquette.
locked · waiting for sign-off
The plan stops at the approval gate. You read the phases, change them or sign off. Until then, no phase starts.
Sign off the expense policy rollout?
3 phases · pilot first · old form retired last
The pilot runs and lands. Only then does phase two open. The order is checked on every advance, whoever is driving.
phase 1 of 3 · running
The expense SOP stops being a wiki page. It becomes a workflow the AI follows step by step, with an approval where a manager decides.
The weekly report runs on a schedule. Each fire creates the task with the whole process attached, so every week has the same shape.
Phases run strictly in order, and nothing starts before you sign off.
The plan is described, scoped and broken down.
Child phases, each an ordered chunk of work.
No phase starts until the plan is approved.
needs approvalEach phase must land before the next one opens.
The result is checked against the plan.
The plan closes only when every phase is done.
Labelled examples from different operations functions.
A manufacturer's close runs as a plan: accruals, reconciliations, review, then reporting. A reconciliation report bound as required keeps its step open until the report is filed, and the controller approves before reporting starts.
Ordered phases, required report, approval
Each new starter gets a task with the onboarding workflow: contract, equipment, accounts, a first-week plan. An access report lists every system granted, and the hiring manager approves before day one.
Required report and approval gate
A bank's weekly access review sits in a program. When a week passes with no run, the program turns silent, and the security lead sees it before the auditor does.
Program with a health verdict
A logistics group runs every new vendor through the same checks: details, sanctions screening, bank verification. The reasoning step stays open until the reason is written, and the buyer approves.
Recorded reason and approval gate
Each control owner's check runs on a monthly schedule, grouped into one program for the audit. The program shows failing after three failed runs in a row, so a broken check surfaces early.
Monthly schedules in one program
Every weekday morning a schedule starts a triage run that tags, routes and summarises the overnight tickets. There is no approval gate: the support lead reads the summary at stand-up.
Weekday schedule, no approval
A retail chain's analytics team has the agent pull the week's KPIs and write what moved and why, with a source for every number. There is no approval gate: the note is read in the Monday meeting.
Weekly schedule, no approval
Six regional teams install the same Weekly Report template. Every report has the same sections, and Review flags any figure with no source before the regional lead approves.
Weekly Report template
Kept by the business, not by whoever was in the meeting. Recalled when the work needs it.
Claims over 500 need a manager. Set in the Q3 review, with the reason.
why we did it
The policy doc, the expense form and the finance sheet. Found once, kept.
where it lives
Field-level history on every task and workflow run. Reviews stop being archaeology.
what changed
Every memory points back to the plan or task that produced it.
traceable
Operations is mostly recurring work. ConvOps gives each process an owner, a rhythm and a verdict.
Every recurring process gets a schedule: daily, weekdays, weekly, monthly or a repeat rule, each in its own time zone. A schedule can spawn a new task on each fire or wake an existing one. Group the schedules into a program with an owner and a goal, and its verdict turns late, silent or failing when the process stops.
Plan the week on Plan: a week and month board with a tray of unplanned tasks, capacity from four weeks of completed work, and spread to place tasks on the least-loaded days before each deadline.
Define the numbers each process must report in Metrics, such as days to close, and bind them at the step where the work runs, so that step holds until they are recorded. Each value carries who recorded it and at which step. ConvOps also records the cost, duration, tokens and outcome of every run by itself, and agents cannot write those.
Phases run under a sequential_children gate. The next phase activates only when the one before it is done.
An approval gate holds the plan until it is approved. The engine refuses the advance and says what is missing.
Weekly reports run on a schedule in its own time zone: daily, weekdays, weekly, monthly or a repeat rule. Each fire creates the task, or wakes the same one where it stopped.
Field-level before and after on tasks and workflow instances, plus an activity feed. The agent label and the signed-in person stay separate.
RPA and automation tools move data. ConvOps governs the work that needs judgement.
| ConvOps | RPA | A workflow automation tool | A chat prompt | |
|---|---|---|---|---|
| Handles judgement | The agent applies each step's instructions to the case | No: fixed clicks and fields | No: the same actions on every trigger | Yes, in no fixed order |
| Approval gate | A gate holds the step until it is approved | Exception queues | An approval step where the tool offers one | None |
| When it stops running | The program turns late, silent or failing | Bot failure alerts | Error notifications | Nobody notices |
| Changing the process | Edit one step; the next run follows | Re-record the bot | Edit the flow on its canvas | Rewrite the prompt |
| Record | Step history, approvals and field-level changes | Bot logs | Execution logs | The chat history |
Connect the AI tool your team already uses, install the workflows, and run one real piece of work through them.
Install the Business Ops pack: meeting notes, weekly report, SOP, decision memo
Run this week's report through the workflow: same shape as next week's
Move one real process into a plan: phases execute in order, after your approval
Write the SOP as steps the AI executes, not prose it might read
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.
In ConvOps, the operations use case runs recurring business processes as workflows your AI agents follow: meeting notes, weekly reports, SOPs, decisions and multi-phase plans. Agents apply judgement where rules run out, gates hold sign-offs until they are approved, and each recurring process can be grouped into a program with an owner and a health verdict.
RPA repeats fixed clicks and fields, and breaks when the screen or the rule changes. ConvOps gives an AI agent a process instead: steps with instructions it applies to each case, gates the engine checks before the run moves on, and a record of every step. Use RPA where nothing varies; use a ConvOps workflow where each case needs reading and judgement.
Through programs. In ConvOps, a program groups the schedules behind a recurring process and gives it a verdict such as healthy, late, silent or failing. It turns silent when no run arrives for one and a half times its longest gap, and failing after three failed runs in a row, so a stopped process shows up before anyone asks about the missing report.
Yes. In ConvOps, put an approval gate on the step, and the gate holds it until an explicit approval is given, recorded with the account that gave it. A step can also require a report, such as a reconciliation or a control check, bound in enforce mode so the step waits until the report is filed. A refused advance returns what is missing.
Any function whose work follows a repeatable shape. In ConvOps, examples include a finance month-end close, HR onboarding and offboarding, an IT access review, procurement vendor checks, compliance control checks and the weekly report. Each one is a workflow with its own steps and gates, and a separate workspace can keep one function's work apart from another's.
With Plan. In ConvOps, Plan is a week and month board with a tray of unplanned tasks. Capacity comes from four weeks of completed work across the workspace, and spread places tasks on the least-loaded days before each deadline, with a preview first and all or nothing. The Plan next week wizard walks through the coming week in one pass.
ConvOps keeps the step history of every run: which step ran, the reasons given, and each approval with the account that gave it. Tasks and workflow instances carry field-level before-and-after changes, and every recorded metric value carries who recorded it and at which step. Each row keeps the agent's label apart from the verified account behind it.