Execution · 2026-07-27 · 5 min

Handling We Already Have a Vendor

We already have a vendor is often the end of the conversation, but not always. Here is how to tell the difference and what a useful reply looks like when it is worth continuing.

"We already have a vendor for that" is one of the more final-sounding replies in outbound, and it tempts people into either giving up entirely or arguing the point too hard. Neither works well. The right response depends on what kind of "already have a vendor" you are actually looking at, and that is worth thirty seconds of thought before you reply.

There are at least three different situations hiding behind that one sentence, and they need different replies.

The three versions of this objection

Genuinely happy with the current vendor. The relationship works, the contract has time left, and there is no active dissatisfaction. Pushing here wastes everyone's time.

Under contract but not particularly happy. Something is not working, but switching costs or timing make it inconvenient to move right now. This is the version worth staying close to.

Reflexive answer to end the conversation. The person has not actually thought about their current setup, they said it because it is the easiest way to close down an unsolicited message. This is more common than people expect, particularly when the reply comes within minutes of your message.

How to tell which one you are dealing with

A single follow-up question usually separates the three.

This question is low pressure and genuinely useful to answer, which is why it gets replies where a harder pitch would not. People who are genuinely happy will say so plainly, and that is your cue to disengage gracefully. People who are quietly unhappy will often say more than they intended to, because you have given them permission to vent about something that has been mildly annoying them.

What to send back depending on the answer

A worked example

Prospect: "Thanks but we already have a vendor for this."

Reply: "No problem. Is it covering everything you need there, or is there a specific piece that's still a gap?"

Prospect: "Mostly covers it, though reporting has been a pain point."

That single word, "reporting," is now a real opening. The reply from here should be narrow and specific to that gap, not a repeat of the original pitch.

When to actually let it go

Not every "already have a vendor" is worth chasing. If the follow-up question gets a short, closed answer with no detail, that is a genuine signal to move on rather than a puzzle to solve. Persisting past a clear no damages the account and, over a campaign, damages the sender's reputation on the platform. The skill here is not always finding a way in, it is knowing quickly which accounts to park and which ones deserve a second question.

Next: the next time you get this objection, reply with one specific question about the current vendor before deciding whether the account is closed or just quiet.

Related Dispatches

Outbound glossary · How it works · Pricing