Skip to main content

SaaS pricing change checklist

Work through customer, billing, sales, and support tasks before a pricing change goes live. Each task has an optional note field for an owner, due date, or link — check items off as you complete them, then export the whole checklist (with your notes) to a branded PDF or a CSV for your team.

Frequently asked questions

Should I grandfather existing customers at their old price?

It depends on the size of the increase and how price-sensitive your base is. Grandfathering existing customers avoids a churn spike and preserves goodwill, but caps the revenue benefit of the change to new signups only, sometimes for years. A common middle ground is grandfathering for a fixed window (e.g. 12 months) with advance notice that the new price applies after that, which gets you the revenue benefit while still giving existing customers time to adjust.

How much notice should I give customers before a price increase?

30 days is the common minimum for a straightforward increase, and 60–90 days for larger increases (more than 20%) or for annual-plan customers who need to budget for the renewal. Whatever window you choose, put the effective date in the notification itself rather than "in the coming weeks" — vague timing is one of the most common sources of support tickets after a pricing announcement.

What is a rollback threshold and why set one before launching?

A rollback threshold is a specific, pre-agreed metric and value — for example, "if 30-day churn among affected accounts exceeds 2x baseline" — that triggers a decision to pause or reverse the change. Deciding this before launch matters because after launch you're reading noisy day-to-day data under pressure, which makes it hard to tell a normal blip from a real problem. Having the threshold and an owner agreed in advance turns that judgment call into a simple check.

Share this tool