Every CS leader has had this conversation with their team. Net revenue retention is the metric the board cares about. Expansion is on the scorecard. The CSM nods, agrees, and then quietly does nothing about it for a quarter.
The reason is not laziness. It is identity. Most CSMs got into customer success because they did not want to be in sales. Asking them to drive expansion feels like asking them to become the thing they avoided.
The mistake is treating expansion like a smaller version of new business. It is not. The CSMs who consistently grow accounts are not running a watered down sales motion. They are doing something different, and most of the language and frameworks the industry uses for expansion miss it entirely.
CSMs Are Better At Expanding Than Sales
A new business AE has a single moment of truth with a customer. They get one window of attention to qualify, demo, negotiate, and close. They build a relationship as fast as the deal cycle allows.
A CSM has months. Sometimes years. They sit on calls where the customer talks about problems that have nothing to do with the contract. They watch teams adopt the product, struggle with it, abandon parts of it, find new uses for it. They hear the offhand complaints about:
- the other tool the company uses
- the team that just got hired
- the initiative the VP keeps pushing
- the headcount plan for next quarter
That context is the asset. A sales rep walking into the same account cold has to do discovery. The CSM already did discovery, twelve weeks ago, on a usage call where the customer was just thinking out loud.
Sales is built for compressed decision cycles. CS is built for continuous ones. Expansion lives on the continuous side. The customer is not deciding once whether to buy. They are deciding, every quarter, whether to keep using more of what you sell. The CSM is the only person on either side of the table with a real view into that decision.
This is also why expansion belongs to CS in the first place. When sales owns expansion, the customer feels it the moment the AE shows up. The conversation changes. The trust earned over six months of QBRs gets cashed out for a one quarter quota target. Most accounts notice, and most accounts pull back. (For more on how to structure CS as a revenue engine, read the modern manager of customer success as a revenue architect.)
On Across the Funnel podcast, Paul Staelin, former Chief Customer Officer at Vercel and currently at Relevance AI mentioned the difference perfectly:
“The CSM really spends a lot of time in the midfield trying to build the motion to feed the striker. But you only feed the striker a few times a game.”
That is the work. The CSM is not closing the deal. They are building the conditions under which the deal becomes possible. The AE shows up at the moment of expansion. The CSM is the reason the moment exists at all.
Expanding Is Not Selling, Here’s Why
The vocabulary is the same. The motion is not.
Selling assumes the buyer does not yet have the product. The job is to build belief in something they have not used. Expansion assumes they already have it. The job is to surface what they have not yet realised they need.
That distinction changes everything:
- The questions are different. Sales asks discovery. CS asks about adjacent problems the customer is now ready to solve.
- The pacing is different. Sales runs on quarter-end pressure. Expansion runs on the customer’s calendar, not yours.
- The proof points are different. Sales leans on case studies. Expansion leans on the customer’s own data because they already have it.
Timing: Expansion as a Natural Outcome of Outcomes
Expansion does not work as a calendar event. It works as a consequence.
If the customer hits the outcome you sold them on, the next conversation about expansion is almost inevitable. They start asking how to do more of it. They want the team next door to have what they have. They run into a limit and ask what is on the other side of it.
If the customer has not hit the outcome, no amount of expansion conversation is going to land. They will hear it as you trying to sell them more of something that has not worked yet. The high performing CSMs know this. They will refuse to push expansion into an account that is not delivering value, even when the number is in their plan.
The right sequence is outcome first, expansion second. Not because it is a tactic. Because the order reverses the trust dynamic. When the CSM is the reason the customer succeeded, the expansion conversation is them asking how to do more of what worked. (See our take on why the traditional customer engagement model is broken for the deeper structural problem most CS teams are working around.)
The Signals That Tell You an Account Is Ready to Expand
You don’t have to guess. The account tells you. The CSMs who are good at this are reading three things at once:
- Usage. Not vanity usage. Specific usage. New users showing up from a department that was not in scope. A core feature being used twice as often as it was three months ago. A workflow getting built around something the customer was not paying for last year. (MAU alone is not a useful expansion signal. Depth of use is.)
- The language on calls. The customer starts using “we” in places they used to say “I.” They reference their roadmap. They ask hypotheticals about scenarios that are not in their current contract. They mention another team by name and what that team is trying to do.
- The absence of friction. Expansion conversations land when the renewal is uneventful, the support tickets are stable, and the QBR slides do not have any red on them. If any of those three things are wobbly, you are not in expansion territory. You are in retention territory, and pretending otherwise will make both worse. (See our guide to improving customer retention in B2B SaaS for the retention side of that equation, and our deeper take on churn for what to watch when those signals shift.)
Most CS teams have all of this data. Very few have it in one place. The CSMs who run good expansion motions either have a tool that surfaces it for them, or they build a manual habit of pulling it together before every account review. The ones who try to remember it from memory miss the timing every time. (How to choose the right CSM software walks through what to actually look for in that tool.)
How to Open the Expansion Conversation Without Crossing a Line
There is a moment in every expansion attempt where the customer decides whether the CSM is still on their side. It happens in the first sentence. After that, the trajectory is mostly set.
The line that gets crossed is the one where the conversation stops being about the customer’s outcome and starts being about your number. Most CSMs feel where it is. The mistake is being so afraid of crossing it that they never get close enough to find the conversation that actually matters.
This is where the difference between “selling more” and “helping the customer go further” gets tested. On Across the Funnel podcast, Sara Archer, CRO at ChartMogul, made the case for precision over volume:
“For all of your Recurly users or your Chargebee users, that product marketing update is largely irrelevant. So that expansion or retention decision is a little bit easier.”
The point is not the integration. The point is that the customer feels thought of. Every message they get is shaped around what they actually use. The CSMs who land expansion are running this same precision motion at the account level. They are not pitching a tier. They are connecting a real moment in the customer’s world to a real piece of the product.
The Language That Works
Lead with what you have observed. Tie it to a limitation or opportunity in front of them. Offer to do work that helps them think about it.
“I have been watching the usage on the marketing team and they have ramped up faster than anyone else in the account. They are running into the export limit on the standard plan. Want me to walk you through what their workflow would look like on the next tier?”
That sentence is not a pitch. It is a CSM doing their job. The expansion is implicit, but it is downstream of an observation about the customer’s reality.
Another version:
“The exec team mentioned in the QBR that they want this rolled out to support next quarter. I pulled some data on what that would actually look like at scale. Worth fifteen minutes to walk through it before you get into planning?”
Again, you are not selling. You are showing up to a conversation they already started.
The pattern across both is the same:
- Reference something the customer said or did
- Tie it to a specific limitation or opportunity in front of them
- Offer to do work that helps them think about it
The expansion happens because they ask for it, not because you presented it.
The Language That Kills the Relationship
The opposite pattern is easy to spot once you have heard it a few times. It is anything that sounds like it could have come from a sales call without the rest of the relationship.
- “I wanted to circle back on the additional seats we discussed last quarter.” Nobody discussed it last quarter. The CSM mentioned it. The customer did not engage. Pretending it was a mutual conversation is how you lose the next QBR.
- “Given how well things are going, I think it makes sense to talk about expansion.” This sentence is structurally a sales close. Customers recognise it instantly. The phrase “given how well things are going” is a setup, and the customer can feel themselves being set up.
- “Our pricing for the next tier includes…” If the first thing out of your mouth is pricing, you have already lost the room. Pricing is the last conversation, not the first.
- “We should look at what else might be a fit for you.” Vague. Puts all the work on the customer. Almost no one does that work. The CSMs who expand accounts have already done it for them.
What Separates High Expansion CSMs From Average Ones
The gap between the top quartile and the rest of a CS team on expansion is enormous. It is not about charisma or aggressiveness. The CSMs at the top tend to be the quieter ones. The gap comes down to two things.
Account Knowledge That Sales Doesn’t Have
The high expansion CSMs know things about their accounts that nobody outside CS knows:
- which director is internally championing the product and which one is sceptical
- the headcount changes that happened last quarter
- the project the customer is launching in six weeks that the contract has nothing to do with yet
- the political tension between the team that bought the tool and the team that has to use it
Most of this never gets written down. The CSMs at the top either have unusually good memory or, more often, they have a discipline around capturing it. After every customer call, they update the account record with what changed in the customer’s world. Not what was said about the product. What was said about everything else. (This is the kind of context that drove us to build Hyperengage in the first place.)
Sales does not have access to this layer. They cannot. They do not sit on enough calls. The CSMs who treat their account knowledge as a strategic asset are the ones who turn it into expansion. The CSMs who treat it as something they happen to know are the ones who lose the conversation when it actually matters.
The QBR Is Where Expansion Gets Won or Lost
Most QBRs are reporting exercises. The CSM walks through usage stats, hits the slide that says “wins this quarter,” and then asks if there are any questions. The customer says no. Everyone hangs up. Nothing changes.
The QBRs that drive expansion look different:
- They are framed around the customer’s business, not the product’s performance
- The agenda is built from the customer’s stated priorities for the next quarter
- The product is positioned as an input to those priorities, not the subject of the meeting
- The data the CSM brings is data the customer would otherwise have to pull themselves
The expansion conversation never happens at the end of these QBRs. It happens in the middle, when the customer hits a slide that shows something they did not expect, and they ask a follow up question. The CSM has the answer because they prepared for it. The next thirty seconds is where expansion either gets opened or stays closed. (We wrote a full breakdown of how to reframe the QBR from a usage review into a business case. That is the practical version of this section.)
The CSMs who consistently land in those thirty seconds prepare for QBRs the way sales reps prepare for first calls. They know:
- what they want the customer to walk away thinking
- which insight the customer has not seen yet
- which question they want the customer to ask
- and they have the answer ready
Building an Expansion Motion Your Whole CS Team Can Run
Most CS teams have one or two CSMs who are unusually good at expansion. The rest hit their plan or do not. The leaders who build a real expansion motion are the ones who figure out how to make the top quartile’s behaviour the team’s behaviour. (For the broader frame on this, see the role of CS in SaaS product growth.)
It comes down to three shifts:
- Make the signals visible to everyone. If only the senior CSMs know which accounts are showing expansion readiness, expansion is going to be a function of who is on the account, not which accounts are ready. Put usage data, account changes, and engagement signals in front of every CSM, every week. The signal is not optional. It is the input the team works from. (AI is starting to change how teams do this at scale.)
- Make the language repeatable. The pattern of leading with an observation, tying it to a limitation, and offering to do work is teachable. It is not a personality trait. Write down the openings that work, the openings that fail, and the framing that consistently lands. New CSMs do not have to invent it from scratch.
- Treat expansion as a CS competency, not a sales target dropped onto CS. The two look similar from a distance and are very different in practice. Expansion as a CS competency rewards the inputs that make expansion likely: adoption depth, executive engagement, account health, business outcomes delivered. Expansion as a sales target rewards only the dollars closed, which incentivises CSMs to push before the account is ready, which is exactly the behaviour that loses accounts in the long term. (Building a proper retention management discipline is the foundation under all three shifts.)
The CS teams that get this right are not running a sales motion in disguise. They are running a CS motion that produces expansion as an output. The customers feel the difference. So does the number.
