Your numbers, not our numbers.
This is the same worksheet we'd fill in with you on a call, run by you instead. Nothing is pre-filled with a customer result, because we don't have one to show you yet. Put your plant's figures in and see whether a pilot pays for itself.
Your plant
Leave anything you don't track at zero — that lever simply won't contribute. Partial input still gives you a defensible number.
5 × 52 = 250
Across every role — planner, quality engineer, plant manager, CI.
Fully loaded, $/hr.
What scrap costs you today.
Hours today. If you only track it as a percentage, multiply by operating hours.
Units. With margin per unit, this gives us margin per operating hour.
What AutoOps AI costs you
Defaults to Plant Pro list price. Replace it with your pilot rate × 12, or your contracted ACV, if you have one.
What it comes to
- Reporting time saved30%
- $0
- Scrap avoided5%
- $0
- Downtime recovered3%
- $0
- Annual value
- $0
- Less AutoOps AI cost
- −$12,000
- Reporting time saved50%
- $0
- Scrap avoided7.5%
- $0
- Downtime recovered4%
- $0
- Annual value
- $0
- Less AutoOps AI cost
- −$12,000
- Reporting time saved65%
- $0
- Scrap avoided10%
- $0
- Downtime recovered5%
- $0
- Annual value
- $0
- Less AutoOps AI cost
- −$12,000
The math, in full
No hidden multipliers. These are the three levers the SAP read path and write-back actually cover today — everything else the product might do for you is deliberately left out of the model.
Reporting time saved
hrs/week × 50 weeks × labor rate × reductionThe weekly Operations Snapshot and SAP-grounded chat replace part of the manual pull-and-slide-prep cycle. 50 weeks, not 52 — holidays and shutdowns.
Scrap avoided
annual scrap $ × reductionQuality notifications surface within the hour instead of next shift, and a supervisor can file the QN without leaving the tool. This is the most variable of the three; anchor it to one batch you actually remember.
Downtime recovered
downtime hrs × reduction × margin per operating hourMargin per hour = margin per unit × volume ÷ operating hours. AI-assisted review of work-order and routing data surfaces at-risk orders earlier in the week.
One thing we don't annualize: a first SAP-grounded report usually surfaces one real issue nobody had escalated yet. That's worth something, but it's a one-time recovery, so counting it as recurring would overstate the case. We track it separately in the pilot recap.