Most churn is not a surprise to the people who work the account. It is a surprise to the people who never sat down and looked. A churn risk review is a short, repeatable meeting where your team looks at every account up for renewal, decides which ones are at risk and assigns a specific next step. This guide gives you a 30-minute agenda, a scoring rubric and a template you can copy today.

Why a standing churn risk review matters

Retention has become harder to take for granted. In the 2026 Aleph and Benchmarkit report, which draws on 342 B2B SaaS and AI-native companies, median gross revenue retention (GRR) fell to 84% in 2025, and the 75th percentile dropped from 95% to 91%. Aleph describes this as a market-level shift, not a few companies missing targets.

Net revenue retention (NRR) matters too, because expansion can hide losses. SaaS Capital calls NRR generally the retention metric it considers most important, and reports a median NRR of 102% for private companies with ACVs of $25,000 to $50,000. If your own numbers sit below the benchmark for your segment, a review process is one of the cheapest fixes. For more on how the two metrics differ, see our guide to NRR vs GRR.

The review does three things that dashboards alone do not:

  • It forces a decision on every flagged account, not just a glance at a chart.
  • It puts an owner and a date next to each risk.
  • It surfaces patterns across accounts, such as the same missing feature coming up three times.

Before the meeting: prepare in 15 minutes

Keep the meeting short by doing the data work beforehand. Whoever runs the review (usually the CS manager or RevOps) should prepare one list.

  1. Pick the scope. Include every account renewing in the next 120 days, plus any account with a major risk signal regardless of renewal date. If you have a 40-account book per CSM, that is usually 6 to 12 accounts each.
  2. Pull the same fields for every account. Use the same columns every time so the team learns to read them quickly: ARR, renewal date, health score, usage trend, last meaningful contact, open escalations, champion status.
  3. Ask each CSM to pre-mark their own risk level (green, yellow, red) before the meeting. Disagreements between the pre-mark and the data are the most useful part of the discussion.

If you use an AI assistant to help assemble the list, keep personal data to what you need and follow your company's data policy. Our post on AI prompts for customer success managers includes a privacy checklist.

The signals to review

Do not try to look at everything. Statisfy's guide to churn risk signals groups them into five that are worth checking on every account:

  • Declining product usage: fewer logins or sessions, users who stop engaging, abandoned key features.
  • Low or falling NPS and CSAT: a drop is often more telling than the absolute score.
  • Loss of a champion: an advocate leaves or becomes less involved.
  • Absence of engagement: slower replies to emails and surveys, skipped training and meetings.
  • Negative feedback and support problems: repeated tickets about the same issue, escalations, complaints.

Look at change over time, not just the current level. An account with a steady 12 sessions a week is not the same as one that fell from 40 to 12. Add two commercial signals your finance team can supply: overdue invoices and a request to reduce seats or scope.

The 30-minute agenda

Run the meeting weekly or every two weeks. Hold the time limits strictly; if a topic needs more, schedule a separate working session for that account.

CHURN RISK REVIEW - 30 MINUTES

0:00-0:03  Scorecard
           Renewals due in 120 days, ARR at risk, changes since last review

0:03-0:08  Resolved and improved
           Accounts that moved from red to yellow or yellow to green. What worked?

0:08-0:25  Red and new-yellow accounts (about 3 minutes each)
           For each account, answer in order:
           1. What is the risk, in one sentence?
           2. What evidence supports it?
           3. Who is the executive sponsor and champion today?
           4. What is the next action, who owns it, by what date?
           5. Do we need help (exec sponsor, product, support, discount approval)?

0:25-0:28  Patterns
           Any repeated cause across accounts? Product gap, onboarding gap,
           pricing, competitor, support quality.

0:28-0:30  Recap
           Read back every action, owner and date. Confirm they are logged.

A simple risk rubric

Debate wastes time when everyone uses a different definition of "at risk." Agree on a rubric and use it consistently. Here is one you can adapt. Score each account by counting the red flags.

RISK RUBRIC (example - adjust to your product)

Red flags (1 point each)
[ ] Usage down 30% or more versus the prior 90 days
[ ] No meaningful contact in 45+ days
[ ] Champion left or changed roles
[ ] No executive sponsor identified
[ ] NPS detractor response or CSAT drop in the last 90 days
[ ] Two or more open escalated tickets, or a repeated issue
[ ] Invoice overdue by 30+ days
[ ] Customer asked to cut seats, scope or price
[ ] Competitor mentioned

0-1 points = Green: monitor
2-3 points = Yellow: action plan this week
4+ points   = Red: escalate, exec involvement, review weekly

The thresholds above are illustrative, not a benchmark. After a quarter, compare your scores to what actually happened and tune them. Our post on the customer health score formula shows how to weight signals and test them against past churn.

Turning risk into an action plan

A risk without a next step is just a worry. For each red or yellow account, write one action plan using this format:

Account: [name]            ARR: [amount]        Renewal: [date]
Risk level: [yellow/red]   Owner: [CSM]
Root cause (one sentence): [e.g. champion left; new admin never trained]
Evidence: [usage, tickets, conversation notes]
Recovery action: [what we will do]
Due date: [date]
Support needed: [exec call, product fix, finance approval]
Success looks like: [e.g. new admin trained, usage back above X by date]

Match the action to the root cause:

  • Champion lost: ask for an introduction to the replacement within a week, and offer a short re-onboarding session. Find a second contact so you are never single-threaded again.
  • Usage dropped: find out which team or feature went quiet, then offer targeted training or a working session on their actual use case.
  • Support frustration: review the open tickets together with support, and have a named person own the resolution and report back to the customer.
  • Value not proven: bring data on what they achieved, and rebuild the success plan around outcomes they care about.
  • Budget pressure: discuss scope and terms early, before the renewal conversation is forced by a deadline. Our renewal timeline checklist shows what to do at 120, 90, 60 and 30 days out.

Common mistakes

  • Reviewing only the loud accounts. Silent accounts churn too. Always include those with no recent contact.
  • Letting the CSM's gut overrule the data without discussion. Optimism is fine, but ask what evidence supports it.
  • Skipping the follow-up. Start every review by checking last meeting's actions. If nothing was done, ask why.
  • Treating it as a reporting meeting. If nobody leaves with a task, shorten it or cancel it.
  • Never closing the loop. When an account churns or is saved, note the real reason. This is how your rubric improves.

Make it stick: a 30-day rollout

  1. Week 1: agree on the rubric and the fields. Run the first review with one team.
  2. Week 2: log every action as a task with an owner and due date.
  3. Week 3: check completion rate and note which signals predicted correctly.
  4. Week 4: adjust the rubric, then make the meeting a standing calendar event.

Try it in XPI CRM

In XPI CRM, the health score (0 to 100) combines seven factors: usage trend, engagement, sentiment, NPS, billing, open work and support tickets. It places each client in Healthy, At Risk or Critical, and alerts you to usage drops, missing contact, overdue invoices, detractors and at-risk renewals. That gives you a ready-made list for the review, with renewals, tasks and playbooks in the same place. See the help guides for setup.

Start free — every feature included, no credit card.