A renewal forecast can look precise while hiding several different questions. Will the customer renew? At what scope? In which period? And what evidence supports that expectation? A useful review makes those assumptions visible before anyone relies on the total. Start with a shared definition, then give each account an explanation and a next step.
Define what belongs in the forecast
Start with the contracts due for renewal in the period. Agree which date determines inclusion, how currency is handled, and whether the value means recurring revenue, contract value, or another measure. Keep the definition consistent between account owners, Finance, and leadership. A change in reporting rules can otherwise look like a change in customer performance.
Show the starting renewal base separately from expected renewal value. Also separate existing scope from potential expansion. If an account may renew a smaller contract while adding a new team later, those are two assumptions with different evidence. Recording them together can make the existing renewal look safer than it is.
Separate customer confidence from process progress
A positive relationship and an unsigned agreement are different facts. An account can be getting value while procurement is delayed. Another can have paperwork in motion while a sponsor is reconsidering the scope. Record both the customer situation and the commercial process rather than letting one substitute for the other.
Use a small set of clearly defined categories. For example, “confirmed” might require written agreement and a completed internal check; “expected” might mean scope has been discussed but approval is pending; “uncertain” might mean a material question remains unresolved. These are example definitions for your team to adapt, not industry standards or promises of an outcome.
Build the account explanation before the total
For each material renewal, record the due date, current recurring value, expected retained value, confidence category, evidence date, open concern, and responsible owner. Add the next customer or internal decision and when it is expected. A short account explanation is easier to challenge constructively than a colour with no supporting detail.
Evidence might include the customer confirming the next period’s scope, a budget decision, or a documented procurement milestone. Usage, engagement, support history, and health can help identify questions to investigate, but they do not replace the commercial conversation. A forecast should distinguish what the customer said from what the team inferred.
Use scenarios to show the uncertainty
Consider a hypothetical cohort with $100,000 of recurring value due. One customer represents $40,000 and has confirmed the current scope. A second represents $35,000, with a discussion underway about reducing to $30,000. A third represents $25,000 and is waiting on a budget decision. These are planning assumptions, not atEaseAI customer results.
An upside scenario of $95,000 assumes the second account renews at $30,000 and the third at its full $25,000. A working case of $70,000 includes the first two only. A downside case of $40,000 includes only the confirmed account. The spread makes the unresolved budget decision visible. It does not assign a scientifically validated probability to that decision.
Be careful with weighted estimates
A weighted total can be useful if everyone understands its limits. Multiplying account values by confidence percentages produces an expected-value estimate, not a set of contracts that will actually be signed. With a small portfolio or one very large renewal, the actual result may be far from that number.
If you use probabilities, document how they are assigned and compare them with past outcomes when enough history exists. Avoid giving each category an impressive-looking percentage without evidence. A transparent range and a list of the decisions that could change it may be more useful than a single precise figure.
Turn the review into assigned work
For every uncertain account, identify what could meaningfully change the view. That might be a sponsor conversation, confirmation of budget, an adoption discussion, or a review of an unresolved issue. Assign the action to someone who can carry it forward and set a reasonable checkpoint. Do not leave “follow up” as the whole plan.
Keep the forecast and the intervention separate. Changing an account from uncertain to expected does not solve the underlying concern. Record the customer evidence that changed, the action completed, or the assumption corrected. If the date slips, update the period and the explanation rather than carrying the same value forward silently.
Keep a history of changes
Save a consistent snapshot before each review. Compare the latest expected value and timing with the earlier view, then explain material movements. Useful reasons include scope reduction, new customer evidence, procurement delay, missed decision date, and a correction to the original record. These tell leaders more than an unexplained movement in a chart.
After the period closes, compare both value and timing with the outcome. Look for patterns such as repeated optimism on budget approvals or late discovery of scope changes. Review process weaknesses without treating every surprise as an individual failure. Better source information and earlier conversations may matter more than another confidence category.
Choose a review rhythm that matches the decision
Review important upcoming renewals often enough to respond to new information. Give larger, uncertain, or time-sensitive accounts more attention than routine contracts with no material change. Keep the discussion focused on what changed, what remains unknown, and which action needs support. Reading every account aloud rarely improves the forecast.
In a connected post-sales process, Analytics helps report the view and explain changes. Account owners still validate customer context and commercial assumptions. Agent Caleb can help prepare work from available context, while Automation and Workflows coordinate supported recurring steps. Confirm the actual capabilities in a demonstration before assuming a particular forecasting process is available.
Hypothetical renewal scenarios
| Scenario | Included assumptions | Expected retained value |
|---|---|---|
| Downside | Confirmed account only | $40,000 |
| Working case | Confirmed plus reduced-scope renewal | $70,000 |
| Upside | Working case plus budget-dependent renewal | $95,000 |
A worksheet for your team
Use these prompts to work through your own situation.
Preview the worksheet
- Forecast period and recurring revenue basis
- Account | renewal date | current amount | commercial source
- Confirmed customer outcome and readiness
- Decision process and relevant stakeholders
- Open concern or uncertainty
- Forecast category and supporting evidence
- Possible contraction and separately qualified expansion
- Next action | owner | review date
- Actual outcome and learning
Put it into practice
- Define the renewal base, period, and value measure.
- Separate renewal scope, expansion, and signing timing.
- Record evidence, uncertainty, owner, and next decision.
- Compare scenarios and explain the assumptions.
- Review changes against actual outcomes.
Common questions
Is account health the same as renewal confidence?
No. Health describes signals about the relationship or value. Renewal confidence also depends on scope, budget, decision makers, terms, and the commercial process. Use health to ask better questions.
Should expansion be included in the renewal number?
Show it separately so readers can distinguish retained scope from additional revenue. You can present a combined outlook as long as both components and their assumptions remain visible.
How accurate should a new forecast be?
Start with consistent definitions and honest uncertainty. Track changes and outcomes over time before claiming a level of accuracy. A new process needs evidence before it can establish a reliable track record.
References & further reading
PUT THE IDEA TO WORK
Renewals & Expansion in atEaseAI
Bring account context into renewal preparation and growth conversations.