Loading...
sales

Handle We're Happy with Our Current Vendor

Practice handling the “we’re happy with our current vendor” objection on a discovery call. Build curiosity about gaps in the current setup and earn a next step without sounding pushy.

Get Started

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Software · Saas · Business Services · Operations

Overview

This AI roleplay practice scenario trains a sales rep to handle the common “we’re happy with our current vendor” objection without turning the conversation into a pitch battle. The situation is a discovery call with a mid-market operations manager who has used the same software vendor for three years, feels the setup is working, and is only mildly skeptical. The learner’s job is to acknowledge that satisfaction, create credible curiosity about a gap or risk in the current approach, and ask for a next step that feels earned.

Use this template when a prospect is not actively shopping, but there may still be a reason to compare. It is designed for reps who need to practice timing, tone, and question quality, not product memorization. The persona should respond realistically: if the rep dismisses the incumbent too quickly, Jordan should become more guarded; if the rep listens and asks a focused question, Jordan should open up.

Do not use this template when the buyer has already agreed to evaluate alternatives, when the conversation is about pricing negotiation, or when the goal is a technical demo rather than objection handling. The point of the practice is to move from polite resistance to a low-pressure next step, such as a comparison call, a process review, or a deeper discovery conversation.

How to use this template

  1. Read the situation so you understand the buyer’s context, the incumbent-vendor status quo, and the learner objective before starting the attempt.
  2. Start the roleplay and let Jordan open with a realistic, polite statement that signals satisfaction with the current vendor.
  3. Respond in conversation, using acknowledgment first, then a specific curiosity-building question, and then a clear ask for the next step.
  4. Complete the attempt and review the scored rubric criteria to see whether you acknowledged satisfaction, created comparison value, asked a focused question, and secured a next step.
  5. Retry the scenario with a tighter opening line, a sharper discovery question, or a softer close until the response feels natural and non-pushy.

Best practices

  • Acknowledge the prospect’s satisfaction before you introduce any gap or comparison point.
  • Use one specific curiosity trigger, such as a process bottleneck, hidden cost, or missed workflow, instead of listing multiple product benefits.
  • Ask a focused question that can only be answered with a real example from their current setup.
  • Keep the tone calm and consultative; sounding eager to displace the incumbent usually makes the persona shut down.
  • Offer a low-friction next step, such as a short comparison conversation or a deeper discovery call, rather than asking for a full demo too early.
  • Match the prospect’s mild skepticism by avoiding exaggerated claims or negative comments about their current vendor.
  • If the buyer says the current setup is fine, probe for exceptions, edge cases, or manual workarounds instead of arguing.

What this template typically catches

Issues teams running this template most often surface in practice:

Jumps straight into product features before acknowledging the buyer’s satisfaction.
Talks negatively about the incumbent vendor instead of creating neutral curiosity.
Asks vague questions that do not uncover a concrete gap, risk, or missed opportunity.
Pushes for a demo or meeting before earning enough relevance.
Uses a generic objection-handling script that sounds scripted rather than responsive.
Fails to secure a clear next step and leaves the conversation open-ended.
Overexplains the product instead of letting the buyer describe their current process.

Common use cases

Mid-market operations manager with an incumbent workflow tool
The buyer says the current platform has been in place for years and the team knows how to use it. The rep needs to uncover whether the process is truly efficient or just familiar.
SaaS rep selling into a stable account team
The prospect is polite, not hostile, and sees no urgent reason to change vendors. The rep practices creating a comparison without triggering defensiveness.
Business services discovery call after a referral
A referred prospect is open to listening but already trusts their current provider. The learner practices earning permission to explore one specific gap before asking for a follow-up.

Frequently asked questions

What does this roleplay template help a rep practice?

It helps a rep respond to a status-quo objection from a prospect who already has a vendor and does not feel urgent pain. The goal is not to force a switch, but to acknowledge satisfaction, surface a credible gap, and earn permission for a next conversation. It is useful when the prospect is polite, guarded, and open only if the rep is relevant.

When should I use this template in the sales process?

Use it during discovery or early qualification when the prospect says their current vendor is working fine. It is especially useful before a demo, when you need to create a reason to continue the conversation. It is not the right fit for late-stage negotiation or a procurement review.

Who should run this practice scenario?

Sales managers, enablement leads, and individual reps can all run it. It works well for new hires learning objection handling and for experienced reps who want cleaner language around status-quo selling. A coach can score the attempt against the rubric and replay the scenario with a harder or softer persona.

How often should a team practice this objection?

Practice it regularly, especially before outbound campaigns or pipeline reviews where incumbency is common. Reps often need repeated attempts to stop jumping straight to product features. Short, frequent roleplays work better than one long session because the skill depends on timing, tone, and question quality.

What is the biggest mistake reps make with this objection?

The most common mistake is arguing with the prospect’s satisfaction or immediately attacking the current vendor. That usually makes the rep sound pushy and defensive. Another common miss is asking vague questions that do not create a real comparison, so the conversation stalls instead of moving toward a next step.

Can this be customized for different products or buyer types?

Yes. You can swap in your product category, the incumbent vendor type, the buyer persona, and the likely gap you want the rep to uncover. For example, you can tailor it for operations, finance, HR, or customer support buyers and adjust the persona’s temperament from mildly skeptical to highly guarded.

How does this compare with an ad-hoc objection-handling exercise?

This template gives the learner a specific situation, a realistic persona, and a scored rubric, so practice is repeatable and measurable. Ad-hoc roleplay often drifts into generic selling advice or random objections. A structured scenario makes it easier to coach one behavior at a time, review attempts, and track improvement.

Can this template connect to CRM or training workflows?

Yes. It can sit alongside call coaching, onboarding, or certification workflows, and the scenario can be assigned as part of a sales readiness path. Teams often use it after call reviews, before manager 1:1s, or as a pre-demo warm-up. The output is a scored attempt that can be discussed in coaching notes.

Go deeper on the topic

Related concepts
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
  • A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
  • A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
Related guides

Ready to use this template?

Get started with MangoApps and use Handle We're Happy with Our Current Vendor with your team — pricing built for small business.

Get Started