A lot of Customer Success conversations right now seem to start and end with expansion.
CS should own expansion. CS should drive NRR. CS should find more revenue inside the existing customer base.
And honestly, that direction makes sense.
Customer Success teams are close to the customer. They understand account health, usage patterns, relationship dynamics, internal champions, blockers, risk, and value realization better than almost anyone else in the company.
So yes, CS should absolutely have a role in expansion.
But there is one part of the conversation that feels too easy to ignore: You cannot expand an account that never fully adopted the product.
Expansion is not a shortcut. It is not something you bolt onto the customer journey after the contract is signed. It is not a motion that magically starts nine months later because someone added an expansion target to the CS team's KPI.
Expansion is the result of everything that happened before it.
The skipped step in the expansion conversation:
The common version of the story sounds something like this: Sales closes the deal. CS manages the relationship. A few months before renewal, the team looks for expansion potential. Then everyone hopes the customer is ready to buy more.
But that is not how expansion really works.
If onboarding was weak, expansion will be hard. If the customer never reached meaningful value, expansion will be hard. If only the champion uses the product, expansion will be fragile.
If the broader team is confused, stuck, or barely logging in, expansion will feel like a sales push instead of a natural next step.
You can call it expansion. The customer may experience it as pressure. That difference matters.
Expansion starts much earlier than the upsell conversation.
Expansion starts during onboarding. It starts when the first users try to complete real work. It starts when they either understand the product, or get lost.
It starts when they either build a habit, or forget why they bought the product in the first place. It starts when the product becomes part of the customer's workflow, not when the CSM schedules a commercial conversation.
The real path is not Sales to silence to renewal to expansion. The real path is Sales to onboarding to activation to adoption to trust to expansion.
That path is less exciting to talk about. It is also the only one that works consistently.
Monthly check-ins are not enough.
A monthly check-in can help maintain a relationship. It can surface some risks. It can keep the account warm. But it cannot replace actual product adoption.
A customer does not become successful because someone asked 'How are things going?' once a month. They become successful because users are getting value inside the product.
They know what to do. They complete the right workflows. They solve their problems. They discover the features that matter. They build confidence. They bring more people into the product.
That is the work that creates expansion, not the meeting itself.
One champion is not account adoption.
A lot of accounts look healthier than they really are because one champion is engaged. The champion joins the calls, likes the product, understands the value, and says the right things.
But inside the account, the actual users may still be struggling. They may not know how to complete key workflows. They may not understand the product deeply enough. They may be using only a small part of what they bought. They may be quietly working around the product instead of adopting it.
That is not a strong expansion foundation. It is a dependency, and dependencies are risky.
If value lives with one person, the account is exposed. If usage is shallow, the account is exposed. If the product never becomes part of the broader workflow, the account is exposed.
Expansion becomes much more natural when value is spread across the account: more users, more workflows, more habits, more reasons to stay, and more reasons to grow.
Adoption problems become revenue problems.
Weak adoption does not always look dramatic at first. It often looks quiet. A user stops logging in. A team never completes setup. A feature that should drive value is ignored. A workflow stalls. A department never gets onboarded. A champion says, 'We just need more time.'
These moments may not look like revenue issues immediately, but they are.
Revenue does not only leak at renewal. It leaks when users fail to activate. It leaks when onboarding does not stick. It leaks when the product is purchased but not embedded. It leaks when friction is tolerated for months because nobody sees it clearly enough or early enough.
By the time the renewal conversation starts, the account may already have made up its mind. By the time expansion is discussed, the customer may not have enough confidence to go deeper.
That is why adoption is not just a product metric or a CS metric. It is a revenue metric.
CS can own expansion, but not by skipping the work.
I agree with the idea that Customer Success should be closer to revenue. I agree that CS should influence expansion. I agree that existing customers are one of the best places to grow.
But the work has to start much earlier.
That means getting users properly onboarded, helping them reach first value quickly, making sure key workflows are completed, removing product friction before it becomes frustration, supporting end users and not only champions, catching stalled adoption before it becomes renewal risk, and building trust before asking for more money.
There is no shortcut around this. A QBR will not create usage that never happened. A renewal conversation cannot fix a year of shallow adoption. An expansion target will not make customers more successful by itself.
Expansion is earned.
CS owning expansion makes sense. But expansion is not the starting point. It is the outcome.
It is what happens when customers have already reached value and can see a clear reason to go further. It is what happens when adoption is broad enough, usage is consistent enough, and trust is strong enough.
It is what happens when the customer does not feel like they are being sold more, but that the next step is obvious.
So yes, let's talk about expansion. But let's not pretend we can skip the steps that make expansion possible.
Expansion is not a shortcut around onboarding and adoption. It is the result of them.