The one Tanzu Application Platform pricing lever most buyers leave on the table.

Tanzu Application Platform now prices on a workload class unit. The class definition is the entire arithmetic of the quote. Buyers who arrive at the renewal conversation with a documented workload class profile that differs from the seller's default classification recover roughly 14 to 28 percent of the headline quote. Buyers who do not arrive with the documented profile accept the seller's default and pay the resulting quote. The Desk has reviewed 17 Tanzu Application Platform renewals across late 2025 and the first five months of 2026. The workload class refactor is the single largest lever inside the new unit definition, and it is the lever buyers most frequently leave unpulled. This article explains the lever, why it is left on the table so often, and how the buyer should approach it.

The article assumes the buyer is renewing a Tanzu Application Platform contract on the post 2025 unit definition. The unit definition uses four workload classes: stateless, stateful, batch, and platform. Each class carries a multiplier on the base unit price. The multipliers in the Q4 2026 quote sample sit at: stateless 1.0, stateful 1.6, batch 0.8, platform 2.2. The effective price the buyer pays per workload is the base unit price multiplied by the class multiplier, summed across the portfolio.

Why the seller's default classification overstates the cost

The seller's default classification, applied when the buyer has not supplied a documented profile, weights the buyer's portfolio toward the higher multiplier classes. The default profile in the Q4 sample assumed roughly 18 percent stateless, 47 percent stateful, 12 percent batch, and 23 percent platform. The actual classification, when the buyer documents the portfolio, typically sits closer to 41 percent stateless, 26 percent stateful, 19 percent batch, and 14 percent platform. The variance between the two profiles produces an effective unit price differential of between 14 and 28 percent on the median portfolio. The seller's default is not arbitrary. It reflects the highest reasonable assumption the seller can make in the absence of buyer information. The buyer's documented profile reflects the actual portfolio.

The documented profile is recoverable from the Tanzu Application Platform itself. The platform exposes workload metadata that maps each running workload to a class against the contractual definitions. The classification can be produced by the buyer's operations team in under a week of work on the median portfolio. The work is not exotic. The work is procedural. The recovery of 14 to 28 percent of the headline quote in exchange for a week of operations time is the cheapest movement available in the entire renewal.

Why buyers leave the lever on the table

Three reasons account for most of the cases the Desk has seen where the buyer did not pull the lever. The first is procedural unfamiliarity. The class multiplier is a relatively new mechanic, introduced in the 2025 unit refresh, and many buyer procurement teams have not yet encountered it in a prior negotiation cycle. The seller's quote presents a total number rather than the multiplier arithmetic, which produces the impression that the unit price is fixed at a higher level than it actually is.

The second reason is timing. The documented profile must be produced and supplied before the renewal anchor date with enough lead time for the seller's deal desk to reissue the quote against the documented profile. Buyers who supply the profile inside two weeks of the anchor date do not give the deal desk time to reissue. The conversation runs on the original quote and the buyer accepts it as a function of the calendar.

The third reason is internal classification disagreement. The buyer's operations team and the buyer's application team often classify workloads differently. The operations team classifies on infrastructure characteristics. The application team classifies on functional characteristics. The contractual definitions, in the Desk's reading, align more closely with the operations classification. Buyers who let an internal disagreement delay the production of the profile burn the calendar and leave the lever unpulled. The Desk's view is that the buyer should produce the profile on the operations classification and document any application team disagreements as footnotes rather than as blockers.

"The seller's default profile is the highest reasonable assumption the seller can make about your portfolio. Your actual profile is the actual portfolio. The difference between the two is the lever. The lever is in your own product."Tanzu Engagement Lead, The Desk

How to pull the lever

The lever has three components and the buyer should execute them in sequence. The first component is the inventory export. The buyer's operations team exports the running workload inventory from the Tanzu Application Platform, dated, with the class assignment applied. The export should sit alongside the contract's class definitions as a reference. The export is the foundational document.

The second component is the documented information request. The buyer's procurement team files a request with the deal desk asking the desk to reissue the renewal quote against the documented profile rather than against the default classification. The request should reference the contractual class definitions explicitly and should include the inventory export as the evidentiary basis. The Desk has filed this request 14 times across the cohort. The desk has accepted the documented profile in 13 of the 14 cases.

The third component is the placement justification challenge. The reissued quote will land at a lower number, but the seller will often place the buyer in the upper portion of the resulting band rather than at the median. The buyer's procurement team should challenge the placement with comparables that the Desk or another qualified advisor can supply. The placement challenge is procedural and is well within the deal desk's authority to respond to. The Desk has seen the placement challenge produce a further 6 to 12 percent reduction on top of the workload class refactor itself, on the cohort where it was filed.

When the lever does not work

The lever does not work on three conditions. The buyer's portfolio is genuinely concentrated in stateful or platform workloads, in which case the documented profile produces no material movement against the seller's default. The buyer is on a fixed bundle that has flat priced the Tanzu component at zero (in which case the workload class price has no direct effect). The buyer is inside an audit posture, in which case the deal desk will not accept a workload classification change as a renewal action until the audit is settled. The first condition is the rarest. The third is the most common reason the Desk delays the lever pull.

What we have seen on live deals

A European financial services buyer ran a Tanzu Application Platform renewal in March. The opening quote sat 31 percent above the prior contract value, sized on the seller's default classification. The Desk worked with the buyer's operations team to produce the workload class profile in eight working days. The documented profile reweighted the portfolio toward stateless and batch. The reissued quote dropped the headline by 24 percent against the original. The placement challenge added a further 9 percent reduction. The final quote landed 4 percent below the prior contract value. No other plays produced material movement on this engagement. The single workload class refactor lever did the work.

The takeaway

• Tanzu Application Platform now prices on a workload class unit with class multipliers from 0.8 (batch) to 2.2 (platform). The seller's default classification overweights the higher multiplier classes by roughly 21 percent at the median. A documented buyer profile is the lever that resets the arithmetic.
• The documented profile is recoverable from the Tanzu Application Platform itself. The operations team can produce it in roughly eight working days. The lever pull is the cheapest meaningful movement available in the Tanzu renewal.
• Three failure modes account for most of the unpulled cases: procedural unfamiliarity with the new unit, timing too close to the anchor date for the deal desk to reissue, and internal classification disagreements that delay the export. The Desk's view: classify on operations characteristics, document any disagreements as footnotes, and supply the profile no later than 30 days before the anchor.