Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Retention & Growth

How to Forecast Renewals Instead of Assuming Them

Pete Furseth 7 min read
renewalsforecastingretentionrevenue forecasting
How to Forecast Renewals Instead of Assuming Them
Home/ Blog/ How to Forecast Renewals Instead of Assuming Them

What is a renewal forecast?

Retained ARR from contracts expiring inside the period, built bottom up from the accounts themselves. Most companies do not have one. They have an assumption: last year's retention rate applied to next year's base, entered into the plan in October and never revisited.

That assumption usually carries more dollars than the new bookings target it sits next to. A company with $40 million in ARR and a 90% gross retention assumption is betting $4 million on a number nobody modeled. Move the real rate two points and the miss exceeds most new business shortfalls.

A renewal forecast has four inputs, and only one of them is a rate.

InputSourceUpdate cadence
Renewal baseContract end dates in the CRM or billing systemMonthly
Risk tier per accountBehavioral signals and account reviewWeekly
Expected retention rate by segmentYour own historical cohortsQuarterly
Expansion and contraction estimateOpen expansion opportunities and seat utilizationWeekly
Put this to work on your numbers
Run your own numbers with the free Forecast Accuracy Scorecard, then see how ORM builds it into a custom model.

Why does a flat retention rate break?

Because renewal exposure is never distributed evenly, and the accounts expiring this quarter are not a random sample of your base. Contracts cluster. A heavy sales quarter two years ago produces a heavy renewal quarter now, and if that cohort came from a channel that converted poorly on fit, the quarter carries risk the annual average cannot see.

Build the base by quarter and inspect its composition before applying any rate. Which segments dominate. What share came from a single acquisition channel. How many of those accounts have changed their economic buyer since purchase. Composition drives the outcome, exactly as it does in new business, where a coverage ratio can look healthy while the underlying pipeline is concentrated in the wrong stage or owned by the wrong reps.

How do you set retention rates by segment?

From your own cohort history, cut finely enough to be useful and coarsely enough to be stable. Four to six segments is usually right. Cutting to twenty gives you cells with three accounts each and rates that swing wildly on one loss.

Segment on the dimensions that actually separate outcomes in your data. Contract size band and acquisition channel usually do. Industry often does not. Then run the rate over at least eight quarters so a single bad period does not set the expectation.

Everyone believes their data is too messy to support this. It is not a real obstacle. Consistent data produces accurate predictions even when it is imperfect, because the model learns the pattern of the imperfection. The failure mode that matters is changing definitions midstream, not dirty fields.

How do you handle risk tiers inside the base?

Override the segment rate with account-level judgment where evidence exists, and document the override. A segment rate is a prior. An account that has gone silent, lost its champion, and skipped two business reviews deserves a lower number than its segment suggests.

Apply tiers rather than individual percentages. Three tiers is enough: at risk, standard, and secure. Assign each a retention rate from your own history of how flagged accounts performed. This is the same logic as a weighted pipeline, where a probability multiplies an amount, and it carries the same caution: weighting is useful for planning a portfolio and useless for predicting a single large account. Read our take on weighted pipeline for why the average hides the outliers.

Large accounts get modeled individually. Any renewal above a threshold you set, typically the point where one loss changes the quarter, gets a named forecast call rather than a rate.

How do you forecast contraction separately from churn?

Model seats and modules rather than logos alone, because most retention dollars leak without an account ever leaving. A customer who renews at 60% of prior ARR shows up as retained on a logo report and as a serious loss on the waterfall.

Contraction is predictable from deployment data. Compare licensed seats to active seats for every account in the renewal base and treat the gap as exposure. A buyer paying for 200 seats with 90 in use will negotiate that gap at renewal, and the earlier you see it the more time you have to drive deployment instead of accepting the cut. Forecast the exposure explicitly as a contraction line so it stops arriving as a surprise.

What breaks a renewal forecast mid-quarter?

Changed conditions applied to unchanged assumptions. Forecasts fail because something moved in the business or the market while the model kept running on inputs set months earlier. Renewal forecasts are the most exposed version of this problem, since retention rates get set during annual planning and revisited almost never.

Four conditions deserve standing attention. Competitive pricing pressure shows up as contraction well before it shows up as churn, because buyers cut seats before they cut vendors. Slower buyer decisions stretch approval cycles and push signatures past term end, which converts a healthy renewal into an administrative lapse. Territory or coverage changes distract the people who own the accounts, and the effect lands on renewals faster than on new pipeline. Seasonality moves the base itself, since renewal dates cluster wherever your heaviest selling quarters fell two years ago. Update the rate when a condition changes rather than waiting for the quarter to prove you wrong.

How accurate should a renewal forecast be, and how often should it update?

Accurate enough to act on at the start of the quarter, and updated weekly as signals move. A number produced in the final week of a quarter has no operational value, because by then the quarter has already happened.

The accuracy standard is worth stating plainly. On new and expansion revenue, teams commonly reach around 90% through heavy manual work that goes stale as conditions change. ORM targets 95% on that motion and holds it from day one through day 90 without manual adjustment. Renewal forecasts should be held to a similar discipline of measurement, tracked with the same forecast accuracy method you use elsewhere so the number improves instead of drifting.

Update the base monthly for new contract dates, the risk tiers weekly from behavioral signals, and the segment rates quarterly from closed cohorts. That cadence matches how the underlying facts actually change, which is the core principle behind any credible sales forecasting practice. Models built on old assumptions miss because the market moved, and retention assumptions go stale faster than most teams expect when buyers start cutting spend.

Frequently Asked Questions

How do you build a renewal forecast?

Start with the renewal base, which is every dollar of ARR whose contract term ends inside the forecast period. Segment that base by risk tier and by size band, apply an expected retention rate to each segment from your own history, and model contraction as a separate line from full churn. The output is retained ARR with a stated range rather than a single number.

Why is a flat renewal rate assumption dangerous?

Because it applies an average to a base that is never average. Renewal exposure moves quarter to quarter with the contracts that happen to expire, so a quarter loaded with accounts from a weak acquisition cohort behaves nothing like the annual average. The error also compounds, since retained ARR is usually a larger number than new bookings.

How far ahead can renewals be forecast?

Further than new business, because you know the contract dates in advance. The base is knowable a year out. What changes is the expected retention rate applied to it, which should update monthly as behavioral signals move on the accounts inside the period.

Should renewals be forecast separately from new business?

Separately, then reconciled into one ending ARR. The two motions have different cycle times, different owners, and different failure modes. Blending them into a single number hides the case where strong new bookings are covering an accelerating loss rate inside the base.

What forecast accuracy is realistic?

On new and expansion revenue, teams commonly reach around 90% with heavy manual effort that goes stale as conditions change. ORM targets 95% on that motion and holds it from day one through day 90 of the quarter without manual adjustment. Renewal accuracy depends on how much of your base carries multi-year terms and how early risk signals fire.

PF
Pete Furseth
ORM Technologies
Pete has built custom revenue forecast models for B2B SaaS companies for over a decade.

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