Government software estates carry recoverable waste at a scale that compounds across administrations, and New York City is the clearest public proof of it. Over 25 years, NYC has saved more than $800 million managing software across 80+ agencies, not through a one-time cleanup but through a standing program of centralized licensing, vendor negotiation, and audit defense. As NYC’s new Chief Savings Officer mandate pushes every city agency to find recurring savings against a $12 billion budget shortfall, the city’s own software program shows where a large share of that money has been hiding all along: in over-licensing, fragmented purchasing, and inflated vendor audit claims that a maintained license position can cut by most of their value.
Key takeaways
- $800M+ saved over 25+ years across 80+ NYC agencies. New York City’s software program is the longest-running public example of government software optimization at scale, spanning multiple mayoral administrations and 7 managed vendors.
- $53M+ documented on Microsoft alone. A single publisher relationship inside the NYC estate produced tens of millions in savings, cost avoidance, and risk avoidance, which is a signal of how much value sits in one vendor line item for a large government.
- An $85M IBM audit claim was settled at $12M. That is an 86 percent reduction, achieved by reconstructing entitlement evidence rather than accepting the auditor’s opening number.
- A $2M Open Text demand was reduced to $115K, and a $1.6M Microsoft SPLA finding was brought under $500K. Across UMS’s published engagements, audit claim reductions have ranged from roughly 78 to 94 percent of the initial demand.
- The NYC Housing Authority found 10,000+ inactive licenses in three weeks. That single Phase 1 review translated to $495K in Year 1 and $2.2M over the five-year Enterprise Agreement term, with no upfront cost to the agency.
Why government software estates accumulate waste
The waste is not the product of any single bad decision. It is structural, and it accumulates the way sediment does.
Procurement cycles fragment purchasing. Large governments buy software agency by agency, each negotiating in isolation. A single publisher may hold dozens of separate agreements with different entities inside the same government, none of them aware of what the others are paying. That fragmentation forfeits volume leverage and produces inconsistent terms that vendors are happy to leave in place.
Administration turnover resets institutional knowledge. Software contracts outlive the officials who sign them. When leadership changes, the context behind a renewal, a true-up, or a prior audit settlement often walks out the door with the people who managed it. The next cycle gets negotiated cold, and hard-won concessions quietly lapse.
Vendor true-up pressure compounds over time. Publishers structure renewals and true-ups to capture growth automatically while making reductions difficult. Inactive accounts, over-provisioned premium tiers, and licenses assigned to departed staff carry forward from cycle to cycle because no one owns the reconciliation. The default direction of a government software bill is up, unless something actively pushes back.
What a compounding savings program looks like
New York City’s program is instructive because the savings did not come from one dramatic renegotiation. They came from an operating model maintained across decades.
The foundation is centralized visibility. UMS consolidated software inventory, entitlement data, and usage analytics across all 80+ city agencies into a single compliance view, so the city and its agencies could see their licensing position across every major publisher in real time rather than discovering it during an audit.
On top of that sits continuous vendor management. Rather than treating each renewal as an isolated event, the program manages the full publisher portfolio, Microsoft, Adobe, VMware, Cisco, Oracle, Dell, and others, against a maintained position. Microsoft, the city’s largest relationship, alone produced more than $53M in documented savings, cost avoidance, and risk avoidance across categories from Office Professional licensing to SQL Server edition rightsizing.
The multiplier is continuity. Because the program persisted across mayoral administrations, every renewal built on the last and every audit defense strengthened the next. That is the difference between saving money once and saving money that compounds. The city recently signed a 6-year renewal, its longest commitment in the partnership’s history.
The audit-defense record
Audit defense is where the largest single-event reductions show up, because publisher audit demands against government estates are structured to open high. The defense is not negotiating harder after accepting the vendor’s math. It is reconstructing an independent, entitlement-based position and negotiating from verified fact. NYC’s published outcomes:
| Publisher | Initial claim | Outcome | Reduction |
|---|---|---|---|
| IBM | $85M | $12M | 86% |
| Open Text | $2M | $115K | 94% |
| Microsoft SPLA | $1.6M | Under $500K | ~69% |
| Oracle (Sales Audit) | $10M | Deferred; self-remediated | Avoided |
Two things stand out. First, the range of reduction is wide but consistently large: across UMS’s published engagements, audit claim reductions have ranged from roughly 78 to 94 percent of the initial demand. Second, the Oracle outcome is a different archetype entirely. The claim was avoided rather than negotiated down, because the exposure was caught and self-remediated before the auditor could price it. For a government estate, catching an issue early is often worth more than winning the argument later.
What the Chief Savings Officer mandate means for other governments
In January 2026, Mayor Mamdani signed Executive Order 12, requiring every New York City agency to designate a Chief Savings Officer tasked with finding recurring, structural savings rather than one-time accounting measures. The mandate set targets of 1.5 percent in Fiscal Year 2026 and 2.5 percent in Fiscal Year 2027, against a $12 billion budget shortfall across the two years. By March, agencies had identified more than $1.7 billion in proposed savings. The administration was explicit that it wanted lasting efficiencies and more reliance on the city workforce, rather than fixed outside consulting contracts.
Software spend is one of the cleanest places to find exactly that kind of recurring saving, and the framing matters. A budget-neutral shared savings engagement is not another fixed consulting contract. The provider is paid only from savings it verifies and delivers, so the agency needs no new appropriation to begin and never spends more on the program than the program returns. That is financially the opposite of the outside consulting spend administrations are trying to reduce. The NYC playbook, centralized visibility, continuous vendor management, and standing audit defense, is replicable by any government carrying fragmented software purchasing, which is nearly all of them.
How to start
A government agency does not need a new budget line or a multi-year commitment to find out what is recoverable. The first step is a diagnostic against the largest publishers by spend.
Run an entitlement-to-deployment reconciliation on your top software vendors, comparing what is actually deployed and used against what is licensed and paid for. That single exercise surfaces the inactive licenses, over-provisioned tiers, and mismatched editions that make up most recoverable software waste, and it is the same work that found 10,000+ inactive licenses at the NYC Housing Authority in three weeks. Because a shared savings engagement is budget-neutral, the diagnostic carries no appropriation risk: it either finds recoverable savings or it does not, and the agency pays only against savings actually delivered.
For an agency under a savings mandate, software is among the fastest paths to recurring, structural reductions that do not cut services. The waste is already in the budget. The only question is whether anyone is looking for it.
Book a diagnostic. We build the counter-position before, and during, a publisher’s renewal or audit, and we are paid only from savings we verify.
Source notes
- City of New York case study: UMS’s 25-year NYC engagement, $800M+ cumulative savings, $53M+ Microsoft savings, and the published audit-defense outcomes.
- NYC Housing Authority case study: 10,000+ inactive licenses found in three weeks, $495K Year 1 and $2.2M five-year EA savings, shared savings model.
- Mayor Mamdani Signs Executive Order to Require Chief Savings Officers: NYC Mayor’s Office announcement of Executive Order 12, January 29, 2026.
- Mayor Mamdani Releases Update on Savings Plan: NYC Mayor’s Office update confirming the 1.5% / 2.5% targets and $1.7B+ in identified savings.