Why AI Budgets Get Cut in Year Two

Year one of a government AI file is a speech. Year two is a bill. The speech had a discounted licence, a borrowed GPU, a workshop with sandwiches, and a minister's sentence. The bill has AMC, power, an SI who is still on site, a token meter that discovered paste-the-PDF, and a utilisation chart that looks like a pulse. Finance cuts the line. Everyone says the government does not understand AI. Everyone is wrong. The government understood the bill.

This is an opinion. The opinion is that most year-two cuts are earned. They are earned by models that never attached to a duty, by cost sheets that hid the recurring lines, and by teams that could not show a before-and-after on a metric the department already believed. They are not earned by lack of vision. Vision is not a budget head.

Prcept has no interest in being the year-one decoration. We would rather sell a smaller on-prem agent that a PAO can renew than a festival that finance is forced to end. If that sounds unromantic, good. Romance is what gets cut.

Four honest reasons the line dies

The discount was the product. Year-one software arrived at a pilot price. Year-two arrived at the list. Nobody had put the list in Ledger A. The renewal looks like a 3× increase. It is not an increase. It is the first true invoice.

Nothing got cheaper or cleaner. The agent drafted text. Officers rewrote it. The MIS still needed the same four clicks. There is no metric the secretary already loves — days to first response, reopened grievances, overtime on a named head — that moved. Users liked it is not a renewal paper.

The hardware is idle and visible. A node bought for a training ambition that never came still draws power. Facilities have the bill. Internal audit has the utilisation. Renewal of AMC on an idle asset is how paras are born. Finance is doing its job. The owner left. The joint secretary who loved the demo took a central deputation. The remaining file is a vendor CSM and a Slack. Recurring money needs a living RACI. Without one, the safe decision is to stop.

The dishonest reasons people cite

Finance is analogue. Finance is literate. They can read a utilisation chart. What they cannot do is invent a duty-improvement you did not measure. We needed more GPUs to show value. Value on a public duty is not a function of VRAM. If a 7B on one card did not attach to the MIS, an 8-GPU node will attach only to the power bill.

The model is now outdated so we must refresh to justify the AMC. That sentence is how you double a cut. Refresh after utilisation, not before. Other states are spending more. Other states are not your DFPR. Peer pressure is not a head of account.

What a renewal note needs, in the order a PAO will look.

Question	Passing answer	Failing answer
What duty?	Named workflow, named circular or office order	AI transformation of the department
What moved?	A metric you already reported last year	A new AI score the vendor invented
What is the year-two cash?	AMC, power, SI, hours — no surprise vs Ledger A	A list price nobody filed
What is utilised?	A chart of busy hours and a reason for idle	A picture of the rack
Who owns it now?	A named officer still in the chair	The vendor success manager

How to be renewable on purpose

Put year-two cash in the first sanction note, even if you only ask for year-one money. The second number should not be a plot twist. Attach the agent to a system of record in year one, even if the model is small and the drafts are clumsy. A clumsy tool that writes into the MIS is more renewable than a fluent toy that lives in a chat tab.

Measure one boring metric from week four. Publish it internally every month. If it does not move by month nine, kill or redesign before finance does it for you. Reassign idle cards before renewal season. An honest smaller footprint is easier to renew than a large embarrassed one.

Shrink is a renewal strategy

A 40 percent cut you propose is a renewal. A 100 percent cut finance proposes is a funeral. Take the first. Power down the unused node, drop the unused workflow, write the year-two cash without the discount, and keep the one duty that moved a metric. That is how four-year agents are born.

Do not invent a new acronym to hide the same bill. PAOs have seen Mission, Cell, Lab and Centre on consecutive files. They read the AMC line. So should you.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

If we show utilisation we will be cut

If you hide utilisation you will be cut later, in public. Show it and shrink.

Year two is when AI pays back

Then put the payback in a metric you already report. A promise that value starts after the next sanction is a novel.

We should move the line to a scheme that still has money

Only if the scheme's purpose actually covers the work. Hiding an AI AMC under a training scheme is how you meet audit.

The minister wants a bigger model for the anniversary

Give the minister a metric and a smaller bill. Anniversaries are not DFPR authorities.

A ninety-day path to a renewable year two

1. Day 1: print last year's Ledger A and this year's draft invoices. Circle surprises.
2. Days 2–30: pick one already-reported metric. Instrument it. Kill any workflow that cannot touch the MIS.
3. Days 31–60: reassign or power-cap idle cards. Write the year-two cash without discounts.
4. Days 61–90: draft the renewal note in the PAO's order of questions. If you cannot fill a row, shrink the ask until you can.

How this shows up in the file

Subject: Renewal of [system] for FY [n] — duty, metric, cash, utilisation, owner.

Duty: [workflow + order]. Metric: [existing report, before/after]. Year-two cash by head: [table], compared to the original Ledger A. Utilisation: [figure], idle action: [reassign / share / power-cap]. Owner: [name, post]. This is a renewal / a shrink / a stop.

This opinion is not legal or budget advice. Romance is what gets cut; dull files get renewed.

This article is informational field guidance for Indian public institutions, not legal, procurement, tax, accounting, tariff or engineering advice. Confirm against the current Gazette, GFR, GeM term, SERC tariff order, IndiaAI portal rule, CAG mandate, DPDP text, departmental finance manual and your counsel before you file it. Figures are methods and order-of-magnitude illustrations, not a dataset of real deployments and not a substitute for a live quote.

How to put this in the finance note

A P1 CIO/CTO searching “AI budget renewal failure” needs a number a CFO can defend, not a GPU brand. “Why AI Budgets Get Cut in Year Two” belongs in a cost model with people, power, idle time, AMC and the cost of a failed pilot.

Year two is when the discount ends, the GPU sits idle, and nobody can show a duty that got cheaper or cleaner. Finance is not anti-AI. Finance is anti-fog. IndiaAI subsidy, if you use it, is a live notice — not a permanent discount. On-prem TCO includes ops headcount. Do not invent Rs/hour. Cite the source of every rupee.

• Separate capex, opex, and one-time cleanup.
• Show utilisation, not just peak GPUs.
• Price the human fallback, not only inference.
• Date every tariff and subsidy assumption.

Close this loop before the next CAB

Put “Why AI Budgets Get Cut in Year Two” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P1 CIO/CTO, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “AI budget renewal failure” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What the next file must contain

“Why AI Budgets Get Cut in Year Two” earns a line in the noting only if a P1 CIO/CTO can attach proof of “AI budget renewal failure.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “AI budget renewal failure.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.