Requesting Legacy Pricing Explicitly at Renewal
Requesting legacy pricing explicitly means asking, in writing and early, to renew on your current unit prices rather than the vendor latest list. Vendors reprice quietly at renewal, so the old rate only stays on the table if you name it before any new quote anchors the conversation.
Key takeaways
- Renewal quotes default to current list, not your historical rate, so the legacy rate disappears unless you ask for it explicitly.
- Make the ask in writing six or more months out, before the vendor anchors a higher number.
- Forced SKU migration that deletes the old price point is a recognised masking tactic; counter it by asking for the equivalent of your current configuration.
- Disciplined renewal negotiation typically lands 10 to 30 percent savings, and the legacy ask is often the highest leverage opening move.
What does requesting legacy pricing explicitly mean?
It means making a clear written request to renew on your existing rate card and unit prices, rather than accepting the vendor current list. The word explicitly matters because the default behavior of a renewal system is to reprice you to today list, and unless you name the rate you signed at, that old number quietly vanishes from the conversation. You are not asking for a favor. You are asking the vendor to honor the commercial relationship you already have rather than treat the renewal as a fresh sale at a higher anchor.
Most buyers assume the renewal will simply continue what they had. It rarely does. The quote that arrives is built from current list with whatever standard uplift the vendor applies, and your historical discount, your locked unit price, and the terms that protected you are treated as expired. Requesting legacy pricing puts the old position back on the table as the starting point, which changes the entire shape of the negotiation.
Why does the old rate disappear if you stay quiet?
Because renewal pricing is engineered to reset upward, and silence is read as consent to the new list. Published market data shows AI driven renewal asks running 20 to 37 percent against a historical 3 to 9 percent annual uplift, and roughly 60 percent of vendors mask their increases rather than state them plainly. One of the three main masking tactics is forced SKU migration into a new bundle that deletes the old price point, so there is no longer a clean line back to what you used to pay.
When you say nothing, the vendor quote becomes the reference number for the whole negotiation. Every concession is then measured against an inflated anchor, so a discount off the new list can still leave you paying far more than your legacy rate. Naming the legacy rate first reframes the discussion: now any increase has to be justified against the price you actually hold, not against a list you never agreed to.
When should the legacy ask go in?
Six or more months before the renewal date, and before the vendor sends a formal quote. The renewal is won early because the first credible number on paper sets the anchor, and you want that number to be yours. If you wait until the vendor opens with a 22 percent uplift, you are negotiating down from their figure instead of up from yours.
Early timing also gives you room to gather the evidence that makes the ask stick: your usage data, your adoption levels, your shelfware, and any benchmark you can attribute. A legacy request backed by a usage picture reads as a serious procurement position, not a hopeful email. The renewal timeline that wins puts this ask near the front of the sequence, well ahead of the vendor manufactured deadline.
How do you phrase the request so it holds?
State the rate, the configuration, and the term in one sentence, then ask for written confirmation. A clean version reads: we intend to renew at our current per unit price of the existing configuration for a further term, and we are asking you to confirm that legacy pricing in writing. This does three things at once. It names the number, it removes ambiguity about scope, and it forces a written response that you can hold the vendor to.
Avoid softening the ask into a question about whether a discount might be available. That invites the vendor to start from list and offer a token reduction. Instead, treat your legacy rate as the baseline and make any movement off it the vendor burden to justify. If they want more, they have to show why, with evidence, against the rate you already pay.
The legacy rate is not a discount you are requesting. It is the position you already hold, and the renewal is the vendor attempt to move you off it.
What is the counter when the vendor resists?
Vendors have a predictable set of responses to the legacy ask. Name each one, then take the counter.
| Vendor response | What it really means | Your counter |
|---|---|---|
| That SKU no longer exists | Forced SKU migration that deletes the old price point | Ask for the price equivalent of your current configuration on the new SKU, plus evidence for any uplift |
| Legacy pricing was a one time concession | An attempt to treat your rate as expired goodwill | Point to the signed agreement and ask which clause sets the reset, not the assertion |
| List has gone up across the board | An anchor to a number you never agreed | Request the rate against your historical price, capped at 3 to 5 percent CPI indexed, not against new list |
| The AI features now come bundled in | Unbundling then rebundling what you already had | Ask for the plan without the AI tier and demand ROI evidence before paying any premium |
The through line is simple. Every response tries to replace your held rate with a higher reference point, and every counter pulls the conversation back to the price you actually pay and the evidence required to move it.
What does the legacy ask look like on a real renewal?
Consider an indicative example. A mid market buyer with a renewal nine months out holds a per seat rate locked two years earlier. Rather than wait for the quote, they send a written request to renew at the current per seat price for a further term and ask for confirmation. The vendor responds that the original edition has been folded into a new AI inclusive bundle and the legacy SKU is retired.
The buyer does not accept the migration at face value. They ask for the price equivalent of their current configuration on the new packaging, request the plan without the AI tier since usage data shows the features would sit unused, and ask for evidence of the value behind any premium. They cap any genuine increase at CPI and anchor every number to the legacy rate. In this indicative example the renewal lands close to the held rate with a small capped uplift, because the buyer never let the new list become the reference point.
Your next step
The legacy ask is one move in a longer sequence. For the full method, read the SaaS Renewal Playbook. To sequence the timing, see The Renewal Timeline That Wins, and to build the evidence behind the ask, see Usage Data, Your Best Renewal Weapon. When you want this run on a live renewal, our buyer side team can take the table or coach yours through it.
Download guide: SaaS Renewal Playbook, or plan the dates with The Renewal Calendar Workbook.
Common questions
What does requesting legacy pricing mean?
When should I request legacy pricing?
What if the vendor says the legacy SKU no longer exists?
Last reviewed May 2026. Market figures cited are published industry data; figures labelled indicative are directional.