① BMC · Renewal advisory
BMC renewals typically arrive as multiyear suite proposals priced on capacity baselines the buyer has never independently verified. We verify them, unbundle them, and negotiate them, starting well before the date controls the conversation.
The proposal is one number. The estate behind it is fifty.
The BMC mainframe estate spans the AMI families, MainView monitoring, data management for Db2 and IMS, AMI Security, the AMI DevX line built from Compuware (BMC), and Control-M for z/OS. Renewals commonly bundle these into suite agreements priced against MSU or MIPS capacity, with multiyear terms and built in escalators.
The patterns we commonly see at renewal time: capacity growth since signature flowing straight into the new baseline, suite composition carried over untouched regardless of what is actually used, escalators compounding quietly across the term, and proposals timed so that serious analysis is no longer possible before expiry. None of it is unusual. All of it is negotiable, if the work starts early enough.
BMC's market position cuts both ways for buyers. As the challenger against IBM and Broadcom (CA) tooling, BMC commonly prices aggressively to win displacement business. As the incumbent at your renewal, the same commercial machine works the other direction. The renewal outcome depends on which dynamic you can put back in the room.
Every BMC product, contract, and amendment on one page: entitlements, capacity tiers, bundle composition, escalators, and expiry. Including the Compuware (BMC) paper, which commonly lives on separate vehicles with different terms.
Per product usage evidence across the suite: what carries production workflow, what is occasionally touched, what has not been launched in years. This is the data that unbundles bundles.
The MSU or MIPS figure the proposal prices against, validated independently against SCRT data and consumption history. Proposals commonly price the peak; buyers should know exactly which peak, and whether it is the right one under the contract.
Credible alternatives evaluated where they exist: IBM tooling, Broadcom (CA) equivalents, open source where realistic, and the modeled cost of each path. A walk away the vendor believes is worth more than any discount request, even if you never use it.
Bundle composition corrected, baseline right sized, escalators capped, consumption protections and exit rights written in. The close protects years two through five, not just the signature price.
Typical renewal reduction across 500+ engagements: 20 to 35 percent.
With $180M+ in mainframe spend negotiated, we know where BMC agreements typically have room: bundle composition, baseline definition, escalator structure, and the competitive dynamic the incumbent would prefer stays dormant. Account teams negotiate differently when the buyer side arrives with usage evidence, reconciled baselines, and a modeled alternative.
For preparation on your own timetable, start with the BMC renewal buyer checklist and negotiating BMC AMI suite bundles. If Control-M dominates the spend, see Control-M renewal levers. Product detail lives on the MainView licensing page and its siblings. If a compliance review is also in motion, BMC audit defense covers that track.
Twelve to eighteen months out. Usage measurement, unbundling analysis, and alternative evaluation take quarters, and leverage that arrives in the final ninety days rarely moves the number much.
The capacity baseline, the bundle breadth, and the escalators. Capacity growth since signature commonly flows straight into the proposal, and bundles commonly carry products with little measured use.
Renewal is when bundle composition is negotiable. With per product usage evidence, underused components can be removed, downgraded, or traded. Without it, the bundle typically renews whole.
At net new, yes; at renewal, the incumbent dynamic takes over. The buyer lever is making competition real again with credible, modeled alternatives.
Our typical renewal reduction is 20 to 35 percent, alongside capped escalators, consumption protections, and bundle composition that matches what you run.