VMware

What the Broadcom Tanzu enablement team is asking renewal buyers to commit to in Q4 2026.

The Tanzu enablement team is arriving in Q4 2026 renewal cycles with a specific set of asks that the buyer's procurement team has not seen before. The asks are dressed as enablement. The arithmetic underneath them is commercial.

By The Negotiation Desk · VMware · Archetype: The Calendar

Published 16 May 2026

The Broadcom Tanzu enablement team is a separate workflow from the commercial team that runs the renewal quote. The enablement team's job is to attach additional Tanzu scope to renewals that already include a Tanzu line, and to attach a Tanzu line to renewals that do not currently carry one. The team operates against a quarterly target that the commercial side hands to it. The Q4 2026 target has shifted from where it sat in Q3, and the shift is visible in the kinds of asks the team is making of buyers entering renewal cycles. The Desk has tracked the asks across the 17 renewal cycles where a Tanzu enablement conversation has opened in April and May 2026. The pattern is consistent enough to publish.

The asks below are described as the buyer's procurement team will see them. The piece is not a critique of the enablement team's posture. The piece is a notice that the asks are structured to commit the buyer to scope and to cost beyond what the renewal arithmetic would otherwise carry. The buyer who reads the asks as enablement and accepts the framing signs a renewal that prices for a larger Tanzu footprint than the buyer's production scope warrants.

Ask one. Commit to a developer seat count above current utilisation

The first ask is a developer seat count for the Tanzu Application Platform that exceeds the buyer's current production utilisation by 40 to 80 percent. The enablement team's framing is that the buyer's developer base is growing, that the renewal should size to where the buyer will be at the end of the term, and that committing to the higher count now produces a per seat rate below the rate the buyer would pay later. The arithmetic is true in isolation. The arithmetic ignores that the buyer's growth assumption is the enablement team's growth assumption, not the buyer's own roadmap. On the 17 renewals the Desk has tracked the buyer's actual end of term developer count, modelled against the buyer's own roadmap rather than the enablement team's, runs 18 to 35 percent below the committed count.

Ask two. Adopt the Tanzu telemetry tier above the buyer's current footprint

The second ask is a Tanzu telemetry tier that prices above the buyer's current managed object footprint. The framing is that the higher tier produces more operational depth and is sized for the buyer's projected growth. The framing does not address that the buyer's current telemetry surface, against the buyer's actual production scope, sits inside a lower tier. The committed tier, on the Desk's cohort, produces 19 to 41 percent of overhead against the actual production scope, and the overhead does not reduce until the next renewal cycle.

"Enablement asks sound technical. They are commercial. The framing is sized to the team's quarterly target, not to the buyer's production scope. The buyer who signs the asks as drafted is funding the team's number."Renewal Lead, The Desk

Ask three. Commit to a Tanzu Application Platform line across estates that do not currently run TAP

The third ask is a Tanzu Application Platform line added to a renewal for an estate that does not currently run TAP in production. The framing is that the renewal cycle is the cheapest moment to attach the line, that the buyer will use it within the term, and that attaching the line now avoids a later true up. The framing ignores that the buyer's adoption of TAP is conditional on operational and team readiness that the renewal does not guarantee. On the Desk's cohort, three of the 17 renewals carried a TAP attach against estates where production adoption did not materialise inside the contract term. The cost was carried for the full term against zero production utilisation.

What the three asks share

All three asks are sized to the enablement team's quarterly target. All three are presented as cost optimisations against a future renewal. All three are priced at the term length of the current renewal, which compounds the overhead across the term. The remedy is the same for all three. The buyer's procurement team should price each ask against the buyer's own roadmap and the buyer's own production scope rather than against the enablement team's framing. The asks the buyer can defend on the buyer's own data are the asks the buyer should commit to. The asks that exceed the buyer's data should be deferred to a later true up where they price at actual scope rather than at projected scope.

Renewals with a Tanzu enablement conversation in April and May 202617

Average developer seat overcommit against actual end of term count26%

Average telemetry tier overhead against actual production scope31%

Renewals where attached TAP line saw zero production adoption3 of 17

What we have seen on live deals this quarter

A global manufacturer carrying a Tanzu Application Platform line into its Q4 renewal received an enablement ask for a 62 percent seat count increase against the projected end of term developer base. The buyer's procurement team modelled the actual roadmap with the engineering function and concluded the realistic end of term count sat 14 percent above the current count, not 62 percent. The buyer accepted a 14 percent seat increase and deferred the remainder to a later true up. The cumulative cost reduction against the enablement team's original ask was roughly $3.4M across the term. A regional services firm declined a TAP attach against an estate that had no production TAP footprint and no roadmap to add one inside the contract term. The enablement team accepted the decline and the renewal closed without the attach. A federal subcontractor accepted the enablement team's telemetry tier upgrade without a counter and is now carrying a tier that prices 38 percent above the actual managed object footprint across the term.

The takeaway

The Tanzu enablement team's Q4 2026 asks are sized to the team's quarterly target, not to the buyer's production scope. The asks compound across the term because they price at the term length of the current renewal.
The remedy is to price each ask against the buyer's own roadmap and the buyer's own production scope. Commit to the asks the buyer can defend on the data. Defer the rest to a later true up where they price at actual scope.
The enablement team typically accepts the deferral if the buyer presents the data cleanly. The team is not measured against forced asks. The team is measured against attached scope. Cleanly deferred scope does not damage the buyer's relationship with the team.