Skip to content

Product · Operations Workbench

One workflow, from the first signal to a confirmed close.

A Workbench runs the Operations Engine across your team's email, ERP and CRM for one workflow. Each change becomes a work item with the evidence, an owner and a next step, and stays open until it's resolved. Your systems stay the record.

One-time setup, from $20,000 · No ongoing services fee · Annual platform fee, included in your quote

Workbench Pilot: $5,000 for 6 weeks, credited in full to setup.

The step up from Starter

Starter shows you the risk. The Workbench is how the whole team closes it, every day.

Live data, not exports

Connected to your ERP and planning data, so it's never working from a stale file.

Runs on its own

Monitors watch for changes around the clock, without anyone opening a chat.

The whole team

One queue across buyers, planners and customer service, with the team view.

Approvals and write-back

Drafted follow-ups for review, and approved updates written back to your systems.

Already on Starter? Your history, rules and document mappings carry over. Starter fees paid in the 6 months before you buy a Workbench are credited toward its setup. Not yet? Start with Starter.

Operations Workbench StarterOperations Workbench
How you start30-day free trial, no cardA quote, then setup with you
Price$199/month or $1,990/yearOne-time setup from $20,000, plus an annual platform fee
SetupNone: add it in Claude or ChatGPT, connect email, add documentsConfigured to your systems, rules and owners
DataYour email, plus documents you add (exports from any ERP)Live connections to your ERP, CRM and planning data
People1 user and 1 mailboxThe 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
SupportEmail supportSetup 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.

  1. 1Weeks 1–2

    Set up

    Connect email, load the exports, agree the baseline and success criteria, configure the rules.

  2. 2Weeks 3–6

    Run it live

    Your team works real exceptions in the Workbench, with a weekly check-in.

  3. 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.

What every workbench includes

The work queue

Every order, PO, deal or account that needs attention, ranked by impact, with the reason and the source.

The work record

What changed, what was promised, what the systems say and what it affects, with every fact labeled and sourced.

The next step, for approval

A recommended action with its reasoning. Follow-ups are drafted for review, and system changes need approval.

Follow-through to a confirmed close

Owners, due dates and closing conditions. A sent email doesn't close an item. Evidence does.

The team view

Where work is stalled, who is waiting on whom, and which commitments are at risk across the team.

See one in action

The Supplier PO Exception Workbench, on a sample company.

Demo · Supplier PO Exception Workbench

Know which late purchase orders will stop your line, and close them out.

Illustrative example · sample company and data

Recognize this? The status of one PO lives in six places.

Monday, Oct 5. Maya Ortiz buys machined parts for a mid-size manufacturer. She has 142 open POs. This is one of them.

Where PO 4512 lives this morning

  • ERPPromise date Oct 12, confirmed in September
  • Supplier email"Tooling issue on line 2. New date Oct 26." Only Maya has seen it.
  • Open-PO sheetMaya's own list. Still says Oct 12.
  • PlanningNeeds the housings by Oct 20 for an assembly run
  • Sales ordersBrightline ships Oct 28, Keller Nov 2. Both depend on that run.
  • PhoneLast week's call with the supplier. Nobody wrote it down.

What it takes Maya to piece it together

  • 0:00Open the open-PO spreadsheet
  • 0:04Search the inbox for "4512" and find the email in a long thread
  • 0:11Check the ERP. Still Oct 12.
  • 0:14Message planning: when do you need these?
  • 0:14–0:38Wait for a reply
  • 0:38Planning: "Oct 20"
  • 0:45Work out which customer orders depend on it

45 minutes for one exception, and about 15 like it a week.

And it gets harder. On Oct 14 the supplier writes "working on recovery, will confirm Monday." It sounds like progress. There's still no date, and the need date is six days away.

Connected to the systems your workflow depends on

How we set it up

Start with one workflow. We configure the rules, owners and follow-up it needs, and connect the systems it depends on.

Your data

Your ERP and CRM keep the master data. The Operations Engine is designed to keep only what it needs to run the work, such as references to the source, the facts it extracted, status, owners and decisions. What's stored, and where it runs, is agreed with you during setup.

Write-back, if you want it

Write-back is optional. Whether approved updates go back to your systems, and which ones, is decided during setup. Every update waits for a person's approval, and your ERP and CRM remain the systems of record.

Starting with follow-up in a shared inbox?

A workbench can start with your team's shared mailbox and add system connections as the workflow needs them. Each item still gets an owner, a next step and a closing condition.

Start with one workflow.

  • A setup fee for the first workflow, with agreed success criteria
  • An annual platform fee that starts at go-live, and no ongoing services fee