Procurement

Agents that chase suppliers and line up order changes. Your buyer approves them.

The agent reads the open orders, writes to the supplier and prepares the change in your ERP. Your buyer approves each new date, quantity or price, and every step goes on a record you can check.

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

AI agents for procurement take the follow-up work that fills a buyer's day: the late order, the missing confirmation, the reply that moves a date in three systems at once. Today a person reads the supplier's email, changes the order in the ERP and tells accounting. The agent does the reading and the carrying between those systems. The buyer keeps the decisions.

What changes for your buyers

  • They work from a short list of changes to approve, not from an inbox.
  • Each proposed change arrives with the order and the supplier reply beside it.
  • A change they reject stays rejected, and the rejection is on the record.

If your ERP already has an assistant your buyers use, keep it. The agent takes its answer to the supplier and to accounting. The industrial page shows the wider set of operations workflows.

Follow one workflow

One late part, from the open order to the new invoice date.

The task: "Part 4410 is late. Follow up with the supplier." You can start this run yourself in the sandbox.

  1. 01ERP

    Take the task and receive a credential for this job only. The credential expires when the job ends.

    Who approves
    No approval on this step
    On the record
    credential issued
  2. 02ERP

    Read the open orders for part 4410.

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

    Draft the follow-up email to the supplier.

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

    Read the supplier reply and its attachment. One line in it is a hidden instruction. It is struck out before the agent reads it.

    Who approves
    No approval on this step
    On the record
    supplier-reply · redacted · hidden instruction
  5. 05Documents

    Try to send a drawing to a new address. The address is outside the permission for this job, so the step is refused.

    Who approves
    No approval on this step
    On the record
    send-drawing · refused · outside permission
  6. 06ERP

    Change the delivery date on the order. The step waits until the buyer approves it.

    Who approves
    Buyer
    On the record
    change-order · approved by buyer
  7. 07Accounting

    Update the expected invoice date.

    Who approves
    No approval on this step
    On the record
    update-date · allowed

In short

  • What if the agent changes an order it should not?Not on its own. In the workflow we build, every change to a date, a quantity or a price waits for your buyer until you decide otherwise. The decision goes on the record.
  • What if a supplier email carries an instruction meant for the agent?Replies and attachments are read at the door before the agent sees them. A hidden instruction is struck out, and the record shows where it was.
  • What if the agent sends a drawing to the wrong address?The permission for each job lists who the agent may write to. A send outside that list is refused and recorded with its reason.
  • What if an order is above what we allow without a signature?You set a threshold in the workflow. Above it the order waits for the person you name, and the record shows who approved it.

Purchasing workflows, and the state of each.

Some of these run in the sandbox today. The others are set out step by step, or scoped with you.

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 on a late order

    The agent reads the order, writes to the supplier and prepares the date change. The buyer approves it.

    Run it in the sandbox
  • Built

    Requisition that stops at a threshold

    The agent drafts the order and checks stock. An order above your threshold waits for a named person, and the supplier stays as set.

    Run it in the sandbox
  • Built

    Buying within a spending mandate

    The agent buys only from approved merchants, under a ceiling and before an expiry. An offer outside the mandate is refused.

    Run it in the sandbox
  • Built

    A quote request that crosses to a supplier

    Your agents ask a supplier's agents to price one order line. The permission narrows at the company boundary, and both sides keep a record.

    Run it in the sandbox
  • Designed

    RFQ round and quote comparison

    The agent sends the request to the suppliers you list and sets the quotes side by side. The buyer makes the award.

  • Designed

    Order confirmation check

    The agent compares each supplier confirmation with the purchase order and lists every change. The buyer approves each one before the ERP is updated.

  • Designed

    Supplier document renewals

    The agent watches expiry dates on supplier certificates and asks for renewals. A person accepts each new document.

  • On request

    Price list updates against open orders

  • On request

    Spend reports across systems

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 choose suppliers or award a contract. Your buyer does.
  • It does not negotiate. It drafts the message, and a person decides what to offer.
  • It does not replace your ERP or your purchasing policy. It works between your systems.
  • It does not decide which changes need a buyer. You set that, and the threshold.
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.

Name the purchasing step your buyers repeat most. We will say whether an agent should take it, and what the first step costs. Fixed price, quoted after one call.

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