Most objection handling advice treats "we already use something for that" as a dead end. It isn't. It's the most honest thing a prospect can tell you on a cold call or a discovery call, because it tells you they care about the problem enough to have paid for a fix. The job isn't to win an argument against their current vendor. The job is to find out whether the fix is actually working.
This post is a short sales training playbook for that moment: what's really going on, the sales scripts that keep the conversation alive, and a practice drill so you don't freeze the next time you hear it. It's written for founders doing founder-led sales, engineers and sales engineers stepping into customer-facing roles, and SDRs and AEs who hear this objection every week.
Why "we already use X" is a status quo objection, not a competitor objection
When a prospect names a tool, it's tempting to start comparing features. That almost always backfires. You're now attacking a decision they made, maybe one they championed internally, and nobody enjoys being told they picked wrong.
What the prospect usually means is one of three things:
- "Switching sounds like work." The pain of changing is higher than the pain they feel today.
- "I don't want to think about this right now." It's a reflex to end the call, same as "send me some info."
- "It's fine, mostly." There are gaps, but nobody has asked them about the gaps.
Only the third one is a real opening, and you can't tell which one you're dealing with until you ask a question. So the first rule is simple: don't pitch, ask.
The three-step map for handling it
Instead of a word-for-word script, use a small map you can hold in your head:
- Acknowledge and agree. Show you heard them and that their choice makes sense.
- Get curious about the outcome, not the tool. Ask how it's going against the goal they bought it for.
- Earn a narrow next step. Ask for something small, like a comparison on one use case, not "a demo."
That's it. Each step is one or two sentences. If you can do these three things calmly, you'll keep a surprising number of conversations going.
Sales scripts for each step
Step 1: Acknowledge and agree
"Makes sense, a lot of teams your size use them. Honestly, if it's working, I wouldn't want you to change anything."
Saying "if it's working" on purpose lowers the pressure and quietly plants the question you'll ask next.
Avoid:
"Oh, we're way better than them."
That one line turns you from a curious person into a salesperson defending a product.
Step 2: Get curious about the outcome
Pick one discovery question. Don't stack five.
"Out of curiosity, when you brought them in, what were you hoping would change?"
"If you could wave a wand and fix one thing about how it works today, what would it be?"
"How are you measuring whether it's paying off?"
"Who on the team uses it most, and what do they say about it?"
Then stop talking. The silence after a good discovery question is where the real answer shows up. If they say "honestly, it's great, no complaints," believe them and move to a graceful exit. If they hesitate or say "well, mostly," you've found the gap.
Step 3: Earn a narrow next step
"Would it be useful to look at just that one piece side by side, fifteen minutes, and if it's not better you keep what you have?"
"Not asking you to switch anything. Would it be worth comparing notes on how other teams handle that?"
Small, specific, low-risk. A narrow next step respects that they already invested in something.
A full example
Here's how the whole thing sounds on a cold call:
Prospect: "We already use a tool for that."
You: "Makes sense. If it's working, I wouldn't want you to change anything. Can I ask what you were hoping it would fix when you brought it in?"
Prospect: "Mostly ramp time for new reps."
You: "And how's ramp time looking now compared to before?"
Prospect: "Better on paper. The new people still freeze on real calls, though."
You: "That's really common. Would it be worth fifteen minutes to look at just the freezing-on-calls part? If it's not useful, you keep what you have."
Notice what didn't happen: no feature comparison, no criticism of their vendor, no "but we're cheaper." The prospect named the gap themselves, which is the only version of the gap they'll actually believe.
Mistakes that kill the conversation
- Badmouthing the competitor. Even if you're right, it makes the buyer defensive about their own decision.
- Jumping straight to price. "We're half the cost" invites a procurement conversation before you've found any value.
- Asking for a full demo. It's too big an ask for someone who thinks they're covered.
- Accepting it on the first try. "Oh okay, thanks anyway" leaves every "it's fine, mostly" prospect on the table.
- Not accepting it on the second try. If they clearly say it's working and they're happy, thank them and leave the door open. Pushing past a real no burns the relationship.
Checklist before your next call
- [ ] I have one acknowledge line I can say without thinking.
- [ ] I have two outcome questions ready, not feature questions.
- [ ] I know the one narrow next step I'll offer.
- [ ] I've decided in advance how I'll exit gracefully if they're genuinely happy.
- [ ] I've said all of this out loud at least five times.
Practice it out loud, not just in your head
Reading sales scripts feels like learning, but objections hit on live calls when your heart rate is up. The fix is sales role play: have a colleague or friend play the prospect, tell them to say "we already use something for that" at a random moment, and run the three steps. Then swap and make it harder: they push back on your outcome question, or they say "it's great, no complaints" and you practise the graceful exit.
Do five reps in a row. By the fifth, the acknowledge line comes out naturally and you stop rushing to defend your product. That calm is what the prospect hears.
If you'd rather practise with virtual customers who push back like real buyers, that's what we're building at Kulissa.
Top comments (0)