For finance leads

A capped first step, and a measure you agree before it starts.

We build agents that do one workflow in your operation, such as matching invoices to orders and receipts. Before you spend beyond the first step, you see what the agent did, what it was refused, and the result against the measure you set.

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.

The cost of AI agents has two parts. One is what you pay for the work. The other is what it costs when an agent does the wrong thing: a payment to the wrong account, an order above budget, a price sent to the wrong customer. A finance lead needs both on the table before the first invoice.

Where we start. We start with one workflow where the money is visible: matching invoices to orders and receipts, following up a late order with a supplier, or preparing a payment run for approval. The agent does the reading, the matching and the drafting across your ERP, your accounting system and email. A person on your team approves each payment, each adjustment and each order above the threshold you set.

What changes for you. You approve a fixed scope and a fixed price, not an open budget. You agree the measure with us before the pilot starts, such as time spent per batch or exceptions caught before payment. At the end you see the measured result and decide whether to go on. We do not promise a saving before the pilot measures it.

Follow one workflow

One payment run, with the money steps on the record.

An illustration of invoice matching and payment approval. The agent prepares the run. Your people approve it.

  1. 01Accounting

    Receive a credential for this payment run only. It can read and propose. It cannot pay.

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

    Match each supplier invoice to its order and its goods receipt.

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

    Flag an invoice whose price differs from the order, and draft a query to the supplier.

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

    An invoice asks for payment to new bank details. Changing a supplier's bank details is outside this job, so the step is refused.

    Who approves
    No approval on this step
    On the record
    change-bank-details · refused · outside permission
  5. 05Accounting

    Propose the payment run. It waits until the controller approves it.

    Who approves
    Controller
    On the record
    payment-run · approved by controller
  6. 06Office suite

    Write the matched and queried invoices to the month-end file.

    Who approves
    No approval on this step
    On the record
    export-summary · allowed

In short

  • What does the first step cost?It is a workflow assessment at a fixed scope. Fixed price, quoted after one call.
  • What do we get for it?A written scope and a price for a pilot, and a plain view of what a wrong action in that workflow would cost you.
  • How do we know whether it worked?You agree the measure before the pilot starts. The pilot ends with the measured result, and the record shows every step behind it.
  • What can go wrong, and what stops it?An agent can be asked to pay the wrong party. It can do only what its job allows, the payment waits for a person, and the refusal is on the record.

Workflows a finance team can start with.

Built items run in the public sandbox today, with real agents on demo data. Designed items list their steps here. On request means we scope it with you in the 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

    A purchase checked against a spending mandate

    The agent holds a ceiling, a list of approved merchants and an expiry. A bundle above the ceiling is refused.

    Run it in the sandbox
  • Built

    An order that stops at the threshold

    The agent drafts the order and checks stock. Above the threshold, the order waits for a person.

    Run it in the sandbox
  • Built

    Supplier follow-up on a late order

    The new delivery date waits for the buyer. The expected invoice date updates after the approval.

    Run it in the sandbox
  • Designed

    Invoice matching and payment approval

    The run above: match each invoice, query each price difference, refuse a bank detail change, and wait for the controller.

  • Designed

    Reconciliation between operations and accounting

    Match receipts to invoices, list each difference, and propose each adjustment. A controller approves each one.

  • On request

    Month-end accruals

    An agent drafts accruals from open orders and receipts for your review.

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 promise a saving. The pilot measures the result against the measure you agreed.
  • It does not replace your accounting system or your approval rules. It works inside them.
  • It does not decide which payments need a person. Your finance team does.
  • A public funding route depends on the program and on your firm. We say whether one may apply. We do not promise it.
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.

We will say whether an agent should do it, what a person should still approve, and what the first step costs. Fixed price, quoted after one call.

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