For the operations lead

AI agents for COOs: the steps, the systems, who approves.

An agent takes the work your team carries between the ERP, email, documents and accounting. Your supervisors approve the steps that matter, in the systems you already run.

Send this page to your teamEmail it

A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.

What changes on Monday

The week a pilot goes live, the work looks different in a few specific places.

  • The late-order list is chased by the agent. Your buyer reads the drafts and approves any change to a date.
  • Nobody keys a supplier reply into the ERP by hand. The agent reads it, and anything that changes a commitment waits for the person who owns it.
  • Each crossing from one system to the next is on the record. A question about an order has an answer you can show.

What stays the same: your systems, your approval rules and the people who sign. The agent works inside the permission you set for each job.

Your data does not need to be perfect

The assessment finds one workflow where the data is ready enough, and says what to fix for the next. We work from the systems you run today, named by type: the ERP or MRP, accounting, email, the document store, ticketing, and the tools you built in-house.

How a pilot runs

We sit with the person who runs the process and write down the steps as they are done today. We mark each step that changes an order, commits money or reaches a customer. Those steps go to a named person. The pilot runs supervised, on your systems, with the record on from the first run.

Follow one workflow

One late shipment, from the operations side.

An illustration of an order-to-shipment job. Each step names the system, the person who approves and the line on the record.

  1. 01Ticketing

    A ticket flags a customer shipment that missed its date. The job opens.

    Who approves
    No approval on this step
    On the record
    job opened · from ticket
  2. 02ERP

    Check the order, the stock on hand and the next production slot.

    Who approves
    No approval on this step
    On the record
    read-order · allowed
  3. 03Email

    Read the carrier's update and draft a new delivery date for the customer.

    Who approves
    No approval on this step
    On the record
    draft-update · allowed
  4. 04ERP

    Move the ship date on the sales order. The step waits for the planner.

    Who approves
    Planner
    On the record
    change-ship-date · approved by planner
  5. 05Accounting

    Extend the customer's payment terms to cover the delay. That is outside the permission for this job, so the step is refused.

    Who approves
    No approval on this step
    On the record
    change-terms · refused · outside permission
  6. 06Email

    Send the approved update to the customer.

    Who approves
    No approval on this step
    On the record
    send-update · allowed
  7. 07Ticketing

    Close the ticket with a link to the record of the job.

    Who approves
    No approval on this step
    On the record
    close-ticket · allowed

In short

  • Will it work with the systems we have?It works across the ERP, email, documents and accounting you run now. The assessment lists each system and what it needs.
  • Our data is a mess. Can we still start?Yes, with one workflow where the data is ready enough. The assessment says what to fix for the next one.
  • Who approves what?Your people, step by step. You name the steps that change an order, commit money or reach a customer.
  • What happens when the agent gets it wrong?A step outside its permission is refused and recorded with the reason. A sensitive step waits for a person.

Operations workflows, and the state of each.

Built runs open in the sandbox with real agents on demo data. Designed items list their steps on this page. On request means we scope it in an assessment.

Built
We have run it.
Designed
The steps and approvals are designed. It has not run yet.
On request
We scope it with you before we design it.
  • Built

    Supplier follow-up across four systems

    The agent chases a late part, strips a hidden instruction from the supplier reply, and waits for the buyer on the date change.

    Run the late-part follow-up
  • Built

    Requisition with an approval threshold

    Stock is checked and the order drafted. Above the threshold the order stops for a person, and the supplier cannot be swapped.

    Run the requisition
  • Built

    An order line quoted by a supplier

    Your agents ask a supplier's agents for a quote. The permission narrows at the company boundary, and both sides keep the same record.

    Run the two-company order
  • Designed

    Late shipment to customer update

    Steps: read the ticket, check the order and stock, draft the customer update, the planner approves the new date, send the update, close the ticket.

  • Designed

    Goods receipt against the purchase order

    Steps: read the delivery note, match it to the order lines in the ERP, flag shortages and damage, the receiving lead approves the receipt, pass the matched lines to accounting.

  • On request

    Quoting and RFQ handling

    Requests read from email, costs and drawings gathered, a draft quote for the estimator to release.

The five guarantees

Every workflow on this page carries them. Each one has a limit, and we state it.

  1. 01

    Each agent can do only what it was allowed to do, for that job.

    The limit

    Permissions are only as good as the rules you approve.

  2. 02

    Sensitive steps go to a person.

    The limit

    You decide which steps are sensitive.

  3. 03

    Documents are inspected before an agent sees them, and answers are checked before they leave.

    The limit

    Filters cover stated patterns and languages.

  4. 04

    Every decision is recorded, including refusals, in a record an outside party can check.

    The limit

    It shows what agents did, not whether a business rule was wise.

  5. 05

    It can run in your building, on one small machine.

    The limit

    Local models differ from the largest cloud models.

What it does not do

  • It does not fix your data. The assessment says what one workflow needs and what to fix for the next.
  • It does not change your approval rules. It follows the ones you set, step by step.
  • It does not run unsupervised in the pilot. A person approves each sensitive step until you choose otherwise.
First step

Assessment, pilot, production.

Each step has a fixed scope and ends with something you keep.

  1. 01

    Workflow assessment

    A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.

    What you get
    A short, paid look at one process, with your process owner.
    What you keep
    A written scope and a price for a pilot.

    Fixed price, quoted after one call.

  2. 02

    Pilot workflow

    One workflow on your systems, supervised, with the record on from the first run.

    What you get
    One workflow at a fixed scope, with your people approving the sensitive steps.
    What you keep
    A working workflow and a measured result.

    Fixed price, quoted after one call.

  3. 03

    Production and run

    The workflow in production on Ares, on your hardware or hosted in your country.

    What you get
    Support, and the next workflows.
    What you keep
    The workflow, and the record of every decision it made.

    Recurring fee for operation and support.

Questions and answers

Tell us about one workflow.

Bring the workflow your team carries between systems today. We will say whether an agent should do it, and what the first step costs.

A senior member of the team replies within two business days.