Why Us · Integration & IT
No nine-month integration project. Nothing installed in your ERP.
Most teams start from exports they already run, with read access your IT team grants. Nobody builds 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 Operations Resolution.
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 the free trial, 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
How we work with IT and the business
Your IT team governs. Your business team decides. LevelOneAI sets it up and keeps it running.
LevelOneAI doesn't ask your IT team to build another AI solution. It takes a workflow your business has chosen and IT has approved, sets it up and keeps it running, while IT keeps control of the technology and the business owns the outcome.
Your business team owns the process and the decisions
- Naming the problem worth fixing
- The business rules and exceptions
- Checking results against real work
- The operational decisions
- Improving the workflow within approved limits
Your IT team governs the technology
- Data access and system permissions
- Which AI tools and accounts are approved
- Security and compliance requirements
- Approval to go live
- Ongoing oversight of access and controls
LevelOneAI sets it up and keeps it running
- Configuring the workflow to your business
- Connecting the approved sources
- Validating it on your own data
- Running and maintaining the product, and supporting changes
Business teams don't have to become AI developers. IT doesn't have to build every workflow.
One workflow, three owners
Supplier delivery exceptions, from first idea to running
- 1Name the problemOperationsSupplier delays are found late, and buyers spend hours piecing together what they affect.
- 2Approve accessITApproves the ERP exports and the buyers' mailboxes the workflow may read.
- 3ConfigureLevelOneAIConfigured and validated against your actual supplier workflow before going live.
- 4ValidateOperationsChecks the results against real work.
- 5Approve go-liveITReviews the data flow, permissions and readiness.
- 6Run itOperations and LevelOneAIBuyers and planners resolve exceptions. LevelOneAI keeps the workflow running.
- 7GovernITKeeps oversight of what is connected and who can see or approve what.
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
After it goes live
When something changes or breaks, who handles it?
Setup is a few hours of IT time; the bigger question is what happens in month six. Here's where the line sits.
- Something is flagged or linked incorrectlyLevelOneAI investigates and corrects it. Your team confirms the fix.
- The team wants different thresholds or ownersYour business team decides. They're settings, changed by your team or by us on request.
- A new data source is neededIT approves the access. LevelOneAI adds it to the workflow.
- An ERP export changes formatWhoever owns the export makes it available. LevelOneAI updates the workflow.
- Something in LevelOneAI breaksLevelOneAI.
- Identity or access policies changeIT.
- Write-back is neededIT approves the permission. The business defines what may be written and who approves it.
What we need from IT
| Free Trial | Operations Resolution | |
|---|---|---|
| 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 and your workflow owner to the demo.
We'll walk through the workflow, the data access it needs, what your IT team controls, and what LevelOneAI takes responsibility for.