How a federal agency right sized its VMware portfolio before the renewal arrived.

The agency runs an enterprise hosting platform that supports eighteen mission systems across three data centres, with a VMware footprint that had grown organically across three prior contract cycles. The platform was carrying capacity that several mission systems had quietly stopped using as their workloads moved to other platforms or were retired. Nobody had taken the time to remove the unused capacity from the contract because each individual unit was small and the aggregate was not visible at the platform level. The Broadcom renewal trajectory projected a thirty four percent uplift against the prior period, calculated on the current contracted capacity and the new subscription economics. The agency procurement officer made one decision that defined the engagement. The portfolio review would happen before the renewal conversation, not during it.

The engagement ran from start of portfolio review to signed renewal across eleven months. The portfolio review consumed the first eight. The negotiation consumed the remaining three. The signed contract closed twelve percent below the prior period in real dollar terms, a forty six point swing against the trajectory projection, on a scope the agency could defend across every line of the audit trail. The right size itself, the structural work that preceded the negotiation, was the single largest source of value.

The Quote

The trajectory uplift of thirty four percent was the seller's reasonable projection against current contracted capacity and the new pricing model. It was not yet a quote because the negotiation had not yet started. The agency would have received the formal quote at approximately that level if the portfolio review had not happened first. The first task of the engagement was to ensure that the formal quote, when it arrived, was anchored to a smaller and more accurately scoped portfolio than the current contract reflected.

That work could only happen if the agency knew, line by line, what it actually needed. Federal procurement processes do not respond well to renegotiations that surface mid cycle. The right place to remove capacity is at renewal. The right time to know which capacity to remove is six to eight months before renewal. The lead time is the asset.

The Find

The portfolio review ran across the eighteen mission systems system by system. Each system owner was asked to confirm current capacity utilisation, projected capacity requirement across the next three years, and any planned platform migrations. The data was reconciled against the agency's own infrastructure telemetry, where the telemetry was the authoritative source on actual utilisation. The reconciliation surfaced four findings.

First, two mission systems had completed migration to alternative platforms and were holding residual capacity that could be released. Second, three mission systems had projected growth that was material and needed to be accommodated in the new contract, not absorbed as anniversary true ups. Third, five mission systems were running at significantly lower utilisation than their contracted capacity, and the system owners confirmed that a reduction was acceptable. Fourth, the platform team itself was holding a contingency capacity pool that had not been drawn upon in two years and could be reduced.

"The portfolio was not oversized because anybody was wrong. It was oversized because nobody had the platform wide view. The platform wide view changed every individual conversation about capacity."Director of enterprise infrastructure

The aggregate effect of the four findings was a documented capacity reduction of approximately twenty two percent against the existing contract, with the three growth requirements priced into the new contract as agreed scope rather than absorbed as future true ups. The portfolio was now the right size for the next contract term. The work happened on the agency's own timeline, with the agency's own data, before any conversation with the Broadcom account team about the renewal.

The Restructure

The restructure conversation with the account team was short because the structural work was finished. The agency tabled a written renewal proposal that specified the reduced capacity, the priced in growth allowances for the three expanding systems, the contingency pool adjustment, and a three year subscription on the standard VCF terms with the agency's specified Aria scope and no Tanzu. The proposal was complete on the buyer side. The account team's role was to price it, not to define it.

The pricing conversation took three rounds across two months. The account team's first response held the per core rate above the agency's working envelope. The agency provided benchmarking data from peer federal customers, on terms the benchmarking permitted to share, that brought the per core rate into a range the account team could not credibly contest. The second round closed the per core rate inside the envelope. The third round closed the contract on the growth allowance pricing and the term language.

The signed contract priced the new term twelve percent below the prior period in real dollar terms, on the right sized portfolio. The forty six point swing against the trajectory was visible at signature. The agency's procurement function had the audit trail, line by line, system by system, to defend the outcome across the contract approval chain.

The Outcome

The agency closed the renewal on terms it had defined rather than terms it had received. The mission system owners had the capacity allocations they had confirmed they needed. The growth headroom was contracted in advance. The retired and reduced capacity was off the contract. The next renewal cycle starts from a portfolio that is in alignment with actual usage, which means the next renewal conversation begins from a defensible baseline rather than from a drift inflated contracted position.

The lesson, the lesson we apply on every federal and large enterprise portfolio engagement, is that the right size has to happen before the renewal. The work cannot be compressed into the negotiation window. The system owners need time. The data needs to be reconciled. The growth allowances need to be agreed inside the buyer's organisation before they can be agreed in the contract. The portfolio review takes six to eight months. The negotiation takes two or three. The lead time is the asset. Buyers who give themselves that lead time receive renewals that reflect what they actually need. Buyers who do not, receive renewals that reflect what they had.

The takeaway

• Portfolio right sizing is renewal work that has to happen before the renewal window opens. Six to eight months of lead time is the difference between a defensible new baseline and an inflated carry forward.
• Mission system owners and platform teams have the data to right size their own portfolio. The work is to give them the platform wide view, reconcile their numbers against telemetry, and consolidate the result into a single renewal scope.
• Growth allowances should be priced into the contract in advance, not absorbed as anniversary true ups. The renewal is the moment to convert known organic growth into agreed scope at the negotiated rate.