When do you stop grandfathering old pricing?
Hey Indie hackers, I’m trying to figure out the right way to handle grandfathered pricing and would love to hear how other founders approach it.
Over the years, we’ve run several pricing experiments.
One rule we’ve always followed is that new pricing only applies to new customers. Existing customers keep the plan they originally signed up for.
Some of our customers have now been paying the same price for more than three years.
My thinking was that customers made their decision based on the product, packaging, and price we offered at the time. It didn’t feel right to make them pay for our pricing experiments.
The downside is becoming more obvious now.
We have legacy plans to support, billing gets more complicated, and some of our oldest customers pay the least despite receiving a much more capable product than when they originally signed up.
The approach I’m considering is:
- Keep customers grandfathered while we’re experimenting with pricing.
- Only migrate them after the product or packaging has changed in a meaningful way.
- Give plenty of notice and make the transition as fair as possible.
I’m curious how you handle this. Do you grandfather customers forever, set a time limit, or only migrate them after a major product or packaging change?
I like that you're treating grandfathering as a trust decision rather than just a pricing decision.
The interesting question isn't when customers should pay more. It's what promise you believe you made when they first bought. Answering that makes the pricing decision much clearer than optimizing around billing complexity alone.