Broadcom's Post-Acquisition Licensing Behaviour
💥 Aggressive Enforcement & Price Increases
After absorbing CA, Broadcom adopted a markedly more aggressive stance on licensing and renewals. Multiple large customers have reported steep price hike demands — sometimes increases of several hundred percent. UnitedHealthcare alleges Broadcom demanded "hundreds of millions of dollars" more for the same CA software. Broadcom has shown willingness to enforce contract deadlines strictly, even threatening to cut off access to mission-critical software if new terms aren't accepted. This hardball approach is far from CA's earlier relationship-driven style.
📈 Pricing Standardisation & "Cash Cow" Strategy
Broadcom standardised pricing and eliminated deep legacy discounts that CA may have granted. Organisations enjoying custom deals have seen Broadcom align them to a higher baseline price. Standard contract terms often include predetermined annual uplift clauses (e.g. up to 7% yearly increase). Broadcom prioritises roughly 600 top-tier accounts and is content to let smaller customers go. Mid-sized enterprises may receive "take it or leave it" offers with little flexibility. The result is pricing standardisation at higher levels across the CA portfolio.
📦 Product Bundling & Reduced Support
Broadcom seeks to bundle renewals of CA software with other Broadcom offerings — even ones customers neither want nor use. Some customers have been required to upgrade to broader (more expensive) suites or include additional tools as part of renewal rather than allowing à la carte renewals. This tactic raises costs and can lead to paying for shelfware. Simultaneously, Broadcom drastically cut CA's sales and support staffing, reducing personal account management. Customer service quality declined with fewer reps and less negotiation leeway.
Negotiating Enterprise-Wide Multi-Year Agreements
Given Broadcom's pricing tactics, negotiating a multi-year, enterprise-wide licence agreement (ELA) is one of the most effective strategies to secure pricing stability and discounts. Rather than allowing each CA product to renew separately — with each exposed to potential hikes — CIOs should pursue a consolidated deal covering the entire CA/Broadcom mainframe portfolio for 3 to 5 years.
🤝 Benefits of Alignment and Bundling
Co-term all CA product licences to a single renewal date. This prevents Broadcom from picking off renewals one by one. A single expiration concentrates your leverage — Broadcom knows you could switch multiple products at once if unsatisfied. Enterprise-wide commitments let you leverage "bundled" discount structures legitimately in your favour. For example, bundling CA 7, ACF2, and IDMS into a single deal may achieve an overall percentage discount impossible if each were negotiated separately.
🚫 Avoiding Staggered Renewals
Co-Term Agreements: If current licences don't align in time, request a co-termed renewal — extending some licences slightly or entering short bridge contracts so all expire together. Renew Early If Needed: If a critical product's contract is due sooner, consider renewing or extending it early to align with a larger deal. Lock in Renewal Caps: Insist on caps for renewal rate increases (e.g. no more than 3% per year) — lower than Broadcom's standard 7% cap. This hedges against future pricing behaviour beyond the initial term.
⚖️ Enterprise Commitment Trade-Offs
Weigh immediate cost savings (bigger discounts, avoided hikes) against flexibility you give up. Ensure the agreement includes provisions for adding new licences at the same discounted rates. Where possible, include a "transferable spend" clause — if you stop using one product, you can apply its value to another Broadcom product. Consolidation is leverage. A multi-year enterprise-wide contract leverages your full footprint to negotiate from a position of strength.
Contract Due Diligence and Legacy Terms Verification
Before entering any negotiations or renewals, CIOs must carefully audit all existing CA contracts, amendments, and order forms. The goal is to identify any legacy terms that can protect you or that Broadcom must honour.
Collect Documents
Gather all CA contracts, addenda, product schedules, proofs of entitlement, invoices, and any communications about the assignment. Include renewal rights and caps, discount levels, entitlements and bundled rights.
Extract Key Terms
For each product or licence, note: term end date, licence type (perpetual vs subscription), metric (MIPS, MSUs, CPU), price, discount percentage, renewal options, and any special provisions (caps, bundling, transfer rights).
Verify Assignment
Locate the assignment notice from Broadcom (from 2018–2019). If missing, request official written confirmation that your contract is now assumed by Broadcom under the same terms. Review the assignment clause to ensure no terms were violated in the process.
SAM & Legal Review
Involve your SAM team and legal counsel to verify usage against entitlements and interpret ambiguous clauses. Have legal compare Broadcom's standard "Foundation Agreement" or new EULA side-by-side with your CA agreement — note any differences (e.g. Broadcom's standard EULA allows up to 7% annual increase which may be less favourable).
Engage Broadcom Early
Well before renewal, send Broadcom a summary of your understanding of the contract terms that should govern renewal. Get their written acknowledgement (or disagreement) before the last minute. This sets a factual basis and can resolve conflicts proactively.
📚 Related Reading
Software Asset Management Best Practices for CA/Broadcom Software
A robust SAM programme is indispensable when dealing with evolving licensing under Broadcom. Changes like product bundling or new metrics can lead to confusion and unintended cost unless you have a precise handle on usage.
📋 Conduct a Fresh Inventory
Perform a comprehensive inventory of all CA/Broadcom software deployed across your mainframe environment, including distributed systems. Identify every instance, version, and usage metric (MIPS consumption, user counts) for products such as CA 7, ACF2, Top Secret, Datacom, IDMS, Endevor, SYSVIEW, etc. Leverage automated discovery tools or Broadcom's asset management agents.
🗺️ Map Usage to Entitlements
For each inventoried product, map it to purchased licences and capacity. Flag any over-deployment or under-deployment. For example, if you own CA ACF2 for 5 LPARs but it's installed on 6, you have a compliance gap. Conversely, you might be licensed for more capacity than you use — indicating potential to reduce at renewal.
🔍 Identify Overlap and Redundancy
Mainframe environments often have overlapping tools. Identify if you have multiple tools serving the same function — e.g. CA Endevor alongside Git-based pipelines, or CA SYSVIEW alongside IBM OMEGAMON. Catalogue overlaps and assess if all are truly needed. Broadcom's bundling may have introduced functionality you already get elsewhere. Recognise those overlaps to avoid paying twice.
📦 Spot "Shelfware"
Identify CA/Broadcom software that is installed but not actively used, or licences purchased that remain unused. Common culprits: development tools, optional modules, legacy products licensed "just in case." Quantify their maintenance costs and prepare to reclaim value by discontinuing at renewal or leveraging their cost in negotiations.
📊 Monitor Usage Trends
Track usage trends over time, especially for capacity-based licences. Broadcom's pricing can depend on peak MSU consumption. Use tooling (CA MICS Resource Management, IBM's SCRT reports) to see if usage is rising, stable, or declining. Document planned reductions to negotiate lower usage-based fees. If growth is expected, aim to obtain additional capacity licences at the old pricing.
♻️ Optimise and Re-Harvest
Engage technical teams to optimise use. Workload capping or tuning could lower peak usage and save costs under sub-capacity pricing. Remove dormant users. Free up licences by cleaning up, then reduce counts at renewal or repurpose elsewhere. Explore Broadcom's Mainframe Consumption Licensing (MCL) model if your usage is highly variable — SAM data will tell you if pay-per-use is more cost-effective than fixed-capacity.
🛡️ Prepare for Audits
Broadcom reserves the right to audit (e.g. with 30 days' notice). Simulate an internal audit: ensure proof of licences is in order and deployment matches entitlements. Proactively fixing issues deprives Broadcom of a chance to levy back charges or force an upsell at high rates. A strong SAM practice means you won't be caught off guard.
Competitive Landscape — IBM and BMC Alternatives to CA Tools
Broadcom's hardball tactics make it imperative to evaluate alternative vendors for each major software domain. IBM (the mainframe OEM) and BMC are the primary competitors, each offering products that can replace or complement CA solutions.
🖥️ Performance & Monitoring Tools
🔐 Security & Compliance
🗄️ Database Management Tools
⚙️ Workload Automation (Job Scheduling)
Leveraging Alternatives to Improve Negotiating Leverage
One of the strongest cards a CIO can play in Broadcom negotiations is a credible threat to move to an alternative solution. Broadcom's strategy relies on customer reluctance to change. Demonstrating that your organisation has evaluated and is willing to switch undermines that assumption.
📊 Perform Benchmarking / RFPs
Proactively engage in a benchmarking exercise or formal RFP for mainframe software domains under Broadcom. Solicit proposals from BMC on migrating CA 7 to Control-M, or ask IBM for a proposal to replace CA security with RACF. Even without a full RFP, getting written estimates or trial licences gives you hard numbers to compare. If BMC says they can replace your CA suite at 30% lower cost over 5 years, that's powerful data for Broadcom negotiations.
📝 Build an "Exit Plan"
Develop an internal exit strategy for each major Broadcom product — how long it takes, resources needed, steps to migrate. For example: "Migrate from CA Top Secret to RACF over 24 months, using vendor X's toolkit, with Y internal FTEs and Z consulting cost, target Q4 2026." The more concrete the plan, the more Broadcom must consider the real risk of losing your business. Involve stakeholders (operations, security, application owners) to ensure feasibility.
🔄 Leverage Partial Moves (Dual Vendor)
Start using a competitor in some capacity to show you're not wholly dependent. For example, use BMC's Control-M for new cloud workloads or implement IBM OMEGAMON alongside CA SYSVIEW. If Broadcom knows you already use a competitor, extending it to replace Broadcom entirely is not far-fetched. Running parallel tools is a temporary cost duplication but can be a tactical investment for immediate bargaining power or future cut-over.
⏰ Use Timing to Your Advantage
Line up engagement with alternatives well before your Broadcom renewal. If Broadcom senses last-minute scrambling, they may call your bluff. But if six months out you're already testing a BMC tool, that seriousness is hard to ignore. Get alternative quotes valid through your decision point around renewal time. Having a firm offer from BMC or IBM that coincides with Broadcom's renewal deadline means you can immediately execute the alternative if terms aren't agreeable.
📢 Know Broadcom's Pressure Points
Broadcom doesn't want negative press or lost deals in key product lines. High-profile departures encourage others to leave. Subtly communicate that you are deeply reviewing alternatives and that executive leadership is concerned about Broadcom's direction. If talks stall, mention: "Our CIO has instructed us to evaluate other vendors — we have a board presentation on alternatives next month." This often gets Broadcom's attention to revisit the deal structure.
Transition and Coexistence Planning with Competitor Tools
If the decision is made to migrate away from a Broadcom (CA) solution, CIOs must ensure a smooth transition that minimises business risk. Mainframe systems are the backbone of critical processes — any tool replacement must be handled with care.
📋 Phased Migration vs "Big Bang"
Opt for phased transitions wherever possible. For workload automation, migrate one application or batch subsystem at a time. Run the new scheduler in parallel to validate jobs execute correctly. Gradually increase the percentage handled by the new tool. For security, running ACF2/RACF in parallel modes during cutover testing. Phased migrations allow learning and adjusting, significantly reducing outage risk.
🔄 Data and Configuration Migration
Security: Export user profiles, access rules, dataset rules and import into RACF equivalents. Extensive verification needed. Scheduler: Convert CA 7 job schedules, calendars, and dependencies — BMC provides conversion utilities. Maintain a mapping document of features that don't translate one-to-one. Database: IDMS/Datacom to Db2 requires unloading data, transforming schemas, rewriting application calls — this is part of larger application modernisation. DevOps: Migrate source code repositories and build configurations, providing dual access during transition.
👥 Training and Change Management
Operations staff and developers may have used CA tools for decades. Include a comprehensive training plan. Engage vendor professional services or consultants for workshops. Use a champion user approach: identify tech-savvy team members to become experts early through pilot projects, then mentor others. Update runbooks, operating procedures, and documentation to reflect the new environment.
🔗 Coexistence Strategy
During the transition period, define how old and new tools coexist without conflict. Deconflict actions if both tools might act on the same target. Watch resource overhead — running parallel tools can increase CPU or memory usage. Have a backup plan: if the new tool encounters a severe issue, be able to temporarily fall back to the old tool. This might mean keeping data in sync until cutover is declared final.
🧪 Testing, Validation, and Go-Live
Rigorously test at multiple stages: unit test each converted rule or job, system test end-to-end processes, run parallel schedules and compare outputs, verify security access results under both systems, benchmark database performance and correctness. Treat cutover like a major go-live event — additional staff, war-room monitoring, extra logging and alerts. Run a parallel run in production for a short period before fully handing control to the new system.
CIO Recommendations and Planning for 2025–2027
Pursue Licence Consolidation and Optimisation
Negotiate a single umbrella agreement for Broadcom software to leverage volume and co-term dates. Use SAM findings to adjust licence counts — negotiate reductions at renewal for underutilised capacity. Eliminate duplicate tools (CA vs others) — decide on a standard and remove duplicates. Paying two vendors for the same functionality is a luxury most budgets can't afford. Consolidation saves costs and strengthens your negotiating position.
Time Procurement for Maximum Advantage
Engage early: Start renewal discussions at least 12 months before contract expiration. Leverage Broadcom's fiscal calendar: Align negotiations so Broadcom has motivation to close by quarter- or year-end. Avoid last-minute negotiations: Never let licences expire while still haggling — have a contingency extension clause. Plan for future capacity: Lock in unit prices for projected growth through 2027, including flex-down options if planning reductions.
Budget Forecasting and Financial Planning
Anticipate price inflation: Budget at least 5–7% annual increase under multi-year maintenance, or budget for a potential step-change increase if contracts are expiring. Incorporate hardware changes: If upgrading to IBM z16, note that increased capacity will increase capacity-based licence costs. Scenario plan: Create both "Stay with Broadcom" and "Migrate to competitor" budget scenarios showing total costs over 3–5 years. Allocate contingency: Hold ~10% of Broadcom spend as contingency for unplanned licence needs or audit findings.
Strengthen Vendor Management and Communication
Establish regular executive touchpoints with Broadcom leadership to discuss roadmap, support issues, and your importance as a customer. Document all commitments in the contract or MOU — personal assurances vaporise if account reps change. Coordinate with peer companies through user groups to share strategies. Keep your CEO or CFO informed — mainframe software has gained board visibility due to significant cost increases. Executive backing empowers IT leadership for tough stances.
Consider Long-Term Mainframe Strategy
If mainframe remains strategic: Invest in stable vendor relations — you may tolerate higher costs for guaranteed support and innovation. Ensure Broadcom's product roadmap aligns with your needs. If planning to downsize: Be more aggressive with Broadcom — don't get locked into long contracts beyond what you need. Negotiate shorter-term extensions or flexible arrangements. For applications slated to migrate off mainframe by 2027, consider not renewing long-term Broadcom licences. Cross-portfolio: Broadcom also owns Symantec and VMware — set internal policy that each domain will be evaluated on its merits. Don't accept bundling across portfolios that doesn't fit your needs.
By following this playbook, CIOs can turn Broadcom's acquisition of CA from a potential cost crisis into a manageable vendor relationship. The key is proactivity — in understanding Broadcom's approach, consolidating and protecting your contracts, maintaining clear awareness of your software assets, and keeping competitive options in play. A savvy CIO armed with the right strategy can ensure their company continues to run critical mainframe systems cost-effectively well into 2025–2027 and beyond.
Managing Broadcom (CA) Mainframe Licensing?
Whether you're facing steep renewal demands, need help auditing legacy CA contracts for protective terms, want to benchmark alternatives from IBM and BMC, or need an independent adviser to support multi-year ELA negotiations — our Broadcom licensing specialists provide vendor-neutral expertise to protect your budget and maintain leverage. Engage early for the best outcomes.