There’s a debate that keeps resurfacing in CS communities, in leadership offsites, and in board decks about why NDR is stuck below 110%.
It goes like this: CSMs shouldn’t own expansion because they’ll damage the relationship. Let sales handle it. Sales is trained to close.
It sounds reasonable. It also misses the actual problem.
The problem is not that CSMs will ruin a relationship by talking about growth. The problem is that most CSMs have no idea when to bring it up, what signal justifies the conversation, or how to frame it so it feels like a natural continuation of the work they’re already doing. Fix those three things, and CS-led expansion becomes the most logical motion in post-sales. Ignore them, and you end up with either CSMs who never mention growth at all, or CSMs who bring it up at exactly the wrong time and create the friction everyone was trying to avoid.
Handing expansion to sales doesn’t solve the problem. It just outsources it.
Why the “Let Sales Handle It” Argument Falls Apart
The case for keeping sales in charge of expansion usually rests on one idea: the CSM’s primary job is to protect the relationship, and introducing commercial conversations puts that relationship at risk.
This view treats the relationship and the revenue as separate things. They’re not.
When a customer is getting real value from your product, expansion feels obvious to them. They don’t experience it as being sold to. They experience it as being helped. The conversation that surfaces an expansion opportunity at the right time, grounded in what the customer has already told you they need, isn’t a sales call. It’s a continuation of the success conversation you’ve been having for months.
The version that damages relationships is different. That’s when a CSM flags an account for upsell because a renewal is coming up, or because a sales rep set a Q3 quota target on the account. The customer can feel the difference between “here’s something that will help you” and “we need to hit a number.” The awkwardness isn’t inherent to CS-led expansion. It’s a symptom of doing it without the right conditions in place. That misalignment between timing and commercial intent is one of the oldest problems in customer retention management, and it doesn’t get better by moving the conversation to a different team.
The CSM Already Has Everything Sales Doesn’t
Here’s what sales reps don’t have when they step into an existing account: they don’t know which problems the customer has been quietly raising for two quarters. They don’t know that the champion switched teams and the new stakeholder has different priorities. They don’t have the context to read whether an account is ready to grow or quietly de-risking before a contract decision.
The CSM has all of that. That relational context is the whole point. The mistake isn’t letting CSMs into expansion conversations. The mistake is sending sales in without giving them that context, and then acting surprised when the conversation lands flat.
Kelly McGuire, VP of Customer Success at Everstage, described the information architecture behind this on the Across the Funnel Podcast:
“We have something that… sales captures a lot of things within the sales process and that gets transferred over to us in CS, so that we have what I’ll call situational fluency in understanding why the customer purchased, what their buying decisions were, what the challenges were, because I want my CSMs to feel like sellers because they are.”
This is the framing that matters. Not “CSMs should become salespeople,” but CSMs who understand the commercial context of the accounts they manage are better positioned to know when and how to raise a growth conversation. Situational fluency is what separates a CSM who stumbles into an expansion conversation from one who leads it with confidence.
The Signal Problem Is the Real Problem
Most CSMs who feel uncomfortable with expansion conversations aren’t uncomfortable because they’re bad at selling. They’re uncomfortable because they have no clear, defensible reason to have the conversation right now.
When expansion timing is driven by the calendar (renewal coming up, Q3 closing), or by a gut feeling, or by a hand-off from a sales rep who noticed whitespace, it puts the CSM in an impossible position. They’re being asked to start a commercial conversation with nothing to stand on except someone else’s revenue target.
Signal-based expansion changes that entirely.
When a CSM can say “I noticed you’ve added four users to this workspace in the past three weeks, and two of your use cases are running into the limits of your current tier,” that’s not a sales pitch. That’s a CSM doing their job well. The expansion follows naturally from the observation. There’s nothing awkward about it because the CSM isn’t initiating a commercial conversation. They’re responding to something real that’s happening in the account.
This is the infrastructure that makes CS-led expansion revenue work. Not sales training for CSMs. Not commission structures that make CSMs feel like account executives in disguise. Timely, specific, product-grounded signals that give CSMs a legitimate reason to have the conversation.
What Signals Actually Matter for Expansion Readiness
Not all signals are created equal. Feature adoption breadth, seat utilization rates, volume metrics approaching plan limits, and the emergence of new use cases inside an account are all meaningful. A spike in logins from users who haven’t been part of previous conversations is often the strongest early indicator of organic demand that hasn’t been formalized yet.
Health scores matter here, but in a specific way. A green health score tells you the account is stable. It doesn’t tell you it’s ready to expand. What you’re looking for is directional movement: accounts where adoption is accelerating, where users are pushing into parts of the product they weren’t engaging with before, or where the champion has been talking about new business problems your product can address. Most health scoring frameworks are built for churn prevention, not expansion readiness, which is why most customer health scores fail to surface the full picture.
The teams getting this right don’t wait until renewal to surface these patterns. They build adoption accountability earlier in the customer lifecycle so the expansion conversation emerges from a foundation of documented progress, not a looming deadline.
Ryan Milligan, CRO at QuotaPath, made this point directly on the Across the Funnel Podcast:
“The standard account manager comp plan is half of your variable off of gross revenue retention and then half of your variable off of expansion. The reason you split it is because you want somebody to feel the pain of churn. And if you just do net revenue retention, sometimes you can have a massive expansion that overshadows all of your churn and contraction. For orgs that want comp plans that are a little more up-funnel, I am seeing more teams use implementation and adoption as components of the variable comp plan so that an account manager cares about adoption well before renewal, basically.”
This is the structural argument. If your customer success strategy only surfaces expansion at renewal, you’re always going to be late. Comp plans that reward adoption visibility early are one lever. But the deeper fix is operational: building a motion where the signals that precede expansion get tracked, surfaced, and acted on well before a contract date is on anyone’s radar.
Building the Operational Framework for CS-Led Expansion
None of this works without the infrastructure to support it. Signal-based expansion requires that signals actually reach CSMs in a usable form. Product telemetry needs to feed into account views. Adoption trends need to be visible alongside renewal dates and account health. And CSMs need to know what patterns to look for and what to do when they see them.
The CS platform conversation is relevant here, but it’s secondary to the process question. The process question is: how does a CSM know, on a given Thursday morning, that a specific account is ready for an expansion conversation? If the answer is “they check the renewal date” or “a sales rep flags it,” the infrastructure is broken. If the answer is “they see that seat utilization crossed 85% and three new users joined in the past ten days,” that’s a CSM who can walk into a conversation with something real.
This connects directly to NRR accountability. CS teams that own expansion as a motion, rather than a handoff, tend to have cleaner data on where expansion revenue comes from. They can point to specific signal categories that preceded expansions. They can run cohort analyses on which onboarding patterns correlate with early upsell. That kind of evidence is what makes a CS leader’s case for resources, headcount, and tooling. It’s also what separates “CS is a cost center” companies from “CS drives NDR” companies.
Hyperengage is built around exactly this problem: making account signals actionable before it’s obvious a conversation needs to happen.
CS-Led Doesn’t Mean CS-Only
There’s a version of this argument that goes too far in the other direction: CS should own expansion entirely and sales should stay out. That’s also wrong.
The more useful model is that CS leads the identification and the timing, and sales gets involved when the commercial complexity justifies it. For many accounts, especially commercial and mid-market, the CSM can carry the entire motion. For enterprise accounts with complex buying committees or significant contract changes, bringing in a sales rep at the right moment can actually accelerate things. Not because CS can’t handle it, but because having someone step into a specific commercial role at a specific point is sometimes strategically useful.
What doesn’t work is handing expansion off to sales as a default, with no CS involvement in surfacing when the timing is right. That wastes the relational context CSMs have built, and it puts sales in the position of recreating context that CS already has. The QBR is one natural place to surface expansion readiness in a structured way, with data, customer goals, and demonstrated outcomes already on the table. Done right, it creates the conditions for the conversation to happen without a CSM ever having to walk in and say “we think you should upgrade.”
Kelly McGuire again on what CS ownership of the customer actually means in practice:
“But for us, the success of that starts well before the handoff. I think customer success is really truly an organization that owns customer obsession across all aspects. Because to me, customers are the heartbeat of the org. If you don’t take care of that heart, what are we doing? Why are we here?”
Customer obsession and expansion aren’t in conflict. A CS org that deeply understands its customers’ evolving goals is the most natural place for expansion conversations to originate. The work is building the infrastructure, the signals, and the operating rhythm to support them.
The Timing Conversation You Actually Need to Have
Expansion readiness isn’t a single signal. It’s a convergence of conditions.
The customer has achieved a clear, documented outcome with the current product scope. That outcome has been recognized not just by the CSM, but by the customer themselves. There’s evidence of new use cases emerging, or growing usage pushing against current constraints. The champion has expressed future ambitions your product can address.
When these conditions exist together, the expansion conversation doesn’t feel like a sales call. It feels like the next natural step in the success conversation. “You’ve hit X, your team has grown from three users to nine, and you mentioned last quarter you wanted to expand to this new workflow. It looks like you’re approaching the limits of your current tier. Want to look at what the next step would look like for you?”
That’s not an upsell. That’s a CSM with the right information, at the right time. And building the system that produces that moment consistently, across every account in the book, is the actual work of customer success in a business that takes revenue seriously.
Conclusion
The argument that CS should stay out of expansion to protect the relationship assumes the alternative is safer. It’s not. Handing expansion to sales means losing the relational context, the signal visibility, and the timing advantage that only a CSM has. What damages relationships isn’t CS-led expansion. It’s expansion conversations that happen for the wrong reasons, at the wrong time, without a legitimate signal behind them. Solve the signal problem and the timing problem, and the relationship problem disappears. CS-led expansion isn’t a risk to manage. It’s a motion to build.
