Pricing design
Grandfathered Prices: Protect Existing Deals Without Losing Track
By the Orvlin team · · 2 min read
Grandfathered pricing policy: what to decide
A pricing change feels safer when current customers can stay put. Months later, though, nobody remembers whether their special rate survives an upgrade or a contract renewal. The transition policy needs to be as clear as the new price.
Version plans rather than rewriting the old catalog. Associate each account with the agreed version and effective dates. Define how additional products, workspace changes and renewal negotiations interact with the protection.
Follow one account through the calculation
An account keeps its old request rate until annual renewal. Buying a new analytics add-on does not necessarily move the existing request meter to the new rate. The agreement should say whether additions are independent or trigger migration.
Check this before launch
Unlimited protection may accumulate unsupported offers that complicate support and forecasting. If there is a sunset, announce it honestly and model account-level impact before sending a generic percentage increase.
Steps to take next
- Record which accounts qualify and why.
- Specify expiry, renewal and upgrade behavior.
- Keep historical price versions accessible.
- Compare promised terms with actual invoices during migration.
Frequently asked questions
- Does grandfathering mean prices can never change?
- No. It means a defined protection applies under agreed conditions. Avoid using the term without explaining its duration and exceptions.