
What happened
AWS introduced an Agentic Value Model for AI CoE leaders, saying the RPA-era ROI formula misses exception handling, decision quality, and maintenance economics, and cites McKinsey's "1:3:5 pattern."
Why it matters
The model gives CoE leaders four value dimensions for sizing agent investments, so they can show finance benefits the old hours-saved formula omits.
What to watch
The framework's payoff hinges on whether released capacity is redeployed to a named outcome or spend falls; watch the illustrative $1.26 million capacity and $151,000 correction benefit.
WHO IT HITSAI center of excellence leaders and finance teams evaluating agentic automation budgets must adopt the Agentic Value Model to size value across time savings, exception handling, decision quality, and maintenance economics, rather than relying on hours saved times labor cost.
Summaries like this, in your inbox every morning.
AWS's post arrives as agentic automation appears on AI center of excellence roadmaps, but the standard ROI model—hours saved times labor cost minus build cost—was built for rule-based robotic process automation (RPA). It assumes stable processes, rule-based tasks, and that saved hours equal banked value. McKinsey's "1:3:5 pattern" suggests successful AI transformations spend three dollars on process redesign and five on capability building for every dollar invested in agentic technology, yet most companies invert this formula.
The Agentic Value Model breaks value into four pools: time savings, exception handling, decision quality, and change resilience and maintenance economics. For exception handling, AWS guidance gives planning ranges—correcting an error can cost 1.5–4 times the original transaction, and human error can account for 2–15 percent of operational cost. Decision quality may matter most for low-volume, high-value decisions like credit, pricing, or risk, where a single better decision can dwarf a year of saved minutes. Maintenance economics goes both ways: agents absorb some variation without a rewrite but shift maintenance into evaluations, prompts, monitoring, and model operations.
An illustrative claims-triage example shows why redeployment matters: automating the routine 70 percent of 200,000 claims releases about 28,000 hours, or roughly $1.26 million of capacity, before oversight. If attrition and lower overtime capture half, the case should carry about $630,000, not the full figure. Of the 8 percent needing correction (16,000 claims), a 40 percent reduction adjusted by a 75 percent realization factor yields a modeled benefit near $151,000. Amazon Quick Automate deployments at Kitsa, dLocal, and Genpact show the dimensions at work, though none proves all four pools. The broader test, per McKinsey, is that nearly two-thirds of enterprises have experimented with agents but fewer than 10 percent have scaled them to tangible value.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Supermicro Computer appointed Mark Long as chief financial officer, bringing an experienced technology finance…

Holtek Semiconductor unveiled its 2026 product roadmap on October 15, focusing on four core areas: smart prote…

TSMC reported about NT$763.1b in Q3 net profit and confirmed that demand for advanced processors is running ah…

Nvidia-backed CoreWeave steadied Thursday after a sharp slump, as investors worried about the debt financing b…

Circlia started a proof-of-concept for TASTE SIGNAL: visitors to Holland Village Cafe FUKUOKA taste cookies an…

Weathernews said on October 15 it implemented its own AI weather-forecasting model, AI-Nowcast, in its Weather…
