Skip to content

Blog

Keep renewal and expansion value separate in the forecast

How much of a combined renewal proposal is retained base versus incremental expansion?

5 min read
Keep Renewal and Expansion Value Separate in the Forecast. Conceptual illustration: A solid renewal ring sits inside separate solid and dashed outer arcs, distinguishing the existing base from additional and possible scope.

The renewal owner forecasts $120,000. The account executive forecasts a $160,000 expansion proposal for the same customer. The commercial team expects one agreement, but the dashboard appears to contain $280,000 of opportunity. Part of the customer's existing business has been counted twice.

Separate the retained base, incremental expansion and possible contraction before combining renewal and expansion forecasts. Describe alternative commercial packages as alternatives, not additive revenue. Then apply the company's approved definitions and evidence requirements to each component. One coordinated customer conversation can support several internal responsibilities without creating several copies of the same value.

Begin with the base that is actually up for decision

Identify the existing scope and recurring value relevant to the renewal under your approved operating definition. Exclude unrelated products, entities or periods unless the renewal genuinely covers them. The opening base must be traceable to the agreement or authoritative commercial record, not reconstructed from whichever opportunity is easiest to find.

Next, distinguish a renewal proposal's total from its incremental value. A proposal that includes the old service plus a new team is not entirely expansion. Likewise, a same-price renewal may preserve valuable revenue without adding incremental value. Both contributions matter, but they answer different planning questions.

Finance owns the company's reporting definitions. This method organizes open commercial decisions; it does not prescribe revenue recognition, accounting treatment or commission credit. Those may use different policies and require separate reconciliation.

Decompose one fictional proposal

Imagine a customer currently has an annual recurring scope of $120,000. The team is discussing three mutually exclusive renewal options: continue at $120,000, expand to $160,000, or reduce to $90,000. All amounts are fictional and use one currency and one annualized-value convention.

Under the expansion option, the proposed $160,000 consists of $120,000 retained base and $40,000 incremental expansion. Under the smaller option, $90,000 is retained and $30,000 contracts. Adding all three options would create $370,000 of pipeline for a customer considering one purchase. Adding a separate $120,000 renewal to the full $160,000 expanded package would create the $280,000 error.

Decompose one fictional proposal
Mutually exclusive optionOpening baseChange from opening baseTotal proposed value
Continue current scope$120,000$0$120,000
Expand scope$120,000+$40,000$160,000
Reduce scope$120,000−$30,000$90,000

The team can retain all three options in its working records without including all three in the same forecast total. The current forecast scenario should state which option it uses and why. Alternative scenarios remain visible for planning, with no suggestion that they can all occur together.

If the buyer has confirmed continuation of the base but has not approved the new team, record that evidential distinction. Do not automatically give the entire expanded proposal the same confidence because one component is well supported. Equally, a sales conversation about more scope does not prove the base renewal is secure.

Choose a record design that preserves the distinction

Some organizations use one commercial opportunity with separate components. Others maintain linked renewal and incremental-expansion opportunities. Either can work if the definitions are explicit, identifiers connect the records and reporting counts the underlying commercial value once.

If using two opportunities, define what the expansion amount contains. In the fictional example it is the additional $40,000 under the stated annualized convention, not the whole $160,000 package. If using one opportunity, ensure the retained and incremental components remain available to the teams whose plans depend on them.

Do not change the record structure solely to make a dashboard easier. Consider who owns the proposal, what the customer will sign, which systems receive the result and how amendments will be handled. A temporary spreadsheet reconciliation is preferable to a hurried CRM design that obscures the agreement.

Preserve timing when components start separately

Expansion may begin later than renewal. A customer could renew the current scope in January and add the new team in April. The agreement value, annualized run rate and in-period contribution then describe different things. Show the relevant effective dates and apply the approved policy rather than assigning every component to the signature date.

Also check dependency. If the customer will renew only if the expanded package meets its needs, the base and expansion are commercially connected. If it will renew regardless and evaluate expansion later, the opportunities have a different relationship. The account team must establish that distinction with the customer; a linked-record label does not establish it.

When the scope changes, update the components and the customer plan together. A smaller proposal may reduce the forecast while making the remaining decision more realistic. Preserve the reason so leadership does not mistake corrected scope for an unexplained loss of confidence.

Give the review one customer story and several clear measures

Sales, CS and RevOps should be able to explain the opening base, the current proposed scope, the incremental change, the timing and the unresolved buyer decision. The person leading the customer conversation may differ from the owner of a forecast component. Agree both responsibilities.

RevTech's Analyst work can prepare agreed CRM questions, and Customer Context can bring relevant account history together. Confirm the available contract mapping and component fields before scoping this analysis. The calculation here is an original operating method, not a claim of an automated renewal-allocation feature.

Review one combined renewal-and-expansion proposal before the next forecast submission. If two teams cannot independently arrive at the same total without adding the base twice, settle the commercial components before discussing confidence. A more accurate view begins with knowing what the customer is actually deciding to buy.

Sources and scope

Original commercial-forecast method and fictional example, reviewed October 30, 2026. Current RevTech Analyst and Customer Context descriptions support preparation only. The separate bookings-to-ARR article explains signed-contract and active-recurring-value reconciliation after the relevant commercial events.

Put the framework to work

Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo