If you asked most CS leaders where their next growth is going to come from, they'd point to the pipeline. New logos. New markets. New product launches. The assumption is that growth lives upstream, in acquisition, and that the job of CS is to protect what's already been won.
That assumption is leaving significant revenue on the table every single quarter.
The most accessible growth opportunity in most SaaS businesses isn't in the pipeline. It's in the existing book of business. It's sitting in accounts that are already paying, already using the product, already in a relationship with your team. It's expansion that makes complete sense for those customers, that they would say yes to if the right conversation happened, that nobody has uncovered yet.
Call it latent expansion. It's not hypothetical. It's not aspirational. It's already there. It just hasn't been found.
Why It Stays Hidden
Latent expansion doesn't stay hidden because CS teams are bad at their jobs. It stays hidden because of a combination of factors that most organizations never stop to examine.
The first is misaligned incentives. In many CS organizations, the CSM is measured on retention. Churn rate, renewal rate, health scores. Expansion is someone else's number, usually sales. So the CSM, consciously or not, optimizes for the thing they're measured on. They keep accounts happy and renewing. They don't proactively look for growth because growth isn't their job.
The second is discomfort. CS professionals, especially those who came from non-sales backgrounds, often have a visceral resistance to anything that feels commercial. They chose this career because they want to help customers, not sell to them. The idea of bringing up additional products or higher service tiers feels like it crosses a line. So they don't.
The third is a lack of framework. Even CSMs who want to identify expansion opportunities often don't know how to do it systematically. They don't have a clear picture of what the expansion path looks like, what milestones signal that a customer is ready for the next step, or how to have the conversation in a way that feels natural rather than forced.
Remove any one of those three factors and you start uncovering latent expansion. Remove all three and you unlock it at scale.
What Latent Expansion Actually Looks Like
Latent expansion isn't a mystery. It's a customer who has grown into a place where the next product, the next tier, the next capability is the obvious next step. They just haven't taken it yet.
It's the customer who started with one module and has built their program to the point where a second module would immediately make their work easier. They haven't asked for it because nobody told them it existed in a way that connected to their specific situation.
It's the customer who is spending hours a month on manual work that a higher service tier would automate. They haven't upgraded because nobody showed them the math.
It's the customer who is about to hit a scale threshold where their current setup is going to start creating friction. They don't see it coming because they're focused on today, not six months from now. The CSM, who has seen this pattern before, could see it coming.
In every case, the value is there. The fit is there. The customer would benefit. The only thing missing is the conversation.
The Orchestrate vs. Execute Decision
Not all latent expansion is equal. Some of it requires orchestration, planting a seed now for a conversation that will happen when the customer reaches a future milestone. Some of it is immediately actionable, the customer is already at the point where the conversation needs to happen now.
Learning to tell the difference is one of the most valuable skills a CSM can develop.
The orchestration play is for customers who are on their way to needing something but aren't there yet. You mention it early. You give them time to think and budget. You commit to coming back when they're ready. You're building a pipeline inside the relationship.
The execute play is for customers where you look at the account and realize: they needed this six months ago and nobody told them. That's not a seed to plant. That's a conversation to have this week. The latent expansion is immediately uncoverable.
Both require a CSM who knows the product expansion path well enough to map it to the customer's journey, and who knows the customer well enough to know where they are on that path at any given time. That's not complicated. But it is specific. And it has to be taught and practiced, not just talked about.
The LTV Equation
Here's the business case in plain terms.
Every month a customer sits at a level below where they should be, where they would genuinely benefit from the next thing and just hasn't gotten there, is a month of LTV that doesn't exist. It's not lost. It was never created. The customer didn't get the value they could have gotten. You didn't capture the revenue that was available. Both sides lose.
Multiply that across a book of business. Across a year. Across every CSM who is waiting for the right moment that never quite comes. The number gets large very quickly.
Latent expansion isn't a nice-to-have. It's not a growth hack. It's the difference between a CS organization that's doing its job and one that's doing part of its job. The part that protects. But not the part that grows.
The revenue is already in your book of business. The question is whether you have a system to find it.
Lincoln Murphy formally named and popularized Customer Success starting in 2010 and has spent 15 years connecting it to expansion revenue and commercial outcomes. Read The Premise.