Corin proposes.Policy authorizes.Your ERP commits.The ledger proves.
One loop carries work from email, Teams, or EDI to a posted document in SAP or Infor. Nothing posts to your ERP without a rule that allowed it and a record that proves it.
The AI agent platform, in four verbs.
Propose
Work arrives by email, Teams, or EDI — or Corin finds it already in the ERP: a blocked order, a failed match, a credit hold. Corin drafts the next step with its reasoning attached.
(drafts only — nothing is sent yet)
Authorize
Your policy decides what may run — set per workflow, per amount, per counterparty. Anything outside the bounds waits for a person.
(commits only what policy allows)
Execute
Corin does the work in SAP or Infor with your existing permissions. It sees only what your login sees — and never grants new ones.
(your permissions — never new ones)
Prove
Every commit lands in the ledger: what changed, who approved it, when. Replay any decision end to end.
(every commit maps to its approval)
The four-verb control flow: propose → authorize (your gate) → execute → prove. Sample ids — illustrative, not a customer record.
Two directions in — and on demand.
A stuck order inside SAP is work exactly like a new email. Corin picks both up — and answers when you ask.
Work arrives
A customer emails a PO. An EDI 850 lands. A Teams thread asks for a quote. Corin picks it up — nobody keys anything.
- Emailed PO with a PDF attached
- EDI 850 from a trading partner
- Web-form RFQ from your site
- Order pushed by an external system
sources: Email (Microsoft Graph) · Microsoft Teams · Slack · EDI X12 · Web forms · External systems (API / webhooks)
Already in the ERP
Corin subscribes to ION Data Fabric events and SAP Event Mesh, and sweeps on schedule — blocked orders and failed matches surface themselves.
- Order 4711 blocked on a credit hold
- Invoice failing its three-way match
- Quote aging past its follow-up window
sources: Infor ION Data Fabric events · SAP Event Mesh · Scheduled sweeps
On demand
Ask @corin anything, from Teams, Slack, the web, or any MCP client — a grounded answer with the proposed fix attached.
- "@corin why is order 4711 on hold?"
- "@corin which invoices fail the match?"
- "@corin can we give this customer net-45?"
sources: Microsoft Teams · Slack · Corin web · Any MCP client
Three futures on the table — nothing has posted.
Every change gets a dry run first — the outcomes on the table before anything posts.
quote request
- Hold list pricemargin 31.2% · win 41%
- Quote −4%margin 27.8% · win 63%selected — proceeds to your gate
- Quote −8%margin 24.1% · win 66%
Illustrative dry run — sample data, not a customer record.
Watch. Draft. Approve. Autopilot.
Autonomy is a dial, not a switch. Corin earns autonomy one workflow at a time — you set the pace.
Work that never gets dropped.
If SAP times out mid-commit, the loop resumes at the same step — no duplicate documents, no lost work.
A record of every decision: what changed, who approved it, when.
Replay any decision end to end — the rule, the approver, the commit, the document.
Illustrative ledger rows — sample data, not a customer record.
The platform, page by page.
Work graph
One live view of every job: what came in, what Corin did, what's waiting on you.
02Procedures
Give Corin the same paperwork you give a new hire — uploaded, compiled, tested, approved, versioned.
03Decisions
Watch. Draft. Approve. Autopilot — the dial, the gates, and the guardrails behind every commit.
04Learning
Corrections become versioned Procedure updates — measured and backtested, never invisible model changes.
05MCP connectivity
Corin speaks MCP in both directions — a governed client of 100+ servers, and an MCP server your own copilots can call, behind the same policy gates.
Four families run the loop.
Commerce — Quotes & Orders
From inbox RFQ to ERP-priced quote in minutes — then the order, the status, the changes.
Finance — Payables & Receivables
Supplier invoices matched and posted; your invoices out, collected, mandate-ready.
Trust — New‑customer checks
New customer → credit check, compliance screening, ERP account — before the first quote.
Service — Warranty & Support
Claims checked, recovery pursued, status answered — without a portal.