What is a retention review meeting?
A monthly session that reconciles the ARR waterfall and attaches named accounts to every line of it.Most retention reporting stops at a rate. Gross retention and net retention get read out, and the meeting moves on. Those numbers are outcomes. The retention review exists to work on the inputs, which are specific accounts that expanded, contracted, or left, and the reasons behind each.
The meeting has a second job that is easy to miss. It produces the retention half of your revenue forecast. New business forecasting gets weekly attention in most companies while renewals are treated as an assumption, which is how a plan that hits new business targets still misses total revenue.
What does the waterfall look like?
Run one reconciling waterfall by month, and let every retention metric sit on top of it.| Line | Type | What it captures |
|---|---|---|
| Beginning ARR | Opening | Ending ARR from the prior month |
| Churned Customer ARR | Contraction | Customers who left entirely |
| Churned Product ARR | Contraction | Products dropped by retained customers |
| Product Decrease ARR | Contraction | Downgrades and seat reductions |
| New Customer ARR | Expansion | ARR from customers acquired in the month |
| New Product ARR | Expansion | New products sold into existing customers |
| Increase Product ARR | Expansion | Upgrades and seat expansion |
| Ending ARR | Closing | Becomes next month's beginning ARR |
Who owns the meeting and who attends?
RevOps owns the numbers and the agenda. Customer success leadership owns the accounts.Finance belongs in the room to confirm the ARR definitions match what gets reported externally. Product leadership should attend when product-driven contraction is a recurring line, because Churned Product ARR is often a product decision showing up as a customer success problem.
Keep the attendee list to people who can commit resources. A retention review with 20 observers becomes a presentation, and presentations do not produce save plans.
What is on the agenda?
Sixty minutes, structured so the accounts get more time than the reporting.- Waterfall reconciliation for the closed month, 10 minutes, RevOps. - Contraction and churn accounts from last month, named, with reasons, 15 minutes. - Renewals closing in the next 90 days with their current category, 15 minutes. - Accounts triggering early risk signals, 10 minutes. - Save plan decisions and resource commitments, 10 minutes.
The 90-day renewal block is where the meeting earns its time. Risk found 90 days out is a workable problem. The same risk found in the renewal month is a discount negotiation.
Which early signals belong on the sheet?
Support case volume, read in both directions.ORM data shows accounts with no support cases at all are at risk, because silence usually means nobody is using the product deeply enough to hit friction. Accounts with seven or more cases in a year are also at risk, for the obvious reason. Three to five ordinary tier 2 or tier 3 cases is the healthiest pattern. Those customers are engaged, they are getting help, and they are generally satisfied.
Three more signals belong next to it:
- The executive sponsor changed roles or left the company. - Usage is flat or declining while contract value is flat. - The economic buyer has skipped the last two scheduled reviews.
Score these before the meeting and bring the list. Reviewing signals live turns an hour into a data exercise.
What decisions come out of it?
A save plan with an owner and a date for every at-risk account named in the room.Three outputs are mandatory. Every at-risk account gets a named owner and a dated first action. Every renewal in the 90-day window gets its category confirmed or changed based on evidence discussed. Every churn and contraction event from the prior month gets a reason from a fixed list rather than free text.
Use a short reason list so the data stays analyzable:
- Outcome not delivered - Sponsor departed - Budget cut or company event - Lost to competitor, named - Product gap, named - Consolidation onto another vendor
Free-text churn reasons are the most common way retention data gets destroyed. Six categories consistently applied will tell you more in two quarters than three years of narrative notes.
How does this connect to the forecast?
Renewals get forecast with the same discipline as new business, and the review is where that number is set.Treat the 90-day renewal list as a pipeline. Each renewal has an amount, a date, a category, and an owner, and the categories move on evidence rather than sentiment. Then measure yourself. Renewals get far less inspection than new business in most companies, and forecast accuracy follows inspection. Apply the same weekly discipline to the renewal list that you apply to new deals and the retention half of your number stops being an assumption.
One caution on assumptions. Retention models built on last year's behavior go stale when conditions change, and the change shows up in contraction before it shows up in logo churn. Price pressure, budget cuts, and consolidation all appear first as smaller renewals rather than as lost customers. Watching Product Decrease ARR month over month gives you an earlier read on market conditions than any churn rate will.
Frequently Asked Questions
What is a retention review meeting?
A monthly meeting that reconciles the ARR waterfall and attaches named accounts to every line in it. Each movement between beginning ARR and ending ARR gets an account list and an explanation.
Who should own the retention review?
RevOps owns the numbers and the agenda. Customer success leadership owns the accounts and the save plans. Finance validates that the ARR definitions used in the meeting match the ones used in reporting.
How often should a retention review run?
Monthly. Quarterly reviews find contraction after the renewal has already been signed at a lower number, which turns the meeting into reporting instead of intervention.
What early signals predict churn?
Support case patterns are among the most useful. ORM data shows an account with no support cases at all is at risk, an account with seven or more in a year is also at risk, and three to five ordinary tier 2 or tier 3 cases is the healthiest pattern.
What should a retention review produce?
A save plan with an owner and a date for every at-risk account named, updated renewal categories, and a churn reason recorded in a fixed category list. A review that ends without changed fields did not happen.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo