Run an Expansion-Discovery Call Without Seeming Pushy
Practice a quarterly expansion-discovery call with a satisfied customer who is wary of being sold to. Learn how to connect an expansion idea to their goals, ask useful discovery questions, and earn a low-pressure next step.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Saas · B2b Services · Operations Software · Customer Success
Overview
This roleplay template simulates an expansion-discovery call with an existing customer who is generally happy with the product but cautious about being sold to. The learner practices opening the conversation with a low-pressure reason for the call, connecting a possible expansion to the customer's own goals, asking discovery questions, and ending with a concrete next step that feels helpful rather than forced.
Use this template when a customer has already seen value in the core product and a new need has emerged, such as reporting visibility, manual work reduction, team growth, or a process bottleneck. It is a strong fit for quarterly check-ins, renewal planning, and customer success conversations where the rep needs to earn the right to discuss expansion. The persona is designed to be friendly but guarded, so the learner has to listen, acknowledge skepticism, and stay consultative.
Do not use this template for a cold outbound pitch, a technical support issue, or a call where the customer has already asked for pricing and procurement details. The point is to practice discovery and positioning, not to rush into a proposal. If the learner jumps to product features too early, the persona should push back, which makes the scenario useful for coaching pacing, relevance, and objection handling.
How to use this template
- Read the situation and customer context so you know what the customer already uses, what they care about, and why the call is happening now.
- Start the roleplay with a low-pressure opening line that gives a clear, relevant reason for the conversation without sounding like a pitch.
- Talk to the persona by asking discovery questions about goals, pain points, current workflow, and what success would look like for their team.
- Use the customer's answers to connect the expansion idea directly to their stated needs before you suggest any product change or next step.
- Complete the roleplay against the scored rubric, then review where you sounded consultative versus where you sounded pushy or premature.
- Retry the attempt with a tighter opening, better discovery, and a more concrete but still low-pressure next step.
Best practices
- Open with the customer's stated goal or pain point, not with a feature list.
- Ask at least one discovery question before you mention any expansion option.
- Reflect the customer's concern in plain language before you propose a next step.
- Keep the next step small, specific, and easy to accept, such as a follow-up review or workflow walkthrough.
- Use the customer's own words to connect the expansion to business outcomes like visibility, time savings, or team efficiency.
- Treat skepticism as a signal to slow down, not as a cue to defend the product.
- Avoid stacking multiple products or add-ons in one conversation unless the customer has clearly asked for breadth.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this roleplay template help me practice?
This template helps you practice an expansion-discovery call with an existing customer who is already satisfied but may have a new need. The goal is not to close immediately, but to connect a relevant expansion to the customer's stated priorities, ask discovery questions, and end with a concrete next step. It is especially useful when you need to avoid sounding like a hard sell.
When should I use this scenario?
Use it during a quarterly business review, a renewal-adjacent check-in, or any customer success conversation where adoption is good but a new pain point has emerged. It fits moments when the customer mentions reporting gaps, manual work, team growth, or process bottlenecks. It is not the right fit for a first-call pitch or a purely transactional support conversation.
Who should run this practice session?
Customer success managers, account managers, and sales reps who handle expansion conversations are the best fit. Team leads can also use it for coaching because the rubric makes it easy to score whether the learner stayed consultative. It works well for both individual practice and manager-led roleplay review.
How often should a team use this template?
Use it whenever a rep is preparing for a real customer check-in that may surface expansion opportunities. It also works well as recurring practice for new hires before they take live accounts. Teams often revisit it after a difficult call to improve discovery, pacing, and objection handling.
How is this different from an ad-hoc roleplay?
An ad-hoc roleplay often turns into a vague sales conversation with no clear learner objective or scoring standard. This template gives you a specific situation, a guarded persona, a realistic opening line, and behavioral rubric criteria. That makes it easier to practice the exact skill of being relevant without being pushy.
What should I customize before using it?
Customize the customer's industry, the current product use case, the likely expansion path, and the pain point they care about most. You can also adjust the persona's temperament to be more skeptical or more open depending on the learner's level. If your team uses a specific discovery framework, you can align the rubric to that language.
Can this connect to CRM notes or account data?
Yes, this scenario works best when you seed it with account context such as product usage, recent support themes, and the customer's stated goals. That makes the conversation feel realistic and helps the learner practice using actual signals instead of generic pitch language. Keep the data limited to what the learner would reasonably know in the call.
What are the most common mistakes this template surfaces?
The most common mistakes are opening too aggressively, pitching before asking questions, and treating a satisfied customer like a cold prospect. Learners also tend to ignore skepticism, over-explain the product, or fail to end with a clear next step. The rubric is built to catch those behaviors so the learner can retry with a more consultative approach.
Related templates
Ready to use this template?
Get started with MangoApps and use Run an Expansion-Discovery Call Without Seeming Pushy with your team — pricing built for small business.
