Cut the metric base before Broadcom quotes the increase
Automic Workload Automation sits at the heart of enterprise batch and scheduling estates, and it is metered on agents and execution volume rather than named users, so the base grows quietly wherever automation spreads. Since the CA acquisition, renewals arrive with sharp opening increases and portfolio led conversations. Both are containable, but only with usage evidence assembled before the quote lands, because a clean inventory is the one argument that moves a number Broadcom presents as fixed.
Prepared by Redress Compliance · August 10, 2026 · Broadcom advisory. Based on 15 to 25 Broadcom and Automic reviews, 2024 to 2025.
Executive summary
The metric scales with agents and execution, so the base inflates without anyone deciding to buy more.
Automic is counted on deployed agents, execution volume across environments, and the breadth of connected systems, which means the number you renew against grows every time a team automates something new.
The binding definition sits in your order form rather than in any product description, so the first task is confirming whether you are counted on agents, on executions, or on a blended metric. Consolidation is the most direct cost lever precisely because the metric rewards it.
Idle and duplicate agents inflated the base by 15 to 30 percent before any price conversation. Estates carry agents on retired hosts, duplicate agents across test environments, environments that carry cost with no remaining value, and connectors nobody uses.
In our reviews, reconciling the agent inventory against active workloads cut the metric base by 15 to 30 percent, and every point of that came off the quantity Broadcom prices against rather than off a discount it has to agree to. Decommission before the renewal opens, not during it.
Opening renewal increases of 20 to 40 percent were common, and they were negotiable downward. Renewal posture hardened after Broadcom acquired CA Technologies, and the pattern repeats across the portfolio: steeper openings, more bundling, and a firmer stance on support and metrics.
The increases are not fixed. What moves them is usage evidence and a credible plan, presented before the number is anchored. Model the next two renewal cycles rather than this one alone, because a concession that expires at the following anniversary is a deferral rather than a saving.
Portfolio bundling helps only when you genuinely need the other products. Broadcom frames Automic inside a wider portfolio deal, which can lower the unit rate while raising total multi year spend.
In most Automic renewals we ran, bundles that included products the buyer did not need raised the total while presenting as a rate cut.
Judge each bundle on net multi year cost and independent need, and negotiate support and maintenance alongside the license, because a license concession is routinely recovered through a support uplift or a quiet reduction in service level.
Where the metric base leaks
| Source | Effect | Buyer move |
|---|---|---|
| Agents on retired hosts | Counted but unused | Decommission before the renewal opens |
| Duplicate test agents | Inflate the base | Consolidate to shared runners |
| Idle environments | Carry cost with no value | Retire or merge environments |
| Unused connectors | Broaden the counted scope | Remove connectors not in use |
The unit in your order form is what matters, not the marketing description of the product.
Automic cost scales with three things: the number of deployed agents, the execution volume across environments, and the breadth of connected systems, so confirm which of them your paper actually counts before anyone builds a reduction plan around the wrong number.
Because the metric grows as automation spreads, the base is almost always larger than the workload justifies by the time a renewal arrives, and fewer agents and environments mean a smaller number to renew against.
The wider Broadcom posture sits in the Broadcom pricing analysis, and the VMware side of the same portfolio in the VMware licensing guide.
The renewal, the bundle, and the support line
- Is the opening increase presented as fixed? It rarely is. Increases of 20 to 40 percent were common after the acquisition and moved with usage evidence and a credible consolidation plan, provided both arrived before the number was anchored.
- Do you need the other products in the bundle on their own merits? A discount on software you would not otherwise buy is not a saving, it is scope you maintain for years.
- What is the net multi year cost of the bundle, not the headline rate? The trap is a better Automic rate bought with unneeded products, which raises total spend while presenting as a cut.
- What flexibility survives if needs change? Bundled scope is harder to unwind than it is to accept, and the exit terms are written at signature or not at all.
- Negotiate support and maintenance in the same conversation. Watch the annual maintenance uplift, any change in service level at renewal, and multi year caps on support increases, because a license concession is routinely recovered through support. The enterprise agreement mechanics sit in the Broadcom practice.
The Broadcom enterprise agreements brief
The post acquisition renewal posture, the portfolio bundling arithmetic, the support uplift traps, and the buyer side moves that hold across the Broadcom catalog.
Get the white paper →Building the evidence before the quote lands
The work that changes the number is inventory work, and it has to be finished before the renewal conversation opens rather than assembled while it runs.
Start by reconciling the agent inventory against active workloads: which agents ran a job in the last quarter, which sit on hosts that were decommissioned two projects ago, and which are duplicates carried into test environments that no longer need their own runner.
Then look at the environments themselves, because an idle environment carries the cost of every agent inside it while delivering nothing, and merging or retiring one removes a block of the base rather than a line of it.
Connectors deserve the same pass, since unused ones broaden the counted scope without broadening the value.
None of this is a negotiation, which is exactly why it works: it removes quantity from the thing Broadcom prices rather than asking for a concession Broadcom has to grant, and it arrives as evidence rather than as an argument.
Model the result across two renewal cycles, because a rate held for one year against an inflated base is worse than a modest rate against a base you have already cut. The portfolio wide view sits in the VCF pillar and the Broadcom practice library.
- 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 Broadcom Automic engagements, 2024 to 2025
Across roughly 15 to 25 Broadcom and Automic reviews we led between 2024 and 2025, post acquisition renewals arrived with steep opening increases and a portfolio conversation attached. The common advice is to accept a portfolio bundle because the blended discount looks strong.
We disagree, because in most of these renewals the bundle raised total multi year spend while disguising it as a rate cut:
The common post acquisition renewal opening, negotiable downward when usage evidence and a consolidation plan arrive before the number is anchored.
How far a clean agent reconciliation cut the metric base before any price discussion, by removing quantity rather than asking for discount.
Three patterns recurred: opening increases of 20 to 40 percent that were common and often negotiable, idle or duplicated agents inflating the metric base by 15 to 30 percent, and portfolio bundling offers that swung both ways and helped only when the other products were genuinely needed.
The buyer side move is sequential rather than clever. Cut the metric base first by retiring idle agents, duplicate test agents, dead environments, and unused connectors. Then judge any bundle purely on net multi year cost and independent need.
Then negotiate support and maintenance alongside the license so a concession cannot be recovered through an uplift. A better rate on software you would never have bought is not a discount, it is scope you pay to maintain for years.
Your first five moves
- Confirm the exact Automic metric in your order form, agents, executions, or a blend, because the binding definition is there rather than in any product description.
- Reconcile the agent inventory against active workloads, then retire idle agents, duplicate test agents, dead environments, and unused connectors, which cut the base 15 to 30 percent in our file.
- Model the next two renewal cycles, not just this one, so a concession that expires at the following anniversary is recognised as a deferral rather than a saving.
- Judge any portfolio bundle on net multi year cost and independent need, because the trap is a better Automic rate bought with products you would not otherwise have purchased.
- Negotiate support and maintenance alongside the license, covering the annual uplift, service level changes at renewal, and multi year caps, since a license concession is routinely recovered through support. The Broadcom practice runs the inventory and the renewal with you.
Frequently asked questions
How is Broadcom Automic Automation licensed?
Automic licensing centres on execution volume and agent based metrics rather than named users, so cost scales with the number of deployed agents, the execution volume across environments, and the breadth of connected systems.
The binding metric sits in your order form rather than in the product description, so confirm whether you are counted on agents, on executions, or on a blended metric before planning any reduction.
Why does the Automic metric base grow on its own?
Because the metric scales with agents and execution, the base expands every time a team automates something new, without anyone deciding to buy more.
That is why consolidation is the most direct cost lever: fewer agents and fewer environments mean a smaller number to renew against, and the reduction comes off quantity rather than out of a discount Broadcom has to agree to.
How much can a clean agent inventory save?
In our reviews, removing idle and duplicate agents cut the metric base by 15 to 30 percent before any price discussion began.
The leaks are consistent: agents left on retired hosts, duplicate agents across test environments, idle environments carrying cost with no value, and connectors that broaden the counted scope without adding use. Decommission before the renewal opens, not during it.
Are Broadcom renewal increases negotiable?
Yes. Opening increases of 20 to 40 percent were common after the CA acquisition and were often negotiable downward, but what moves them is usage evidence and a credible consolidation plan presented before the number is anchored.
An increase that looks firm in the first meeting is being tested against whether you can describe your own estate.
What changed after Broadcom acquired CA Technologies?
Renewal posture hardened. The practical effects for buyers are steeper opening increases, more bundling across the wider Broadcom portfolio, and a firmer stance on support terms and metric interpretation.
The pattern rhymes with the mainframe and VMware playbooks, so a buyer who has been through one of those already knows the shape of the Automic conversation.
Does portfolio bundling help on an Automic renewal?
Only when you genuinely need the other products. Bundling can lower the Automic unit rate while raising total multi year spend, and in most of the renewals we ran, bundles containing unneeded products did exactly that.
Test every bundle on three questions: do we need the other products on their own merits, what is the net multi year cost rather than the headline rate, and what flexibility survives if needs change.
Why negotiate Automic support terms alongside the license?
Because a license concession is routinely recovered through support. Watch the annual maintenance uplift, any reduction in service level that accompanies a price rise, and whether multi year caps on support increases are available.
A lower license rate paired with a higher support uplift can be no saving at all once the term is modelled end to end.
The Quote That Arrives Late
Part 4 of the Negotiating Broadcom series. Documented case by case in court papers rather than in any policy, and effective for reasons that need no intent at all. The three mechanics behind a late quote, and why the counter is a calendar rather than a complaint.
