Why 60 percent of vendors mask increases

Why do vendors mask price increases?

Vendors mask price increases because a hidden rise meets far less buyer resistance than a stated one. A plain line that says the price went up by a given percentage invites a negotiation, while an increase folded into a new bundle or a new unit of measure arrives looking like a product change rather than a price change. About 60 percent of vendors mask increases rather than state them plainly, per 2026 pricing analyses, so the masked increase is the norm rather than the exception.

The pressure to do this is high in 2026. AI driven renewal asks run 20 to 37 percent against a historical 3 to 9 percent annual uplift, and a number that large is hard to defend in the open, so the incentive to hide it is strong. The top 500 SaaS companies made 339 pricing and packaging changes in one year, which is the churn of repackaging the masked increase relies on. The buyer side answer is to compare to prior cost in plain terms, the method in our SaaS Benchmarks Guide.

What is forced SKU migration?

Forced SKU migration is when the vendor retires the SKU you currently buy and moves you onto a new one, usually an AI inclusive bundle, so the old price point no longer exists to compare against. Because the legacy SKU is gone, there is no like for like number, and the new bundle rate looks like the only option. The increase is real, but it is hidden inside a product the vendor presents as an upgrade rather than a price change.

The counter is to request legacy pricing explicitly and to ask for the plan without the AI where the AI features go unused. Even when a SKU is being retired, vendors can usually hold a comparable configuration or honor the prior rate for a transition period. Naming the migration as a price change, not a product change, is what reopens the conversation, and the detail of the tactic sits in forced SKU migration into AI bundles.

What is unbundling then rebundling?

Unbundling then rebundling is when a vendor splits features out of the package you already had, then sells them back to you inside a new bundle at a higher combined price. You end up paying again for capability you previously owned, dressed as a richer package. The move works because the new bundle has no direct predecessor to benchmark against, so the increase disappears into the repackaging.

Your counter is to price each component on its own and rebuild the comparison the vendor took away. Ask for the standalone price of every element in the new bundle, line them up against what you paid before, and the masked increase becomes visible. Once it is visible, it is negotiable. The full mechanics of the tactic are in unbundling then rebundling explained.

How does credit based pricing hide the rate?

Credit based pricing hides the rate by converting your spend into a pool of credits that are then consumed by different actions at different rates. Because the credit sits between your dollars and the unit of value, you cannot easily compare the cost of a given action to last year or to another vendor. The credit is a layer of abstraction, and abstraction is what defeats benchmarking, which is precisely why the model is attractive to a vendor raising prices.

The counter is to convert credits back into a real unit cost before you sign. Work out how many credits each action you rely on actually consumes, multiply by the credit price, and you have the true cost per action you can benchmark and negotiate. Refuse to evaluate a credit pool in the abstract. The detail of why this matters is in the credit based pricing problem.

How does a buyer counter a masked increase?

A buyer counters a masked increase by insisting on a like for like comparison to prior cost, in plain terms, before discussing anything else. Whatever shape the new proposal takes, ask the vendor to show what the same outcome cost last year and what it costs now. If the vendor cannot or will not produce that comparison, that refusal is itself the signal that an increase is being hidden. The number exists, so the work is to surface it.

Once the real increase is visible, hold the rate at SKU level so a repackage cannot reset it, cap any uplift at a modest CPI indexed figure, and benchmark every line against what comparable buyers pay. Start the renewal 6 or more months early so you have time to do this before the vendor anchors a number. The masked increase only works in the dark, and a buyer who demands plain comparison turns the lights on.

A worked example

Indicative example. A buyer received a renewal as a new AI inclusive bundle with no reference to the prior SKU, presented as a modernization rather than an increase. Asked for a like for like price, the vendor produced a legacy configuration that revealed the true increase was a fraction of what the bundle implied. The buyer took the legacy rate for the unused AI features, priced the wanted components standalone, held the rate at SKU level, and capped the uplift. The renewal landed close to the prior year. The figures here are indicative and shown to illustrate the mechanics.

How do you build a like for like comparison the vendor cannot dodge?

You build a like for like comparison the vendor cannot dodge by fixing the outcome, not the product, as the unit of comparison. Ask one disciplined question: what did it cost last year to support this number of users, this volume of usage, or this set of capabilities, and what does it cost now under the new proposal. By anchoring on the outcome you need rather than the SKU the vendor is selling, you make the repackaging irrelevant, because the same outcome has a cost in both years regardless of how the product is named.

Document each component of the new proposal and map it back to what you previously paid for the same function. Where a feature was bundled out and sold back, list its old inclusion against its new price. Where a SKU was retired, request the legacy configuration for reference. Where credits replaced a unit rate, convert them to cost per action. The resulting table is the comparison the vendor would rather not produce, and once it exists, the hidden increase is simply a number on a page that you can negotiate like any other.

What does the scale of repricing mean for buyers?

The scale of repricing means a buyer should expect a masked increase at almost every renewal and prepare for it rather than be surprised by it. The top 500 SaaS companies made 339 pricing and packaging changes in one year, which is more than one change every working day across the leading vendors. That churn is the environment the masked increase lives in, because constant repackaging gives every vendor cover to reset a price under the banner of a new product.

Preparation is the defense. A buyer who assumes the renewal will arrive repackaged builds the like for like comparison before the proposal lands, starts the conversation 6 or more months early, and benchmarks each line against the market. About 60 percent of vendors mask increases rather than state them plainly, so treating the masked increase as the default, not the exception, is simply realistic. The buyer who expects it is rarely the buyer who pays it.

What is the move when the increase is hidden?

Demand the comparison the vendor would rather not give. Ask what the same outcome cost before and costs now, convert any bundle or credit pool back to a real unit cost, and hold the rate at SKU level with a capped uplift. Benchmark every line, request legacy pricing where a SKU is being retired, and start early so you have room to do the work. The benchmarking method sits in our SaaS Benchmarks Guide, and the wider counter is in the SaaS Negotiation Guide.

Frequently asked questions

Why do SaaS vendors hide price increases?

Because a hidden increase meets less buyer resistance than a stated one. A plain percentage rise invites negotiation, while an increase folded into a new bundle or a new unit of measure looks like a product change. About 60 percent of vendors mask increases rather than state them plainly, per 2026 pricing analyses.

What are the three ways vendors mask increases?

Forced SKU migration retires your current SKU and moves you to a new bundle so the old price point disappears. Unbundling then rebundling splits features out and sells them back in a package. Credit based pricing converts spend into credits that hide the unit rate and defeat benchmarking.

How do you spot a masked SaaS price increase?

Insist on a like for like comparison to your prior cost in plain terms before discussing anything else. Convert any bundle or credit pool back to a real unit cost, request legacy pricing where a SKU is being retired, and benchmark every line. If the vendor cannot produce a plain comparison, that refusal signals a hidden increase.

Published market figures reflect 2026 SaaS pricing analyses and are labelled indicative where appropriate.