The Pricing Migration Risk Mapper: Turn a Billing Model Switch Into a Churn-Ranked Rollout Plan

Why this prompt matters
Pricing migrations announced without segment-level risk mapping lose the customers least able to absorb the change first, and that churn typically surfaces 60 to 90 days after the switch — well past the point where the rollout can still be adjusted, and after the board has already signed off on a retained-revenue projection the churn then quietly invalidates.
What we use it for
A SaaS company's finance and product teams have finalized a switch from per-seat to usage-based billing starting next quarter, and the person running the migration has been handed a spreadsheet of 40 customer accounts with rough usage estimates two days before briefing the board on rollout risk — with no time to build a segment-by-segment model from scratch.
Prompt
Role: Act as a senior SaaS pricing strategist who has run pricing migrations for B2B software companies and has seen which customer segments churn when billing models change. Context: My company is switching from [CURRENT PRICING MODEL, e.g. "flat per-seat pricing at $49/user/month"] to [PROPOSED PRICING MODEL, e.g. "usage-based pricing billed per API call, roughly $0.002/call with a $500/month minimum"]. The change takes effect on [LAUNCH DATE]. Here is my customer segment data: [PASTE A TABLE OR LIST WITH: SEGMENT NAME, NUMBER OF ACCOUNTS, CURRENT MONTHLY REVENUE, ESTIMATED USAGE PATTERN UNDER THE NEW MODEL (e.g. "high seat count, low usage" or "low seat count, high usage"), CONTRACT RENEWAL DATE, ANY KNOWN CHURN RISK SIGNALS LIKE RECENT SUPPORT TICKETS OR DECLINING LOGINS] Task: 1. For each segment, estimate whether their bill goes up or down under the new model, and by roughly what percentage. 2. Rank every segment by churn risk, weighing both the bill change and the churn risk signals I provided. 3. For the top 3 highest-risk segments, write a specific retention argument I could make to them that isn't just "sorry, here's a discount" — identify what they're actually buying from us that the new pricing model undervalues or overvalues for their specific usage pattern. 4. Flag any segment where the bill increase is large enough that losing them would be a net win for margin, not a loss worth fighting to prevent. Constraints: - Do not recommend delaying or scrapping the migration — assume the business decision to switch pricing models is already final. - Do not suggest "grandfather clauses for everyone" as a blanket fix — treat grandfathering as a tool to use selectively, and say exactly which segments should get one and why. - Flag any segment where you don't have enough data to make a confident risk call, rather than guessing. - Keep the retention arguments specific to each segment's actual usage pattern, not generic value-proposition language. Output Format: A ranked table: Segment | Bill Change (%) | Churn Risk (High/Medium/Low) | Key Risk Signal | Recommended Action. Followed by a section titled "Segments Worth Losing" (if any apply) and a section titled "Retention Scripts for Top 3 At-Risk Segments" with one paragraph per segment.
Result
| Segment | Bill Change | Churn Risk | Key Risk Signal | Recommended Action |
|---|---|---|---|---|
| Mid-Market Dormant Seats (8 accounts, $31K MRR) | +140% avg | High | 23 seats billed per account on average, but only 4 active logins/seat/month — the new model exposes unused capacity instantly | Proactive outreach before the first new invoice lands; offer a guided usage-based onboarding call |
| Enterprise Power Users (5 accounts, $58K MRR) | -35% avg | Low | Already high API call volume per seat; contract renewal in 45 days | Fast-track renewal under the new model as a retention win, not a risk to manage |
| SMB High-Frequency (12 accounts, $19K MRR) | +210% avg | High | Small teams running heavy automation workflows; 3 accounts have open support tickets about API rate limits | Needs a capped or hybrid plan option before renewal — a conversation alone won't fix this |
| Agency Multi-Client (6 accounts, $27K MRR) | +15% avg | Medium | Usage scales with their own client count, which is currently growing — net positive for us if retained | Standard migration communications; no special handling needed |
Segments Worth Losing: None of the four segments cross the threshold where losing them nets a margin win. Even Mid-Market Dormant Seats, despite the steepest bill increase, represents $31K in MRR at close to 100% gross margin given how little they actually use the product — losing them would cost more than retaining them at a temporary discount.
Retention Scripts for Top 3 At-Risk Segments:
Mid-Market Dormant Seats: Lead with the fact that they're currently paying for 23 seat licenses but only 4 people log in monthly. Frame the usage-based switch as them finally paying for what they use, not a punishment, and offer a 90-day true-up period where their bill is capped at their current rate while they right-size actual usage internally.
SMB High-Frequency: These accounts are heavy users precisely because the product works well for them — don't discount. Offer a capped-usage tier at a predictable monthly rate slightly above their current bill, framed as "built for teams running this hard," which protects margin while solving their real objection (unpredictable billing), not the price itself.
Agency Multi-Client (if risk rises): Position the usage-based model as aligned with their own growth — their bill only climbs because their client roster is climbing, which is the argument their own clients are paying them to make. Tie our pricing language directly to language already in their client contracts.
Most pricing-migration advice stops at "communicate early and offer a transition period," which is true and also useless at the level this prompt operates on: deciding which of your actual named accounts are about to have a genuinely bad month. The real risk in a pricing switch isn't the average customer — averages always look fine — it's the specific segment whose usage pattern happens to collide badly with the new billing logic.
The prompt's first instruction is deliberately mechanical: estimate the bill change per segment before making any risk judgment at all. This matters because churn risk and bill increase don't correlate the way most people assume. A segment can absorb a 200% bill increase without blinking if the absolute dollar amount is trivial to them, while a 20% increase on an already-skeptical account can be the final straw. Separating "what changes" from "who's actually at risk" stops the model from collapsing both questions into one fuzzy judgment call.
The constraint against "grandfather clauses for everyone" exists because that's the default advice most generic pricing frameworks give, and it quietly erases the entire margin benefit of the migration. Forcing the model to name which specific segments earn an exception, and why, turns the output into an actual decision instead of a hedge that avoids making one.
The "Segments Worth Losing" section is the part most pricing frameworks skip entirely, because it's uncomfortable to write "fighting to keep this account loses you money." It's often the single most useful line in the whole analysis, because retention effort is finite — a team that doesn't know which accounts aren't worth fighting for ends up spending equal energy on all of them, including the ones where winning the fight is itself a loss.
Use case: a SaaS company's finance and product teams have finalized a switch from per-seat to usage-based billing starting next quarter, and the person running the migration has been handed a spreadsheet of 40 customer accounts with rough usage estimates two days before briefing the board on rollout risk — with no time to build a segment-by-segment model from scratch.
Why it matters: pricing migrations announced without segment-level risk mapping lose the customers least able to absorb the change first, and that churn typically surfaces 60 to 90 days after the switch — well past the point where the rollout can still be adjusted, and after the board has already signed off on a retained-revenue projection the churn then quietly invalidates.
This works best once you already have rough usage estimates per account — it's a risk-ranking tool, not a usage-forecasting one. It's the wrong prompt to reach for before you have any usage data at all; feed it guesses and it will rank your guesses with total confidence, which is worse than no ranking at all.