'We Already Have a Vendor' Doesn't Mean the Deal Is Over

Objections · medium difficulty · 6 min read

A closed folder labeled Current Vendor beside an open notepad with one question written on it, a phone mid-call blurred in the background, bright desk

The situation

Twenty seconds in, you have explained who you are and what you do, and the prospect stops you cold: "We already have a vendor for this." Not rude, not rushed, just a flat statement of fact. Unlike "not interested," this one sounds researched. It comes with an implied history: a contract, a relationship, probably a renewal date somewhere on a calendar. Most reps hear that implied history and back off, because arguing with a fact feels different from arguing with a reflex.

That instinct is the whole problem. "We already have a vendor" is a true statement about the past, not a verdict about the future. Every prospect who eventually switches vendors was, at some point, a prospect who already had one. The line tells you almost nothing about whether that relationship is working, ending, or quietly tolerated because nobody has had a reason to look elsewhere. Your job is to find out which, and you cannot do that from outside the call.

Why reps lose here

Confusing tenure with satisfaction. A vendor relationship that has lasted three years sounds stable, but longevity and satisfaction are not the same measurement. Plenty of accounts stay with an incumbent purely because switching costs feel higher than the friction of staying, right up until a renewal date forces the comparison. Reps who hear "vendor" and assume "happy" are pricing in a fact that was never stated.

Conceding the account on the spot. The most common failure is a polite surrender: "Ah, no worries, I'll let you go then." This treats the objection as a closed door rather than as the first data point in a conversation. It also wastes the one thing a cold call is actually for, which is finding out something you did not know five seconds earlier.

Pitching against a vendor you cannot see. The opposite failure is attacking the incumbent by name or category ("most vendors in this space are outdated") without knowing anything about them. This reads as presumptuous, and worse, it can be flatly wrong about a tool the prospect actually likes. Reps who do this are pitching against an imagined competitor instead of the real one.

What the buyer is actually thinking

There is a narrow set of things actually happening behind this line, and none of them require you to argue that their current vendor is bad.

The contract is fine, so the door is closed for now. Some prospects genuinely have no reason to look. Nothing is broken, the renewal is a year out, and there is no urgency to create. This is a real no for today, and the honest move is to ask permission to check back near the renewal window rather than manufacture false urgency.

The vendor is fine, but a specific thing is not. Far more common: the relationship is broadly acceptable but one feature, one support experience, or one growing need is not covered. The prospect is not thinking about switching vendors; they are thinking about a specific gap they have half-stopped noticing because nobody has asked about it directly.

Nobody has actually checked the vendor lately. In some accounts, "we have a vendor" is closer to "somebody signed a contract two renewal cycles ago and nobody has revisited it since." The prospect saying the line may not personally know whether it is a good fit anymore; they are reciting an organizational fact, not a personal endorsement.

Your first question after the objection should sort these apart, not argue against any of them.

The dialogue

Marcus is a fictional IT manager at Halstead Freight, a mid-size trucking company. The rep sells a driver-safety monitoring platform.

Weak handling:

Rep: Hi Marcus, this is Chelsea from Roadview, we help fleets cut accident rates with in-cab monitoring. Got a minute?

Marcus: We already have a vendor for that, actually.

Rep: Totally understand, but a lot of fleets who said that ended up switching once they saw our accident data. Can I send over a quick comparison?

Marcus: I'd rather not, we're happy with what we've got.

Rep: No problem, I'll follow up down the road.

Chelsea's response assumed Marcus's vendor was inferior before learning anything about it, which is exactly the kind of generic claim a prospect has heard from every competitor that ever called. Marcus, who had not actually complained about anything, defended a system he was never asked a real question about. Chelsea leaves with nothing: no sense of contract timing, no idea whether there is a gap, nothing to follow up on besides a vague promise to try again someday.

Strong handling:

Rep: Hi Marcus, this is Chelsea from Roadview, we help fleets cut accident rates with in-cab monitoring. Got a minute?

Marcus: We already have a vendor for that, actually.

Rep: Makes sense, most fleets your size do. Are you locked in for a while, or is this more of an open renewal where you'd actually look at options?

Marcus: Renewal's not for another eight months, so honestly, not really shopping.

Rep: Fair, I won't push a demo then. Since you've got some runway, can I ask one thing: does your current system flag near-misses in real time, or is it mostly after-the-fact footage review?

Marcus: It's after the fact, mostly. We pull footage when something happens.

Rep: That's the one gap we get asked about most, the real-time alert piece. I'll send you one page on just that, no pitch, and if it's not relevant with eight months left on your contract, no worries at all.

Marcus: Yeah, that's fair. Send it over.

Chelsea's first question did not contest the vendor relationship at all; it asked about contract timing, which told her immediately that this was not an urgent switch and reset her own expectations for the call. Instead of pitching against a vendor she knew nothing about, she asked one narrow, specific question about capability, the kind of question that is easy to answer honestly because it is not an invitation to defend the whole relationship. Marcus's answer, "it's after the fact, mostly," is the actual gap, and Chelsea only got it because she asked about a feature instead of asking Marcus to rate his overall satisfaction. The close matched the size of the moment: one page, explicitly low-pressure, respecting the eight months of runway Marcus had just told her about.

How to run this live

Set up a cold call scenario with a busy, skeptical buyer persona so the vendor objection shows up early, the way it does on a real list. Goals for the practice run:

  1. When you hear "we already have a vendor," do not concede and do not attack the incumbent by name or category.
  2. Ask about contract timing first. It tells you how much urgency actually exists before you invest another question.
  3. Ask one narrow, specific capability question rather than a broad "how happy are you" question that invites a defensive, generic answer.
  4. Size your close to the runway the buyer just gave you. Eight months left on a contract earns a one-page follow-up, not a demo request.

Run it several times against a buyer who is genuinely locked in and a few more against one whose vendor has a real gap. Learning to tell a closed door from a door that is only stuck is what this drill is for.

Run this scenario for real

ConvoSparr drops you into a live voice call with an AI buyer who runs this exact play. Handle it out loud, then get a transcript, scores, and coaching notes on how you did.

Start practicing free

Free to start. No credit card required.

Keep practicing