① Guide · IBM Tailored Fit Pricing
IBM Tailored Fit Pricing replaces traditional monthly license charges with a consumption model priced against a baseline you agree once. The headline savings get the attention. The baseline and the exit decide what you actually pay for years. Here is how to negotiate both.
48 hour mobilization Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →Tailored Fit Pricing for IBM Z is IBM's consumption based alternative to the traditional sub-capacity model. The Software Consumption Solution, formerly called the Enterprise Consumption Solution, prices your software against measured MSU consumption rather than a rolling four hour average peak, with an included capacity baseline and a rate for everything above it. A separate Hardware Consumption Solution adds a subscription corridor of pay for use hardware capacity on z15 and later machines for customers already on a Software Consumption Solution.
The appeal is real. The model removes the operational penalty for letting workloads run uncapped, and it makes billing more predictable. But it converts a metered relationship into a baseline relationship, and the baseline is set once, often early, and referenced for the life of the agreement. Get it wrong and the simplification becomes the most expensive thing on the mainframe.
The three numbers that decide TFP cost
| Lever | What IBM proposes | What to negotiate for |
|---|---|---|
| Baseline measurement window | A recent period, often a busy one | A representative window, validated against your own SCRT history, excluding one off spikes |
| Included capacity | Sized to the proposed baseline | Headroom that matches realistic growth, not last year's peak |
| Rate above baseline | A single consumption rate | Tiered or capped rates so a growth year does not become a penalty year |
| Term and reopener | A multiyear commitment | An exit or reopener provision agreed before signing |
Run the model against three scenarios before you commit: a flat estate, a shrinking estate, and a growth estate. A TFP deal that beats your current bill in a growth year can lose badly in a flat one, and the mainframe estates we see are more often flat or shrinking than growing. The baseline must be measured, not assumed, and validated on your side of the table.
The single most common regret we see with Tailored Fit Pricing is the absence of an exit. Returning to the traditional sub-capacity model after committing to TFP is commonly difficult, frequently requires hard negotiation, and can forfeit discounts earned under the agreement. None of that is a reason to avoid TFP. It is the reason to negotiate the exit before you enter. A reopener tied to a defined event, a capped consumption rate that survives a growth year, and a documented right to revert protect you from the one outcome the model makes hardest to undo.
This is the discipline of our IBM mainframe cost optimization work: the baseline gets validated independently, the growth case gets modeled honestly, and the exit gets written into the agreement before the signature, not sought after it.
The Software Consumption Solution prices your bill against a measured consumption baseline. It sets included capacity and the rate above it, and everything references it. A baseline measured in a busy period locks in cost for the term.
Returning to traditional sub-capacity is commonly difficult and rarely clean, and can forfeit discounts earned under TFP. Negotiate the exit before you enter; a reopener agreed up front is worth far more than one sought later.
The Software Consumption Solution is consumption based software licensing replacing monthly license charges. The Hardware Consumption Solution is a pay for use hardware capacity corridor on z15 and later. They are negotiated together but distinct.
Not automatically. It depends on the baseline, the growth assumption, and the rate above the included level. A model that looks good against last year can be expensive against a flat or shrinking estate. Run the math both ways. See SCRT explained.
The model TFP replaces, and how to defend it when you stay on it.
The full IBM estate, from MLC to TFP to sub-capacity.