Broadcom CA mainframe pricing, the bundle is the negotiation
Broadcom moved the former CA mainframe software to a portfolio model: MSPS bundles a defined product set under a single MSU based metric mapped to the IBM Million Service Units measure on the host LPARs, so the same peak drives both vendors' bills. The bundle simplifies the contract and locks the customer to it, and everything negotiable happens at signing, because mid term the shape only moves in Broadcom's favor.
Prepared by Redress Compliance · August 7, 2026 · Broadcom advisory. Based on 20 to 30 Broadcom CA mainframe renewals reviewed 2024 to 2025.
Executive summary
The uplift outruns the usage, reliably.
Opening renewal quotes carried 12 to 30 percent uplift against flat application development MSU consumption across our reviews, and the discount bands themselves narrowed under Broadcom, with the legacy CA pricing room shrinking 10 to 25 percent in many renewal cycles.
Renewal escalators run high by default, and caps of three to five percent are negotiable but never granted unasked, which makes the escalator clause the first page to mark.
The bundle protects the high value tools with the low value ones.
MSPS bundles systems management, storage, security, database, and development tools under one metric, and the pattern we kept finding was low value products bundled to protect high value DevOps tooling, with unbundling cutting 10 to 22 percent.
The bundle is fixed at signing: adding a product mid term carries an uplift, removing one rarely reduces the price, so the sizing conversation happens once, before signature, or not at all.
The baseline is wrong in six of ten estates, in Broadcom's favor.
The MSPS metric maps to the IBM MSU measure on the host LPARs, and sub capacity reporting errors inflated the baseline in six of ten estates: test and development LPARs charged at full capacity when sub capacity was available, and peaks unreconciled against what the paper actually entitles.
The same MSU peak drives the IBM bill and the Broadcom bill, so every point of capacity discipline pays twice.
Term length and swap rights are the two structural levers.
Multi year terms are the default, with three to five year terms unlocking the deeper discount bands, and the Flexible Software Portfolio adds swap rights that let the customer trade between bundled products inside the term, the one mechanism that softens the fixed bundle.
The buyer who arrives with the bundle sized to actual use, the baseline corrected, the escalator capped, and alternatives priced negotiates a different renewal than the one who arrives with the quote.
The MSPS bundle, what sits inside
| Category | Typical products | The sizing question |
|---|---|---|
| Systems management | CA SYSVIEW, CA NetMaster, CA OPS/MVS, automation | Which automation is actually wired to operations |
| Storage management | CA Disk, CA Vantage, backup and recovery | What the storage team would keep if it paid the bill |
| Security | CA ACF2, CA Top Secret, compliance tools | The load bearing products, rarely the negotiable ones |
| Database management | CA IDMS, CA Datacom, DB2 tools | Which databases still run, and until when |
| Application development | CA Endevor, CA Easytrieve, developer tools | The high value tooling the rest of the bundle shields |
The bundle shape is fixed at signing, and it only flexes one way. Adding a product mid term carries a price uplift; removing one rarely reduces the price; so every product that enters the bundle unexamined is a term long commitment to software nobody may run.
The buyer side response is sizing at signature, category by category, with the retirement candidates identified before the quote arrives rather than after the term locks them in.
The MSU baseline, corrected before it prices anything
- Map the metric to the LPARs: the MSPS metric follows the IBM MSU measure on the host, so the Broadcom bill inherits every error in the IBM capacity picture.
- Check the sub capacity posture per LPAR: production typically subsets to peak, but test and development LPARs charged at full capacity were the recurring six of ten error.
- Reconcile reported peaks to entitlements before renewal, because an inflated baseline compounds through every percentage the negotiation moves.
- Run the capacity discipline first: defined capacity caps and batch retiming cut the same R4HA peak that drives both vendors' bills, paying twice per point.
The Broadcom enterprise agreements brief
The portfolio model mechanics, the bundle sizing discipline, and the negotiation sequence across the Broadcom estate.
Get the white paper →The renewal levers, in sequence
The renewal works as a sequence, not a discount ask: correct the baseline first, because six of ten were inflated; size the bundle against actual use, where unbundling the protective low value products cut 10 to 22 percent.
Price the term deliberately, since three to five years unlocks the deeper bands but locks the bundle shape for the duration; negotiate the Flexible Software Portfolio swap rights that let products trade inside the term; cap the escalator at three to five percent in writing.
And arrive with alternatives priced, third party support and selective tool retirement, because the wider Broadcom playbook rewards the customer with a credible walkaway.
The IBM side of the same estate, where the identical MSU peak sets the MLC bill, is worked in the mainframe CIO advisory and the MSU reduction guide; the Broadcom negotiation pattern at estate scale in the Broadcom audit defense guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across CA renewals, 2024 to 2025
Across roughly 20 to 30 Broadcom CA mainframe renewals Morten Andersen reviewed between 2024 and 2025, the opening uplift ran far ahead of MSU growth:
The opening quotes, carried against application development MSU consumption that had not grown.
How far the legacy CA pricing bands shrank under Broadcom across renewal cycles.
The portfolio model is working as designed, for its designer: the bundle converts a product by product negotiation into a single number conversation where the low value products hide behind the high value ones, the fixed shape converts sizing errors into term long commitments.
And the narrowed bands mean the discount conversation starts closer to list than CA customers remember.
The counterweights are all structural rather than rhetorical, the corrected baseline, the signature time sizing, the swap rights, the escalator cap, and the priced walkaway, which is why the renewals that went well started months before the quote arrived.
Your first five moves
- Correct the MSU baseline per LPAR, because sub capacity reporting errors inflated six of ten, and every negotiated percentage compounds on it.
- Size the bundle at signature, category by category, identifying the retirement candidates before the quote arrives.
- Unbundle the protective low value products, where 10 to 22 percent came out of our renewals.
- Cap the escalator at three to five percent in writing and negotiate the FSP swap rights into the term.
- Arrive with alternatives priced, third party support and selective retirement, the credible walkaway the playbook rewards. The Broadcom practice runs the renewal with you.
Frequently asked questions
How does Broadcom price CA mainframe software?
Through the MSPS portfolio model: a defined set of CA products, systems management, storage, security, database, and development tools, bundled under a single MSU based metric that maps to the IBM Million Service Units measure on the host LPARs.
Multi year terms of three to five years are the default and unlock the deeper discount bands.
What did Broadcom change about CA mainframe pricing?
The room narrowed: legacy CA discount bands shrank 10 to 25 percent in many renewal cycles, opening renewal uplifts ran 12 to 30 percent against flat MSU consumption in our reviews, and escalators default high with three to five percent caps negotiable only when asked.
The bundle model also fixed the product shape at signing, converting sizing errors into term long commitments.
Can you remove products from an MSPS bundle?
Rarely with any price effect mid term: adding a product carries an uplift, removing one seldom reduces the price, so the bundle only flexes in Broadcom's favor once signed.
The negotiable moment is signature, where the bundle sizes against actual use, and the Flexible Software Portfolio swap rights, letting products trade inside the term, are the one softening mechanism worth negotiating in.
How do you reduce Broadcom CA mainframe costs?
In sequence: correct the MSU baseline, where sub capacity reporting errors inflated six of ten estates; unbundle the low value products shielding the high value tooling, which cut 10 to 22 percent; cap the escalator in writing.
And arrive with third party support and selective retirement priced as a credible walkaway.
Capacity discipline on the R4HA peak pays twice, on the IBM and Broadcom bills alike.
What is in the MSPS bundle?
Five categories of former CA products: systems management with SYSVIEW, NetMaster, and OPS/MVS; storage with CA Disk and Vantage; security with ACF2 and Top Secret; database with IDMS, Datacom, and the DB2 tools; and application development with Endevor and Easytrieve.
The bundle typically shields the development tooling, the products customers cannot leave, with categories they could.
Does the IBM MSU peak affect the Broadcom bill?
Directly: the MSPS metric maps to the same Million Service Units measure on the host LPARs, so the rolling four hour average peak that sets the IBM MLC bill also sizes the Broadcom CA position.
Defined capacity caps and batch retiming therefore reduce both vendors' invoices at once, which puts capacity discipline ahead of either negotiation in the sequence.
