How to respond to “We already use another tool”: 3 answers
“We already use another tool.”
“We already use another tool” isn't a no, it's information. Three answers to learn what's missing and whether switching is worth it, no trash talk.
Practice this objectionWhy buyers say it
Someone who already uses a tool is, in a way, the best kind of prospect: they have the problem, they know it, and they pay to solve it. The objection only says the need is covered today, not that it's covered well. The risk, if you built the product, is to jump straight into a comparison: “ours does this and that too.” Don't. They didn't ask for a comparison, and switching has a real cost: time, data to move, habits to break. The right work is to learn how things are going with what they use, what's missing, and how much that gap hurts. If nothing is missing, they're not your customer today. If something is, that's the conversation.
What it often means
- They don't want to switch: migrating data and habits is expensive
- The current tool is so-so, but not bad enough
- They're locked in by a contract or by the colleague who picked it
Three answers that work
Good, that means you already know the problem. Can I ask how it's going with it? Not to knock it. If it works, it works. But if there's one thing that eats your time every week, I'd like to know what it is.
Why it works: You don't attack the tool and you don't ask them to switch. You ask about their experience. Talking about how it's going, the buyer often surfaces the thing that doesn't work, and that's your opening.
Got it. Then I won't suggest replacing it. One question, though: is there something you wish it did that it doesn't? Sometimes the point isn't to change everything, it's to add the piece that's missing.
Why it works: It removes the fear of a full switch and lowers the stakes. Not “throw it all out,” just “add a piece.” That's easier to say yes to, and meanwhile you learn what the concrete gap is.
Fair, and switching has a cost: data, habits, time. Here's what I usually do. I'll show you in twenty minutes how we'd handle [a typical case of yours], and you compare it to how you do it today. If there isn't a difference worth the switch, I'll be the first to say so.
Why it works: It acknowledges the switching cost without shrinking it and offers a side-by-side on a real case from their business. Promising to be the first to say “not worth it” makes the comparison credible.
Avoid this one
Oh, that one? Honestly, it's full of problems, everyone who switches to us says the same.
Why not: Badmouthing the tool they chose means telling them they chose badly. They get defensive, they defend their choice, and you become the salesperson who trashes competitors. Even if you were right, you lost.
Example dialogue
BuyerWe already use another program for contacts. We're fine.
YouGreat, so the tracking part is handled. How's it working for you?
BuyerFine, mostly. A bit clunky when we send updates to clients.
YouClunky how? One at a time?
BuyerYeah, copying from the program into text messages. We lose an hour a day, maybe more.
YouThat's exactly the piece we could try, without touching anything else. Want me to show you on one of your actual listings, twenty minutes?
Practice this objection
A simulated buyer says it to you out loud (or in writing), you answer, and you get a score plus the model answer. Free, no account, 2 minutes.
FAQ
Should I do a head-to-head comparison with the tool they already use?
Only if they ask, and only on the points that matter to them. A feature-by-feature comparison is boring and sounds biased. Better to ask what's missing today and show how your product handles exactly that case. The buyer makes the comparison themselves, and that's the only comparison they care about.
What if their current tool genuinely works well?
Say so and close gracefully: “Then switching doesn't make sense. Let's stay in touch and if things change, we'll talk.” A prospect happy with another tool isn't a loss. They'll remember you didn't push. Many come back when their tool raises prices or stops improving.
How do I handle the fear of migrating data?
Don't minimize it, it's real. Explain exactly how migration works, how long it takes, what can go wrong and what you do when it does. If you can, offer a period where both tools run side by side. Fear shrinks with details, not with reassurance.