Most teams start with one person on Operations Workbench Starter, free for 30 days. Add LevelOneAI in Claude or ChatGPT, connect your email and add any exports you have, such as open POs or a schedule. Starter shows which changes put orders at risk, with the evidence, and tracks each one to a close. When the whole team needs it, with live ERP data, approvals and write-back, that's the Operations Workbench.

How do Starter, the Workbench and the Operations Engine fit together?

The LevelOneAI Operations Engine does the work: it treats each order, PO or job as one record (Work), compares what changed with what was promised (Context), works out what it affects and who needs to decide (Decision), and assigns, drafts and tracks the next step (Action), until it's resolved. Starter runs the engine on one person's email and the documents they add. A Workbench runs it across a whole team's email, ERP and CRM for one workflow, with live data, approvals and write-back.

Is there a free trial?

Yes. Operations Workbench Starter is free for 30 days, and you don't need a card. After that it's $199/month or $1,990/year (two months free), for 1 user and 1 mailbox. If you don't continue, your account becomes read-only and your data is deleted 30 days later.

What do I need to use Starter?

A paid Claude or ChatGPT plan (the free tiers don't include the access it needs) and a Gmail or Outlook mailbox. For work email, a business or enterprise plan from that provider is recommended. Documents are optional: exports from any ERP or spreadsheet work.

What's the difference between Starter and the Operations Workbench?

Starter works from one person's email and the exports they add, and you set it up yourself in minutes. It's built to show the value on your own work. The Operations Workbench connects live to your ERP and planning data, runs on its own, puts the whole team in one queue, and adds approvals, drafted follow-ups and write-back. Starter fees paid in the 6 months before you buy a Workbench are credited toward its setup.

Which documents should I add to Starter?

Whatever you have, or none. It works on email from the first run, and tells you which document would sharpen the results most. Typical ones are an open-PO export, a production schedule, open sales orders or an AR aging report. It keeps only the fields it needs from them, encrypted, never the files.

It says what it doesn't know. Each fact shows its source and when it arrived. When an email could match more than one order, it asks instead of guessing, and when a document is missing it says "impact not assessed" rather than "no impact." Your team makes the call.

How does billing work?

Starter is billed monthly or annually by card, with a receipt emailed for every payment and invoices on your billing page. Cancel anytime. A Workbench is a one-time setup fee, invoiced on the schedule in your quote, plus an annual platform fee that starts at go-live.

When does my team need a Workbench?

When the work depends on more than one person's inbox: the evidence sits in your ERP, CRM or planning data, several people need to see the same item, and someone has to make sure it closes. A Workbench gives the team one queue, one record per item, approvals and a team view.

What's built, and what do you configure for us?

The Operations Engine, the work queue, the work record, approvals, follow-up tracking and the team view are built. For each Workbench we configure the connections to your systems, the rules that decide what counts as an exception, who owns what, what closes an item, and whether approved changes are written back. Which systems it connects to, and how, is worked out during setup.

Operations Workbench Starter is free for 30 days, then $199/month or $1,990/year. An Operations Workbench is a one-time setup fee, from $20,000 per workflow, plus an annual platform fee that's included in your quote. There's no ongoing services fee: once it's live, your team runs it, and our help is optional. The platform fee covers hosting, AI processing, connector updates and improvements to the Operations Engine. It starts at go-live, and in the first year you can cancel 90 days after go-live if the agreed measures aren't met. The payback calculator compares the setup fee with what the delay costs you each year. The next Workbench reuses the connections you already have, so it costs less to set up. See Pricing for what's included.

How long does setup take?

Starter works the same day. A Workbench typically goes live in 6 to 12 weeks, depending on how many systems it connects and how complex the rules are. We agree the baseline and what success looks like before setup starts.

What happens to our ERP and CRM?

They stay where they are and keep the master data. A Workbench reads from them. Write-back is optional: whether approved updates go back, and to which systems, is decided during setup. Nothing changes in your systems without approval.

What data does LevelOneAI keep?

It's designed to keep only what it needs to run the work, such as references to the source, the facts it extracted (a date, a quantity, a price), status, owners and decisions. For a Workbench, exactly what's stored is agreed with you during setup. Starter never stores email: it keeps short labels, plus the fields it needs from documents you add, encrypted.

What will this ask of our IT team?

Starter needs no IT: you connect your own email in Claude or ChatGPT, and there's a one-page security summary to share with IT. A Workbench needs read-only access to the systems the workflow uses, granted once by whoever administers them, and typically a few hours of IT time during setup. Nothing is installed, and nothing changes in your systems without approval. See Growing Businesses if you don't have an IT department, or Enterprises for how we fit an IT review.

What happens when it isn't sure, or data is missing?

If an email could belong to more than one order or PO, it shows the candidates with their evidence and asks a person to confirm, instead of guessing. If a source is unavailable or a record can't be found, the item is marked incomplete, so your team knows the picture isn't complete. Every fact is labeled confirmed, conflicting, inferred or unknown.

Is this a product or a consulting engagement?

A product. The Operations Engine, the work queue, the work record and approvals are built. Setup configures them to your systems, rules and owners for one workflow. You pay a one-time setup fee and an annual platform fee. There's no ongoing services fee, so your team runs it without us.

Do you have a SOC 2 report?

No SOC 2 report yet. We'll walk your security team through the data flow and complete your security questionnaire on request.

What happens to our data if we stop?

You can export your work history and audit trail. With Starter, your data is deleted 30 days after you cancel or after a trial ends without a paid plan. Your ERP and CRM keep their own data, because they were the record all along.

That's decided with you during scoping, based on your security and IT requirements.

To read the messy information around a piece of work (the email, the attachment, the system field), match it to the right order or PO, compare it with what was promised, and recommend the next step. Every fact is labeled confirmed, conflicting, inferred or unknown, with its source. Your people make the call, and nothing changes in a system without approval.

Why can't we just add an AI agent?

You can, and it will do the steps. What an agent won't do on its own is keep one record of each order across email and your systems, notice a change nobody asked about, know which promise it breaks, and keep the issue open until it's resolved. That's what you'd have to build and maintain around it. LevelOneAI already does that, and works alongside the agents you use. See Why AI Agents Fail under Resources.

How is this different from process mining?

Process mining reads event logs from your ERP or CRM, so it can't see what happens in email, spreadsheets and phone calls, which is where most exceptions start. It also tells you where the process breaks; it doesn't work each exception to a close. A Workbench does.

Why not wait for our ERP or CRM vendor to add AI?

Use it. ERP AI is getting good at work inside the ERP, such as reading a supplier's email and proposing the PO change. A Workbench is for what happens next, across systems: which jobs and customer orders the change puts at risk, what the planner's sheet says, who has to approve, and whether it was actually resolved. If the problem starts and ends inside your ERP, its own AI may be all you need.

When is our ERP's own AI enough?

When the problem starts and ends inside the ERP, updating the record is the whole job, and everything the decision needs is already there. Add a Workbench when the change matters because of what it affects elsewhere (jobs, customer orders, invoices), when the numbers people trust live in a spreadsheet or portal, when resolving it takes several people and an approval, or when someone has to confirm it was actually resolved.

What if our workflow changes?

Rules, owners, thresholds and closing conditions are configuration, so they can be updated as your process changes, without a new project.

What if our team doesn't adopt it?

A Workbench brings the context to each piece of work instead of asking people to go and look for it, and it fits around the systems they already use. We also agree the measures up front, so you can see whether it's working.

All insights

General

Your Procurement System Tracks the Purchase Order. Who Tracks What Happens After It Changes?

By Shanshan Ma

Buyers spend more time chasing changed supplier commitments than placing orders. How LevelOneAI keeps every promise and every slip tied to the PO, and keeps the exception open until it's actually resolved.

"They said the 12th. Then the 26th. What did they say yesterday?"

PO 4512 for machined housings was confirmed for Oct 12. Two weeks ago the supplier emailed: the 26th. Yesterday, a second email: "working on recovery, will confirm Monday." The ERP still shows the 12th. Planning needs the parts on the 20th. The buyer has 141 other open POs and is piecing this one together from three threads.

The PO is still in the system. The work of resolving it isn't.

Buyers spend their time after the PO, not on it

Procurement systems handle requisitions, POs, approvals and receiving. But supplier commitments keep moving: dates slip, quantities ship short, confirmations never arrive, a supplier offers a substitute that engineering has to review.

Each change sets off the same questions:

Which PO and part is this about?
What did they promise before, and what changed?
Does the new date still meet the requirement?
Who needs to weigh in, and what's still outstanding?
When is this actually resolved?

The buyer answers them by searching old emails for the last promise, comparing it with the ERP, asking planning for the need date and going back to the supplier. When the supplier replies without fixing anything, it starts over.

An alert is not a resolution

Dashboards, portals and alerts help. They show a date changed. They don't tell the buyer what it affects, whether the supplier's recovery plan is credible, or whether the issue will stay visible after the first follow-up goes quiet. A task in someone's queue doesn't mean the answer ever came back.

So the buyer becomes the integration layer, reconciling, interpreting and chasing across teams. Another system to check doesn't change that.

What LevelOneAI does differently

LevelOneAI treats each supplier exception as a piece of work with a history, not a message. For every PO that changes, it:

Keeps the full commitment history. Every date the supplier promised, when they promised it and the email that says so: Oct 12, then Oct 26, then "Monday." Nobody has to dig for the last promise.
Shows conflicts instead of overwriting. When the supplier's date and the ERP disagree, both are shown and the buyer decides. The ERP stays the record.
Connects the change to what it affects. The need date, the requirement and, where planning data is available, the production run that depends on it.
Shows the next step and who owns it. A firm date from the supplier, a recovery plan, a planner's impact check, an engineering review. Confirmed facts, open questions and decisions are kept separate.
Keeps the exception open until it's resolved. A sent email isn't resolution. "Working on recovery" isn't a date. It closes when the confirmation or decision is documented.

That history pays off twice. Buyers stop rebuilding the story, and a new owner can pick up a PO without losing the thread. Over time, the same history shows which suppliers slip and by how much, the basis for knowing which suppliers to plan around (more in Your ERP Says 2 Weeks. Your Supplier Takes 6.).

Buyers still negotiate, evaluate alternatives and approve changes. LevelOneAI isn't an autonomous purchasing agent and doesn't replace your procurement system. It does the reading and the remembering.

Start with late deliveries and missing confirmations

A buyer can start today with Operations Workbench Starter on their own inbox and an open-PO export. It catches when a supplier's date moves, shows which jobs it affects, and tracks the PO until it's resolved. Free for 30 days. For the whole team, the next step is a Supplier PO Exception Workbench that adds live ERP data and planning need dates, read-only at first, with buyers approving every follow-up.

Take a baseline first:

How many delivery exceptions does the team handle each week?
How long does a buyer spend reconstructing each one?
How often does the supplier's latest date differ from the ERP?
How many exceptions are open right now, and does anyone know for sure?

If your current tools already track every exception to resolution, you don't need another layer. If buyers are still the glue between supplier emails, the ERP and planning, that's the problem worth fixing.

Try this week

Pick five late POs. For each, list every date the supplier has promised. Time how long it takes.
Compare the supplier's latest date with the ERP date on your 20 most urgent open POs.
Ask a buyer which supplier owes them an answer today. Then ask how they know.

Let buyers spend their time on decisions, not on chasing information.

See how the LevelOneAI Operations Engine works

Talk to us