① Guides · IBM zSeries renewal
An IBM Z software renewal is won or lost in the eighteen months before the signature, not in the final meeting. This is the buyer side strategy: the timeline, the leverage you have to build, and the levers that actually move the number across MLC, IPLA and Tailored Fit Pricing.
Leverage is built, not asked for.
IBM is highly motivated to lock major mainframe customers into long term agreements, and that motivation is the buyer's opportunity, but only if you arrive with data and options rather than a request for a discount. Leverage in a zSeries renewal comes from two things: a defensible, independently validated picture of what you consume, and a credible alternative that IBM believes you can act on. When IBM thinks you might reduce mainframe spend or move it, caps, credits and rate concessions appear. When it does not, the renewal is whatever the account team proposed.
Both of those take months to build. Profiling the R4HA peak, validating twelve months of SCRT, modeling a Tailored Fit Pricing baseline, and pricing any alternative are not things you do in the final quarter. That is why the strategy is a timeline, and why the timeline starts at eighteen months.
Profile the R4HA peak per LPAR and product, validate SCRT independently, and execute the operational levers first: peak shaving, zIIP offload, and defined capacity. You negotiate the optimized number, not the historical one. Optimize after you sign and the savings stay with IBM until the next cycle.
Classic MLC, IPLA with subscription and support, and the consumption and capacity solutions under Tailored Fit Pricing each produce a different number on the same estate. Model them against your optimized profile so you know which structure serves you, and so a TFP baseline is something you propose rather than something IBM derives unchallenged from your trailing history.
The walk away has to be real before it has value: third party support evaluated, workload rebalancing priced, or a partial offload scoped seriously enough to defend. You may never execute it. But IBM prices very differently against a customer who has a documented option than against one who has none.
If a broader IBM enterprise agreement is in play, write the mainframe specifics out explicitly: MLC rate schedules and growth assumptions, IPLA support rates, dev and test capacity pricing, and TFP baseline and ramp terms. Specialized mainframe terms absorbed into a broad ELA are terms you cannot defend later. Insist on a true down clause; reductions when usage drops are not standard and have to be demanded.
Lock the structure with uplift caps, a defensible baseline, dev and test carved out where it qualifies, and exit and true down rights written in. The signature should capture every gain from the previous fifteen months. A renewal closed under deadline pressure with none of the prep behind it is the outcome this entire timeline exists to avoid.
The levers that move the number.
Across 500+ engagements and $180M+ of negotiated mainframe spend, the same levers recur on IBM Z renewals. None of them is a trick. Each is the product of work done early.
Where the money moves
Eighteen months out for a major renewal. The optimization that creates your leverage, profiling the peak, validating SCRT, modeling a TFP baseline, takes months, and any credible alternative needs time to become real. A renewal that starts six months out is a renewal IBM sets.
Usually carve them out or negotiate them explicitly. MLC caps, SCRT billing, sub-capacity rules and TFP baselines are specialized and tend to get lost inside a broad enterprise agreement. A bundle can deliver real concessions, but only if the mainframe specific terms are written out rather than absorbed.
No. TFP changes the mechanics, but the baseline IBM derives from your trailing SCRT history is negotiable, and accepting one set on an unoptimized estate locks the waste in for the life of the agreement. The negotiation moves to the baseline and the growth ramp; it does not disappear.
An independently validated consumption position plus a credible alternative. When IBM believes you can and might reduce or shift mainframe spend, caps, credits and rate concessions appear. When it believes you cannot move, they do not. Everything else is detail around those two facts.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →