Separate a Renewal from a New-Scope Expansion

An existing customer may discuss a renewal and an additional service in the same meeting. That does not make them one decision. If the expansion fails, the original service might continue unchanged. If the renewal fails, the expansion may become irrelevant. Your opportunity structure should make those dependencies visible rather than hiding them inside one optimistic amount.

Begin with what the customer is deciding to continue and what it is deciding to add. A renewal preserves or changes an existing commitment. An expansion introduces additional scope. Those definitions need an explicit commercial boundary because a revised agreement can contain both without making the underlying decisions identical.

Write the baseline before the opportunity values

Record the current scope, term and amount basis from the relevant approved commercial information. Do not treat last year's opportunity amount as an unquestioned baseline: it may include one-time work, discounts or a different period. Note exclusions and unknowns before calculating an increase.

Then describe the proposed renewal and expansion in plain language. For example, renewing support for four sites differs from adding support for a fifth site. A proposed increase in price for the same four sites is not automatically a new-site expansion. Your reporting definitions should determine how that price change is categorized.

CRM labels alone cannot establish the distinction. HubSpot documents default deal types such as New Business and Existing Business and allows those options to be edited in HubSpot: Default deal properties. A label is useful only when your team consistently applies a defined meaning to it.

A completed linked-record example

Consider fictional Harbor Learning Forum. Its current agreement covers registration support for four regional workshops over a twelve-month term. For this illustration only, the renewal proposal is US$24,000 for another twelve months. The customer is separately evaluating a new exhibitor-coordination service at US$8,000 for that same proposed term. These are invented figures, not pricing advice or reported results.

The renewal record, RN-12, identifies the four-workshop support scope, the existing-service owner and the next-term decision. Its US$24,000 amount excludes the optional exhibitor service. The expansion record, EX-09, identifies the additional workflow, its operational evaluator and the separate US$8,000 proposal. Neither record claims acceptance merely because both proposals were discussed.

A relationship note says: EX-09 assumes RN-12 continues, unless the parties agree a standalone arrangement. The dependency is not reciprocal. RN-12 may proceed without EX-09. The account summary shows a US$24,000 renewal proposal and a US$8,000 optional expansion, not a US$32,000 renewal plus another US$8,000 expansion.

Test three outcomes before choosing the structure

If the buyer renews and declines the new service, RN-12 records the accepted renewal according to the team's process, while EX-09 records the factual decline. Do not label the whole account a lost opportunity or remove the continuing support context.

If both proceed in one agreement, link both decisions to the executed commercial evidence and apply a documented reporting treatment. The same US$8,000 must not be counted once as expansion and again inside a combined opportunity without an adjustment. Whether your CRM uses separate records or line items is a design choice to verify against its capabilities and your finance requirements.

If the renewal decision is delayed, reassess the expansion's dependency. It may remain an optional proposal, need a revised standalone scope or become inappropriate. Do not move the expansion's expected date merely to preserve an attractive quarterly total. Record the underlying change in decision conditions.

Keep timing and authority distinct

The current service's end date is not automatically the signing date for either proposal. Ask which action must happen by that date and what happens if it does not. Likewise, a service owner who approves continuing operations may not have authority to add a new workflow or budget.

Use a short review checklist: Is the existing scope explicit? Does each amount name its period and basis? Is optional work counted once? Can the renewal proceed if expansion is rejected? Are the decision owners and timing evidence independently recorded? Can someone reconcile the account summary to the actual proposed agreement?

This separation is not a demand to create more records. It is a demand to preserve distinct decisions wherever they live. A small team may use one record with clearly separated components; a larger team may use linked opportunities. Either approach works only when a reviewer can distinguish continued business, additional scope and the evidence that supports each.

Continue with Create a Weekly Pipeline Review That Ends with Decisions or Keep Research Notes Separate from Customer Commitments.