Answer · Renewal Forecast

What is a renewal forecast?

A renewal forecast is not the same as a new sales forecast. It covers the installed base, runs on health scores and usage data, and gets owned by customer success rather than new logo sales.

Start free trial See pricing

Short answer

A renewal forecast is a committed prediction of how much contracted revenue a company will retain, lose, or expand across a defined period, usually the next quarter or year. It combines the renewal book of business, per-account risk tiers, health signals, and customer success manager judgment. The output rolls up into gross retention, net retention, and churn commits that leadership plans the business against.

Key points

What matters most.

The six things every revenue leader should know before building, running, or buying a renewal forecasting process.

The core definition

A renewal forecast predicts retained, lost, and expansion revenue.

A renewal forecast projects what portion of contracted revenue in the installed base will renew, churn, downgrade, or expand across a period. It is a committed number, submitted on a cadence, and tracked against actual renewal outcomes. The forecast feeds gross retention, net retention, and churn planning the board sees every quarter.

The book of business

Every account up for renewal in the window gets a call.

The renewal book is every contract with an end date in the forecast window. Each account carries a renewal amount, a target close date, a risk tier, a health score, and an owner. The book is the universe. The forecast is the committed number against that universe, split by category the same way a new sales forecast is.

The risk tiers

Green, yellow, red map health to likelihood.

Mature teams tier every renewal account green, yellow, or red. Green is a near-certain renewal, usually paired with expansion. Yellow is a renewal with friction, requires active work, and may downgrade. Red is at serious churn risk and triggers a save play. The tiers roll up into the forecast categories and change weekly as health signals move.

The math

GRR, NRR, and logo retention each tell a different story.

Gross retention tracks revenue kept, ignoring expansion. Net retention adds expansion on top. Logo retention counts customers kept regardless of dollar value. A healthy renewal forecast surfaces all three so leadership can see whether a strong NRR is masking a weak GRR, which usually signals large customers growing while small ones churn.

The cadence

Weekly submit by CSMs, monthly rollup to leadership.

Customer success managers update their renewal calls weekly, flagging movement in tier, risk, and expected amount. The number locks each Friday. Monthly, the rollup rolls to the VP of Customer Success and the CRO. Quarterly, every submit is reconciled against actual renewals and CSM accuracy scores update, same as rep accuracy scores on the new sales side.

The owner

Customer success owns the forecast, not new sales.

A renewal forecast is owned by customer success leadership, not the new logo sales org. The signals are different, the plays are different, and the compensation plans are different. Treating renewals as sales forecast line items hides churn risk until it is too late to run a save play. Separating the two surfaces produces more honest numbers on both sides.

The model explained

How a renewal forecast is built from the account up.

A good renewal forecast is layered. The account carries a health score, the health score maps to a risk tier, the risk tier maps to a forecast category, and the categories roll up to GRR and NRR commits. Each layer feeds the one above it. Change a signal at the bottom and the committed number updates on its own.

Health score

Product usage, support tickets, and relationship signals combine.

The health score blends product usage trend, support ticket volume and tone, executive sponsor engagement, invoice payment history, and NPS or CSAT where available. The score is numeric, bounded, and updated at least weekly. The best scores weight recent signals heavier than old ones so a sudden drop in logins shows up before the renewal meeting.

Risk tier

Score bands map to green, yellow, or red.

The health score bucket drives the risk tier. Teams tune the band thresholds against their own churn history so the tiers reflect reality, not a default. A score above eighty might be green at one company and yellow at another. The tier is what the CSM, the manager, and the VP see on every forecast surface, not the raw number.

Forecast category

Tier plus CSM judgment lands on commit, best case, or risk.

Green accounts default to commit. Yellow accounts default to best case. Red accounts default to risk or omit. The CSM can override the default with a written reason, which gets audit logged. The override exists because tier is a signal, not a verdict. A green account can still have a buying committee change nobody saw coming.

Expansion stack

Upsell and cross-sell sit on top of the base renewal.

Every renewal line item carries a base amount and an expansion amount. The base is what renews flat. The expansion is seat growth, module adds, or usage tier jumps. Reporting both separately lets leadership see where NRR is coming from and lets CSMs set expansion targets without inflating the base renewal number.

Save play

Red accounts trigger a documented recovery plan.

A red tier is not a prediction, it is a trigger. When an account crosses into red, a save play opens with an executive sponsor, a timeline, and a target outcome. The play lives inside the account record and feeds the forecast as a probability-weighted entry. Teams that run save plays well recover thirty to fifty percent of red accounts in a given quarter.

Rollup

CSM to manager to VP, every tier visible at every level.

A manager sees every CSM's book stacked as rows with drill-down to the accounts behind each number. The VP sees every manager's rollup stacked above that. The entire installed base rolls up on one page with GRR and NRR targets drawn across the top. No pivot tables, no exported CSVs, no quarterly scramble to find the number.

The weekly workflow

What a real renewal forecasting cadence looks like.

Renewal forecasting runs on a weekly rhythm the same way new sales forecasting does. The signals are different and the owners are different, but the shape of the week is familiar. Here is what the cadence looks like from Friday afternoon to the following Monday review.

Friday 3pm

Submit nudge goes out to any CSM not yet in.

Customer success managers who have not submitted their weekly renewal number get an in-app and email nudge at 3pm local time. The nudge includes a one-click link to the renewal submit surface. The point is friction removal so the manager has every call by close of business, same as the new sales side.

Friday 5pm

Submit lock closes the week.

By 5pm every CSM has submitted. The number locks. Any resubmit after lock is audit logged with timestamp, reason, and the delta from the prior submit. The lock turns the weekly cadence from a cultural habit into a product feature and gives the manager a frozen snapshot to run the rollup against.

Saturday overnight

Health score refresh and risk tier re-evaluation.

An overnight job recomputes health scores against the latest usage, ticket, and engagement data, then re-evaluates risk tiers. Accounts that moved into red surface on the Monday rollup with a flag. CSMs see which calls their own health model is pushing against, same way reps see AI risk flags on commit deals.

Monday 9am

Manager rollup is on the leader's desk.

The manager has already walked the book, challenged the calls on yellow and red accounts, and submitted the team number. The VP opens the leader view and sees every manager stacked, every CSM inside each manager, every account inside each CSM, with GRR and NRR targets across the top. One page, no spreadsheet.

Monday 10am

The renewal meeting runs against locked numbers.

The renewal meeting is thirty minutes. Everyone looks at the same page. The agenda is red accounts, yellow accounts that moved from green this week, expansion that stalled, and variance from last week. The meeting is a working session on the accounts that will swing the quarter, not a status update.

Quarter end

Reconciliation and CSM accuracy scoring.

When the quarter closes, every weekly renewal submit gets reconciled against actual renewals, churn, and expansion. CSM accuracy scores update. Leadership sees which managers called the quarter inside the band, which inflated commit, and which left expansion on the table. The scores feed how much weight each CSM's call carries next quarter.

Run your renewal forecast on a surface built for the installed base.

Strkr ships risk tiers tied to health scores, weekly submit lock, GRR and NRR rollups, save play workflow, and CSM accuracy scoring out of the box. Fourteen-day trial, no credit card, every forecasting surface on every plan.

Start free See forecasting

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.