Building a Renewal Forecasting Process Separate From New Business

In most B2B SaaS companies at the $3M–$10M ARR stage, renewal management lives in one of two inadequate places: either informally in the heads of CSMs who know which accounts are happy and which are not, or in the new business pipeline where renewal opportunities sit alongside new deals with no differentiation in risk profile or management process.

Both approaches produce the same outcome: surprises. A CSM who knew a customer was unhappy did not flag it to finance because there was no process for doing so. A renewal opportunity sitting in the pipeline at 70% probability turns out to have a 0% probability because the champion left three months ago and nobody was tracking that.

A renewal forecasting process that is designed as a distinct operational workflow — with its own pipeline, its own health score inputs, its own forecast categories, and its own review cadence — produces accurate ARR retention predictions rather than end-of-month surprises. This guide covers the design of that process from the CRM architecture through the weekly operating cadence.

Why Renewal Forecasting Is Fundamentally Different From New Business Forecasting

The intuition that renewal forecasting is just like new business forecasting — assign a probability, multiply by ARR, sum across deals — breaks down because the signals that predict renewal outcomes are completely different from the signals that predict new business close.

New business forecasting relies on: deal stage progression, rep activity (calls, meetings, proposals sent), economic buyer engagement, and competitive positioning. These signals are all within the sales team's direct observation and control.

Renewal forecasting relies on: product usage patterns, support ticket sentiment, executive sponsor stability, champion employment status, competitor evaluations initiated by the customer, and the CSM's relationship quality with the account. None of these signals come from a sales pipeline — they come from a customer success operational data model that most sales forecasting processes do not touch.

When renewal ARR is tracked in the new business pipeline, it inherits the probability assumptions calibrated for new business — deal stage completion rates, rep attainment distributions — that do not apply to renewal scenarios. A renewal in the "Proposal Sent" stage is not the same as a new deal in the "Proposal Sent" stage. The renewal's probability of closing depends on health scores and champion stability, not on proposal content and competitive differentiation.

According to SaaS Capital's annual B2B SaaS survey, companies with dedicated renewal forecasting processes — separate from new business, with health score inputs — achieve median NRR 8 percentage points higher than companies relying on informal renewal management. The mechanism is intervention timing: when at-risk accounts are identified 90 days before renewal rather than 30 days before, there is enough time to address the underlying issues.

The Renewal Pipeline Architecture

The first operational step is creating a dedicated renewal pipeline in the CRM. This is a separate set of opportunity records with renewal-specific stage definitions and fields.

Renewal Opportunity Creation Timing:

Renewal opportunities should be created automatically by a CRM workflow triggered when the remaining contract term reaches 120 days. Earlier than 120 days, the renewal is not operationally urgent. Later than 90 days, there is insufficient time for meaningful intervention on at-risk accounts.

The automated creation workflow should:

1. Identify all customer accounts with Contract End Date between 90 and 120 days from today
2. Check whether a renewal opportunity already exists for the account (to prevent duplicates)
3. Create a renewal opportunity with: Account = current customer account, Owner = assigned CSM, ARR = current contract ARR, Renewal Date = contract end date, Stage = "Renewal Identified"
4. Create a task for the CSM to complete a health assessment within 14 days

Renewal Stage Definitions:

• Renewal Identified: Renewal opportunity created. Health assessment not yet completed.
• Health Assessment Completed: CSM has reviewed all health signals and assigned a health score for the account. Renewal risk level determined (Low, Medium, High).
• Renewal Conversation Initiated: CSM has had the first explicit renewal conversation with the customer's primary contact.
• Terms Agreed: Commercial terms for the renewal (including any price changes, seat adjustments, or contract modifications) have been verbally agreed upon. Contract is being prepared.
• Renewed: Signed renewal contract received. ARR updated in billing system.
• Churned: Customer has confirmed non-renewal. Churn ARR recognized in the reporting period containing the contract end date.
• At-Risk: A health assessment revealed significant churn signals. Intervention plan in progress. A lateral stage that can be combined with any of the above (e.g., "At-Risk + Renewal Conversation Initiated").

Renewal-Specific Fields:

Required fields on the Renewal Opportunity:

• Current ARR (the existing contract ARR)
• Renewal ARR (the ARR being quoted for the renewal — may include expansion or contraction)
• Health Score (at the time of the health assessment)
• Risk Level (Low / Medium / High / Critical)
• Champion Employment Status (Confirmed Employed / Departed / Unknown)
• Last QBR/EBR Date
• Renewal Forecast Category (Commit / At-Risk / Lost — the CSM's classification)
• Last Renewal Conversation Date
• Churn Reason (required if Stage = Churned — controlled picklist)

Building the Customer Health Score

The health score is the quantitative backbone of the renewal forecast. A health score that accurately predicts renewal vs. churn converts the renewal forecast from CSM intuition to a structured, auditable prediction.

Health Score Component Design:

The health score should aggregate leading indicators that have been validated against historical renewal outcomes. For most B2B SaaS companies, the most predictive components are:

Product Usage Score (weight: 30%): Calculated from product analytics data — active users / contracted seats ratio (seat utilization), feature adoption depth (are customers using core features or only surface-level features?), and session frequency (daily, weekly, monthly active users relative to expected usage patterns for the use case). A customer using 30% of their contracted seats and only the most basic features is at high churn risk regardless of what they tell their CSM.

Support Health Score (weight: 15%): Volume and sentiment of support interactions. High unresolved ticket volume, tickets with negative sentiment flags, or escalations to engineering signal operational friction. This component should use the support ticketing system data, not just the CSM's impression of support interactions.

Engagement Score (weight: 15%): Recency and depth of CSM engagement with the account. Last QBR date, number of business reviews conducted in the last 12 months, executive sponsor engagement (last contact with a VP or above), and multi-threaded contact depth (number of stakeholders engaged at the account beyond the primary contact).

Relationship Stability Score (weight: 20%): Champion employment status (verified via LinkedIn or direct contact), executive sponsor change in the last 6 months, and org restructuring signals (company acquisition, layoffs, or leadership changes that might affect the buying decision). This component is qualitative but high-weight because champion departure is one of the strongest predictors of churn.

Financial Health Signals (weight: 10%): Payment history (on-time vs. late payments), invoice disputes, requests for billing adjustments. Financial friction often precedes formal non-renewal notifications.

Voice of Customer Score (weight: 10%): NPS scores, CSAT ratings, case study and reference willingness. A customer with an NPS of 9 who has provided a case study is a very different renewal risk than a customer with an NPS of 5 who has declined multiple reference requests.

The composite health score should produce a 0–100 scale. Calibrate the thresholds against historical data: what health score did churned customers have 90 days before churning? What was the threshold below which the churn rate exceeded 30%? These thresholds determine the "At-Risk" and "Critical" classifications.

For additional context on churn signals and their predictive value, see the SaaS Early Warning Churn Signals post and Churn Root Cause Taxonomy.

The Renewal Forecast Categories

With the health score and renewal pipeline in place, the forecast categorization follows a structured decision tree:

Commit: Renewal is high-confidence. All of the following are true:

• Health score above 75
• Renewal conversation initiated and customer expressed intent to renew
• Champion is confirmed employed and engaged
• No open unresolved support escalations
• Last QBR completed within 90 days
• Renewal Forecast Category: Commit (CSM designation)

Expected renewal probability: 90–95%. Finance includes full Commit ARR in the renewal forecast.

At-Risk: Renewal has meaningful churn signals. One or more of the following:

• Health score between 40 and 75
• Champion employment status unknown or recently changed
• Renewal conversation not yet initiated with 45 days until renewal
• Open unresolved support escalations
• CSM designates as At-Risk

Expected renewal probability: 40–60% (calibrate from historical data). Finance applies a 50% haircut to At-Risk ARR in the renewal forecast.

Critical At-Risk: Strong churn signals. One or more of the following:

• Health score below 40
• Champion has departed and no replacement identified
• Customer has explicitly raised budget concerns or non-renewal signals
• Customer is known to be evaluating competitors

Expected renewal probability: 10–30%. Finance applies a 75% haircut to Critical ARR. Escalation to VP of CS required.

Lost: Churn confirmed. Customer has notified of non-renewal or contract has passed the renewal date without a signed renewal. ARR is recognized as Churned in the period.

Upside: Not in the base renewal pipeline, but there is a realistic path to expansion ARR from a known renewal conversation. Tracked separately from base renewal to avoid double-counting expansion in the NRR forecast.

The Renewal Forecast Operating Cadence

A renewal forecast is a living document, not a monthly report. The cadence that keeps it current is a weekly review combined with monthly rollup reporting.

Weekly Renewal Review (30 minutes — CS Leadership + RevOps):

Agenda:

• Renewals due in the next 30 days: status by account, ARR at stake, action required
• Newly identified At-Risk or Critical accounts: what changed, intervention plan
• Renewals that moved from At-Risk to Commit: what intervention worked (build the playbook)
• Confirmed churns: churn reason, ARR amount, early warning sign in retrospect
• Net change in renewal forecast since last week

Output: Updated renewal forecast spreadsheet, escalation tickets for Critical accounts, playbook updates for successful interventions.

Monthly Renewal Forecast Report (Finance + CS Leadership):

The monthly report shows:

• Total ARR up for renewal in the next 90 days by bucket (Commit / At-Risk / Critical / Lost)
• Probability-weighted expected renewal ARR
• Expected NRR calculation (renewal ARR + expansion ARR - churned ARR / beginning ARR)
• Renewal forecast accuracy vs. prior month predictions (actuals vs. forecast)
• Trend in health score distribution across the customer base

The monthly report is the input to the finance team's NRR line in the financial model. For accurate ARR forecasting, see SaaS ARR Forecasting and NRR Calculator and Net Revenue Retention Guide.

Intervention Playbooks for At-Risk Accounts

A renewal forecast identifies which accounts need intervention. The intervention playbooks define what the intervention looks like for each risk signal.

Champion Departure Playbook:

1. Identify the departed champion's replacement within 14 days (LinkedIn research, internal company org chart, direct outreach to the account)
2. Request an introduction from any remaining contacts at the account
3. Schedule an onboarding conversation with the new champion to understand their priorities, reintroduce the product's value proposition, and establish the new relationship
4. Conduct an Executive Business Review with the new champion and their manager within 30 days
5. If no replacement is found within 30 days, escalate to VP of CS and potentially VP of Sales for executive outreach

Low Usage Playbook:

1. Identify the specific adoption gap (which seats are unused, which features are underutilized)
2. Schedule a product training session targeting the adoption gap
3. Create a 30-day usage improvement plan with specific metrics (target: seat utilization above 70%)
4. Assign a customer success engineer to provide hands-on support for feature adoption if technical barriers are present
5. Review progress at 30-day mark; if usage has not improved, escalate to an at-risk intervention that includes commercial discussion

Budget Risk Playbook:

1. Confirm the budget concern is real (ask directly: "Is budget a constraint for the renewal? What would need to be true for us to work within your budget?")
2. Quantify the ROI the customer is getting from the product (use usage data and customer-provided metrics)
3. Explore contract restructuring options: multi-year discount, seat reduction with expansion option, payment terms flexibility
4. Involve finance and deal desk for any commercial accommodation
5. Escalate to VP of CS and account executive if the deal requires executive involvement

Measuring Renewal Forecast Accuracy

The renewal forecast is only useful if it is accurate. Track accuracy by comparing predicted renewal ARR (from the forecast at 90 days and 30 days before renewal) to actual renewal ARR.

Forecast accuracy at T-90: What percentage of total renewal ARR expected to renew at the 90-day mark actually renewed? A well-calibrated renewal forecast should achieve 85–90% accuracy at the 90-day mark for accounts in the Commit bucket.

At-Risk conversion rate: What percentage of At-Risk accounts at the 90-day mark were saved vs. churned? Track this by intervention type to identify which playbooks are most effective.

Churn surprise rate: What percentage of churns in a given month were not flagged as At-Risk at the 90-day mark? A churn surprise rate above 20% indicates the health score model is missing signals. Audit recent surprises to identify which signal would have caught the at-risk status earlier.

Frequently Asked Questions

Why does renewal forecasting need to be separate from new business forecasting?

Renewal forecasting uses different input signals (health scores, champion stability, product usage) than new business forecasting (deal stage, rep activity, competitive positioning). Mixing them creates category errors — renewal risk appears as solid pipeline and new business expansion gets mixed with base renewal.

What data inputs are required for a renewal forecast?

Required inputs: renewal date and ARR, customer health score, last QBR date, champion employment status, executive sponsor engagement, and CSM forecast sentiment (subjective assessment of renewal likelihood).

What is the ideal timeline for renewal management?

T-120 days: Renewal Opportunity created, health assessment initiated. T-90: health review completed, at-risk accounts identified. T-60: renewal conversation initiated. T-30: renewal proposal sent. T-0: contract signed or churn confirmed.

How do you build a customer health score for renewal forecasting?

A health score aggregates: product usage (30%), support health (15%), engagement recency (15%), relationship stability/champion status (20%), financial health signals (10%), and NPS/CSAT (10%). Calibrate the weights against historical renewal vs. churn outcomes.

What is the renewal forecast accuracy metric?

Compare predicted renewal ARR (at T-90 and T-30) to actual renewal ARR. Track Commit bucket accuracy (target: 85–90%), At-Risk conversion rate (saved vs. churned), and churn surprise rate (churns not flagged as At-Risk at T-90 — target: below 20%).

Conclusion

A renewal forecasting process that is separate from new business, grounded in health score data, and reviewed on a weekly cadence gives customer success and finance teams a shared, accurate view of ARR retention. It surfaces at-risk accounts with enough lead time to intervene, provides finance with a reliable NRR forecast for cash planning, and creates the accountability structure that drives CS team behavior toward the actions that actually prevent churn.

The companies that build this process before they reach $10M ARR are the ones that maintain NRR above 110% at scale — not because their product is necessarily better, but because their operational process for managing renewals is systematically better.