Plenty of AI business cases promise efficiency and leave it there. A governed agent deserves better: a number you set before the build and check after launch. The good news is that the work to remove a process is also the work that lets you measure it — if you baseline first.

Why ROI gets hand-waved

Most AI ROI claims fail for one of two reasons: there was no baseline to measure against, or the cost side was ignored. "It saves time" is not a business case. "This workflow handles 1,200 items a month at nine minutes each, and the agent removes seven of those minutes at a model cost of pennies per item" is. The difference is rigour, not optimism.

Baseline before you build

Pick one workflow and quantify it honestly: how many items, how long each takes, the error and rework rate, and the fully loaded cost of the people doing it. This baseline is the single most valuable artefact in the whole exercise, because every later claim is measured against it. If you cannot baseline a workflow, that is a sign it may be the wrong first candidate.

The three levers

Agent value almost always comes from a combination of three things:

  • Time saved. The manual minutes the agent removes, multiplied by volume.
  • Error reduction. Fewer mistakes, less rework, and the downstream cost those errors would have caused.
  • Throughput. More work handled in the same time, or the same work handled faster — capacity you can redeploy.

Do not forget the cost side

A credible model nets the savings against the agent's real running cost: model and infrastructure spend, the human oversight the workflow still requires, and the maintenance and evaluation needed to keep quality high. This is also where good AgentOps earns its keep — cost monitoring and model routing keep the spend side predictable so the ROI holds.

Measure after launch, not just before

The business case is an estimate. The truth comes from production. Monitoring and evaluation should track real usage, quality and cost, reported against your baseline, so the operational impact is measured rather than assumed. That is how an ROI number stops being a sales artefact and becomes a management metric. It is built into how we run an agentic operations workflow — and the first estimate is exactly what an Agentic Operations Sprint produces.