Your CSM heard the customer mention an adjacent use case three months ago.
Nothing happened. The customer expanded with a competitor last week.
The motion has phases or it doesn't. Most CS teams don't.
Why CS Expansion Motions Stall Without Defined Phases
A CSM hears the customer mention an adjacent use case in a check-in. They make a note. Three weeks later, they remember to follow up. The customer has already started talking to a competitor. The expansion that was sitting in front of CS for a month becomes a renewal conversation about why the customer is looking elsewhere.
Or the inverse failure. A CSM logs a signal, but nobody defines what "qualified" means. The deal sits in limbo for two months while CS waits for the customer to "make it more concrete." The customer expands with someone else — they thought the conversation had stalled.
Both failure modes are the same root cause. Expansion is a motion with phases — Signal, Qualification, Close — and most CS teams haven't defined them. The signal sits without an owner. The qualification has no completion criteria. The close happens (or doesn't) based on whoever feels ready, whenever they feel ready. There is no protocol. There is only a hope that expansion will happen if you wait long enough.
The most common cause of expansion deal slippage isn't pricing, product fit, or customer readiness. It's that the motion has no defined phases — so signals stall, qualifications drag, and closes happen by accident. The most common failure mode is also the most fixable.
The Unit Economics of Expansion Revenue vs New Acquisition
The unit economics on expansion are dramatic enough that the operational sloppiness most companies tolerate around it is hard to justify once the numbers are in front of you.
Bessemer Venture Partners analysis of Pacific Crest SaaS data calculated the cost of acquiring expansion revenue at roughly forty-three percent of new-customer CAC — twenty-seven cents per dollar of expansion ARR versus one dollar and thirteen cents per dollar of new ARR. Expansion is roughly four times more capital-efficient than acquisition. Most SaaS companies treat the more efficient revenue source as the afterthought and spend the bulk of their sales energy on the less efficient one.
McKinsey's 2024 analysis of more than one hundred B2B SaaS companies put top-quartile NRR at one hundred thirteen percent and bottom-quartile at ninety-eight percent. The fifteen-point spread isn't a product or relationship problem. It's an ownership and protocol problem. The companies running structured expansion ownership compound. The companies without it don't.
The compounding shows up most clearly at scale. Best-in-class SaaS companies above fifty million ARR derive more than half their new ARR from expansion, while bottom-quartile companies at the same scale derive less than a fifth. The companies that build the expansion ownership protocol at five million ARR don't have to retrofit it at twenty million when expansion becomes the primary growth driver. The companies that don't build it early are scrambling at the exact stage when scrambling is most expensive.
For Alex at eight million ARR with one hundred and two percent NRR, moving to one hundred and ten percent over twelve months is worth roughly six hundred forty thousand dollars in retained-and-grown ARR — at twenty-seven cents per dollar of expansion versus one dollar and thirteen cents per dollar of new acquisition. The protocol is the highest-impact operational change available because it costs nothing: no new headcount, no new tools, just a stage definition and a handoff trigger.
Expansion · Grow Scalably
Three phases of the expansion motion. Define each one. Set the trigger between them.
In most $5–10M ARR companies, CS owns the whole motion. Three phases on the customer record — with one explicit trigger between qualification and close.
Phase 01
Signal
Usage hits 80% of tier limit. A 10th seat gets added. Customer expresses an adjacent use case. CS noticing what the customer is doing.
Phase 02
Qualification
CS-led discovery of use case, scope, timing. Relationship context CS already has — not commercial expertise.
Phase 03
Commercial Close
Pricing confirmed, procurement mapped, contract drafted. The motion that started as a signal now closes.
The trigger
Qualification complete when the customer has done three things
01
Customer named the use case in their own words — not the CSM’s framing.
02
Customer attached the expansion to a timeframe or business event.
03
A second stakeholder on the customer side is engaged.
The unit economics
Expansion costs $0.27 per dollar of ARR. New acquisition costs $1.13 — roughly 4x more.
15pt
NRR gap between top quartile and bottom quartile — a protocol problem, not product
The motion has phases or it doesn’t. The trigger between qualification and close is what separates a protocol from an accident.
The Three Phases of SaaS Expansion: Signal, Qualification, Close
Expansion is a motion with three distinct phases — Signal, Qualification, and Close. CS owns the motion end-to-end, with one explicit trigger between Qualification and Close. (If you have dedicated expansion AEs who own existing accounts and get comped on expansion, the Close phase hands off to them. Same framework, different team configuration.)
Phase one: Signal. An expansion-readiness indicator surfaces. Usage hits eighty percent of the tier limit. A tenth seat gets added. The customer expresses a use case adjacent to current scope. An executive ask comes up in a CS conversation. The signal is observable in product data or in the customer relationship. The signal phase isn't yet a deal motion — it's CS noticing what the customer is doing.
Phase two: Qualification. CS-led discovery of the use case, scope, and timing. What outcome is the customer trying to achieve. Who else on their side is involved. What's the timeline. What's the rough scope. The qualification is what turns a signal into a deal. It requires the relationship context CS already has — and it doesn't yet require commercial expertise. CS owns this phase because CS has the relationship and the use-case context to qualify properly.
Phase three: Commercial Close. Pricing, contract, procurement. This is where commercial expertise matters. When sales takes Close, it's because sales has the close playbook, the procurement navigation, the commercial term negotiation. CS doesn't have those skills — not because CS isn't capable, but because that's not what CS hours are calibrated for.
In most $5–10M ARR companies, CS owns all three phases — the CSM who notices the signal also qualifies and closes the expansion deal. The phases describe the work, not the team handoff. What matters is that each phase has defined entry criteria, an owner, and a trigger that says the work in that phase is done.
The Trigger That Defines When Qualification Becomes Close
The motion breaks without a defined trigger between Qualification and Close. Most teams have an ambiguous one — "we move it to Close when it feels right" — which means deals move to commercial conversation too early (proposal lands without enough customer context) or too late (the customer is ready to buy and the deal drags). The fix is making the trigger explicit, observable, and on the customer's side of the line.
The mistake most CS teams make in expansion is measuring qualification with internal artifacts — notes logged, calls scheduled, opportunities created in the CRM. Those activities tell you what the CSM did. They tell you nothing about whether the customer has progressed. "Use case documented in the CRM" is not a trigger — it's note-taking. A diligent CSM can log everything for a customer who isn't ready, and a careless CSM can log nothing for a customer who is. Documentation is what happens after the trigger fires — not the trigger itself. The trigger has to be observable in the customer's behavior, independent of whether anyone wrote it down.
Qualification is complete when the customer has produced three signals. Not when the CSM has produced three internal records. The customer articulated the use case in their own words — not the CSM's framing, not what the CSM thinks they meant. The exact gap or need, expressed by the customer. If the CSM has to translate what the customer "meant," the customer hasn't articulated anything yet. The customer anchored the expansion to a timeframe or business event — a Q3 launch, a new hire ramp, a year-end deadline, a board commitment. Without a timeframe attached, there is no urgency on the customer side, and without urgency the deal drifts past the moment when it would have closed. The customer engaged a second stakeholder — not someone the CSM emailed, but someone the customer pulled in. A budget owner, a technical lead, a peer team. That action signals internal political capital committed to the expansion. It doesn't happen until the customer decides the conversation is real.
When all three are visible, the motion moves to Close: a commercial proposal gets drafted, pricing gets confirmed, the procurement path gets mapped. Before all three are visible, qualification continues — and the CSM keeps working on whichever signal hasn't yet emerged. The CSM's job is to create the conditions for those signals to emerge, not to substitute internal documentation for them.
The most common failure mode in CS expansion isn't lack of process. It's mistaking internal activity for customer commitment — running the qualification phase against the team's own checklist instead of the customer's behavior. CRM hygiene improves visibility into the motion. It does not create customer readiness. The hygiene is downstream of the readiness, not the same thing as it. Once the trigger lives on the customer's side, the team stops confusing what it wrote down for what the customer decided.
What to Do This Week
Three steps. Each one takes under an hour. None of them require new software.
One. Audit your last five expansion deals. For each, write down: who first identified the expansion signal, who ran the qualifying conversation, who ran the pricing conversation, where did each handoff happen. Look for the pattern. If your team can't answer "where did this expansion come from and who owned each stage?", you don't have a protocol — you have a series of accidents. Takes forty-five minutes.
Two. Define your three stages. Write down what counts as Signal, what counts as Qualification, what counts as Commercial Close — for your specific business. The definitions are operational, not theoretical. "Signal: customer hits eighty percent of tier limit OR adds a tenth seat OR expresses use case adjacent to current scope" is operational. "Signal: customer is ready" is theoretical. Specific is what works. Takes thirty minutes.
Three. Define the customer-side trigger this week. Pick three customer-behavior conditions that define "Qualification complete" — things the customer does or says, not things the CSM documents. The trigger has to be on the customer's side of the line. Tell your CS team. The next expansion that hits all three moves to Close. One deal is enough to start. The motion proves itself on the first one.
The CSM who heard the customer mention an adjacent use case three months ago didn't fail because they were untrained or busy. They failed because the motion had no phases. No definition of what to do with the signal. No completion criteria for qualification. No trigger to move to close. In most companies under $20M ARR, CS owns the whole expansion motion. What changes is whether the phases are defined or whether expansion happens by accident.
If your expansion signals aren't being captured upstream of the protocol — if CS isn't yet seeing the readiness indicators when they appear — the signal capture system is the foundation. And if you want the broader NRR-as-growth-metric frame this protocol drives, the NRR compounding math is where to start.
.svg)
.svg)
.svg)
