GM.
Most companies treat expansion like it should happen naturally.
The customer is live. The account has users. The CSM has a relationship. If there is more budget, more seats, or a second team that needs the product, surely the opportunity will surface.
Sometimes it does.
More often, expansion gets discovered late, handed off awkwardly, or confused with renewal activity. The team celebrates account health while missing commercial timing. By the time sales is invited back in, the budget is already allocated, the customer has built a workaround, or the renewal call has become a pricing negotiation.
The problem is not that CS is bad at spotting opportunity.
The problem is that most companies do not run an expansion pipeline. They run customer sentiment, renewal tasks, and occasional upsell requests.
Those are not the same operating system.
Renewal is not expansion
A renewal protects the base.
Expansion grows the account.
They are related, but they require different signals, owners, and next steps.
A renewal question sounds like:
Is the customer getting enough value to continue?
Are there adoption or support risks?
Is procurement likely to push back?
Who signs the renewal?
What has changed since the last contract?
An expansion question sounds like:
Where is usage spreading beyond the original team?
Which workflow is creating measurable pull?
Who else has the same problem?
Is there a trigger that creates urgency?
What commercial event should sales pursue?
If those questions sit in the same account note, the expansion work gets buried.
CSM notes might say, “Customer is healthy. Marketing team interested in broader rollout.”
That is useful, but it is not a pipeline entry.
A pipeline entry needs a defined signal, owner, next step, and commercial hypothesis.
For example:
Signal: second department has requested admin access
Hypothesis: product is being pulled into another team workflow
Owner: CSM validates use case; AE maps economic buyer
Next step: joint expansion discovery with department lead
Exit path: create expansion opportunity, defer to renewal, or close no-opportunity
That is something a sales leader can inspect.
“Customer seems happy” is not.
Build the expansion signal ladder
Expansion should not depend on someone remembering to ask, “Anything else we can help with?”
The better system is a signal ladder.
At the bottom are weak signals. At the top are commercial triggers.
A simple ladder might look like this:
Usage signal — more active users, more frequent workflows, new teams logging in.
Pain signal — customer asks about limits, integrations, permissions, reporting, or manual workarounds.
Stakeholder signal — a new manager, department lead, finance contact, or executive enters the conversation.
Strategic signal — customer ties the product to a company initiative, hiring plan, consolidation project, or operational review.
Commercial signal — budget owner asks about packages, contract structure, pricing, procurement, or rollout timing.
Not every signal deserves an opportunity.
That is the point.
The ladder prevents two common mistakes: logging every happy conversation as pipeline, and ignoring early signs until procurement appears.
CS can own early signal capture. Sales can own commercial development. RevOps can define the conversion rules.
The CS to sales handoff needs criteria
A weak handoff sounds like:
“Customer might be ready for an upsell. Can someone follow up?”
That creates predictable friction.
Sales says the opportunity is vague. CS says sales is being too transactional. The customer gets a clumsy commercial email disconnected from the relationship.
A stronger handoff includes five pieces:
Account context: current contract, renewal date, primary use case
Signal: what changed recently
Evidence: usage pattern, stakeholder comment, support trend, meeting note
Hypothesis: what expansion path might exist
Recommended move: discovery, exec alignment, renewal packaging, or wait
Illustrative scenario:
A 60-seat customer has 48 active users and support tickets from a second business unit asking about permissions. The CSM notes that a department lead joined the last QBR and asked whether the platform can support a regional rollout.
That is not automatically an upsell.
But it is enough for a structured handoff: CS validates the second team’s workflow, AE maps budget and buying process, and the next QBR includes a specific expansion agenda rather than a generic health check.
Give expansion its own stages
Do not force expansion opportunities through the exact same stages as net-new deals.
Net-new sales stages are built around problem discovery, vendor evaluation, business case creation, and procurement.
Expansion stages should reflect customer reality:
Signal captured
Fit validated
Stakeholder mapped
Expansion path defined
Commercial plan agreed
Proposal or renewal package sent
Closed won, deferred, or closed no-opportunity
Expansion pipeline should allow “deferred” and “no-opportunity” as healthy outcomes.
If every signal becomes forecastable pipeline, teams inflate the number.
If every weak signal gets ignored, teams miss timing.
The discipline is in the middle: capture early, qualify cleanly, and only forecast when there is a real commercial event.
Weekly action
Pick five active customers with upcoming renewals or high product usage.
For each one, complete this expansion inspection:
What changed in the last 90 days?
Is there a usage, pain, stakeholder, strategic, or commercial signal?
Who owns the next validation step?
What would make this a real expansion opportunity?
Should the account be marked signal captured, fit validated, deferred, or no-opportunity?
Do not start by asking CSMs for “upsell ideas.”
Start by making the signals visible.
— Pipeline Playbook