① Journal · IBM
IBM took roughly 6 percent on most software for 2026 and up to about 7 percent in 2025, and that annual adjustment is only one of the patterns that move the bill. Here are five recurring IBM (International Business Machines) price patterns on the mainframe, and the buyer counter to each.
The annual percentage is the visible increase. The peak, the hardware cycle, and the model transition are the larger ones.
IBM applies a global price adjustment to much of its software portfolio every year. For 2026 most offerings rose by roughly 6 percent effective in January, and the 2025 adjustment reached up to about 7 percent, with software around 6 percent globally. On MLC products such as z/OS, CICS, Db2 for z/OS, and IMS those increases compound year over year, so the annual figure that looks modest in any single renewal becomes a significant slope across a multi year term. That said, the annual list adjustment is the increase buyers see most clearly and fixate on, while the patterns that move the bill more sit elsewhere.
The larger movers are the measured peak and the hardware cycle. The rolling four hour average peak drives MLC charges, and a move onto a new generation machine such as the z17, generally available since June 2025, invites workload growth and higher peaks that reset the baseline the renewal builds on. A transition toward Tailored Fit Pricing, IBM's consumption model, can move the bill more than any list change because it commits you to a baseline and a floor. Countering IBM is therefore not about refusing the annual percentage; it is about controlling the peak, the cycle, and the model. Read this with our explainer on Tailored Fit Pricing and the IBM publisher hub.
What we commonly observe · the pattern and the buyer counter
| Price pattern | What it looks like | Buyer counter |
|---|---|---|
| Annual global adjustment | Roughly 6% for 2026, up to ~7% in 2025, applied broadly | Cap the uplift and fix the list reference in the term |
| Hardware cycle repricing | A z17 move invites higher peaks and a reset baseline | Reduce the peak before the baseline is set |
| Tailored Fit Pricing transition | Consumption model commits you to a baseline and floor | Model TFP on real consumption, negotiate the floor |
| MLC and IPLA bundling | Monthly and one time charges presented as one program | Unbundle the vehicles and value each separately |
| Discount reset via list alignment | A list increase quietly erodes your effective rate | Protect the effective rate, not just the headline list |
Increase figures are publicly reported list adjustments, not a fixed contractual rate for any customer, and may change. Patterns are what we commonly observe, not statements of IBM policy. Your entitlement, pricing model, and SCRT data govern the real number.
A one time discount fades; a cap on the annual uplift governs every year of the term. Fix the maximum annual increase, pin the list reference so a list move cannot reset your effective rate, and the compounding slope flattens. The annual adjustment is predictable, so the protection should be structural rather than renegotiated each cycle.
Govern every year, not just this invoice.
The rolling four hour peak drives the MLC bill and becomes the baseline a hardware move or a consumption deal builds on. Soft capping, workload timing, and sub-capacity discipline cut the measured peak. Done before the z17 move or the renewal, the lower profile flows into the contract; done after, it is given away as headroom.
Cut the peak first, then take the upgrade.
Tailored Fit Pricing can be the right call for a growing estate, but only on a baseline built from independently validated consumption. A floor set above your true run rate locks in overspend for the life of the deal. Model the transition on your SCRT and R4HA data, compare it to staying on MLC, and choose on the math.
Take consumption pricing on your data, not their forecast.
④ Where the IBM number is countered
The annual percentage is the increase you see. The peak, the cycle, the model are the ones that count. Cap the mechanism, lower the peak, model the transition.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
IBM applies an annual global adjustment. For 2026 most offerings rose roughly 6 percent in January, and 2025 reached up to about 7 percent, software around 6 percent globally. These are list adjustments, not a fixed rate for any customer, and they compound on MLC products like z/OS, CICS, Db2 for z/OS, and IMS. See MIPS and MSU explained.
How it lands on your account is shaped by your contract. The lever is capping the uplift, fixing the list reference, and protecting your effective rate so a list move does not reset your discount. A multi year term with a hard cap governs every year, which is worth more than a one time discount. See negotiating caps and inflation clauses.
The measured peak and the hardware cycle. The rolling four hour peak drives MLC charges, and a z17 move invites higher peaks that reset the baseline. A Tailored Fit Pricing transition can move the bill more than any list change. See what the z17 cycle means for software costs.
Cap the annual mechanism, reduce the peak before the cycle or the renewal, and model any consumption transition on validated data. Our license negotiation service sets the caps and our cost optimization lowers the peak the deal is built on. See also our five IBM negotiation levers.
Related: IBM publisher hub · Tailored Fit Pricing · the z17 cycle and software costs · five IBM negotiation levers · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →