① Journal · Vendor negotiation
A Rocket renewal is won on the portfolio map, because the catalog grew by acquisition and the overlap is where the spend hides. Five levers move the number, and most of the work is the inventory you do before the renewal opens. Here is where the leverage really sits.
The Rocket deal is mostly decided by the map you bring to it.
Negotiating with Rocket Software on the mainframe differs from a single product renewal because Rocket has grown by acquisition. The ASG portfolio joined in 2021, and the former OpenText Application Modernization and Connectivity business, which itself carried Micro Focus and Serena heritage, joined in 2024. The result is a wide catalog of legacy tools with real overlap, inherited licensing models, and entitlements that customers often carry without running. The price you pay is driven less by a single meter than by what is on the order and what maintenance stream sits behind it.
That reframes the exercise. The buyers who win a Rocket renewal arrive with an accurate map of what they actually use against what they are billed for, having already found the overlap the acquisitions created. The five levers below run in roughly that order, mapping and scope first, support terms and timing last, because each later lever depends on the map being right. Read this with our Rocket Software publisher hub and our Rocket Servergraph licensing page.
What each lever moves · the portfolio map sets the floor the support terms then shape
| Lever | What it moves | When it pays most |
|---|---|---|
| Portfolio map | What you run versus what you are billed for | Before the renewal, across the acquired catalog |
| Maintenance scope | Which entitlements and environments stay on support | Where redundant or unused products sit on the order |
| Support uplift | The annual increase on the maintenance stream | On steady state products that are not changing |
| Displacement | Whether Rocket keeps mature tools at all | Where third party support or migration is credible |
| Timing and the term | The leverage window and the multi year price hold | At the term boundary, before auto renewal |
Product ownership and licensing models change with each acquisition; verify the current ones on your own order. The order is the durable part: the map lowers the floor, and the support terms price what is left.
Everything else depends on this. Acquisitions stack catalogs, and the overlap between former ASG, Micro Focus, and Serena products is where redundant entitlements hide. Inventory what you actually run against what you are billed for before the renewal, and the unused and duplicated entitlements become the first thing to remove.
Find the overlap the acquisitions created.
Many Rocket mainframe products are perpetual with an annual maintenance stream, so the recurring cost follows what stays under support, not a continuous meter. Drop entitlements and environments you no longer use from the support scope, and confirm the metric on each, because the acquired portfolio mixes several inherited models.
Stop paying support on what you retired.
On steady state products the annual maintenance uplift is the number that moves, and it is rarely tied to any new value you receive. Where a tool is stable and you are not consuming new releases, ask what the uplift buys. Negotiate a cap in the contract rather than accepting a percentage that compounds every year.
An uplift with no new value is just inertia.
On mature tools that are not changing, first party maintenance is mostly insurance, and a credible third party support option or a costed migration changes what that insurance is worth. A real alternative on one product turns the support renewal from an assumption into something Rocket has to justify.
Insurance you can replace has a ceiling.
Leverage exists in a window before the term ends and before auto renewal narrows your options. Start early enough to do the mapping and scope work, and negotiate the multi year price hold as part of the same event. Run out of runway and the renewal happens on Rocket's calendar, not yours.
Start before the clock favors the vendor.
④ The order that wins
Procurement argues the discount. The inventory decides what is even on the order. Map the estate first, then negotiate what is left.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
The portfolio map. Rocket grew by acquisition, so the catalog carries overlap and inherited entitlements. Mapping what you run against what you are billed for, before the renewal, surfaces the redundant and unused products that are the first thing to remove.
Many mainframe products are perpetual with an annual maintenance stream, and some are scoped by capacity or environment rather than metered like IBM monthly license charge products. The acquired portfolio mixes models, so confirm the metric and scope on your own order before you negotiate.
On steady state products it can be. Where a tool is stable and you are not consuming new releases, first party maintenance is mostly insurance. A credible alternative or a costed migration on one product makes the support uplift something Rocket has to justify rather than assume.
Early enough to complete the mapping and scope work before the term boundary, usually months ahead. The inventory takes time across an acquired catalog, and the commercial levers are worth more once it is done. See our renewal advisory service and third party support options.
Related: Rocket Software publisher hub · Rocket Servergraph licensing · third party support options · negotiating with IBM
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →