I've spent the better part of a decade thinking about what drives expansion in enterprise software accounts.
Not the obvious answers — good product, happy customer, strong relationship. The more specific ones. The behavioral and organizational factors that predict whether a customer who starts at one level will grow to five times that investment or stagnate and eventually churn.
Three patterns show up consistently.
1. Second Use Case Velocity
The single strongest predictor of expansion I've found is how quickly a customer adopts their second meaningful use case.
Not their first. Every customer has a first use case — it's what they bought the platform for. The first use case is selection. The second use case is adoption.
When a customer moves from their initial use case to a second one within a defined window — and that second use case is in a different business domain or serves a different internal user group — the probability of expansion increases dramatically. When they stay on one use case for an extended period, the probability of expansion approaches that of churn.
The practical implication: stop celebrating go-live. Start measuring and accelerating the second use case.
2. Internal Advocacy Infrastructure
The accounts that expand don't just have happy users. They have internal advocates who actively promote the platform within their organization.
This is different from executive sponsorship, which many customer success programs track. Executive sponsorship gets you budget. Internal advocacy gets you adoption across teams.
The advocate is often not the buyer and not the primary user. They're the person who goes to other team leaders and says "you should see what we're doing with this" — who creates the internal demand that the account team then converts into expansion.
Building the conditions for internal advocacy to emerge — and tracking whether it's happening — is one of the highest-leverage things a customer success program can do.
3. Outcome Attribution
Customers who can clearly articulate the outcomes they've achieved from the platform — in their own words, to their own leadership — expand at significantly higher rates than customers who experience value but can't attribute it.
This sounds obvious. It is not widely operationalized.
The attribution work requires your customer success team to help customers build the narrative of value — connecting platform usage to specific outcomes, in terms that resonate at the executive level. Not "we completed the integration" but "we reduced the time to provision a new customer from six weeks to two days, which contributed to a 15% reduction in time-to-value for our own customers."
When that narrative exists, the customer can make the internal case for more investment. When it doesn't exist, even happy customers struggle to justify expansion to their CFO.
The Implication for Customer Success Programs
Most customer success programs are optimized for retention — preventing churn. The interventions are reactive: red accounts get attention, green accounts get left alone.
Expansion-oriented customer success is proactive and leading-indicator-driven. It tracks second use case velocity, monitors for the conditions that produce internal advocacy, and invests in outcome attribution as a core CS motion.
The difference in results between retention-oriented and expansion-oriented programs is not marginal. It's the difference between a flat business and a growing one.
Views are personal.