① Journal · IBM
Tailored Fit Pricing trades the rolling four hour average game for a committed MSU baseline. The pitch is predictability. The reality buyers report is more mixed: real relief from sub-capacity engineering, paid for with a multi year commitment that is only as good as the baseline you negotiate.
Tailored Fit Pricing (TFP) is not a discount. It is a different bet, and whether it pays depends almost entirely on the baseline you sign.
IBM positions Tailored Fit Pricing for IBM Z as a cloud like alternative to traditional sub-capacity charging. Under the consumption model, now named the Software Consumption Solution and previously the Enterprise Consumption Solution, compute is measured per MSU consumed across the year rather than against the monthly rolling four hour average peak. That removes the engineering treadmill of soft capping to shave a single high interval. For buyers who have spent years tuning defined capacity to dodge the R4HA penalty, that relief is real and the operational story is genuinely simpler.
The catch is structural. The consumption baseline is typically set from your previous twelve months of MSU usage, drawn from the N7 section of the Sub-Capacity Reporting Tool (SCRT), plus a growth commitment. You are committing forward to a number derived from your past. If that number is set high, on a peak year, or padded with optimistic growth, you pay for capacity you do not use for the length of the term. The mechanics matter more than the marketing, which is why we treat TFP as a baseline negotiation, not a pricing menu. See the rolling four hour average explained for what TFP is replacing.
Buyers whose consumption is flat or trending down, and who have already exhausted the easy sub-capacity wins, commonly report the strongest outcome. The baseline reflects a settled estate, the growth commitment can be kept modest, and the model removes ongoing capping engineering. Predictability is worth real money when the number behind it is honest.
If new workload is coming on platform anyway, consumption pricing can absorb growth at a marginal rate that beats stacking new full capacity licenses. Buyers report this works best when growth is real and planned, not assumed. The model rewards you for putting work on the box; it does not reward you for guessing.
The most common regret we hear is a baseline anchored to an unrepresentative high. A migration spike, a one off batch surge, or a year of dual running can inflate the twelve month figure that becomes your floor. Buyers who did not scrub the baseline period report paying for that peak every year of the term.
A multi year commitment is leverage you hand the vendor for the duration. Buyers report that once inside TFP, the appetite to entertain a competing product or a metric change drops, because the commitment is sunk. The relief from the R4HA game is real; the reduced negotiating room at the next cycle is the cost that rarely appears in the business case.
| Factor | Outcome buyers like | Outcome buyers regret |
|---|---|---|
| Baseline period | Scrubbed for spikes, representative year | Peak or migration year taken at face value |
| Growth commitment | Modest, tied to a real plan | Optimistic, padded to please the vendor |
| Estate trajectory | Flat or declining, easy wins already taken | Shrinking after signing, paying for gone capacity |
| Term length | Matched to a planning horizon you trust | Long term locking in a number that aged badly |
| Exit position | Renewal levers preserved for next cycle | Commitment sunk, leverage handed over |
TFP terms, model names, and baseline mechanics described here reflect IBM documentation and buyer patterns commonly observed as of 2026. IBM applies periodic price harmonization; your specific agreement and SCRT data govern.
Three questions settle most of the TFP decision before you ever see a quote.
First, is the baseline period representative, or does it carry a spike you should argue out? Second, is the growth commitment something you would forecast independently, or a number the vendor needs to make the deal work? Third, what does this commitment cost you in leverage at the next renewal, and is the predictability worth it? Buyers who answer those three honestly tend to land well. Buyers who treat TFP as a take it or leave it menu tend to inherit a number they did not interrogate. For the deeper trade off against traditional sub-capacity charging, see Tailored Fit Pricing vs sub-capacity, and to read the proposal itself, the renewal quote anatomy.
Audit notice or renewal under 18 months out? We mobilize within 48 hours. Weighing a TFP baseline before you commit? Start with mainframe license negotiation.
Every issue of the journal, plus renewal benchmarks we do not publish on the site. No vendor sharing, ever.
More from the journal: MSU optimization quick wins before the renewal, when a 60 percent uplift lands, and why renewal preparation starts at 18 months. Explainers: the rolling four hour average and zIIP engines and software cost offload. Hub: publisher licensing hubs.