You hear it constantly: "we already have a vendor." But most reps respond by pitching replacement value—and lose. Here's what actually works.
You hear "we already have a vendor" and your instinct is to pivot to TCO, switching costs, or ROI. Then the conversation dies.
The objection itself isn't the problem. The problem is your mental model: you're treating "already using" as a barrier to entry, when it's actually a signal of where the pain is.
When a prospect tells you they have a competitor's tool, most reps go defensive. They talk about feature parity, price, or implementation speed. They're trying to justify why switching makes sense.
But the prospect didn't say they were unhappy with their vendor. They said they have one. Those are different things.
Here's what actually happens: the prospect is evaluating you against their existing vendor at the same scope. They're asking, "Is yours better at the same thing?" The answer is almost always no—not because your product is worse, but because they've been using theirs for six months or two years. It works. It's installed. People know how to use it.
Comparison-based objection handling loses because it fights on ground the prospect chose.
When someone says "we're already using a vendor," they're really saying one of three things:
You need to know which one you're hearing. Pitching replacement value assumes #1. But #2 is where deals happen.
Ask: "I hear you. Are they handling everything you need, or is there a part of the process where you're still getting gaps?"
Listen for where they're stitching together tools, running manual work, or managing workarounds. That's the gap. That's not about replacing them—that's about expanding your footprint while keeping their vendor in place.
The best response to "we're already using them" is: "Good. Our customers who use [competitor] also use us for [specific problem that's outside their tool's scope]."
This flips the frame. You're not asking them to rip and replace. You're offering to solve something their current vendor doesn't touch.
Example: If they're using a project management tool but manually tracking dependencies across teams, you have an angle. You're not the project manager—you're the thing that makes their project manager more effective by solving the dependencies problem.
When you position this way, the vendor objection stops being an objection. It becomes context.
After you've found the real pain, the conversation has to move to who else cares about solving it.
"If we could handle that piece, who else on your team would need to be part of deciding to bring something like this in?"
You're no longer defending your product against theirs. You're building a coalition around a gap. That's a multithreading play, not a comparison play.
The vendor objection only stays an objection if you let it be one.
Only if they name it first. If they say 'we use Asana,' you can reference it: 'Asana is great at X, and what I'm hearing is Y is still a challenge.' Never lead with competitor names—it signals you're defensive about your position versus theirs.
Don't fight the contract. Ask when it renews and what problems need solving in the meantime. Most contracts let them layer in new tools for specific pain points. You're not replacing the vendor—you're adding capability while they're locked in, then you're the obvious choice at renewal.
Ask them directly: 'Are they solving everything you need, or are there gaps?' The quality and specificity of their answer tells you everything. Genuine satisfaction sounds like, 'It works fine for project tracking.' Dismissal sounds like, 'It does what we need.'
That's often not true—and your job is to find what they're actually doing to work around it. Ask: 'How are you currently handling [specific workflow that's hard]?' The workaround is where the real problem lives, and that's your in.
Part of our guide to Gap Selling.
Repwing listens to your discovery calls and puts the next question on your phone while you are still in the conversation. Fourteen days free, no card.
Start free trial