From the Anthropic edition of October 30, 2026
McKinsey: as subsidized government AI pricing ends, token-based agentic workloads push costs up; state and local buyers should set hard caps
McKinsey & Company (Public Sector Practice) · Federal, state and local government finance and procurement · United States
- Publisher
- McKinsey & Company
- Original publication
- September 29, 2026
- Source retrieved
- 2026-10-31
What happened
McKinsey argues that while unit token prices fall, total government AI bills will rise as agentic workflows consume 5 to 30 times the tokens of simple queries. It cites a GAO finding that officials in all five agencies examined struggled to understand AI costs, and its own survey of 120 mostly private enterprises in which 93% exceeded planned AI budgets. For state and local buyers it says there was likely no $1 subsidy, so an unplanned run rate becomes a same-year shortfall; it recommends hard caps, request tagging, a "TokenOps" discipline and cooperative vehicles with exit clauses.
Why it matters
Newly relevant this week: Claude per-user promotional pricing ends Oct. 31 and OneGov token billing (Oct. 27-30) is now orderable by SLTT buyers. This is the only non-vendor cost analysis found that addresses state and local budgeting under token pricing; it is not Claude-specific but names Claude's $1 federal deal.
Evidence and measured results
Consultancy article citing GAO, FinOps Foundation and Gartner, plus a McKinsey survey of 120 enterprises (75 advanced adopters) that is primarily private sector. No SLED-specific cost data.
Limitations and uncertainty
Not peer reviewed; consultancy with commercial interest in advisory work. Private-sector survey findings may not transfer to SLED budgets. Secondary sources were not independently opened.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-31; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- State and local AI budgets are fixed annually, while token-based agent workloads can grow unpredictably.
- Stakeholders
- CFO/budget director
- CIO
- Chief procurement officer
- Chief AI officer
- Discovery questions
- What run rate have you budgeted for after promotional pricing ends?
- Do you cap spend per agent or workflow?
- Can you measure cost per outcome for a target workflow?
- Does your contract include exit or portability terms?
- Value hypothesis
- A capped, instrumented rollout may keep AI spend within a fixed appropriation while showing cost per outcome.
- Potential engagement
- A TokenOps readiness assessment: tagging, caps, forecast and cost-per-outcome baseline for one or two workflows.
- Unsupported claims
- That token costs will fall overall for the agency
- That private-sector overrun rates apply directly to SLED
- Specific savings percentages
Pre-sales engineering
Role takeaway
- Fit
- Applies to any consumption-billed Claude deployment, especially agentic ones.
- Architecture and integration
- Request tagging, model routing, per-agent caps and anomaly alerts feeding a single spend view alongside cloud costs.
- Prerequisites
- Tagging scheme
- Telemetry pipeline
- Quality metrics per workflow
- Constraints
- Framework is not Claude-specific
- No SLED cost benchmarks provided
- Security
- Tagging also supports audit trails; ensure tags do not carry sensitive data.
- Proof of value
- Measure tokens per task for a pilot agent before scaling
- Test that per-agent caps halt a runaway loop
- Track quality alongside cost after model routing
Delivery
Role takeaway
- Work
- Create an AI spend owner, a monthly spend-to-outcome review and post-promotional budget rebaseline.
- Dependencies
- Finance and IT agreement
- Outcome metrics per workflow
- Usage data
- Ownership
- Agency CFO with CIO, as joint owners named in policy.
- Skills and adoption
- Build FinOps literacy among finance and IT staff.
- Governance checkpoints
- Budget rebaseline before renewal
- Quarterly cost-per-outcome review
- Retirement review for low-value workflows
- Acceptance criteria
- Proposed: cost per outcome reported for each production workflow
- Proposed: fiscal-year spend within approved cap
- Risks
- Caps that degrade service quality
- Consultancy framing taken as evidence
- Agent loops consuming budget before alerts fire
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Recommends tagging every AI request by agency, program, use case, model and environment, model routing to the cheapest model meeting a quality bar, and per-agent caps with anomaly alerts.
Governance
Who approves, reviews and stays accountable for outcomes?
Proposes a named owner for AI spend across CFO, COO, CTO, CPO and chief AI officer roles, and cost-per-outcome tracking tied to continued funding.
Security and privacy
What data, permissions and controls need testing?
Notes request-level tagging also supports security posture; no privacy analysis.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Implies a need for FinOps/TokenOps skills in public finance and IT teams.
Procurement
What should contracts, pricing and exit terms secure?
Favors usage-based or tiered pricing, pricing-transparency clauses, short terms, portability and cooperative vehicles with Participating Addendum exit clauses for state and local buyers.
Operating model
Which teams own the service once it runs?
Treat AI spend as a managed category with chargeback or showback, not a generic IT line item.
Publication history
- 2026-10-30Anthropic · Issue 0210 resources
Stable resource ID: mckinsey-government-ai-economics-token-cost-caps-20260929