Price Increase Cap

A price increase cap is a contractual limit on how far a supplier may raise your price when the term renews. It is usually written as a maximum percentage per renewal, sometimes tied to an inflation index, and it applies to the rates in the order form rather than to any new products you later add. Its purpose is to make the second year predictable, which the first year never is. The reason it matters is arithmetic. A large introductory discount that is followed by unrestricted renewal pricing is a loan, not a saving: the vendor recovers the discount at renewal, at a point when you have integrated the product, trained your staff and moved your data into it. The negotiating leverage that produced the discount is gone precisely when the increase arrives. A cap converts a one-year price into a multi-year one, and it costs the buyer nothing except the willingness to ask. Three details decide whether a cap is real. What it applies to — the unit rate, or the total invoice, because a cap on the rate does nothing if the vendor reclassifies your plan or moves features into a higher tier. What the baseline is — the discounted price you actually pay, or a list price you have never paid, which is the common way a cap ends up permitting a large increase. And whether it survives more than one renewal, because a cap that applies only to the first renewal simply delays the conversation by a year. Notice provisions belong in the same clause. A renewal increase announced a fortnight before an auto-renewing term begins is not a negotiation, it is an invoice. Sensible contracts require the vendor to state any change well before the renewal notice deadline, which gives the buyer the option to cancel, to negotiate, or to start a migration with time to complete it. For AI products the cap has an extra dimension, because part of what you are buying is compute that the vendor itself buys. Model prices move, and a vendor may reasonably decline to fix a consumption rate for three years. The workable compromise is usually to cap the platform or seat component tightly while agreeing a transparent mechanism for the usage component — published rates, advance notice of changes, and the right to terminate without penalty if a change exceeds a threshold. The habit worth building is to record, for every contract, the current rate, the cap, the renewal notice date and the last increase. Most organisations discover their software costs have drifted upward not through any single decision but through a series of renewals nobody was tracking, each individually defensible and collectively expensive.