Grandfathering SaaS Customers on Old Pricing: Pros and Cons

When a SaaS company changes its pricing, it has to decide what happens to the customers who are already paying. Grandfathering means letting those customers keep their current price, sometimes indefinitely, while new customers pay the new one. It is a common way to avoid backlash, and in the right situation it is a generous and sensible choice. But grandfathering pricing in SaaS has real costs that tend to show up slowly, long after the decision was made, in billing complexity, stalled upgrades and revenue that never catches up with the value of the product.

This guide explains the forms grandfathering takes, the genuine benefits and drawbacks, when it makes sense and when it does not, and the middle-ground options that many teams end up choosing. The aim is to help a small team make the decision deliberately rather than by default.

What grandfathering looks like

Grandfathering is not one policy but a family of them, and the version you choose matters as much as the decision to grandfather at all.

Permanent grandfathering lets existing customers keep their price for as long as they stay subscribed. It is the most generous version and the hardest to undo. Time-limited grandfathering keeps the old price for a set period, such as six or twelve months, after which customers move to the new price. Plan-locked grandfathering keeps the old price only while the customer stays on the same plan, so upgrading or changing plans moves them onto current pricing. Partial grandfathering applies the old price to a specific group, such as early adopters or customers who joined before a certain date, while others move to the new pricing.

Each version sends a different message to customers and creates different operational work for your team, so it is worth deciding which one you mean before announcing anything.

The pros

It protects goodwill

Customers who took a chance on you early often feel they helped build the product. They tolerated bugs, gave feedback and recommended you before you had much proof. Rewarding that with a stable price signals loyalty and fairness, and it can turn early customers into vocal supporters. For a young company that relies on word of mouth, that goodwill has real value.

It reduces churn risk

A price increase is a moment when customers reconsider their subscription. Even customers who are happy with the product may take the opportunity to review alternatives or cut costs. Grandfathering removes that moment for your existing base, which keeps churn predictable during a period when you are already changing a lot.

It simplifies communication

Telling customers "nothing changes for you" is much easier than explaining an increase. There are no difficult support tickets, no negotiations with large accounts and no risk of a public complaint thread. For a small team without dedicated customer success staff, that simplicity matters.

It lets you test new pricing safely

When only new customers see the new price, you can learn how the market responds without putting existing revenue at risk. If conversion drops sharply, you can adjust the new pricing without having upset your whole customer base.

The cons

It leaves revenue on the table

Many SaaS companies underprice early. If your existing customers make up a large share of your revenue and they are paying well below what the product is now worth, grandfathering locks that underpricing in. The gap can grow every year as you add features and raise prices for new customers, until a large portion of your base is paying a fraction of current list price.

It creates complexity

Every grandfathered price point is something your billing system, finance reports, support team and sales team need to understand. After a few pricing changes, you may have many versions of the same plan, each with slightly different limits and prices. That complexity makes reporting harder, slows down support and increases the chance of billing mistakes.

It can block upgrades

Customers on cheap legacy plans often avoid changing plans because they would lose their price, even when a newer plan would suit them better. That keeps them on older packaging with fewer features, which can hurt their experience and your expansion revenue at the same time.

It can feel unfair to newer customers

If legacy pricing becomes visible, through a community forum or a conversation between customers, newer customers may feel they are paying more for the same product. That can create awkward support conversations and requests for matching discounts.

It makes future changes harder

The longer legacy pricing lasts, the more painful it becomes to move those customers later. A modest increase after one year feels reasonable. A large jump after five years of a frozen price feels like a betrayal, even if the new price is fair.

When grandfathering makes sense

Grandfathering tends to be the right call when the price increase is large enough to cause meaningful churn, and when your existing customer base is small compared with the growth you expect. In that case, the revenue you forgo is limited, and the goodwill you protect is worth more. It also makes sense when early customers took real risks or helped shape the product, since rewarding them is both fair and good for advocacy. Finally, it is a reasonable choice when you are unsure about the new pricing and want to test it on new customers before applying it more widely.

When it may not

Grandfathering is harder to justify when existing customers make up most of your revenue and are significantly underpriced, because you would be freezing the bulk of your business at the wrong price. It is also risky when your costs have risen and the old price is no longer sustainable, for example when infrastructure or support costs per customer have grown with usage. If you have already accumulated several legacy plans, adding another makes the complexity problem worse. And if the product has improved substantially since customers signed up, keeping them on an old price indefinitely means they receive the new value without contributing to it.

Middle-ground options

Time-limited grandfathering

Keep the old price for a defined period, then move customers to the new price with plenty of notice. This rewards loyalty and gives customers time to budget, while making sure legacy pricing does not become permanent. Be specific about the end date from the start so the eventual change does not come as a surprise.

Gradual increases

Move legacy customers toward the new price in steps rather than all at once. A series of smaller increases over a year or two is easier to absorb than a single large one, and it gives you a chance to watch churn at each step.

Lock-in offers

Let customers lock in their current price by switching to an annual plan before the change takes effect. This rewards commitment, improves cash flow and gives you a predictable window before the new price applies.

Grandfather the price, not the plan

Allow legacy customers to keep their price, but make it easy and attractive to move to the new plans. If the new plans include features legacy customers want, many will move voluntarily, which reduces the number of legacy price points over time.

A loyalty discount from the new price

Move everyone to the new pricing structure, but give existing customers a loyalty discount for a set period. This keeps billing simple, because everyone is on the same plans, while still recognizing that existing customers deserve better treatment. When the discount ends, they are already on current plans.

How to communicate

Whatever you choose, clarity matters more than the policy itself. Tell customers what is changing and when, who is affected, what they will pay and for how long, why the change is happening and what options they have. If you are grandfathering permanently, say so. If it is time-limited, give the end date. If there are conditions, such as staying on the same plan, spell them out.

Avoid vague language like "your pricing may be adjusted in the future" without specifics. Customers read vague statements as a warning that something bad is coming, and they will ask about it. A clear policy, even one that includes a future increase, tends to generate fewer worried tickets than an ambiguous one.

Track the impact

After the change, monitor churn among existing customers, broken down by cohort and plan. Track revenue per customer for each cohort so you can see how much legacy pricing is costing you. Keep a count of active legacy price points, because that number tends to grow without anyone deciding it should. Watch support tickets about pricing, which can reveal confusion about the policy before it turns into churn.

Then review legacy pricing once a year. Ask whether each grandfathered group still deserves its price, whether the complexity is still worth it and whether a gradual move to current pricing would now be reasonable. Making this an annual decision prevents legacy pricing from becoming permanent by default.

A worked example (illustrative)

A small SaaS company selling scheduling software to clinics had launched with a single flat price. Three years later, the product had added reminders, payments and multi-location support, and the team introduced tiered plans with a higher entry price. Existing customers still made up most of the company's revenue.

Permanent grandfathering would have frozen the majority of revenue at the launch price, so the team ruled it out. A full immediate move felt too abrupt for customers who had supported the company from the beginning. They settled on a combined approach. Existing customers kept their price for twelve months, with the end date stated clearly in the announcement. During that year, anyone could move to a new plan at a loyalty discount, and customers who switched to annual billing before the change could lock in their old rate for one more year.

The announcement explained what had been added since launch and why the pricing was changing. Support received a short guide covering common questions and a clear rule for who could approve exceptions. Most customers either accepted the timeline or moved to a new plan early, and the number of legacy price points stayed at one, with a known end date, instead of becoming permanent.

The takeaway

Grandfathering protects goodwill and reduces churn, but it also locks in underpricing and creates complexity that grows over time. For many SaaS companies, time-limited grandfathering offers a good balance: it respects existing customers, avoids sudden shocks and keeps legacy pricing from turning into long-term financial and operational debt. Whatever you choose, decide on purpose, communicate it clearly and revisit it every year.