Forced SKU Migration into AI Bundles
How the old price point disappears, and how to get it back.
Unbundling then rebundling is the tactic where a vendor splits out features you already had, then sells them back inside a higher tier. It is one of the three ways vendors mask increases, and the counter is to price only what is genuinely new.
Unbundling then rebundling is a packaging tactic where a vendor takes capabilities that sit inside your current plan, separates them out, and then sells them back to you inside a higher priced tier or an AI inclusive bundle. The repackage is presented as a new and richer offering. In reality, much of what is inside the new tier is what you already had, now reframed as added value. It is one of the three ways vendors mask increases, and it works because it hides a price rise inside a story about new features.
The tactic is effective for a specific reason. A straight increase on a familiar line item invites a challenge. A new bundle with a new name invites a comparison the buyer is not equipped to make on the spot. By the time the buyer realises that two thirds of the bundle is last year's plan, the deadline is close and the comparison is hard to reconstruct.
It works because it breaks the buyer's reference point. When the plan you renewed last year no longer exists as a named SKU, you lose the clean before and after that makes an increase obvious. The vendor controls the framing, the bundle name changes, and the conversation shifts from price to features. About 60 percent of vendors mask increases in ways like this, and against a backdrop of 339 pricing and packaging changes across the top 500 SaaS companies in a single year, a buyer who does not rebuild the comparison is negotiating blind.
There is nothing improper about a vendor improving and repackaging a product. The issue is purely commercial. A repackage should be priced on the value of what is new, not on the loss of a clean comparison. Restoring that comparison is the whole of the defense.
You counter unbundling then rebundling by rebuilding the line by line comparison the tactic is designed to remove. The table sets out the steps.
| Step | The move | Why it works |
|---|---|---|
| Map | List every capability in the proposed bundle against your current plan. | Surfaces how much of the new tier you already pay for. |
| Separate | Mark each item as existing, improved, or genuinely new. | Isolates the only part that justifies a premium. |
| Price | Negotiate a price for the new capability only, not the whole bundle. | Stops you paying again for features that moved tiers. |
| Protect | Lock the new package at SKU level for the term. | Prevents the same repackage resetting your baseline next year. |
The discipline is to refuse the bundle as a single price and insist on the decomposition. A vendor confident in the new value will engage with the line by line view. A vendor relying on the repackage to hide an increase will resist it, which is itself a signal of where the price is soft.
The tactic has accelerated because AI gives vendors a fresh reason to repackage. An AI inclusive bundle is the perfect vehicle for unbundling then rebundling, because the AI capability provides the headline while familiar features ride along inside the same higher tier. Published figures put AI driven renewal asks at 20 to 37 percent, against a historical 3 to 9 percent annual uplift, and a repackage is often how that ask is delivered. The buyer sees an AI story and a single new price, when the underlying move is the old plan plus a premium for one new feature.
The counter is the same, with one addition. Ask for the plan without AI, priced at the level you consume, so you can see the AI premium as a separate line rather than a number folded into a repackaged tier. That separation turns a masked increase back into a clear decision about whether the AI capability earns its price.
Consider a mid market software buyer, anonymized, presented with a new platform tier that replaced its existing plan. The quote was 28 percent above the prior year and described as an upgrade. A line by line map showed that of roughly twelve capabilities in the new tier, nine were already in the old plan, two were modest improvements, and one was a genuinely new AI feature the teams had not yet adopted. The buyer priced the negotiation on that single new feature, asked for ROI evidence before paying any premium for it, and held the existing nine at last year's effective rate. The repackage that opened at 28 percent settled close to a CPI indexed increase, because only the new value was paid for.
The lesson is that the bundle is beaten by decomposition. Once the buyer could see what had actually changed, the premium had nowhere to hide.
Unbundling then rebundling sits alongside the other masking tactics in the AI pricing defense. Read the full sequence in the AI Pricing Defense Guide, then study its siblings: forced SKU migration into AI bundles, which deletes the old price point, and the AI premium and paying for features you do not use. Together they cover the repackage, the migration, and the unused capacity that buyers are asked to fund.
For the full picture, read the AI Pricing Defense Guide. To put it to work on your deal, get a quote or book a strategy call.
Last reviewed November 2025.
One SaaS pricing or packaging change a week, why it matters for buyers, and one move you can make before your next renewal. Free, and written from your side of the table.
More from this cluster.