Home / Guides / Negotiating IBM Tailored Fit Pricing Baselines
① Buyer guide · IBM Tailored Fit Pricing
The Tailored Fit Pricing baseline is your previous twelve months of MSU divided by twelve. Whatever your consumption looked like in that window becomes your cost for the agreement. The leverage is in the window, the corridor, and the reset, not the rate.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →IBM introduced Tailored Fit Pricing for IBM Z in 2019 as an alternative to the rolling four hour average that had driven MLC billing since the late 1990s. Under the Software Consumption Solution, formerly the Enterprise Consumption Solution, IBM commonly establishes the annual baseline by taking total MSU consumption over the previous twelve months and dividing by twelve to produce a predictable monthly rate. The model can reward growth and simplify billing. But it has one property buyers underweight: it freezes a snapshot. Whatever pattern existed during the measurement window, peaks, untuned workloads, deferred optimization, becomes the baseline you pay against for the agreement. The negotiation is therefore mostly about what gets measured, when, and how growth is treated afterward.
Where the number actually moves
Directional only, to show why the window dominates. Two measurement windows over the same estate, one including a seasonal peak quarter and one measured on representative months.
| Driver | Window includes peak | Representative window |
|---|---|---|
| Trailing 12 month MSU total | 14,400 | 12,000 |
| Baseline (total ÷ 12) | 1,200 MSU/mo | 1,000 MSU/mo |
| Locked for the agreement | Higher | ~17% lower |
Same machine, same workload, a 17% difference in the rate you pay for years, driven only by which months IBM measured. Optimization done before the window compounds on top. This is why the sequencing, optimize, then measure, then sign, matters more than the headline negotiation.
Across 500+ engagements and $180M+ of negotiated mainframe spend, sequencing optimization ahead of the TFP measurement window and negotiating the corridor and reset terms typically produces renewal reductions of 20 to 35% against the initial proposal, with the gains carried forward rather than reset away.
Under the Software Consumption Solution, IBM commonly establishes the annual baseline by taking your total MSU consumption over the previous twelve months and dividing by twelve to set a predictable monthly rate. The window IBM measures is therefore the single largest lever, because a window that includes seasonal peaks sets a higher baseline for the life of the agreement.
Before, almost always. The baseline captures whatever consumption pattern existed during the measurement window. Sub-capacity discipline, zIIP offload, and workload tuning done before the window is measured lower the baseline permanently; the same work done after only earns credit against an already inflated number.
TFP includes a growth corridor: a band of additional consumption included before higher charges apply, plus terms for how growth above it is priced and how a new baseline is set at renewal. The corridor width and the renewal reset method determine whether growth is absorbed or repriced, so both belong in the negotiation, not just the headline rate.
Not inherently. TFP can simplify billing and reward growth, but the outcome is set by the baseline window, the corridor, and the reset terms, not the model itself. A baseline measured over a peak period can lock in a higher cost than a well managed sub-capacity R4HA position. The model is only as good as the terms you negotiate into it.
Related: IBM license negotiation, IBM cost optimization, and the IBM publisher guide.