Tiny SaaS Pricing Change Checklist

# Tiny SaaS Pricing Change Checklist

Pricing changes are risky for small SaaS products because the product often has little buffer: few support people, thin analytics, and a small set of early users who remember every previous promise. A pricing change checklist should make the change legible before it becomes a support issue.

## 1. Identify what is actually changing
Do not write “new pricing” until the moving part is clear. Is the change about plan names, seat limits, usage caps, annual discounts, legacy user treatment, trial length, or feature gates? Each one creates different user questions. A small product can usually change one or two of these at a time, but not all of them safely.

## 2. Preserve the old promise
Early users may have signed up under wording that was informal but still meaningful. Capture the old plan description, help text, and checkout copy before editing. If users ask why a feature moved, the team needs the previous promise rather than a memory of it.

## 3. Write the migration rule before the announcement
A pricing page can be simple; migration rules cannot be vague. State who keeps the old price, who moves automatically, who must choose, and when the change takes effect. If there is no migration rule, the announcement will become the migration rule under pressure.

## 4. Test the edge cases
Check canceled subscriptions, failed payments, annual plans, coupon users, manually upgraded accounts, and users with more seats than the new plan allows. These cases are easy to ignore until the first support ticket arrives.

## Example
Bad: “We are simplifying our pricing next month.”
Better: “Plan names change on July 1. Existing paid users keep their current monthly price. New usage caps apply only after renewal. Annual customers are unchanged until their current term ends.”

## Practical rule
If the change cannot be explained in one paragraph plus a migration table, it is probably too complex for a tiny SaaS team to support cleanly.

Tiny SaaS Pricing Change Checklist

// COMMENTS

ON THIS PAGE