ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial3 min readDisconfirmAI Editorial

Accenture and Amazon Web Services Propose a Three-Phase Sequence for Optimizing AI Token Costs, with Four Clients Reporting Reductions of 40% to 85%

After enterprises scale their deployment of artificial intelligence (AI), the price per token decreases but total expenditure increases. This article outlines six token cost optimization levers jointly proposed by Accenture and Amazon Web Services (AWS), ordered into three phases: configuration changes, architectural changes, and infrastructure investment. It reports actual results from four clients: an insurance client and a mining client using only a single caching layer saw reductions of approximately 40%, while a large enterprise and a telecommunications operator applying multiple levers combined achieved reductions of 85% and 68%, respectively. The core argument is that the optimization goal is not to minimize tokens at all costs, but to match the appropriate level of intelligence to each business outcome.

2026-11-20 02:48 GMT+8

A counterintuitive phenomenon often arises after enterprises scale their deployment of AI: while the price per token is falling, total token expenditure is rising. This occurs because cheaper tokens stimulate greater adoption, and agentic workflows split a single user interaction into multiple model invocations. A practice article jointly published by Amazon Web Services (AWS) and Accenture points out that in response to this situation, the correct optimization goal is not to reduce the number of tokens at any cost, but to match the appropriate level of intelligence to each business outcome—finding the corresponding point between cost, quality, and risk.

The article categorizes six optimization levers into three phases based on implementation complexity. Phase 1 involves pure configuration changes without altering infrastructure: prompt caching reuses repetitive system instructions and tool definitions, with design goals aimed at reducing cached input token costs by up to 90%; batch inference asynchronously processes non-urgent tasks in batches, costing 50% less than on-demand calls. Phase 2 involves architectural changes: intelligent prompt routing directs requests to different-sized models within the same model family, reportedly reducing costs by up to 30% without sacrificing accuracy; Retrieval-Augmented Generation (RAG) optimization reduces irrelevant context entering the model through hierarchical chunking, metadata filtering, and reranking. Phase 3 requires infrastructure and training investment: semantic caching stores semantically similar previously answered requests in vector storage; model distillation transfers knowledge from large models to small models, reportedly increasing speed by up to 500% and reducing costs by up to 75%.

Sign in / Sign up
ReadingResearchRadarInvestment framework

The logic behind this sequencing is dependency. The article emphasizes that before applying any lever, cost attribution must be established—tagging by team, workload, and agent through Amazon Bedrock application inference profiles, then tracking consumption sources using Cost and Usage Reports (CUR) version 2.0 and model invocation logs. Without attribution, it is impossible to determine if optimization is effective or to distinguish whether a growing bill reflects success driven by business expansion or pure waste. To address this, Accenture proposed the Cost per Business Transaction framework, which aggregates all model invocations, retries, tool calls, and agent handoffs behind a single successful business output into one fully loaded cost figure, translating technical token consumption into metrics directly usable by business leaders.

Actual results from four clients confirm the sequence logic. A large enterprise previously routed all requests to frontier models with no caching, tiering, or batching; after Accenture applied model tiering, prompt caching, and batch processing simultaneously, monthly token costs dropped by 85%. A telecommunications operator with $12 million in annual token spend suffered major waste from agents fanning out requests without limits and sending all requests to frontier models regardless of complexity; after Accenture combined triage routing, semantic caching, and context compression, annual spend fell to $3.8 million, a 68% reduction. An insurance client and a mining client each applied only a single caching layer—the former using model-layer prefix caching, the latter using an application-layer semantic cache—and together they reduced token spend by approximately 40%, involving no model routing changes or training investment.

The article recommends the following operational order: first connect consumption to owners and business outcomes, then apply one lever to one workload at a time, measure cost, quality, and business value, and proceed further based on what works. For regulated industries (financial services, insurance, healthcare), quality test results and rollback procedures should be included in standard change management records.

Sources

  • aws.amazon.comAmazon Web Services↗
Continue researching →