AI agents · finance

The Procurement Agent

It watches what you consume, notices when a reorder is due, compares vendors on delivered cost rather than headline price, and drafts the purchase order. Committing spend stays with a person, because a purchase order is a contract and an agent should not be signing them.

Where is spend leaking?

Send a year of AP detail. We will show you duplicate vendors, off-contract spend, and pricing drift.

1 / 3
Drafts POs, never commitsCompares on landed costCatches maverick spend

What it does

Six jobs, end to end.

Each of these is work a person does today. The agent does them in sequence and stops at the first thing it is not confident about.

Watch consumption

Usage patterns per item, site, and season, so a reorder is proposed on the trend rather than when someone notices a shelf is empty or a licence has lapsed.

Compare on landed cost

Unit price plus freight, duty, payment terms, and historical defect or return rate. The cheapest quote is regularly not the cheapest vendor and only the delivered figure shows it.

Draft the purchase order

Correct vendor, agreed pricing from the contract, right GL coding and dimensions, and the delivery terms that actually apply.

Catch off-contract spend

Buying from a vendor at list when you hold a negotiated rate, or from a new vendor when an approved one supplies the same thing. This is where most recoverable savings sit.

Flag price drift

A vendor whose pricing has crept above the agreed schedule over eighteen months. Nobody notices monthly; the agent compares against the contract every time.

Route for approval

Through your existing matrix by amount, category, and department, with the comparison and reasoning attached so the approver is deciding rather than guessing.

Authority

Where this agent sits, and who decides.

Level 1 · default

Draft and recommend

Purchase orders prepared with vendor comparison attached, waiting for a person. This is where most customers keep it permanently.

Level 2 · narrow

Reorder within contract

Enabled for specific items from contracted vendors under a threshold — consumables and licences on agreed pricing, where the decision is genuinely mechanical.

Never

Commit spend at will

A purchase order is a contractual commitment. There is no configuration in which an agent creates an unbounded obligation to a vendor.

The savings are in comparison, not in negotiation

Procurement software is usually sold on negotiating leverage, which is real and mostly matters above the mid-market. For a company between $10M and $150M, the recoverable money is almost entirely in three unglamorous places: buying off-contract when a negotiated rate exists, paying prices that drifted above an agreed schedule, and duplicate vendors supplying the same thing at different rates.

None of these require negotiating harder. They require noticing, consistently, across thousands of transactions — which is exactly the shape of work that a person does badly and software does well.

Most mid-market procurement savings are not won at the negotiating table. They are lost quietly afterwards, by nobody checking the invoice against the deal.

Landed cost changes the ranking more often than you would expect

A quote is a unit price. What you actually pay includes freight, duty where applicable, the working-capital cost of payment terms, and the historical rate at which that vendor ships late or ships wrong.

Once those are included, the cheapest quote is frequently not the cheapest vendor. A supplier three percent higher on unit price with net-60 terms and a clean delivery record regularly beats one offering net-15 and a five percent defect rate — and no purchasing decision made from a quote sheet can see that.

Why it drafts rather than orders

A purchase order creates a legal obligation to pay. Automating the creation of obligations is a different risk class from automating a coding decision, and the failure mode is not a misclassified expense but a commitment you did not intend to make.

Level 2 exists narrowly for genuinely mechanical reorders — a consumable from a contracted vendor at agreed pricing under a threshold — and even there it is bounded by item, vendor, and amount. Everything else is drafted, with the comparison attached, for a person to commit.

Questions

What people ask first.

Will it order things automatically?
Only at Level 2, only for specific items from contracted vendors under a threshold you set. Everything else is drafted for a person, because a purchase order is a contractual commitment.
How does it know our contracted pricing?
From the vendor agreements held in the business graph. Where a contract has not been captured it compares against your own purchase history and flags the drift rather than assuming a rate.
Does it handle inventory reordering?
Yes, on consumption trend and lead time rather than a fixed reorder point, which handles seasonality better. It is one of the higher-value uses for distributors specifically.
Can it work without our using your purchasing module?
Yes. It can read AP history and vendor contracts and surface off-contract spend and pricing drift as analysis, even where the PO process stays where it is.
What about services procurement?
Subcontractors, professional services, and software subscriptions are handled as contracted spend with renewal dates tracked — which is where most software over-spend hides.

Find the spend that leaked.

A year of AP detail is enough to surface duplicate vendors, off-contract buying, and pricing that drifted.