Expansion signals: how to spot upsell opportunities

Your dashboard says an account is healthy. That does not mean they are ready to buy more seats, upgrade a tier, or add another product.

Expansion signals answer a different question: which existing customers are realistically ready to grow now?

Health score tells you who might churn. This page tells you who might expand. For risk scoring, see customer health score. For dollar impact when you retain and grow, see net revenue retention.

Healthy is not the same as ready to buy more

A green health score is good for retention. It is not an automatic upsell trigger.

• Healthy but narrow: one champion, one team, one workflow.
• Ready to expand: breadth across users, repeat day-to-day usage, and a viable commercial path.
• Rule of thumb: treat health as the floor. Expansion readiness is the next layer on top.

Four signs a customer may be ready to grow

1. Usage spreads beyond one champion

What it looks like

• Multiple users active, not only admins.
• Adoption in more than one team or function.
• Operators repeat core workflows, not just the person who set it up.

What to do

• Track seat utilization and team-level activity, not account-level login counts alone.
• If only one person uses the product, focus on enablement before any sales motion.

2. Non-admin users keep coming back

What it looks like

• Day-to-day operators return week after week.
• Key actions repeat beyond launch week or a one-off project.
• Usage survives after onboarding, not just during rollout.

What to do

• CS runs multi-user enablement and documents impact before looping in sales.
• Spikes without repeat behavior stay in "watch" mode.

3. They outgrow basic workflows

What it looks like

• Advanced features become part of normal work.
• The team asks for scale, governance, or visibility capabilities.
• Value is obvious enough that broader adoption is a rational next step.

What to do

• Tie expansion talk to outcomes they already get, not generic "upgrade" language.
• Note capacity pressure: nearing seat limits, usage caps, or process bottlenecks.

4. Commercial timing and buyers align

What it looks like

• Renewal or planning window is open.
• Budget influencers are mapped and engaged.
• The expansion motion matches a stated outcome (more seats, higher tier, add-on).

What to do

• Package the account story: what changed, why now, which motion fits (seats, tier, cross-sell).
• If there is no economic buyer or timing, stay in CS-led adoption mode.

Emerging vs ready: when to involve sales

Use two stages so you do not outreach too early.

Emerging

Early breadth and repeat usage, but evidence is still thin.

• CS deepens adoption and proves impact across users.
• Do not force a sales conversation yet.

Ready

Signals are durable and cross-functional.

• Repeat non-admin behavior is established.

• Usage spans enough users or teams to support growth.

• Commercial context supports a timely conversation.

• CS and sales run a coordinated plan with clear ownership and timing.

Calling too early wastes sales time and erodes customer trust. Waiting until ready improves conversion.

False positives to filter out

Most failed expansion motions start from misread signals:

• Single champion bias: one power user drives most activity.
• Project spikes: short bursts during onboarding or one campaign.
• Admin-only behavior: setup and config without frontline adoption.
• No buying path: strong usage but no economic buyer or renewal window.

Filter these before you hand off. Premature upsell pitches train customers to ignore you.

CS-to-sales handoff playbook

1. CS validates evidence. Confirm spread, repeat non-admin usage, and concrete value outcomes.
2. CS packages the narrative. What changed, why it matters, which motion fits (seats, tier, cross-sell).
3. Sales runs the commercial conversation. Clear timing, stakeholder map, outcome framing tied to NRR.
4. Review wins and losses. Refine readiness criteria each quarter.

Expansion sits beside retention in the same customer success motion. For save playbooks when accounts slip, see how to reduce SaaS churn. For team habits that catch risk early, see proactive vs reactive customer success.