SaaS pricing change checklist before emailing existing customers

This checklist helps small SaaS teams change pricing without surprising existing customers. It focuses on what to verify before the announcement: who is affected, which plans are grandfathered, what date the change starts, and what support replies should say.

Start by separating new customer pricing from existing customer pricing. A public pricing page can change instantly, but existing customers need a clear rule. Some teams keep current customers on their old price, some move them after a notice period, and some apply the new price only at renewal. The record should say which rule applies to each plan, not just “prices are changing.”

Next verify billing dates. A monthly subscriber who renews tomorrow is in a different situation from an annual subscriber with nine months left. If the email does not mention renewal timing, support will receive the same question repeatedly. Include the first invoice date that can change, whether tax is affected, and whether customers can switch plans before the deadline.

Then prepare the reason in customer language. “Costs went up” is sometimes true, but vague. A better explanation names the product value or cost driver: larger storage limits, better export features, more usage included, higher third-party processing cost, or a clearer plan split. The reason should be honest enough that support can repeat it without adding private context.

Check the rollback path. If a billing rule is wrong, the team needs to know how to credit, refund, or restore a plan. This does not have to be visible in the customer email, but it must be clear internally before the email is sent. The worst pricing change is one where the team cannot explain or correct the first mistaken invoice.

Finally, test the announcement with three customer examples: a new free user, a current monthly paid user, and an annual customer near renewal. If the message answers all three without extra explanation, it is ready to send. If not, the pricing rule is still too ambiguous.

SaaS pricing change checklist before emailing existing customers

// COMMENTS

ON THIS PAGE