Grandfathered SaaS pricing is the arrangement where existing customers keep paying an old rate after the vendor raises it for everybody else. It used to be indefinite by default. Loyal customers kept their price, sometimes for a decade, and nobody wrote it down because nobody had to.
That default has flipped. The 2026 pattern is time-limited grandfathering: twelve to twenty-four months of protection, paired with feature gates so anything new belongs to the current tier. Your rate is safe. Your product slowly stops improving.
Why vendors changed the deal
Grandfathering used to be a marketing expense that retention paid for. A customer sitting on a five-year-old rate still threw off near-100% gross margin, so protecting them cost the vendor an opportunity rather than a dollar.
AI broke that arithmetic. Inference is a real per-use cost, so a grandfathered customer who uses AI features can now cost the vendor actual money every month. Withholding those features forever is not an option either, because they are the roadmap, and a legacy tier that visibly falls behind churns on its own.
So the industry landed on time-limited grandfathering with feature gates. Existing customers get a defined runway, any increase is tied to visible new capability, and, in the part that matters to you, a protection that used to have no expiry date now has one.
The feature gate is the part people miss
Most buyers hear “your price is protected” and stop listening right there. The gate is where the cost actually accrues.
On a gated legacy tier your rate holds, but every new capability ships to the current tier instead. For a few months you will not notice. By month twelve your team is working around gaps that a competitor’s users do not have. By month eighteen the migration you turned down is one you are asking for, at whatever the price is by then, with no leverage at all, because you are the one who brought it up.
That is the design. Time-limited grandfathering does not stop the increase. It schedules it, and arranges for you to request it.
Whether that is a bad deal comes down to whether you use the gated features. A team that will never touch AI summarisation should take the gated legacy rate cheerfully and look again in a year. The mistake is accepting the gate without working out which side of that line you are on.
Six questions to ask before you sign
In writing, before renewal. Keep the answers.
- Is our current tier being retired, and on what date? The whole conversation in one question. A vendor who will not answer it by email has answered it.
- How long is the grandfathered rate guaranteed, and is that in the contract? “You’re fine for now” from an account manager who will have changed roles before your next renewal is not a commitment.
- Which features are gated to the current tier, and which of those are on the roadmap? The forward-looking half is the half that matters, and the half they would rather answer vaguely.
- What is the migration price, quoted today? Get the number while you can still do something with it. A migration quote at 120 days is a completely different document from the same quote at 20.
- Does our uplift cap survive a SKU change? Usually it does not. A cap governs renewal of a product, and a retired product cannot be renewed. Better to find that out now than in the quote. See Forced SKU Migration.
- If we migrate, is the new rate protected, and for how long? Routinely forgotten. Move to an AI tier with no cap and you are doing all of this again next year, from a higher base.
Getting the protection into the contract
Four clauses do most of the work. None of them are unusual asks.
- A price-hold with an explicit end date. The rate and the term, in writing. Without this the rest is decoration.
- A SKU-continuity clause. If the tier is discontinued mid-term, you migrate at an equivalent effective rate instead of at list. This is the clause that survives a forced migration, so it is the one to spend your negotiating capital on.
- An uplift cap that applies across SKU changes. The wording carries real weight here. A cap on “renewal of the Services” is far stronger than a cap on “renewal of the Plan”.
- A notice period on tier retirement. Ninety days minimum. Productiv gave four days’ notice on a full shutdown in August 2026, which is the argument for writing a number down rather than trusting the market norm.
If you have already lost it
Once the rate is gone, what is left are the moves that do not need the vendor to agree to anything. Reclaim unused seats, because most organisations are meaningfully over-licensed and a migration is the natural moment to audit. Consolidate overlapping tools, because AI bundling means you are probably paying twice for the same capability now. Trade term length for rate if you are staying regardless. And price one real alternative, not as a threat, just so you know.
Watch it happen to someone else first
Grandfathering usually ends for a vendor’s entire customer base at once, in a wave that starts months before it reaches your renewal date. Seeing the wave early is most of the advantage.
CopperFeed records those changes as dated entries: launches, releases, repricings and shutdowns, in the order they happened. The running list of retirements is in Legacy Plan Sunsets: Every SaaS Tier Being Retired in 2026.
Figures here come from published third-party reporting. General guidance, not legal or procurement advice. Contract language varies, and your own terms govern.