Who should move?
Segment customers by contract, tenure, usage, value received, and support burden before choosing a universal migration rule.
The new price is not the hard part · Founding edition
Your new price works. What should existing customers pay?
A seven-day decision sprint for SaaS founders weighing grandfathering, migration, notice, and retention risk after choosing a higher price.
Take the 3-minute fit check Founding enrollment closed
This is probably your decision if…
01
You have evidence for a higher new-customer price but no rule for accounts already on the books.
02
The loudest internal objection is churn, even though nobody has segmented who is actually exposed or at risk.
03
The team is drafting announcement copy before deciding the migration policy, exceptions, and success criteria.
What the sprint resolves
Turn an emotional grandfathering debate into a bounded migration decision.
What transition earns trust?
Choose notice, temporary discounts, renewal timing, and exception policy as parts of one deliberate customer promise.
What would change the decision?
Set retention, expansion, support, and revenue guardrails before sending the first announcement.
Anonymized advisory case note
One migration rule created two different renewal risks.In one packaging decision, a proposed account-size model could stabilize large enterprise organizations while destabilizing smaller contracts sitting near the existing minimum.
‘Existing customers’ was not a useful segment. Contract shape, organization size, value received, and renewal economics had to become explicit cohorts.For existing-customer price changes
Make the decision before another quarter makes it for you.
Bring one live pricing question and the customer, revenue, and usage evidence you already have. Leave seven days later with a decision memo your team can ship.
See if the sprint fits Founding enrollment closed September 1, 2026. Take the fit check or ask about the next edition. Terms · Privacy