Government Isn't A Hyperscaler

On Monday, Alphabet fell about 5%, dragging the communication services sector down with it. Memory chip stocks plunged in Asia overnight and the selling crossed the Pacific by Tuesday morning. Beneath the price action, the cause was specific and revealing: investors are starting to ask whether the enormous sums being poured into artificial intelligence will earn their keep, and reports of senior talent leaving Alphabet's AI teams added to the unease.

That question — will the AI capex pay off — is the right question for shareholders. It is the wrong question for a government.

What the market wobble actually says

The sell-off was narrow, not broad. The Russell 2000 closed above 3,000 for the first time even as the big tech names tumbled. That tells you the market is rotating, not collapsing. The doubt is concentrated in a handful of names whose valuations had assumed the AI trade would compound for several more years without a pause.

The question being asked is simple. Amazon, Microsoft, Alphabet and Meta have collectively guided to roughly 25 billion in capital expenditure for 2026. Their combined free cash flow is forecast to fall to about billion in the third quarter — a decade low. At that ratio, the cash being spent is no longer comfortably backed by the cash being earned. That is what the nervous side of the market is pricing.

Why this question doesn't translate to government

Public administration does not sell tokens. It does not have shareholders. Its “revenue” is taxes and its “product” is rights, services, and the slow accretion of public trust. The whole logic of equity-style ROI — free cash flow divided by capex — is structurally absent.

And yet, watch any AI tender written by any government this year and you will see private-sector language smuggled in. Pilots. Use cases. Productivity gains. Cost savings per FTE. We are evaluating public AI investments in the only vocabulary the consultants brought to the room, and the result is that everyone ends up arguing over a metric nobody in the citizen-service chain actually cares about.

From inside a national tax administration, having worked on conversational AI for citizens at scale, I can say something specific. The right number was never “queries handled per rupee of compute.” It was something closer to: did the next confused taxpayer get an accurate answer, in the language she actually speaks, in time to act on it, without having to travel to a counter? That is an outcome question. It is not a capex question.

An outcomes-first lens

If the market is pricing AI on cash flow, the government should price AI on three different things:

• Service latency. How much faster does a citizen get an answer, a refund, or a decision after the system is deployed?
• Service reach. How many more citizens, in how many more languages and pin codes, can the same service touch without adding counters?
• Officer leverage. How much higher-order work can the same officer do because the system has absorbed the routine?

None of these are radical. They are simply restatements of what the public sector exists to do. The discipline is to write them into the procurement document before the vendor walks in, not after the dashboard is built.

A proposal: separate the two stacks

Here is a concrete proposal. A government should split its AI estate into two stacks and evaluate them by two completely different rules.

The internal stack — drafting, summarisation, case retrieval, file review, internal search across decades of orders — can be evaluated commercially. Hours saved, error rates, contractor-substitution ratios. That is fair, because the work being replaced was already priced.

The citizen-facing stack — multilingual chatbots, eligibility navigation, guidance on a new statute, status tracking on a refund — must be evaluated as service delivery. The metric is not unit economics. The metric is whether a person previously locked out of a service is now inside it.

Confuse the two stacks and the second one will always lose to the first on a finance committee's spreadsheet. It will be quietly defunded the moment an AI valuation cycle turns. And, as Monday's tape made plain, the AI valuation cycle will turn.

The public sector organisations point

Professor Michael Ting's course on the Analysis of Public Sector Organizations at SIPA made an argument that has aged into something close to a law. Public agencies serve multiple principals — legislatures, ministers, courts, auditors, citizens — and the metrics they adopt silently decide which principal they end up serving. Adopt private-sector ROI metrics for public AI and the system will end up optimising for the auditor's spreadsheet, not the citizen at the window. That is not a hypothetical risk. It is the default trajectory.

What to do this quarter

Three moves, for any department about to sign an AI contract:

• Write the outcome metrics before the price negotiation, not after.
• Build at least one citizen-facing metric whose headline a non-technical minister can defend in question hour.
• Keep funding the citizen stack even when the headline AI trade in the markets is going through one of its periodic doubts. Especially then.

The market is reminding everyone this week that the private bet on AI is a bet. Government is not making the same bet. It is deploying a tool that should be judged by whether the queue moved. The discipline is to keep saying that out loud while the news cycle is busy saying everything else.

#AIinGovernment #PublicSectorAI #DigitalGovernance #AICapex #IndiaAI #Governance #PublicFinance