No invented statistics. Every number is sourced or labelled as an example. Our standards

Objection Handling

How to Handle "We're Already Using a Competitor"

Older woman in glasses and a striped jumper smiling and talking over a cup of coffee, seen past the shoulder of the person listening
Photo: Age Cymru / Unsplash

"We're already using someone for that" is the most common brush-off in B2B, and it's usually true. It is also not a no. It's a statement of fact that the prospect expects will end the conversation, which is exactly why a calm, curious response is so disarming.

What it does mean is that your job has changed. You're no longer selling against doing nothing; you're selling against switching costs, sunk investment, a relationship with a named human being, and the personal risk your contact takes if a change they sponsored goes badly. That last one is the biggest and the least discussed.

The first response

Don't try to create doubt in the first thirty seconds. Acknowledge, then get specific.

"That's good to hear, honestly — most people we speak to have something in place. Can I ask how long you've been with them, and how it's going? I'm not going to try to talk you out of a supplier you're happy with."

The last sentence does a lot of work. It removes the thing they're braced for, which makes the honest answer more likely. And it should be true: if they're genuinely happy and well served, you want to know that early rather than after four meetings.

Then listen for the texture of the answer. "Yeah, they're fine" is different from "they've been great." "Fine" is the sound of tolerated mediocrity, and it's the most common opening you'll get.

Questions that find the gap

You're looking for the difference between what they bought and what they now need. That gap widens naturally over time, because the business changes faster than the contract does.

That second-to-last question is quietly the best one. An incumbent who only appears at renewal time has a relationship problem, and relationship problems are what actually cause switching. The last question matters because satisfaction is rarely uniform: the person who bought the system is often the last to hear that the team hates it.

These sit inside normal discovery questioning rather than being a special competitive routine.

Never slate the incumbent

Criticising the current supplier attacks the buyer's past decision. They chose it, defended it internally and have lived with it. Tell them it was a bad call and you've made an enemy of the person you need on your side.

Say this instead:

"They're a solid product — for what you needed three years ago I'd probably have recommended them too. The question is just whether the shape of what you need has changed. If it hasn't, stay put."

Generous about the competitor, honest about the criterion, and it frames the decision around their change rather than the incumbent's failure. Where you do have a real, specific difference, state it factually and let them judge — no adjectives, no implied incompetence.

Take the switching cost seriously

Reps routinely underestimate what switching actually involves: data migration, retraining, a period where things work worse than before, and someone's name attached to all of it. If you dismiss that, you look naive. If you name it first, you look credible.

"To be straight with you, moving is a pain. You'd have three or four weeks where your team is learning something new and productivity dips. That's only worth doing if what you get afterwards is meaningfully better, not marginally. So let's work out whether it is — and if it's marginal, I'll tell you."

Then address the personal risk directly, because it's the real blocker in most incumbent displacements. Concrete de-risking beats reassurance: a parallel run, a single-department pilot, a phased migration, a clear rollback point, a fixed-price implementation. Your contact needs something they can present internally that doesn't read as "I'm betting my credibility on a supplier I met in September."

Timing: find the contract, find the trigger

Even a persuaded buyer can't act mid-term without a reason. Two pieces of information determine everything about how you run this deal:

  1. When does the contract end, and what's the notice period? Ask plainly. Most people will tell you. Auto-renewal clauses with a 90-day notice window are common, and missing that window costs a whole year.
  2. What internal event might force a review? A system being retired, a site opening, an acquisition, a compliance requirement, a new manager who wants to make their mark.

"When does the current agreement run to? I ask because if there's a notice period, the useful conversation is three months before that, not the week of renewal. I'd rather diarise it properly than keep bothering you."

That answer turns a dead lead into a scheduled opportunity. It also stops you forecasting something that cannot legally close this quarter. Worth reading alongside renewals are not guaranteed, which is the same dynamic viewed from the incumbent's side — and it's a reminder that you are somebody's incumbent too.

Staying in touch without nagging

Most incumbent displacements are won by whoever is credible at the moment the incumbent stumbles. You can't control when that happens; you can control whether they think of you.

When to walk away

Some accounts are genuinely closed and the honest thing is to stop. Disqualify when:

In those cases, be direct: "Sounds like you're in good shape. I'll leave you to it — if that ever changes, you know where I am." Then set a reminder for a year out and mark the deal lost with a reason, rather than letting it rot in your pipeline inflating a forecast nobody believes. There's more on that discipline in spotting a deal that's never going to close.

The trade-off

Chasing incumbent-held accounts is slower and lower-yield than selling to people with no solution at all, but the deals are often larger and the buyer is already educated — they've budgeted for this category and understand what it does. The mistake isn't working these accounts; it's working them at the wrong intensity. Persistent, low-frequency, genuinely useful contact over eighteen months beats a hard push over six weeks, almost every time.

Spotted a mistake or a number we can't back up? Tell us and we'll fix it.