Renewal Forecasting Guide for Sales, CS, and RevOps

Renewal forecasting has become a bigger part of revenue planning because most B2B revenue does not come from brand-new customers. Forrester says 73% of B2B revenue comes from existing customers through renewals, cross-sell, and upsell. That makes renewals more than a Customer Success checkpoint. They are part of the revenue number.

The challenge is that renewal risk usually builds before the renewal conversation starts. Product usage may drop. Executive engagement may fade. Support issues may pile up. The account may still look fine in the CRM, but the revenue is already less secure than it appears.

Below, we break down how renewal forecasting works, which signals matter, and how Sales, CS, and RevOps can turn customer risk into a more reliable revenue forecast.

Table of Contents:

• What is renewal forecasting?
• Renewal forecasting vs. sales forecasting
• How to Forecast New Business, Renewals, and Expansion Together
• 5 signals every renewal forecast should include
• How to Measure Renewal Forecast Accuracy
• How to build a renewal forecast, step by step
• How MaxIQ helps teams forecast renewals with more confidence

What is Renewal Forecasting?

Renewal forecasting is the process of estimating how much existing customer revenue is likely to renew, expand, contract, or churn in a future period.

That sounds simple, but it is different from just tracking upcoming renewal dates. A renewal date tells you when a decision is due. A renewal forecast tells you how much confidence the team should have in that revenue before the date arrives.

For a SaaS business, that matters because existing revenue is part of the number. If a large renewal contracts or churns, new business has to make up the gap. If an account is likely to expand, the forecast should show that upside early enough for Sales, CS, and RevOps to plan around it. if Sales and CS do not share the same context from the start, renewal risk usually shows up late. A practical way to fix that is to align both teams early using a structured approach like the Sales to CS Handover Playbook

A useful renewal forecast usually combines a few things: contract value, renewal date, account health, product usage, stakeholder engagement, support history, and expansion potential. The goal is not to predict the future perfectly. It is to give the team a clearer view of which customer revenue is safe, which accounts need attention, and where the forecast may change before the quarter closes.

Renewal Forecasting vs. Sales Forecasting

Sales forecasting and renewal forecasting both help revenue teams predict future revenue, but they look at different parts of the business.

Sales forecasting focuses on new revenue. It asks whether open opportunities will close, when they will close, and how much revenue they will bring in. The main signals usually come from pipeline stage, close date, buyer engagement, deal activity, and rep judgment.

Renewal forecasting focuses on existing revenue. It asks whether current customers will renew, expand, contract, or churn. The main signals come from account health, product usage, support history, stakeholder engagement, value delivered, and commercial risk.

A simple way to think about it:

The important point is that these forecasts should not live in separate worlds. A company can hit new business targets and still miss the revenue plan if renewals are weak. The reverse is also true. Strong renewals can protect the number even when the new pipeline is slower than expected.

For Sales leaders, renewal forecasting shows how much pressure new business really has to carry. For CS leaders, it turns account health into revenue visibility. For RevOps, it connects both sides into a cleaner view of the quarter.

How to Forecast New Business, Renewals, and Expansion Together

New business, renewals, and expansion all contribute to the revenue plan, but each one needs different forecasting signals.

A new business forecast looks at open opportunities and estimates which deals will close. A renewal forecast starts with existing customer revenue and estimates how much will renew, contract, or churn. An expansion forecast looks for additional revenue from customers adding products, teams, seats, or new use cases.

The forecasts should remain separate enough for teams to use the right evidence:

• New business: Deal stage, buyer engagement, close date, competition, and next steps
• Renewals: Product usage, value delivered, account health, stakeholder engagement, and commercial risk
• Expansion: Adoption growth, new use cases, team growth, customer outcomes, and product interest

Leadership should then see all three in one revenue view. This shows how much revenue is expected from existing customers, how much may be lost through churn or contraction, and how much new business must close to cover the remaining target.

Without this combined view, a company may appear on track based on its sales pipeline while a large renewal gap is building elsewhere.

5 signals every Renewal Forecast should include

A renewal forecast is only useful if it looks beyond the contract date. The renewal date tells you when the decision happens. The signals below tell you whether the customer is likely to stay, expand, contract, or churn.

1. Product usage and adoption

Usage is usually the first place to look. If the customer is logging in, using the right features, and adoption is spreading across the account, the renewal is usually more secure.

But usage alone is not enough. A few active users do not always mean the account is healthy. The better question is whether the product is being used by the people and teams tied to the original business case.

2. Customer health

Customer health gives the team a broader view of renewal risk. It can include usage, support activity, engagement, sentiment, onboarding progress, and account history.

The mistake is treating health score as the forecast itself. A health score should inform the forecast, not replace judgment. If the score drops, the team should know why it dropped and what needs to happen next.

3. Value delivered

A customer renews because they believe the product is still worth paying for. That means the forecast should look at whether the customer has actually reached the outcomes they bought for.

Did they solve the problem? Did they hit the milestone? Did they get the efficiency, visibility, revenue impact, or risk reduction they expected? If the answer is unclear, the renewal forecast should carry more risk.

4. Stakeholder engagement

Renewal risk goes up when the relationship gets too narrow. A champion may still be active, but if the executive sponsor is gone or the economic buyer has not seen value, the renewal can weaken quickly.

A strong renewal forecast should show whether the right stakeholders are still engaged, not just whether someone at the account is responsive.

5. Commercial and support risk

Some renewal risk shows up outside usage and health scores. Open support issues, unresolved escalations, pricing pressure, procurement delays, payment concerns, and downgrade conversations can all change the forecast.

These signals matter because they often appear before the customer says they are at risk. A useful renewal forecast brings them into view early, so CS, Sales, and RevOps are not surprised when the renewal gets closer.

How to build a Renewal Forecast, step by step

A renewal forecast does not need to start as a complex model. It needs to help the team see which customer revenue is safe, which accounts are at risk, and what needs action before the renewal date gets close.

Step 1. Build your renewal book

Start with every customer coming up for renewal in the next quarter, half year, or year. Include the basics: account name, renewal date, ARR, owner, contract term, product package, and current forecast status.

This gives Sales, CS, and RevOps one shared view of the renewal base instead of separate spreadsheets and account notes.

Step 2. Segment accounts by value and risk

Not every renewal needs the same level of attention. A large strategic account with low adoption should not be managed the same way as a small account with stable usage.

Segment accounts by ARR, renewal date, health, product adoption, and strategic importance. This helps the team decide where to spend time first.

Step 3. Score each account using the five signals

Use the signals from the previous section: usage, health, value delivered, stakeholder engagement, and commercial or support risk.

The goal is not to create a perfect score. It is to create a consistent way to judge renewal confidence across accounts.

Step 4. Choose a Renewal Forecast Model

Start with categories people can understand without needing a separate explanation:

• Likely to renew
• At risk
• Likely contraction
• Expansion opportunity
• Needs review

For a smaller renewal book, that may be enough. Once the number of accounts grows, though, leadership usually needs more than a label. They need to know how much revenue is realistically expected to renew.

One simple approach is to assign a probability to each account. If a customer has $100,000 in renewal ARR and the team believes there is an 80% chance it will renew, that account contributes $80,000 to the weighted renewal forecast.

Weighted renewal forecast = Renewal ARR × renewal probability

The percentage should come from what is actually happening in the account. Product usage, value delivered, stakeholder engagement, support issues, and commercial discussions all matter. It should not be based only on whether the account owner feels positive about the renewal.

The model does not need to be complicated. It just needs to give leadership a realistic revenue number while making it clear why each account sits where it does.

Step 5. Review changes weekly

Renewal forecasts should move as customer reality changes. If usage drops, an executive sponsor leaves, or a support issue escalates, the forecast should update before the renewal call is already in trouble.

A weekly review helps teams catch movement early and avoid last-minute surprises.

Step 6. Turn risk into action

Every at-risk renewal should have a next step. That might be an executive check-in, a value review, an adoption plan, a support escalation, or a commercial conversation.

This is the part that matters most. A renewal forecast is not just a prediction. It is a way to decide where the team should act next.

How to Measure Renewal Forecast Accuracy

A renewal forecast should be judged by whether it gave the team enough warning to do something useful.

It is easy for a forecast to look accurate at the end of the quarter when account owners have been updating it every week as renewal decisions come in. The better test is to go back to an earlier snapshot and compare what the team expected with what actually happened.

Start with the revenue number. How close was the forecasted renewal ARR to the amount that renewed? Then look account by account. Did customers marked as likely to renew actually stay? Were contractions identified early? Did any churn come as a surprise?

Pay close attention to the misses. They often reveal more than the final accuracy percentage. Maybe product usage dropped but nobody noticed. Maybe the executive sponsor left. Maybe an open support issue never made it into the forecast. Or perhaps the team relied too much on the CSM’s confidence without enough evidence behind it.

Reviewing those patterns helps RevOps improve the model and gives CS leaders a clearer sense of which signals actually matter.

What to Look for in Renewal Forecasting Software

A renewal calendar tells you what is coming up. Renewal forecasting software should help you understand what is likely to happen to that revenue and why.

Look for a system that helps your team:

• See renewal dates, ARR, owners, and forecast status in one place
• Connect product usage, customer health, conversations, and support issues
• Track renewals, contraction, churn, and expansion separately
• Understand why an account is considered safe or at risk
• Spot changes early enough for the team to take action
• Compare forecasted renewal revenue with the final result

The goal is not another complicated score. It is a clear view of what changed, which revenue is exposed, and what the team should do next.

How MaxIQ helps teams Forecast Renewals with more confidence

Renewal forecasting gets harder when the context is split across teams. Sales knows what was promised during the deal. Customer Success knows whether the account is getting value. RevOps needs a forecast number leadership can trust. When those signals live in different places, renewal risk shows up too late.

MaxIQ helps bring that context together. It connects deal history, customer conversations, account health, usage signals, and renewal risk so teams can see whether existing revenue is still on track.

That matters because a renewal forecast should not depend only on a health score or a renewal date. It should show the reason behind the forecast. Is the customer using the product? Did they reach the outcomes they bought for? Are the right stakeholders still engaged? Are there unresolved risks that could turn into churn or contraction?

With MaxIQ, teams can use renewal forecasting as an operating rhythm, not just a reporting exercise. CS can identify accounts that need attention earlier. Sales and account teams can see where expansion or contraction is likely. RevOps can connect renewal risk to the broader revenue forecast.

The goal is simple: give every team a clearer view of which customer revenue is safe, which accounts need action, and where the forecast may change before the renewal date arrives.