Product
Pricing
Start with Starter on your own email and documents, free for 30 days. Prove the value with your team in a 6-week pilot, credited in full to setup. Then a Workbench connects your systems and runs one workflow end to end.
Start here · for one person
Operations Workbench Starter
$199/monthor $1,990/year (two months free)
30-day free trial · no card
- 1 user and 1 mailbox (Gmail or Outlook)
- Runs in your paid Claude or ChatGPT plan
- Reads your email and any exports you add: open POs, schedules, AR aging
- Changes ranked by risk, with the evidence for each one
- Tells you what's missing to sharpen the results
- Tracks each item to a verified close
Email support. Cancel anytime.
Prove it · with your team
Workbench Pilot
$5,000 for 6 weeksOne workflow, your team's real data
Credited in full to your Workbench setup
- One workflow, for up to 5 people who work it
- Your real email, plus ERP exports or one read-only ERP connection
- Read-only: nothing is written to your systems
- Baseline, success criteria and exit criteria signed before day one
- Weekly check-ins and a final readout against the baseline
- Built on your production setup, so a successful pilot becomes phase 1
No platform fee during the pilot. 8 weeks, at the same price, for workflows where exceptions come up less often, such as engineering changes or quality exceptions.
For the whole team
Operations Workbench
One-time setup, from $20,000No ongoing services fee · Annual platform fee, included in your quote
- One workflow, configured for your team
- Connected to the email, ERP and CRM that workflow depends on
- The work queue, the work record, approvals and the team view
- Follow-through to a confirmed close
- Optional write-back to your systems, with approval
Once it's live, your team runs it. You don't pay for our people unless you want ongoing help, such as new rules, more connections or changes as your process changes. The annual platform fee covers hosting, AI processing, connector updates and improvements to the Operations Engine, and starts at go-live, not at signing. In the first year, you can cancel 90 days after go-live if the measures we agreed before setup aren't met.
Starter fees paid in the 6 months before you buy a Workbench are credited toward its setup.
Starter and the Workbench, side by side
| Operations Workbench Starter | Operations Workbench | |
|---|---|---|
| How you start | 30-day free trial, no card | A quote, then setup with you |
| Price | $199/month or $1,990/year | One-time setup from $20,000, plus an annual platform fee |
| Setup | None: add it in Claude or ChatGPT, connect email, add documents | Configured to your systems, rules and owners |
| Data | Your email, plus documents you add (exports from any ERP) | Live connections to your ERP, CRM and planning data |
| People | 1 user and 1 mailbox | The whole team, across departments |
| Prioritized work with risk and evidence | ||
| What's missing, and how to sharpen it | ||
| Owners, next steps and proof of close | ||
| 30-day scorecard | ||
| Runs continuously, without anyone opening it | ||
| Shared team queue and approvals | ||
| Write-back to your systems, with approval | ||
| Several workflows connected | ||
| Support | Email support | Setup with you, then your team runs it; optional ongoing help |
Workbench Pilot
See the value on one workflow before you commit to setup.
$5,000 for 6 weeks, on your team's real email and ERP data. It's built on your production setup, not a throwaway demo, so a pilot that meets its criteria becomes phase 1 of your Workbench.
- 1Weeks 1–2
Set up
Connect email, load the exports, agree the baseline and success criteria, configure the rules.
- 2Weeks 3–6
Run it live
Your team works real exceptions in the Workbench, with a weekly check-in.
- 3End of week 6
Readout
Results against the baseline, and a go or no-go on the Workbench.
What's included
- One workflow, for up to 5 people who work it
- Your real email, plus ERP exports or one read-only ERP connection
- Read-only: nothing is written to your systems
- Baseline, success criteria and exit criteria signed before day one
- Weekly check-ins and a final readout against the baseline
- Built on your production setup, so a successful pilot becomes phase 1
How the fee works
The pilot fee is credited in full to your Workbench setup if you sign within 60 days of the pilot ending. Workbench pricing is set in the pilot agreement, so a successful pilot doesn't start a new negotiation.
No platform fee during the pilot. If the agreed criteria aren't met, you don't go ahead, and you keep the readout.
8 weeks, at the same price, for workflows where exceptions come up less often, such as engineering changes or quality exceptions.
Billing questions
- Do I need a card for the trial?
- No. The 30-day trial needs no card. You add one only if you keep Starter after the trial.
- What happens on day 30?
- You choose monthly or annual and add a card. If you don't, your account becomes read-only and your data is deleted 30 days later.
- Monthly or annual?
- $199/month, or $1,990/year, which is two months free. Switch at renewal.
- Can I cancel?
- Anytime, from your billing page. Monthly plans stop at the end of the month you've paid for. Annual plans run to the end of the paid year. Export your history before your data is deleted 30 days later.
- Receipts and invoices
- A receipt is emailed for every payment, and invoices can be downloaded from your billing page.
- Moving up to a Workbench
- Starter fees paid in the 6 months before you buy a Workbench are credited toward its setup.
- How is the pilot billed?
- $5,000 for 6 weeks, invoiced when the pilot agreement is signed. The pilot fee is credited in full to your Workbench setup if you sign within 60 days of the pilot ending. Workbench pricing is set in the pilot agreement, so a successful pilot doesn't start a new negotiation.
- What if the pilot doesn't meet its criteria?
- You don't go ahead, and there's nothing more to pay. You keep the readout and the baseline we measured.
- Workbench billing
- The one-time setup is invoiced on a schedule in your quote. The annual platform fee starts at go-live, not at signing.
See the Terms, Privacy and Cancellation & refunds pages.
What a Workbench includes
Included in every workbench
- The Workbench and the Operations Engine
- The work queue, work records, approvals and the team view
- Change detection, evidence labeling and closing conditions
- Hosting, monitoring and updates
Configured for you during setup
- The connections to your systems and how they're accessed
- How records are matched across email and systems
- The rules for what counts as an exception and how it's ranked
- Who owns each kind of issue, and who approves what
- Write-back, if you choose to turn it on
What affects the price
- How many systems the workflow connects
- How those systems are accessed
- Whether write-back is turned on
- Volume of work items
A second workflow reuses the connections you already have, so it costs less to set up.
How setup works
Start with one workflow. We configure the rules, owners and follow-up it needs, and connect the systems it depends on. It's a fixed scope, agreed up front.
What an engagement defines
- One workflow and the type of exceptions it handles
- The data sources and how they're accessed
- How records are matched across systems
- The rules for detecting and prioritizing issues
- The people responsible for acting and approving
- The evidence that confirms an issue is resolved
What you provide
- A workflow owner who knows how the work runs today
- Read access to the systems involved, granted by your IT team
- Two to three hours a week from the team during setup
- A few examples of real exceptions from the last few months
Timeline and results
Typically 6 to 12 weeks from kickoff to go-live, depending on the systems involved.
We measure, against your own baseline:
- How early problems are caught
- Time spent gathering evidence
- Coordination effort per issue
- Share of issues closed with evidence
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 |
No IT department? Here's what it takes. Large IT team? Here's how we fit your IT review.
Your first workflow
What it involves, start to finish
- Scope
- One workflow, kept deliberately narrow. For supplier POs, that can be one supplier mailbox, your open POs and the need dates. More sources are added only if the workflow needs them.
- What you provide
- A workflow owner who knows how the work runs today, read-only access to the systems involved, a few hours a week from the team during setup, and a few real exceptions from recent months.
- Who configures it
- We do, with your workflow owner: how records are matched, what counts as an exception, who owns what, and what closes an item.
- Time to first result
- Workbench Starter works the same day. A Workbench typically goes live in 6 to 12 weeks, depending on the systems involved.
- When data is missing
- 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.
- How it's judged
- Measures and a baseline agreed before setup. In the first year, you can leave 90 days after go-live if they aren't met.
Sample scorecard
How the first workflow is judged
| Measure | Baseline | Target, set with you | Result at 90 days | Value, from your numbers |
|---|---|---|---|---|
| How early problems are caught | Your number | Agreed before setup | Measured | Change × your unit cost |
| Time spent gathering evidence | Your number | Agreed before setup | Measured | Change × your unit cost |
| Coordination effort per issue | Your number | Agreed before setup | Measured | Change × your unit cost |
| Share of issues closed with evidence | Your number | Agreed before setup | Measured | Change × your unit cost |
Expand
The targets were met. Add the next workflow, reusing the connections in place.
Adjust
Close, but not there. Change the rules, sources or owners, and measure again.
Stop
The targets weren't met. In the first year, you can leave 90 days after go-live.
We don't promise an improvement percentage. The result is whatever your own numbers show.
Weigh it against the problem
Compare the price with what the delay costs you each year.
Before setup, we agree the measures and take your baseline. The price is judged against that baseline, not against a saving we assume. Put in your own two numbers below.
A supplier delay, a short shipment, a spec or customer change that reached production, shipping or billing too late.
Expedites and premium freight, overtime, line-down time, late or lost shipments, penalties.
Your yearly impact
$360,000
12 times a year × $30,000 each, lost to changes nobody acted on in time.
Payback
LevelOneAI pays back the $20,000 setup if it helps you catch 1 of those 12 in time.
Setup only. The annual platform fee is in your quote.
From $20,000 per workflow. Use your quote if you have one.
Your numbers, your estimate. We measure the real result against your own baseline after go-live.
Read-only by default
It reads what it needs. Nothing changes in your systems without approval.
Approval on every change
Follow-ups are drafts and updates are proposals until a person approves them.
A baseline agreed up front
We agree the measures before setup and report against them.
A 90-day exit in year one
If the agreed measures aren't met, you can leave 90 days after go-live.
Start with the workflow that costs you the most.
We'll show you a workbench on work like yours, and scope the first one with you.