Why Us · Integration & IT
No nine-month integration project. Nothing installed in your ERP.
Most teams start from exports they already run. Your IT team grants read access. It doesn't build API bridges to your ERP, and nothing is written back without a person approving it.
Older or heavily customized systems, such as Epicor, Infor, Prophet 21 or a home-grown ERP, start the same way: if it can export a report, it can feed a Workbench.
How it connects
Three levels. Most pilots never need more than the first.
- 1Start here
The exports you already run
Open POs, requirements, sales orders and stock, as scheduled or manual exports from any ERP or spreadsheet. Export guides for NetSuite, Dynamics 365, Acumatica and Epicor.
- 2When it's worth it
One read-only connection
Replaces the exports for the data the workflow needs. Whether you need it is decided with your IT team in week 1 of the pilot, not before you start.
- 3Only if you turn it on
Approved write-back
Off by default, and off for the whole pilot. Turned on afterwards by type of update, such as PO promise dates, with an approver for each.
Email is read through the access your IT team grants, limited to the mailboxes in the workflow. With Workbench Starter, it's read by your own Claude or ChatGPT and never reaches us.
For a small IT team
What your IT team does, and what it doesn't
Does, typically a few hours during setup
- Grant read access to the mailboxes in the workflow
- Share or schedule a few ERP exports
- Walk through the data flow in a security review
- Decide whether a read-only connection is worth it
Doesn't
- Build or maintain API bridges
- Install or customize anything in your ERP
- Give write access during the pilot
- Run a data migration or replace a system
Write-back guardrails
AI never writes a blind update to your ERP.
Every change to a live record passes a person first. The evidence sits on the same card, so checking it is quick, and nothing reaches your ledger or your shop floor on the strength of an AI answer alone.
Off by default
Nothing is written to your ERP during the pilot. Write-back is switched on later, one type of update at a time.
Proposed, never silent
Every update is shown as a proposed change, field by field, from the old value to the new one.
The evidence is on the card
The approver sees the source, such as the supplier's email, next to the record it would change. Reported facts are labeled as reported.
A named person approves
Each type of update has an owner and, where you want one, a threshold, such as expedites over $5,000 going to the plant manager.
Every write is recorded
Who approved it, when, what changed, and the evidence behind it.
Proposed ERP update
Waiting for approvalPO 4512 · line 2 · promise date
Source: Ridgeway email, Oct 5: "New ship date Oct 26." Reported by supplier.
Affects: Run A-88 on Oct 20, and two customer orders worth $214K.
Approver: Production planner
Illustrative example · sample company and data
What we need from IT
| Workbench Starter | Operations Workbench | |
|---|---|---|
| Install anything | No | No |
| Access needed | The person's own email connector | Read-only access to the systems the workflow uses |
| Who grants it | The person | Whoever administers those systems |
| Time from IT | None | Typically a few hours during setup |
| Changes to your systems | None | None without approval |
Bring your IT lead to the demo.
We'll walk through the data flow for your ERP and what your team would need to do.