# Measure completed work, not AI activity.

> Useful automation economics follow the transaction through errors, review and recovery.

Canonical URL: https://marmation.com/review/measuring-ai-workflow-value/

By Vikram Roy · 2026-11-12

A company reports that its AI system processed 15,000 documents. That sounds impressive until someone asks how many resulted in correct completed transactions, how many required manual correction and whether the error rate changed.

## The decision behind the technology

Volume is not value. A good business case starts with the baseline: time spent per task, rework, error cost, wait time, customer impact and the number of cases requiring specialist attention. The AI system then needs comparable measures that include exception handling and operational cost.

## A better way to frame the work

Choose one workflow and instrument its states. Measure completed correct outcomes, time to resolve exceptions, review workload, failed integrations and total operating cost. For commercial products, include user adoption and retention or revenue where credible.

## Put the idea under realistic pressure

An order-processing workflow can extract fields rapidly but still delay fulfillment if staff must check every field. The right product may prioritize high-confidence straight-through processing and fast review for exceptions, with clear rules for when that is safe.

## When the recommendation changes

In some cases AI improves quality rather than speed. In others it increases capacity during demand spikes. The metric should follow the business job rather than default to hours saved.

## What to decide before moving forward

Before claiming a percentage improvement, record a baseline, define the calculation, include error/rework and identify how long the measurement must run to be meaningful.

### References and context

[RSM survey 2026](<https://www.rsmus.com/insights/services/digital-transformation/rsm-middle-market-ai-survey>); [McKinsey State of AI 2026](<https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai>).

## Sources

- [2026 Middle Market AI Survey](<https://www.rsmus.com/insights/services/digital-transformation/rsm-middle-market-ai-survey>) — RSM. Survey of 1,030 US and Canadian middle-market executives at organizations already using AI; 86% integrated in operations; 36% fully embedded across core processes. Limit: Do not generalize to all middle-market firms; cross-sectional self-report; use survey date.
- [The state of AI in 2026](<https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai>) — McKinsey. AI adoption/agentic coding and build-vs-buy survey; 32% of respondents had foregone a product/feature purchase due to ability to build with coding agents. Limit: Verify actual wording and survey population when quoted; does not mean SaaS is obsolete.

## Related reading

- [Make intelligence part of the work](https://marmation.com/review/operations/)
- [Document extraction is not document automation.](https://marmation.com/review/document-extraction-is-not-automation/)
- [Your ERP is a system of record. It is not the entire workflow.](https://marmation.com/review/erp-is-not-the-entire-workflow/)