Product · Pilot
Prove it on one workflow before you commit to setup.
Six weeks on your team's real email and ERP data, measured against a baseline you agree up front. It runs on your production setup, so a pilot that meets its criteria becomes phase 1 of Operations Resolution.
Not ready for a pilot? The free trial shows your own exceptions in 14 days, free.
$5,000 for 6 weeks · Credited in full to your Operations Resolution setup · See the pilot kit · See a pilot, week by week
Six weeks, three stages
- 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 Operations Resolution, with a weekly check-in.
- 3End of week 6
Readout
Results against the baseline, and a go or no-go on Operations Resolution.
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
The pilot kit · Supplier delivery exceptions
Everything the pilot needs, defined before day one
The data, the setup and the acceptance criteria are defined before day one, so you're buying a configured product with a known method, not a custom AI project. Most teams start with supplier delivery exceptions.
The exception it handles
- The trigger
- A supplier moves a date, ships short, changes a price, or goes quiet after a PO was sent.
- What it checks
- The new date against the need date, the job or run it feeds, and the customer orders behind that job.
- The decisions
- Accept the new date, expedite, split the shipment, use an alternate source, or re-sequence the run, with the right approver.
- Resolved when
- A confirmed date meets the need date, or the plan has changed and affected customers have been told. A reply alone doesn't close it.
The data it needs
Exports from any ERP or spreadsheet work, with export guides for NetSuite, Dynamics 365, Acumatica and Epicor. Whether a read-only connection replaces the exports is decided in week 1.
- Required
Supplier email. The buyers' mailboxes where supplier confirmations and updates arrive.
- Required
Open PO lines. PO, line, part, quantity, supplier and promised date.
- Recommended
Requirements or production schedule. Part, need date and the job or run it feeds, which turns a late date into production impact.
- Recommended
Open sales orders. Order, customer, ship date and value, linked to the job, which turns impact into customer and dollar risk.
- Optional
Stock and receipts, and the planner's own sheet. On-hand and in-transit quantities, and the spreadsheet your planner actually trusts.
Set up in week 1
Together we agree the need date, the suppliers and parts in scope, who owns each exception, who approves, and what closes one. It's stored as configuration, not code, so it carries straight into Operations Resolution.
Tested on your data
The workflow is tested against representative scenarios from your own data before your team works live exceptions.
Acceptance criteria
Agreed with you and signed before day one.
- No wrong automatic matches between emails, POs and jobs
- Every at-risk item shows the jobs and customer orders affected, with the source of each fact
- Impact claims your team dismisses stay under the rate you agree, such as 1 in 20
- Every item has an owner, a next step and a close condition
- Items close only on evidence, never on a sent email
Signed before day one
What we agree up front
- The workflow
- One workflow, kept narrow. For supplier delivery exceptions, that can be one supplier mailbox, your open POs and the need dates.
- The baseline
- How the work runs today: how early problems are caught, how long it takes to gather the evidence, how many issues close with proof.
- Success criteria
- The targets that mean go, set with you before day one.
- Exit criteria
- What means stop. If the criteria aren't met, you don't go ahead, and there's nothing more to pay.
From your side
What you provide
- A workflow owner who knows how the work runs today
- Read access to the email and the ERP exports, or one read-only ERP connection, granted by your IT team
- Up to 5 people who work the exceptions
- A few real exceptions from recent months, to set up the rules
- Two to three hours a week from the team during setup
End of week 6
The readout: what changed, measured against your baseline
Time saved and problems prevented are reported separately, and a result only counts where Operations Resolution flagged the problem first. Dollars at risk are shown as exposure, never as savings.
Business outcomes
Problems flagged before anyone acted, resolved before the need date, misses, and expedite and premium freight spend avoided.
How the work changed
Items with the impact assembled automatically, issues worked without searching other systems, and time from signal to decision.
What your team knows
The rules, workarounds and approvals your team confirmed during the pilot, written down and checked. They're yours to keep.
Sample scorecard
How the first workflow is judged
| Measure | Baseline | Target, set with you | Result at 90 days | Value, from your numbers |
|---|---|---|---|---|
| Days of warning before the need date | Your number | Agreed before setup | Measured | Change × your unit cost |
| Expedite and premium freight spend | Your number | Agreed before setup | Measured | Change × your unit cost |
| Customer ship dates missed because of supplier delays | Your number | Agreed before setup | Measured | Change × your unit cost |
| Line-down hours waiting on parts | Your number | Agreed before setup | Measured | Change × your unit cost |
| Time to resolve an exception | 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.
Questions about the pilot
- What happens to the fee?
- The pilot fee is credited in full to your Operations Resolution setup if you sign within 60 days of the pilot ending. Operations Resolution pricing is set in the pilot agreement, so a successful pilot doesn't start a new negotiation.
- What if the criteria aren't met?
- You don't go ahead, and there's nothing more to pay. You keep the readout and the baseline we measured.
- Does anything change in our systems?
- No, the pilot is read-only. Nothing is written to your ERP or email.
- Is there a platform fee during the pilot?
- No. The annual platform fee only starts when Operations Resolution goes live.
- Why 6 weeks?
- Long enough for your team to work real exceptions and compare them with the baseline. 8 weeks, at the same price, for workflows where exceptions come up less often, such as engineering changes or quality exceptions.
- What happens after a successful pilot?
- It becomes phase 1 of your Operations Resolution, because it runs on your production setup. Operations Resolution pricing is set in the pilot agreement, so there's no new negotiation.
Pick the workflow that costs you the most.
We'll come back with a pilot plan: the scope, the baseline and the success criteria.