CA Technologies

Three signs your CA renewal is anchored to legacy entitlements.

The contract you are renewing was written for a portfolio that no longer matches what you run. The quote prices the old shape, not the live one, and the difference is the largest single line of buyer side opportunity in any CA motion.

By The Negotiation Desk · CA · Archetype: The Tell

Published 12 May 2025 · Updated 30 Oct 2025

CA portfolios carry the longest tails in the Broadcom catalogue. Most of the contracts we read in 2026 reference entitlements that were assembled between 2014 and 2019, under three different ownership regimes, with product naming, packaging, and unit definitions that have all moved since. The quote on the renewal table prices that legacy footprint at current list, with the seller's assumption that the buyer's deployment matches the contract record. The deployment almost never does. The three tells below are how the buyer sees the gap before the seller does, and they sit inside the renewal pack itself.

None of these tells require an external review. All three sit on the renewal documents the seller has already produced. The Desk runs this read in the first analyst call on every CA renewal that crosses our desk. It is the cheapest piece of buyer side work in any CA motion, and it almost always reframes the conversation before the price discussion opens.

Tell one: the product list includes items that no longer exist as separate products

The first tell is the product list. CA has reorganised its portfolio repeatedly. Products that were sold separately in 2016 have been folded into broader suites. Suites that existed in 2019 have been redivided. The renewal pack often carries product names that match the buyer's purchase history but no longer correspond to live SKUs. The seller renews against the historical name, the buyer signs against a name that has no current product, and the entitlement gets carried forward as a paid line that the operational team has either never deployed or stopped using.

We see legacy product entries on roughly two thirds of the CA renewal packs we review. The most common categories are legacy automation suites, identity components that have been superseded by Identity Suite consolidations, and AIOps precursor products that predate the current operational intelligence packaging. Each legacy line carries an annual value. Each annual value compounds across the renewal term. A typical legacy line is worth between $200,000 and $1.4M per year on a mid sized CA contract.

Tell two: the unit of measure does not match the deployment model

The second tell sits in the unit of measure. CA products have historically been licensed against three primary units. Named users for identity and access products. Transactions or API calls for the API Management portfolio. MIPS or capacity points for the mainframe products. Each unit has been redefined at least once since most in force CA contracts were signed. The renewal pack often prices against the unit that was in the original contract, not the unit that reflects the current deployment.

The mismatch can cut both ways. We have seen buyers paying for named users against an active count that is smaller than the contracted count, and we have seen buyers paying for API calls against a transaction count that has moved to a different metric in the current product. Either way the renewal does not price against the live operational reality, and either way the buyer has a defensible position to restructure the unit at renewal.

Tell three: the support tier reflects an estate that has been deprioritised

The third tell is the support tier. Most CA renewals carry a support tier that was set in the original contract and rolled forward. The tier was set against a criticality profile that may no longer apply. CA portfolios in 2026 often sit alongside modern replacements, in a containment posture, with the buyer running CA only for workloads that cannot easily be migrated. The criticality of those workloads is usually lower than the criticality of the original deployment. The support tier on the renewal does not reflect that.

"The contract was renewing six products. Two of them did not exist as separate SKUs any more. One was being run on a parallel platform with the CA install kept only for compliance. The support tier was anchored to a 2017 design that nobody at the buyer could remember signing off."CA Practice Lead, The Desk

How the three tells compound

The three tells are not independent. In a typical CA renewal we see at least two of the three. The product list carries legacy entries that no longer match live SKUs. The unit of measure prices against the original definition rather than the current operational reality. The support tier anchors to the original criticality profile. Each tell on its own is a 5 to 15 percent question. Together they move a renewal by 18 to 38 percent on quoted value, before any structural restructure of the package or the term.

The structural restructure conversation is also more available on CA renewals than on most other Broadcom motions, because the buyer's exit options are real. CA products have credible modern replacements in almost every category. The seller knows this. The lever the legacy entitlement read creates is amplified by the credibility of the exit conversation that sits underneath it.

The reading order on the renewal pack

When a CA renewal pack arrives, the Desk reads it in a specific order. First the product list, against the buyer's live deployment inventory. Second the unit of measure for each product, against the active operational metric. Third the support tier, against the current criticality of the workloads that depend on each product. Only after those three reads is the total price line worth opening. The reverse order, where total price is read first and line items second, is how CA renewals close at quoted value rather than at corrected value.

Renewals carrying at least one legacy product line~66%

Typical value of a legacy line$200K to $1.4M per year

Unit of measure mismatch on active deployments~58% of contracts

Combined entitlement correction on $8M renewal$1.4M to $3.0M

What we have seen on live deals

A European telco brought us a CA renewal pack in 2025. Total contract value $8.4M over three years. The product list carried four CA Automation modules, two of which had been superseded in the current Broadcom catalogue and one of which had not been deployed in production since 2022. The unit of measure on the Identity component priced against named users at a count that was 31 percent higher than the active directory population. The support tier was set at a Premier band on workloads that had been moved to a parallel modern platform two years earlier. The combined correction removed $2.7M from the renewal before any structural restructure. The structural restructure produced another 12 percent. The renewal closed at $4.4M against an opening of $8.4M.

A Fortune 200 financial services group brought a smaller CA renewal in early 2026. Same pattern. Three legacy lines, one unit definition mismatch, support tier anchored to a 2018 design. The correction alone produced a 24 percent reduction. Different size, different sector, the same three tells.

The takeaway

The CA renewal prices the contract record, not the live deployment. The two have drifted in every renewal we have reviewed, often by more than a decade of portfolio reorganisation, and the drift always lands on the buyer if nobody reads the renewal pack against current reality.
Three tells matter most. Product list against live SKUs. Unit of measure against operational metric. Support tier against current criticality. Each is a 5 to 15 percent question on its own. Together they move the renewal by 18 to 38 percent.
The legacy entitlement read goes first in the buyer side motion. It is the cheapest piece of work, the cleanest argument, and the one the seller has the least ground to push back on. It also opens the exit conversation that sits underneath every CA renewal.