Purchase Order Automation
Purchase order automation that runs on your purchasing rules.
We encode your purchasing rules — approvals, price checks, vendor terms — into AI agents that draft the PO and chase the acknowledgment.
Built with the leading AI platforms
NVIDIA
Anthropic
The broken Friday
The PO goes out. Then the chase begins.
From purchasing desks we have sat with: a PE-backed manufacturer running seven ERPs across its business units, where a purchase order still starts as an email or a hand-written form.
Requisitions on paper and email
Parts of the business still hand-write requisitions; the rest email a spreadsheet. Nothing enters the ERP until a buyer reads it and keys the PO.
Approval by email ping
Spend approvals move as email threads across business units — the PO waits in a drafts folder while someone chases the signature.
The acknowledgment chase
The PO goes out by email; the vendor’s confirmation comes back to one buyer’s inbox, or doesn’t. Nobody knows what is confirmed and what is open.
Price checked against the last invoice
Whether the vendor’s price matches the contract gets checked against memory or the last invoice — when it gets checked at all.
The rules live in one buyer’s head
Each vendor’s quirks — minimums, lead times, the right contact for a shortage — live with the buyer who has always run that desk.
Seven ERPs, seven PO processes
Each business unit keys POs its own way into its own ERP — the sponsor’s roll-up never sees a clean picture of open spend.
What manual costs
The purchase order is typed. Everything else is chased.
What the manual way looks like at a manufacturer whose requisitions arrive by email and paper, and whose purchasing rules live in buyers’ heads. Your numbers will differ — the first week puts figures on yours.
From anonymized engagements — PE-backed manufacturing business units
How it works
We encode your purchasing rules.
No purchasing platform for your team to adopt. The rules your best buyer carries become the check every PO passes.
- 01
Shadow one purchasing desk
We trace a week of POs from requisition to acknowledgment — reading, keying, chasing — and write down the rules only one buyer knows.
- 02
Encode the purchasing rules
Approval thresholds, contracted prices, vendor terms, per-business-unit logic — documented, encoded into agents, and deployed in your cloud environment.
- 03
POs draft; buyers decide exceptions
Each requisition is read against the rules and the PO drafted and dispatched; violations land in an exception queue a buyer decides.
The software sells you a license. Your purchasing rules are the product.
Purchasing software is a license plus a configuration project your team then maintains inside the vendor’s data model. The demo assumes one clean catalog; your business units run seven ERPs and a spreadsheet.
We are an AI implementation services firm: our AI reads each requisition against your encoded rules, drafts the PO, and routes only exceptions to a buyer — running in your cloud environment, yours to keep.
Led by Peter Enestrom.
Questions
Asked by presidents and purchasing leads.
The straight answers, before you book anything.
What’s holding your business back?
A workflow ready for automation. An AI product you want to build. A problem that has sat on the roadmap for years. Let’s talk about what it would take to solve it.
Talk to Zaigo