Four agents we've built, and the pattern behind them.
These are examples, not a catalogue. Every engagement starts with your workflow — these show the shape of what we build and how far it goes into your systems.
Reference agents
PO → Order entry agent
Reads purchase orders arriving as email or scanned PDF, extracts the header and every line, creates the order in your OMS, and flags low-confidence fields for approval before anything posts.
- Outlook
- NetSuite
- Zoho
- custom OMS
Invoice → PO matching agent
Matches incoming invoices against open POs on vendor, totals and line items. Clean matches post themselves; anything off routes to AP with the discrepancy shown side by side.
- Gmail
- QuickBooks
- Xero
- SAP B1
Shipment status auto-reply agent
Reads “where’s my order” emails however they’re phrased, looks up live status, and drafts a customer-ready reply. On-time answers can send unattended; delays always show a person first.
- Outlook
- Zendesk
- carrier APIs
Exception routing agent
Not a separate product — the trust layer under the other three. You define what counts as an exception; it routes each one to a named owner with full context and a clock, instead of guessing quietly.
- Slack
- Teams
- your ticketing tool
Your workflow isn't on this list.
That's the normal case. The four above share the same ingestion, extraction, approval and audit core — pointing it at a new document type and a new system is the work, and it's measured in days.