Start with customer value and the buying unit
Before pitching expansion, confirm what additional work the customer wants to do and whether the product can support it. Name the Customer Success owner for adoption and service work and the commercial owner for renewal or expansion.
- Match people, workspace, and buying account before interpreting usage.
- Ask which workflows and outcomes matter, what has changed, and what blocks value.
- Check what people are doing in the product, what their contract allows, and whether a buyer has confirmed a need for more.
- Do not let one power user hide weak adoption across the intended team.
Translate a signal into a question
For seat pricing, compare paid seats, assigned seats, and users who completed the defined core workflow over the same period. For usage pricing, compare consumption with the contracted allowance and the customer outcome. Higher consumption may mean more value, or it may mean waste that needs fixing.
- More teams asking for access: can existing seats meet the need, and who owns the new workflow?
- Approaching allowance: is the usage valuable, expected, and economically suitable?
- Interest in a tier capability: which additional outcome requires it?
- A new product or business unit: is there a sponsor and implementation capacity?
- Low adoption or a service issue: diagnose recovery, right-sizing, or core product fit before a growth pitch.
Coordinate one useful customer action
Customer Success and the commercial owner agree who will ask about the additional need and what to validate. Create expansion pipeline when the customer confirms a problem and an evaluation. Keep an unchanged renewal separate from added contract value.
- Record account and buying unit, current outcome, changed fact and date, usage and entitlement definitions, denominator, window, and source.
- Distinguish confirmed intent from a working hypothesis; include risk or recovery needs.
- Name the action, commercial and success responsibilities, date, and evidence needed for a qualified buying process.
- Keep the customer's existing promises and service work visible so parallel teams do not create conflicting asks.
Confirm the expansion need and adoption
Review which signals became confirmed needs, qualified evaluations, and signed expansions. After signature, check whether the new users adopted the product and achieved the outcome discussed. Review churn and contraction alongside expansion.
- Track validated additional needs among reviewed signals, separated by signal type.
- Review wins among qualified expansion cohorts after a defined follow-up window, keeping unresolved cases visible.
- Check adoption and the promised outcome after expansion rather than stopping at signature.
- Keep renewal risk, contraction, and customer harm alongside growth measures.