Measurement · Operating decision guide
How to measure AI value in EBITDA terms
Otomat editorial · Revised · Original edition 16 March 2026
A usable bridge from accepted tasks and reviewer effort to capacity, cash, full cost and finance-approved attribution.
Define the denominator before the demo
Record the workflow, eligible task population, baseline window and inclusion rules. Measure accepted task completion, rework and human review effort. Select a comparison group or phased rollout where feasible; if comparison is unavailable, record confounders and lower confidence in attribution.
Capacity released is not automatically a cash saving. A salary cost does not fall because one task takes less time. Record a specific mechanism such as avoided external spend, reduced overtime, an approved hiring decision or redeployment to measured additional throughput.
Build an inspectable value bridge
Net operating value = attributable realized gross benefit − incremental running cost − transition cost for the stated period. Investment ROI = (cumulative attributable benefit − cumulative full cost) / cumulative full cost. Include implementation, integration, reviewer time, correction, model/tool usage, monitoring, training, assurance and maintenance. Keep one-time investment distinct from recurring cost.
Worked example: illustrative arithmetic only
The example below is synthetic. It is not a client case, forecast or promised return. It illustrates why a time estimate alone is insufficient. If no cash mechanism is established, report the observed capacity separately and leave accepted financial benefit unknown.
| Step | Synthetic inputs | Interpretation |
|---|---|---|
| Gross task time | 1,000 tasks/month × 6 minutes saved ÷ 60 = 100 hours | Task estimate before review; not cash |
| Review and correction | 100 hours − 30 additional review hours = 70 net hours | Potential capacity; verify with observed tasks |
| Cash mechanism | Hypothetical approved avoidance of 20 external hours × $50 = $1,000/month | Only if the expense was actually avoided and attributed |
| Running cost | $1,000 − $300 tools − $200 maintenance = $500/month | Illustrative net recurring value before transition cost |
| Investment recovery | $6,000 one-time cost ÷ $500/month = 12 months | Simple arithmetic; assumes sustained benefit, excludes tax/financing |
Keep evidence stages separate
Record four separate states: a hypothesis or forecast, an observed task change, released capacity, and a finance-accepted realized benefit. For each, retain the source, measurement window, owner and next decision gate. A later stage requires new evidence; a spreadsheet formula does not promote the earlier stage.
For example, accepted tasks multiplied by observed net minutes saved and divided by 60 gives capacity hours. The cash bridge still needs an actual expense or contribution mechanism, attributable benefit, and full costs. The value worksheet captures those evidence stages separately.
Agree the approval and stop rule
Finance owns the bridge to EBITDA, including accounting treatment and overlap with other initiatives. State the measurement window and uncertainty; avoid annualizing a short pilot with unproven sustained use. Hold the financial claim if attribution, costs or cash conversion remain unresolved. Publish only the authorized metric, population, window and limitation.
Use the working tools
Blank templates are ungated. Adapt them to the workflow; inputs are not submitted.
Sources and limits
These are Otomat’s proposed operating methods and original decision artifacts. External references inform risk management; they do not certify this method or establish client results. Linked sources were selected for this review; their live revision dates may change.
For anonymous documentation and proposal patterns, see delivery evidence and its boundaries.
Related decisions
Bring a workflow to the discussion
Share the business goal and constraints through the mandate process. Do not send sensitive production data in the initial brief.
Scope an Operating Mandate