How should a CRO structure renewal forecasts differently from new-business pipeline to predict cash retention?

Question

Pulse RevOps · The Machine · Accepted Answer

## Direct Answer Renewal forecasts must separate by **cohort + contraction risk**, not stage. Model at **contract-renewal-date granularity** (not quarter), and weight by **actual historical churn-by-cohort** (not salesperson confidence). A typical SaaS structure uses **3 tiers**: Base (91–100% renewal rate), At-Risk (60–90%), and Churn-Pending (<60%), weighted against net-dollar-retention (NDR) trending in that segment. ## Operator Playbook ### 1. Segment renewals by cohort + expansion path, not salesperson - **Cohort maturity matters:** A 12-month customer renews at 85% probability; a 36-month customer at 96%. New-business pipeline assumes binary win/loss; renewals assume _partial_ loss (contraction) or multi-year holds. - **NDR is the forecast anchor:** If cohort ABC12 shows 110% NDR, renewal risk is low even if base-contract risk is medium. New business has no equivalent. - **Vendors:** Gainsight (Forecast Ops module) and Catalyst both cohort-slice renewal propensity at scale; Vitally flags expansion/contraction on a per-account basis. ### 2. Build a risk-tier model tied to real churn drivers Instead of "50% probable close", use account-level churn signals: | Risk Tier | Churn Rate (Historical) | Triggers | Forecast Weight | Example Tools | |-----------|---|---|---|---| | **Base (Green)** | 5–9% | Usage >80%, NPS >40, no seat reductions | 95% renewal | Totango usage scoring | | **At-Risk (Yellow)** | 25–50% | Usage drop >30%, support tickets >3/mo, seat shrink, exec sponsor left | 70% renewal | ChurnZero health score | | **Churn-Pending (Red)** | 60–85% | Net churn (revenue lost to downsell) >20%, no engagement 90+ days, RFP issued | 20% renewal | Pavilion AI intent data | **Build this model from YOUR historical data**, not templates. If your base cohort churned at 12% last cycle, use **12%**, not industry benchmark. ### 3. Forecast at contract-renewal-date granularity, not quarter - **New-business pipeline:** Salesperson says "I'll close $500K this quarter." - **Renewal forecast:** Say "Cohort 2024-H1 has $8.2M up for renewal on 2025-06-15; I forecast $7.7M base + $440K contraction + $900K expansion = $9.04M NDR." - **Gainsight** and **Catalyst** let you date-anchor and cohort-filter; **Bridge Group** has benchmarks by company size and vertical to sanity-check your forecast. - **Calendar lock:** CSM manager owns the renewal-date view; AE pipeline manager owns new. Non-overlapping ownership kills forecast double-counting. ### 4. Link forecast to cash, not bookings - **New business:** Bookings = cash (mostly). - **Renewals:** Bookings ≠ cash if you allow multi-year lock-in or monthly payment plans. Forecast the **cash inflow date**, not signature date. - **Vendor:** **Vitally** and **Totango** reconcile contract-vs-payment-schedule for accuracy. ### 5. The CSM → AE handoff - **CSM drives renewal risk forecast** (is this account staying, contracting, or churning?). - **AE owns expansion asks** (can we upsell into that At-Risk segment?). - **Separate scorecard:** If a CSM nails health-score accuracy but the AE missed 70% of expansion in At-Risk accounts, you see the gap. (Pavilion and Bridge Group show this breakdown.) ## Forecast Model ```mermaid graph LR A["Renewal Queue
(by contract date)"] --> B["Cohort + Historical Churn"] --> C["Risk Tier
(usage, NPS, seats)"] --> D{"NDR trending?"} D -->|>110%| E["95% forecast +
expansion upside"] D -->|80–110%| F["70% forecast +
selective upsell"] D -->|<80%| G["20–40% forecast +
save motion"] E --> H["Cohort Net Revenue
Forecast"] F --> H G --> H H --> I["Aggregate by month
→ Cash plan"] ``` **Bottom line:** Renewals forecasts live in contract-cohort time, not salesperson time, and weight by churn-prediction (not sales confidence). Separate CSM health signal from AE expansion signal, and reconcile forecast against actual cohort churn rates monthly. Most operators miss that the forecast error in renewals is 3x new business because they treat it like pipeline instead of a retention model. TAGS: renewals,forecasting,churn,revenue-ops,ndr,csm,risk-scoring,cash-flow

Risk Tier	Churn Rate (Historical)	Triggers	Forecast Weight	Example Tools
Base (Green)	5–9%	Usage >80%, NPS >40, no seat reductions	95% renewal	Totango usage scoring
At-Risk (Yellow)	25–50%	Usage drop >30%, support tickets >3/mo, seat shrink, exec sponsor left	70% renewal	ChurnZero health score
Churn-Pending (Red)	60–85%	Net churn (revenue lost to downsell) >20%, no engagement 90+ days, RFP issued	20% renewal	Pavilion AI intent data

How should a CRO structure renewal forecasts differently from new-business pipeline to predict cash retention?

Direct Answer

Operator Playbook

1. Segment renewals by cohort + expansion path, not salesperson

2. Build a risk-tier model tied to real churn drivers

3. Forecast at contract-renewal-date granularity, not quarter

4. Link forecast to cash, not bookings

5. The CSM → AE handoff

Forecast Model

What does the score mean?