Recognize a Real Expansion Opportunity
Tell the difference between casual interest and an expansion opportunity with an owner and problem.
The buyer moment
A successful team asks whether another department could use the product.
Interest from another department starts a new discovery conversation. The new team may use different systems, own a different risk, and need a different sponsor. Ask what prompted their interest and which workflow they want to change. A customer success manager can carry useful history from the first team while treating the new conversation as its own decision. This approach gives the expansion an owner, an adoption plan, and a clear problem to solve.
A useful way to open
“What is different in that team’s workflow, and who would need to agree that this problem is worth solving?”
Move the decision forward
Treat an expansion as a new discovery conversation. The new team may have different systems, risks, goals, and decision owners.
Coach account teams to run a small discovery process and learn how the new team’s needs differ.
Practice before the next call
Roleplay a customer who says, “Our other team might like this.” Practice asking for the trigger, affected workflow, and introduction.
Next step
Schedule a discovery call with the new team. Use the existing customer’s story to provide context and ask what evidence the new team needs.
Practice these next
Help buyers separate a real capacity constraint from a vague reason to defer.
Build an EBR around decisions, evidence, and unresolved operating questions.
Use trial activity to learn what the buyer is trying to prove.
Surface adoption ownership before the project reaches implementation.
Discover the country, language, support, data, and operating differences behind a global rollout request.
Transfer the customer’s goals, constraints, and promises so onboarding begins with continuity.