"We're already using someone else"
Most reps treat this as the end of the call. It's close to the opposite. An incumbent tells you three valuable things instantly: the budget line exists, the problem is real enough to have been solved once, and someone inside that company already made the internal case for spending on it. You're not creating a category - you're competing for a slot that's already funded.
Quick Answer
Never attack the incumbent - you're insulting the person who chose them. Instead: acknowledge the vendor positively, ask what's working, then ask what they've had to build a workaround for. Workarounds are where switching triggers hide. Then find out when the contract renews, because that's the only date that matters. Your goal on the first call isn't to displace anyone, it's to be the obvious call when something breaks.
Why this is a good objection
- Budget exists. They're already paying for this category. You're not asking for new money, you're asking for a reallocation - a much easier internal conversation.
- The problem is validated. Nobody buys software for a problem they don't have. They've told you the pain is real.
- Someone already sold this internally. There's a person in that building who has made the case for this category and survived it.
- Incumbents create their own dissatisfaction. Every long-running vendor accumulates workarounds, unmet requests, and a support experience someone is unhappy about.
Compare that to a genuine greenfield prospect, who has no budget, no validated pain, and no internal champion. The incumbent objection is the better starting position by a wide margin.
The one thing you must not do
Do not criticise the incumbent. Someone on that call chose them, defended them, or is responsible for the contract. Attacking the vendor attacks a decision they made, and people defend their decisions much harder than they defend their vendors.
Wrong"Yeah, we hear a lot of complaints about them - their reporting is really weak."
Right"They're good - most of the teams we talk to are using them. What's working well for you?"
Praising the incumbent is counterintuitive and it works, because it removes the need to defend and makes the honest answer socially available. People will tell you what's wrong with a vendor much faster if you've just said something nice about them.
The question sequence
1. Confirm and compliment
You"Good choice, they're solid. How long have you been on them?"
Tenure matters. Six months in, they're still justifying the purchase. Three years in, they've accumulated grievances and the contract has been renewed on autopilot.
2. Ask what's working
You"What do they do well? I ask because if it's the thing we're strongest at too, I'll save us both the time."
Disqualifying yourself out loud is a credibility move, and it makes everything you say afterwards more believable.
3. Ask about workarounds - the key question
You"Is there anything you've had to build a workaround for? Spreadsheet on the side, manual step, something you export and fix?"
This is the one that finds the gap. People rarely describe their tools as inadequate - loyalty, sunk cost, and the fact that they chose it - but they will happily describe a spreadsheet they maintain manually every Friday, because that's just an annoyance rather than an indictment. Every workaround is an unmet requirement.
4. Ask about the renewal
You"When does the contract come up? I'm not going to pester you before then - I'd just rather know whether this is a now conversation or a six-months-from-now one."
The renewal date is the single most valuable piece of information on the call. Everything else is timing around it.
Switching cost is your real competitor
You're rarely competing with the incumbent's features. You're competing with migration effort, retraining, integration rework, and the internal risk of being the person who championed a change that went badly.
| Switching cost | How to reduce it |
|---|---|
| Data migration | Do it for them, and say so early |
| Retraining the team | Onboarding included, quantified in hours |
| Integration rework | Confirm their exact stack works before anything else |
| Career risk for the champion | Pilot with one team, not a company-wide rip-out |
| Contract overlap | Start free until their renewal date |
Notice that none of these are about your product being better. Displacement deals are won on de-risking, not on feature comparison.
Play the long game
Most competitor displacements aren't won on the first call. They're won because you were the person who was polite, useful, and specific twelve months ago when the incumbent had an outage or a price increase or a support failure.
How to stay in the picture without being annoying
Get the renewal date and diarise it. Reach out 90 days before, not the week of.
Send something useful twice a year. Not a check-in. Something they'd have wanted to read anyway.
Be the first call when something breaks. That's the entire strategy, and it works.
Log the workaround they mentioned. Referencing it a year later is the most credible thing you can do.
When to walk away
If they're genuinely happy, recently signed, and can't name a single workaround, believe them. Get the renewal date, leave a good impression, and go. Grinding a satisfied customer is how you get remembered as the vendor who wouldn't take a hint - which costs you the deal you might have won at renewal.
See the objection framework and discovery questions.
Frequently Asked Questions
How do you respond when a prospect already uses a competitor?
Acknowledge the vendor positively, ask what's working well, then ask what they've had to build a workaround for. Praising the incumbent removes their need to defend the decision and makes honest answers socially easy. Workarounds - the spreadsheet on the side, the manual export - are where unmet requirements hide, and they're a far better source of openings than asking what they dislike.
Should you criticise a competitor in a sales call?
No. Someone on that call chose the incumbent, and attacking the vendor attacks their judgment, which people defend far harder than they defend software. It also makes you sound insecure. The counterintuitive move is to compliment the competitor genuinely - it removes the defensive posture and makes the prospect much more willing to tell you what isn't working.
Is the competitor objection a good or bad sign?
Good, generally. An incumbent proves that budget exists for the category, that the problem is real enough to have been solved once, and that someone inside the company already made the internal case for spending on it. Compared with a true greenfield prospect who has none of those things, an incumbent situation is a substantially more qualified opportunity.
How do you win a deal against an incumbent vendor?
By reducing switching cost rather than by winning a feature comparison. Handle the data migration yourself, include quantified onboarding, verify their integrations before anything else, and propose a pilot with one team rather than a company-wide replacement so nobody's career is on the line. Then get the renewal date and time your real push for about ninety days before it.
Related Articles
- Objection Handling: The Complete Framework
- "It's Too Expensive": Handling the Price Objection
- The 12 Cold Call Objections You'll Hear Most
- 35 Discovery Call Questions That Surface Real Pain
- The Best Sales Roleplay Apps and AI Practice Tools
- "Not Interested": The Six-Second Save
Scope
This article is practical sales guidance based on widely used objection-handling frameworks, not a guarantee of results - what works depends heavily on your market, deal size, and sales cycle. Where other products are mentioned, features are described as publicly stated in August 2026 and change often. CloserLab is made by the author of this site.