AI agent workflows for operations: The business that runs on rails.

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

example · Claudeconnected
Plan the rollout of the new expense policy.
plan created · 3 phases drafted
Pilot, all teams, retire the old form. In that order.
sign-off · waiting for you
The plan is ready. Nothing starts before your sign-off.
Signed off.
complete · every phase landed in order
ConvOps · task · examplePlan
task

Expense policy rollout

step 1 of 6
define phases sign-off approvalin order verify complete
in short

What are AI agents for business operations?

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

  • A gate holds the step until an explicit approval is given, recorded with the account that gave it.
  • Phases of a plan run in order: the next one opens only when the one before it lands.
  • A program groups a process's schedules and gives it a verdict: healthy, late, silent, failing, paused, new or retired.
  • A program turns silent at one and a half times its longest gap, and failing after three failed runs in a row.
  • Plan sets capacity from four weeks of completed work across the workspace.
  • Every recorded value carries who recorded it and at which step.

best for

  • Operations, finance and HR teams with weekly or monthly processes
  • Processes that need a sign-off and a record
  • Teams whose SOPs sit unread in a wiki

not for

  • Fixed data moves between two systems, where an integration tool fits
  • One-off projects that never repeat

updated

the problem

The process lives in people.

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.

watch it work

One rollout, plan to done.

A real change, run as a plan from Claude. Then the weekly report, on a schedule.

01you, in Claude

Describe it once.

You describe the change in plain words. ConvOps creates a plan and drafts its phases. The work has a shape before anyone starts.

example
example · Claudeconnected to ConvOps
Plan the rollout of the new expense policy. Pilot with finance first.
plan created · 3 phases drafted
Pilot, all teams, retire the old form. Waiting for your sign-off.
02the AI · phases

Phases, in order.

Each phase is its own ordered chunk of work. Phase two stays locked until phase one lands. The engine checks that order, not etiquette.

example
example · plan · Expense policy rolloutnot started
  1. 1Pilot with financefirst
  2. 2All teamsafter the pilot
  3. 3Retire the old formlast

locked · waiting for sign-off

03you sign off

Nothing starts before sign-off.

The plan stops at the approval gate. You read the phases, change them or sign off. Until then, no phase starts.

example
waiting for approval

Sign off the expense policy rollout?

3 phases · pilot first · old form retired last

Change itSign off
signed offPhase 1 unlockedPhases 2 and 3 stay locked until their turn.
04the engine

Phase two waits for phase one.

The pilot runs and lands. Only then does phase two open. The order is checked on every advance, whoever is driving.

example
example · plan · Expense policy rolloutin order
  1. 1Pilot with financefirst
  2. 2All teamsafter the pilot
  3. 3Retire the old formlast

phase 1 of 3 · running

05you, once

The SOP becomes steps.

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.

example
Expense process (wiki) · last edited 2 years ago
example · SOP · expense claimworkflow
  1. Receipt attached
  2. Checked against policy
  3. Manager approveswaits for approval
  4. Finance posts it
06the schedule

Every Friday, the same report.

The weekly report runs on a schedule. Each fire creates the task with the whole process attached, so every week has the same shape.

example
every Friday · 16:00next fire · Friday 16:00fired
example · ConvOps · runsone task per fire
  • Weekly report · week 41drafting
  • Weekly report · week 40done
  • Weekly report · week 39done
example
example · Claudeconnected to ConvOps
Plan the rollout of the new expense policy. Pilot with finance first.
plan created · 3 phases drafted
Pilot, all teams, retire the old form. Waiting for your sign-off.
the workflow

The plan lifecycle, running.

Phases run strictly in order, and nothing starts before you sign off.

workflow · Planrunning · step 1 of 6
  1. 01

    Define

    The plan is described, scoped and broken down.

  2. 02

    Elaborate phases

    Child phases, each an ordered chunk of work.

  3. 03

    Sign-off

    No phase starts until the plan is approved.

    needs approval
  4. 04

    Phases run in order

    Each phase must land before the next one opens.

  5. 05

    Verify

    The result is checked against the plan.

  6. 06

    Complete

    The plan closes only when every phase is done.

what teams run it for

What operations teams run on it

Labelled examples from different operations functions.

example · financeenterprise

Month-end close in ordered phases

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

example · HR

New-starter onboarding

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

example · IT and securityenterprise

A weekly access review that shows when it stops

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

example · procuremententerprise

Vendor onboarding with a sanctions check

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

example · compliance

SOC 2 control checks every month

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

example · customer support

Daily ticket triage

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

example · analytics

A weekly KPI review

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

example · operations reporting

One report shape for every region

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

what it remembers

Why the rules are the rules.

Kept by the business, not by whoever was in the meeting. Recalled when the work needs it.

Decisions

Claims over 500 need a manager. Set in the Q3 review, with the reason.

why we did it

Where things live

The policy doc, the expense form and the finance sheet. Found once, kept.

where it lives

The record

Field-level history on every task and workflow run. Reviews stop being archaeology.

what changed

Linked to the work

Every memory points back to the plan or task that produced it.

traceable

recurring work

Run it every week

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.

schedule firesmonthly, in its time zone
gather inputsledgers and notes
reconciliationreport required
controller sign-offapproval
days to closemetric required
program verdicthealthy
the difference

Wiki process vs running process.

  • SOPs sit in a wiki nobody opens
  • Phases start before anyone signs off
  • Every report has a different shape
  • Reviews mean digging through old chats
  • SOPs run as workflow steps
  • Nothing starts before sign-off
  • One shape every week, on a schedule
  • Field-level history on every task and run

Order is a gate

Phases run under a sequential_children gate. The next phase activates only when the one before it is done.

Sign-off is a gate

An approval gate holds the plan until it is approved. The engine refuses the advance and says what is missing.

Recurring on a schedule

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.

What the audit covers

Field-level before and after on tasks and workflow instances, plus an activity feed. The agent label and the signed-in person stay separate.

next to what you use

ConvOps next to what you already use

RPA and automation tools move data. ConvOps governs the work that needs judgement.

ConvOps next to the operations tools teams already weigh
ConvOpsRPAA workflow automation toolA chat prompt
Handles judgementThe agent applies each step's instructions to the caseNo: fixed clicks and fieldsNo: the same actions on every triggerYes, in no fixed order
Approval gateA gate holds the step until it is approvedException queuesAn approval step where the tool offers oneNone
When it stops runningThe program turns late, silent or failingBot failure alertsError notificationsNobody notices
Changing the processEdit one step; the next run followsRe-record the botEdit the flow on its canvasRewrite the prompt
RecordStep history, approvals and field-level changesBot logsExecution logsThe chat history
start this week

Four moves to your first run.

Connect the AI tool your team already uses, install the workflows, and run one real piece of work through them.

  1. move 1

    Install the Business Ops pack: meeting notes, weekly report, SOP, decision memo

  2. move 2

    Run this week's report through the workflow: same shape as next week's

  3. move 3

    Move one real process into a plan: phases execute in order, after your approval

  4. move 4

    Write the SOP as steps the AI executes, not prose it might read

install these

built on

The parts doing the work.

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.

questions

What teams ask.

What is the operations use case in ConvOps?

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.

How is ConvOps different from RPA?

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.

How does ConvOps tell me a recurring process stopped running?

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.

Can a finance or compliance step require an approval?

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.

Which operations functions can run on ConvOps?

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.

How do we plan a week of operations work across the team?

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.

What record does ConvOps keep of operations work?

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.