Blog
The bundle that hides the increase
The bundle that hides the increase is a tactic where a vendor folds your existing product into a larger package, adds new features, and retires the standalone SKU so you cannot compare like for like. The counter is to reconstruct the old price in writing, ask for the plan without the additions, and refuse to let the new features ride in on an automatic uplift.
Key takeaways
- Bundling hides a rise by deleting the old SKU, so there is no clean before and after price for the buyer to point at.
- The added features supply a story that reframes a price increase as a new package, steering the conversation toward value instead of the size of the rise.
- About 60 percent of vendors mask increases rather than state them plainly, per 2026 pricing analyses, and the bundle is one of the main vehicles for doing it.
- The counter is to rebuild the like for like price in writing, request the plan without the additions, demand ROI evidence, and carve the new features out of any automatic uplift.
What is the bundle that hides the increase?
The bundle that hides the increase is a pricing tactic in which a vendor folds the product you already buy into a larger bundle, usually one with new features added, and quietly retires the standalone SKU you used to purchase. Because the old line item no longer exists on the price list, you have nothing to compare the new number against. The higher bundle price reads as a fresh package with more in it, when in commercial terms it is a price increase wearing a new label.
This is one of the three masking moves that define the 2026 landscape, alongside unbundling then rebundling and credit based pricing. It is effective precisely because it removes the evidence a buyer would normally use to push back. Naming the tactic is the first step to countering it, which is the buyer side discipline at the heart of our SaaS Negotiation Guide.
Why do vendors bundle to hide a price increase?
Vendors bundle to hide a price increase because bundling defeats comparison, and comparison is the buyer's strongest tool. When the old SKU is deleted, there is no clean before and after to put on a slide, so the buyer cannot say "you raised this by a specific amount" with the numbers to prove it. The added features, often AI capabilities, supply a ready made justification: the price went up because you are getting more. The conversation drifts toward debating the value of the bundle, which is exactly where the vendor wants it, and away from the size of the increase, which is where the buyer would win.
The scale of this is documented. The top 500 SaaS companies made 339 pricing and packaging changes in a single year, per 2026 analyses, and a large share of those were repackaging moves rather than honest list rises. Around 60 percent of vendors mask increases instead of stating them plainly. AI driven renewal asks now run 20 to 37 percent against a historical 3 to 9 percent annual uplift, and the bundle is one of the cleanest ways to present a number in that range as something other than a rise.
| What the vendor says | What is actually happening | The buyer counter |
|---|---|---|
| This is a new bundle with more value | The old SKU was deleted to block comparison | Ask in writing for the like for like price of what you had |
| The AI features are included now | You are paying for features you may not use | Request the plan without AI and demand ROI evidence |
| The whole bundle uplifts together | The new features ride in on the automatic rise | Carve the new features out of the uplift as a separate decision |
| This is just the current packaging | The standalone option still exists internally | Request legacy pricing explicitly and in writing |
How do you spot the bundle tactic on your renewal?
You spot the bundle tactic when the renewal quote names a package you were not buying last year and the standalone product you did buy is no longer listed. Three signals give it away. The SKU changed, so the line item on the quote does not match the one on your prior invoice. New features appear that you never requested, framed as included rather than optional. And the price moved by a margin well above the historical uplift, often into the 20 to 37 percent range that signals an AI repricing rather than a routine adjustment.
When you see those signals together, treat the quote as a repricing, not a renewal, and reset the conversation accordingly. Pull last year's invoice, note the exact product and price you held, and put the comparison the vendor removed back on the table yourself. The discipline of insisting on the like for like number is the same one that disarms the related forced migration tactic, which we cover in forced SKU migration into AI bundles.
How do you counter the bundle that hides the increase?
You counter the bundle that hides the increase by rebuilding the comparison the vendor deleted, then negotiating against it. The first move is to ask, in writing, for the cost of the capability you had before, separated from the new additions. Vendors can almost always produce this, because the standalone option usually still exists internally even when it has left the public price list. Requesting legacy pricing explicitly forces the real number into the open, and once it is visible the size of the increase becomes the subject again.
From there, run the standard AI defense. Ask for the plan without the added features so you can choose them rather than inherit them. Demand ROI evidence before you accept any premium for capabilities you have not yet proven you will use. And push to carve the new features out of the automatic uplift, so they sit as a separate, optional decision rather than riding in on the renewal. Each move turns a forced bundle back into a set of choices you control, the approach we set out in the AI carve out clause.
A worked example
Indicative example. A buyer received a renewal quote naming a new suite at a number roughly a third above the prior year. The standalone product they had used for years was absent from the quote. The buyer pulled the previous invoice, requested the like for like price in writing, and asked for the suite without the bundled AI module. The vendor produced the standalone price, the gap between it and the suite turned out to be the AI premium, and the buyer carved that module out of the automatic uplift as an optional add on to evaluate separately. The renewal landed close to the prior price plus a modest indexed uplift. The figures here are indicative and shown to illustrate the mechanics.
How does the bundle tactic fit the wider masking pattern?
The bundle tactic fits the wider masking pattern as one of three related moves that all share a single goal: making a price increase hard to see and harder to challenge. Bundling deletes the old SKU so there is nothing to compare. Unbundling then rebundling strips a feature out and sells it back, so you pay again for what you already had. Credit based pricing replaces a clear per unit rate with a credit currency that defeats benchmarking entirely. Recognising them as a family matters, because the counter to all three rests on the same instinct: restore the comparison, then negotiate against it.
That is why a buyer who can name the tactic is already most of the way to disarming it. The vendor's advantage is the information gap, and every move that closes the gap, the written legacy price, the plan without AI, the carve out, the benchmark, returns leverage to your side of the table. The full set of masking tactics and their counters runs through our SaaS Negotiation Guide, and the related rebundling move is broken down in unbundling then rebundling the tactic explained.
What is the move on your next renewal?
Treat any renewal that introduces a new bundle as a repricing until proven otherwise. Pull last year's invoice, ask in writing for the like for like price of what you actually had, request the plan without the new features, and demand ROI evidence before paying any premium. Carve the additions out of the automatic uplift so they remain your choice. Do that, and the bundle stops hiding the increase and starts revealing it. The full method sits in our SaaS Negotiation Guide.
Make the hidden increase visible.
Use the SaaS Negotiation Guide to name every masking tactic, counter the forced repackaging with forced SKU migration into AI bundles, and disarm the sell back move with unbundling then rebundling the tactic explained.
Download guide →Frequently asked questions
What is the bundle that hides the increase?
It is a pricing tactic where a vendor folds your existing product into a larger bundle, often one with AI features added, and retires the standalone SKU you used to buy. Because the old line item no longer exists, you cannot compare like for like, and the higher bundle price reads as a new package rather than the price increase it actually is.
Why do vendors bundle to hide a price increase?
Bundling defeats comparison. When the old SKU is deleted there is no clean before and after price to point at, the added features supply a story that justifies the higher number, and the buyer is steered toward debating the bundle's value rather than the size of the rise. About 60 percent of vendors mask increases rather than state them plainly, per 2026 analyses, and the bundle is one of the main ways they do it.
How do you counter a bundle that hides an increase?
Reconstruct the like for like price first: ask in writing for the cost of the capability you had before, separate from the new additions. Request the plan without the added features, demand ROI evidence before paying for anything you will not use, and push to carve the new features out of the automatic uplift so they are a separate, optional decision rather than a forced one.
Published market figures reflect 2026 SaaS pricing analyses and are labelled indicative where appropriate.