Churn prediction gets the majority of signal science attention in CS analytics. That makes sense — preventing revenue loss is an urgent, measurable problem with clear business consequences. But the same behavioral telemetry that identifies at-risk accounts also contains a second category of signal that most CS teams are systematically undercollecting: early markers of expansion readiness.
Identifying expansion-ready accounts 30–45 days before the CSM's quarterly check-in isn't a nice-to-have. It's a capacity question. A CSM managing 100 accounts who proactively reaches out to expansion-ready accounts at the right moment can generate conversations that would otherwise happen reactively at annual renewal — if they happen at all. The product usage data to do this is likely already in your event stream. The question is whether you're reading it for this purpose.
What Expansion Signals Look Like in Product Data
Expansion signals are behavioral patterns that indicate an account is getting more value from the product than their current plan accommodates — and that they're running toward natural constraint points where an expansion conversation is timely and low-friction.
The most reliable expansion signals in mid-market B2B SaaS product telemetry:
Seat saturation
An account consistently using 90%+ of their licensed seats with a stable or growing WAU trend. This is the most straightforward expansion signal: the team that bought 10 seats now has 9 actively using the product and is adding new team members. The expansion conversation is about additional licenses, and the timing is evident in the usage data before the account owner thinks to ask.
Feature ceiling behavior
An account repeatedly reaching the limit of a feature quota or hitting the boundary of their current tier — export limits, API call ceilings, storage thresholds, record count limits. Each threshold event is a data point that signals the account is getting value (they're using enough to hit the ceiling) and is constrained by their current plan. The expansion motion here is tier upgrade, and the signal fires automatically when the ceiling is approached.
Feature adoption breadth approaching cross-tier value
An account on a starter tier that is adopting features associated with higher-tier plans — not through technical access but through consistent engagement with the lower-tier versions of those capabilities. This is a softer expansion signal but a meaningful one: they've found value in the adjacent feature set and are the right audience for an upgrade conversation framed around getting more of what they're already using.
New use case introduction
An account that begins using the product for a materially different workflow than their original purchase use case. In a workflow automation SaaS, the original purchase might have been for finance team automation; the new use case is the operations team starting to use it independently. This often appears as a new cluster of user activity with distinct session patterns (different times of day, different feature paths). It signals an organic expansion that the account might formalize with a second seat block or a separate contract if the CSM identifies it and facilitates.
A Scenario: The Expansion Signal That Arrived Before the QBR
Consider an account like Mosaic Labs — a 45-seat B2B analytics company using a project management SaaS on a Growth plan. Their last QBR was 8 weeks ago. At that time, usage was stable, no expansion conversation was planned, and the account was categorized as healthy-flat.
Over the following 6 weeks, the account's product telemetry showed: seat utilization climbed from 72% to 91%, three new users were added (two of them in a department that hadn't previously used the product), and session frequency in that new department was following an onboarding-style ramp pattern — the behavioral signature of a team that was newly integrating the product into their daily workflow.
That telemetry is an expansion signal reading "high" — 35 days before the CSM's next scheduled QBR. A CSM who sees that signal and reaches out proactively to acknowledge the new team adoption and offer onboarding support has a natural, non-pushy entry point for an expansion conversation. A CSM who doesn't see the signal until the QBR is in a more reactive position, often discovering the new usage when the account mentions it rather than leading with it.
Expansion Signals vs. Churn Signals: The Overlap
There's an important subtlety in how expansion signals relate to churn signals: they're not mutually exclusive, and in some situations they're sequential. An account showing strong expansion signal six months out from renewal is likely to have a high renewal rate. But expansion signals that plateau or reverse — a team that was ramping usage and then goes flat — can be an early indicator of churn risk, particularly if the account was expanding organically into new use cases that then stopped.
A well-calibrated account health model should track expansion signal trend, not just expansion signal presence. An account whose expansion signals are strong and growing is healthy and expansion-ready. An account whose expansion signals peaked three months ago and are now declining is potentially at risk — even if their current usage looks solid by absolute metrics.
The CSM Capacity Argument for Expansion Signal Automation
Manual identification of expansion-ready accounts requires a CSM to actively look at product analytics for every account on a regular cadence. For a CSM with 80 accounts, that means reviewing usage trends for accounts that may not have triggered any risk-based alert — a proactive posture that gets deprioritized under workload pressure.
Automated expansion signal detection solves this the same way automated risk detection does: instead of the CSM reviewing every account for expansion readiness, the system flags the accounts that have crossed defined expansion signal thresholds and queues a CSM task for follow-up. The CSM acts on the flagged accounts; they don't need to find them.
The trigger criteria for expansion signals are different from risk criteria — positive rather than negative — but the automation architecture is identical: a threshold is breached, a task is created, and the CSM has contextual information about why the account is being surfaced.
Contraction Signals: The Other Side
Expansion signals have a mirror category: contraction signals. Accounts that are actively reducing usage, letting seats go dormant, or decreasing feature adoption breadth are showing early signs of the kind of disengagement that precedes either a downgrade or a non-renewal. Contraction signals aren't churn confirmations — they're leading indicators that warrant CSM investigation before the account's renewal status is clear.
Common contraction signals: seat utilization dropping below 60% for a plan where it was previously above 80%, a power user going dormant, feature usage narrowing from broad adoption to single-workflow dependency, or export/download activity spiking (which can indicate a team that is collecting data in anticipation of migrating away from the platform).
Tracking both expansion and contraction signals as complementary categories — in the same system that tracks churn risk — gives CS teams a full lifecycle view of each account rather than just a "good/bad" health binary. The accounts that are expanding are the ones worth investing relationship time in for proactive growth conversations. The accounts contracting need triage before risk scores turn red.
The usage data that drives both signals is typically already flowing. Whether it's being read for both purposes is a configuration question, not a data access question.