How do you coach a CSM to spot expansion opportunities?

What signal-spotting actually is, and why it decides your net revenue retention

Expansion signal-spotting is a repeatable reading skill, not a personality trait. The CSM already holds the richest commercial dataset in the company — login frequency, seat consumption, feature adoption curves, support ticket themes, stated roadmap goals from the last three QBRs, and the org chart of who got promoted. What they usually lack is a translation layer that turns "this account uses 92% of its licenses" into "this account has an unfunded hiring plan and a procurement window in six weeks." Coaching closes that translation gap.

The stakes are structural. In most subscription businesses, net revenue retention is the single largest determinant of growth efficiency, because expansion dollars carry almost no acquisition cost. A dollar of expansion from an account that already trusts you does not require a demand-gen spend, an SDR sequence, a discovery call, a security review, or a legal redline cycle. It requires someone noticing at the right moment and saying something useful. That asymmetry is why RevOps leaders keep pushing expansion motion ownership toward the team with the most account context, and why the coaching conversation is worth doing well rather than delegating to a one-off enablement deck.

There are four distinct failure modes, and they demand different coaching. A skill gap looks like a CSM who can narrate account health fluently but stalls when asked "so what's the play?" — they see the data and not the move. A will gap looks like a CSM who names the play accurately and then never runs it, usually protected by a phrase like "I don't want to be salesy." A knowledge gap looks like a CSM who cannot describe what actually unlocks the next tier, so they cannot recognize an account that has outgrown its plan. A process gap looks like a CSM who does everything right, hands the signal off, watches it disappear into an AE's pipeline, and receives no credit — after which they quietly stop.

The diagnostic is cheap. Pull three of the CSM's healthiest accounts, put the usage data on screen, and ask a single question per account: "What's the next expansion here?" If they answer "they're happy, nothing needed," you have will or knowledge. If they describe the opportunity but shrug at the next step, you have skill or process. Three accounts and twelve minutes gets you a real diagnosis instead of a guess, and the diagnosis determines whether you spend the next month on portfolio training, role-play, or rebuilding the handoff.

One nuance worth naming early: healthy accounts are the biggest expansion misses. Most CS cadences are built around risk — the weekly meeting is a churn-risk review, the alerting is tuned to declining usage, and the escalation paths all point downward. An account that is quietly succeeding generates no alert, appears in no meeting, and gets a fifteen-minute check-in. That is precisely the account with the highest expansion probability, and your cadence structurally hides it. Fixing the cadence is often a bigger lever than fixing the CSM.

The step-by-step coaching process, from diagnosis through logged opportunity

Run the coaching as a defined sequence rather than an ambient encouragement. The sequence below takes about a month to install and roughly a quarter to show up in pipeline numbers.

Step one — build the signal checklist before you coach anyone. A CSM cannot spot what has not been named. Write down six to eight concrete triggers specific to your product: seat or license saturation above a threshold you pick (many teams use 85–90%), a new team or department appearing in the login data, a stated business goal in QBR notes that your current tier cannot deliver, a champion promotion or lateral move into a larger org, support ticket volume clustering around a capability that lives in a higher tier, an integration request pointing at a system you charge for, a usage pattern that indicates workarounds (heavy CSV export usually means someone is rebuilding a report you already sell), and renewal timing with strong health. Keep it to one page. A checklist nobody can recite is a document, not a habit.

Step two — run a GROW 1:1 with real account data on screen. Twenty-five minutes, one account, no slides. Open with the reframe: the CSM's job is making sure the customer gets every bit of the outcome they bought, and sometimes that outcome needs more than they currently own — staying quiet about it is the actual disservice. Then move to reality: read three live signals aloud and ask the CSM what each one implies and what it would unlock for the customer. Then options: tee it up for the AE with a warm intro, co-run a value conversation, or raise it directly in the next QBR. Then will: commit to a logged opportunity today with a named next step inside two weeks.

Step three — pre-empt the trust objection instead of dismissing it. When the CSM says "I don't want to seem salesy," the worst response is "that's not selling." The fear is real and often earned by a bad prior experience. Use the road analogy: if someone told you where they were trying to get and you knew the route, would silence be a kindness? Then make it concrete with their own account — they already told you they want EMEA coverage; you already know what it takes. Connecting those two facts is service.

Step four — separate spotting from closing, formally. Write a No-Sell Handoff Protocol and hand it to the CSM as a document, not a vibe. The CSM never quotes a price, never sends a contract, never negotiates. Their line is close to: "I see a way to get you more value here. I'd like to bring in [rep] to walk through options — my role is making sure it's the right fit, not selling you anything." Then they pass a short written summary — signal, desired outcome, recommended tier, key stakeholders, timing constraints — and stay on the first call. Practice the script aloud until it stops sounding memorized, usually three to five repetitions.

Step five — install the cadence. Month start is a signal sweep: every account reviewed against the checklist, every green signal logged. Weeks one and two are for teeing up the strongest signals with warm intros or booked value conversations, with you role-playing the handoff first. Weeks three and four are co-selling, where the CSM owns the outcome narrative and the AE owns commercials, followed by a debrief on each. Ongoing, coach the CSM to end every QBR with the next outcome rather than a usage recap, which converts the QBR from a report into a harvest.

Step six — debrief the misses harder than the wins. A closed expansion teaches one outcome. A signal that was spotted late, or handed off badly, or died in an AE's queue teaches you where the system leaks. Keep a running list of dead signals and read it monthly; the pattern in that list is your actual coaching curriculum.

Effort, timelines, and the ranges you should expect

Coaching this well costs less time than most managers assume and pays back slower than most executives assume. Budget honestly on both sides.

Manager time. Building the signal checklist takes one working session — two to three hours if you pull a product marketer and an AE into the room, which you should, because the checklist is only credible if it reflects what actually gets sold. The initial GROW 1:1 is twenty-five minutes per CSM. The weekly signal-to-play drill runs fifteen minutes inside an existing standup, so its marginal cost is near zero. Monthly sweep review is roughly thirty to forty-five minutes per CSM depending on book size. For a team of six CSMs, that lands around four to six hours of manager time per month once installed, front-loaded with maybe eight hours in the first two weeks.

CSM time. The sweep itself is the real cost. A CSM carrying 40–60 mid-market accounts can review their full book against a one-page checklist in two to four hours if the data is in one dashboard, and considerably longer if they have to assemble it manually from three systems. That gap is a RevOps problem, not a coaching problem — if the sweep takes a full day, it will be skipped by month three, and no amount of accountability will save it. Fix the data assembly before you demand the habit.

Ramp curve. Expect logged-opportunity volume to jump in weeks two through four, because the first sweep surfaces a backlog of signals that have been accumulating unnoticed. Do not read that spike as steady-state performance. The honest baseline shows up around month three, after the backlog is drained and the CSM is flagging genuinely new signals. Pipeline conversion lags further; if your expansion sales cycle runs 30–60 days, closed expansion revenue attributable to the coaching typically appears in the second quarter after install, not the first.

Volume ranges. A reasonable working target is roughly three to eight logged expansion opportunities per quarter per fifty accounts, but treat that as a starting hypothesis rather than a benchmark. The real number swings hard on product complexity, tier structure, and average deal size. A product with a single upgrade path and a $40k tier jump produces far fewer, far larger signals than a product with six add-ons and per-seat pricing. Calibrate against your own first two quarters, not against a number you read somewhere.

Where the math breaks. If your tier boundaries are fuzzy — if nobody can say cleanly what Enterprise includes that Pro does not — the CSM cannot spot anything, and the coaching will fail for reasons that have nothing to do with coaching. Same if the expansion pricing requires a custom quote every time. Signal-spotting depends on a legible product ladder. When the ladder is illegible, fix packaging first and treat the coaching as phase two.

Where teams get this wrong

Comping only on retention and CSAT. This is the dominant failure, and it is not subtle. Whatever the reframe says, the comp plan tells the CSM what the company actually wants. If renewal rate and satisfaction score are the only inputs, expansion is unpaid work performed at personal risk, and rational people stop doing unpaid risky work. Add an expansion-sourced component or an NRR component — it does not have to be large, but it has to exist and it has to pay on *sourced*, not closed, or you have made the CSM dependent on an AE's execution for their own income.

Turning CSMs into AEs. The overcorrection is as damaging as the neglect. Mandating that CSMs close deals usually destroys the trusted-advisor position that made the expansion visible in the first place, and it puts someone who was hired for outcome expertise into a negotiation they are not trained for. Spot-and-warm-hand with clean credit is the right default for most teams. Full CSM-owned closing works in specific conditions — small, standardized expansions with published pricing and no procurement cycle — and poorly outside them.

Coaching the skill before building the path. If a CSM flags a signal and nothing happens, they have learned that flagging is pointless, and that lesson is very hard to un-teach. Build the route first: where does the opportunity get logged, what field marks it CS-sourced, who picks it up, what SLA governs response, and how does the CSM find out what happened? A two-day response SLA on CS-sourced opportunities does more for signal volume than any amount of encouragement.

Coaching the deal instead of the reading. Jumping into an active expansion and helping close it feels productive and teaches almost nothing transferable. The compounding skill is pattern recognition across the whole book. Spend the coaching time on drills that build the reflex, and let the AE run the deal.

Dismissing the trust fear. Telling a CSM their concern is unfounded produces compliance in the meeting and resistance everywhere else. Address it directly, give them a script that structurally cannot violate trust because it contains no commercial ask, and then show them proof from their own accounts — a customer who thanked them for surfacing a capability is worth more than any framework.

Building a cadence that only looks at risk. Covered above, but it belongs on this list too, because it is the most invisible mistake. Audit your weekly team meeting: if every account discussed is red or yellow, your operating rhythm has made expansion structurally unobservable.

Letting the sweep degrade into a checkbox. Month four is when the sweep becomes a spreadsheet someone fills in the morning of the review. Guard against it by spot-checking two accounts per CSM per month against the raw data — not to catch people, but because a sweep that nobody verifies stops being a sweep.

A decision framework for who runs the expansion, and when

Not every signal deserves the same motion, and forcing one motion onto all of them is how teams end up with either a bottlenecked AE or a CSM out of their depth. Segment by deal shape.

CSM raises it directly in the QBR when the expansion is small, standardized, and priced publicly — additional seats on an existing contract, a well-known add-on, an extension of an existing agreement. The customer already knows what it costs, there is no negotiation, and involving a rep adds friction without adding value.

CSM tees it up and hands off warm when the deal involves a new tier, a new business unit, a security or procurement review, or any pricing that requires a quote. Here the CSM's job is the introduction and the context transfer, and their credibility is the asset — the AE inherits a warm room instead of a cold one.

CSM and AE co-run when the expansion depends on a value case that the CSM alone can build but cannot close. The CSM owns the outcome narrative — what the customer said they wanted, what the data shows, what the gap costs them today — and the AE owns commercial structure, terms, and timing. This is also the best learning motion; a CSM who has sat through six co-run conversations reads signals far better than one who has read six frameworks.

Escalate to leadership when the signal is a strategic expansion — a multi-department rollout, a platform consolidation, a competitive displacement inside the account. These are rarer, they need executive air cover, and they usually fail when a CSM tries to run them through a mid-level champion.

The adjacent case worth planning for: renewal timing. A signal spotted 90 days before renewal behaves completely differently from one spotted 30 days out. Early, you have room to build a case and expand cleanly. Late, the expansion conversation gets tangled in renewal negotiation, and the customer will often use it as leverage on price. Coach the CSM to treat the renewal calendar as part of the signal — the same green light means "act now" at 90 days and "flag it and wait for post-renewal" at 30.

Drills that build the reflex, and the metrics that prove it worked

Frameworks fade; drills stick. Run these on a schedule rather than when you remember.

Signal-to-play, weekly, fifteen minutes. You name a signal — "they hit 100% of licenses," "their champion just became VP of Ops," "they asked whether reporting can be scheduled" — and the CSM has thirty seconds to state the play and the buyer. Speed matters here; the point is building an automatic association, not a thoughtful essay. The hard rule that makes this work: no signal counts as spotted without a concrete next action attached, and "mention it at the next QBR" is not a next action. "Send the champion the upgrade comparison today" is.

Outcome gap articulation. Give the CSM a real account and have them state, in two sentences, the outcome the customer is chasing and what is currently blocking it. If the blocker is something a higher tier or add-on resolves, that is a clean, non-commercial expansion trigger. Then have them script one sentence to surface it: "Your team is spending roughly twelve hours a week rebuilding that report manually — there's a way to cut that substantially. Want me to show you?"

Warm-handoff role-play. The CSM introduces an AE into an account they own, aiming for the handoff to land as a gift rather than a pitch. Coach the specific language that preserves their advisor position. Most CSMs over-apologize here; the fix is usually removing three words, not adding a paragraph.

Health-score audit. Hand the CSM their book sorted by health descending and have them flag the green-but-not-expanding accounts. The exercise makes the structural blind spot visible in a way no explanation does.

Reverse role-play. The CSM plays a manager talking a nervous peer into a commercial conversation. Arguing the case out loud internalizes it faster than hearing it.

On measurement, pick leading indicators over lagging ones for coaching purposes. Expansion pipeline sourced by CS — dollar value flagged or warm-handed, credited regardless of who closes — is the cleanest proof the reading skill is working. Signal-flagging rate per account per quarter tells you whether the sweep is actually happening. Time-to-action on a signal catches the slow leak where signals are seen but sit; stale signals are missed expansion with extra steps. QBR-to-opportunity conversion tells you whether QBRs went commercial or stayed as usage recaps. And NRR is the shared outcome the whole motion exists to move, which is exactly why it is useless as a coaching metric — it moves too slowly and depends on too many hands to give a CSM feedback they can act on this week.

One adjacent measurement worth watching from a RevOps seat: the ratio of CS-sourced opportunities that convert versus AE-sourced expansion opportunities. If CS-sourced converts materially better, you have quantitative proof that account context beats prospecting on expansion, and that number is the argument that gets the comp plan changed.

Related questions

Should CSMs carry a quota?

Usually not a closing quota. A sourced-pipeline target or an NRR component works better — it pays for the reading skill you actually want without pushing the CSM into negotiations that damage the advisor relationship the expansion depends on.

How do you spot expansion in a flat, non-growing account?

Look for workaround behavior rather than growth signals: manual exports, shadow spreadsheets, support tickets about capabilities you already sell. Flat accounts expand through efficiency gains, not headcount, so the outcome gap is about wasted effort.

What if the AE ignores CS-sourced opportunities?

Fix it with an SLA and visibility, not escalation. Set a two-day response requirement on CS-sourced opportunities, report response rates by rep monthly, and make sourcing credit visible to both parties.

Does this work for a CSM with 200 low-touch accounts?

Not as a manual sweep. At that scale, the checklist becomes automated alerting and the CSM coaching shifts to acting on a queue rather than reviewing a book. The reading skill is identical; the surfacing mechanism changes.

How early should a new CSM start expansion coaching?

After they can run onboarding and a QBR competently, typically month three to four. Teaching commercial signal-reading before they have product and outcome fluency produces mechanical pattern-matching without credibility.

FAQ

What is the most common reason CSMs miss expansion opportunities?

The belief that their job is strictly adoption and retention, and that any commercial conversation damages trust. It is a mindset barrier far more often than a skill barrier, which is why enablement decks about the product portfolio rarely fix it on their own.

How do I tell a skill gap from a will gap?

Ask the CSM to name the play on a healthy account. If they identify the signal but cannot connect it to a next step, that is skill. If they identify both and still do nothing — usually accompanied by "that feels salesy" — that is will, and it needs a reframe plus a script, not more training.

Which signals should a CSM actually watch?

Seat or license saturation, a new team appearing in usage data, a stated goal that requires a higher tier, a champion promotion, support volume clustering around a paid capability, integration requests, workaround behavior like heavy manual exports, and renewal timing with strong health. Any one of them warrants a logged opportunity.

How do you coach someone to act without feeling like they are selling?

Give them a script with no commercial ask in it. The CSM names the gap, offers to bring in someone who can walk through options, and explicitly states their role is fit, not sale. A script that structurally cannot violate trust removes the fear far better than reassurance does.

Should the CSM run the deal or pass it to sales?

Depends on deal shape — standardized and publicly priced, the CSM can raise it directly; new tier or procurement involved, hand it off warm. What matters more than the routing is that no green signal ever sits unlogged while someone decides.

Do health scores and product analytics make this coaching unnecessary?

No — they invert the problem. When tooling surfaces signals automatically, the bottleneck moves from detection to action: which signals matter, what to say, when to involve sales, and how to keep the relationship intact. The coaching gets more valuable, not less.

Sources

• Gainsight blog — customer success and expansion practice
• Winning by Design resources — recurring revenue models
• Harvard Business Review — customer relationships and growth
• Vitally blog — customer success operations
• Gong Labs — conversation research
• Clari blog — revenue operations and retention
• OpenView Partners — SaaS benchmarks and expansion metrics
• Bessemer Venture Partners — cloud metrics and NRR

Related on PULSE

• [Top 10 Coaching Techniques for Renewals and Expansion Reps](/knowledge/cg0799)
• [How do you coach an account manager to expand NRR inside a flat renewal?](/knowledge/cg0930)
• [How do you spot a struggling remote rep before it's too late?](/knowledge/cg0190)
• [Top 10 questions to coach a rep on strategic account planning](/knowledge/cg0851)
• [Top 10 questions to coach a rep on value-based selling](/knowledge/cg0838)
• [How do you coach a brand-new sales manager on their first hire?](/knowledge/cg0802)