"We Already Use Someone For That" — How to Keep Talking Without Trashing the Incumbent

Nine out of ten times I hear a rep get discouraged on a cold call, it's this. They open, they get through the first ten seconds, and the prospect says some version of "yeah, we already use someone for that." The rep says "okay, no problem, I'll follow up down the road" and hangs up. Then they mark it as a no in the CRM and move on to the next name.

That's a rookie error, and I did it for longer than I'd like to admit.

Here's the thing that took me too long to understand: if the buyer is worth calling, they almost certainly already have a vendor. Companies with real problems and real budgets do not sit around with the problem unsolved waiting for your cold call. They solved it, badly or well, sometime in the last few years. The greenfield prospect — nobody in the seat, no tool, no incumbent — is usually greenfield because the problem isn't painful enough to spend money on. Those are the accounts that ghost you after three great meetings.

So when someone says "we already have a vendor," they are not rejecting you. They are handing you a qualification signal that most of your pipeline would kill for. The trick is knowing what to do with the next sixty seconds.

What that sentence actually tells you

Break the objection apart and there are three separate facts inside it, and every one of them is good news.

First, they bought the category. Somebody at that company sat in a room, agreed that this class of problem was worth solving with money, and signed something. You do not have to educate them on why the category exists. That's the hardest, longest, most expensive part of selling and it's already done. You've inherited the work of whichever rep got there before you.

Second, there is a budget line. It's approved, it's recurring, and somebody owns it. That line item renews. When you're selling into a company with no incumbent, you're asking finance to create new spend, which means a business case, a committee, and a fiscal year. When you're selling against an incumbent, you're asking them to redirect spend that's already allocated. Those are completely different conversations and the second one is much, much easier to get funded.

Third — and this is the one reps miss — they have opinions. Nobody who has used a product for eighteen months is neutral about it. There is something that annoys them. There is a promise made during the sales cycle that didn't hold up. There's a support ticket that took too long, a feature that shipped late, a rep who churned and got replaced by someone who doesn't know the account. You cannot get that texture from a prospect who has never bought anything. You get it for free from a prospect who has.

So the goal on this call is not to convert. It's to get those opinions out of their mouth and onto your notes, and to leave the conversation in a state where you're allowed to call back.

The three-question sequence

I run the same three questions every time, in the same order. They work on cold calls, they work at trade show booths, they work when someone brings up their incumbent halfway through a discovery call you thought was going well.

Before the questions, though, one line. When they say "we already use someone," the first thing out of your mouth should be agreement. Not a pivot, not a "that's exactly why I'm calling" — agreement.

"Good. Honestly, I'd be more worried if you didn't."

That one sentence does a lot. It tells them you're not shocked, you're not about to launch into a rebuttal, and you're not going to spend the next four minutes explaining why they made a bad decision. The tension drops. People who expect a fight and don't get one tend to keep talking.

Then:

Question one: when did you sign?

"Out of curiosity, how long have you been with them?"

This is the least threatening question in sales and it's the most valuable. Nobody guards the answer. Nobody thinks they're giving you anything. And what you get back is the single piece of information that determines whether this account is worth a follow-up sequence or a slot in your calendar six months out.

If they signed three months ago, you're done selling on this call. Full stop. Nobody rips out a tool they just implemented — the person who championed it would be admitting they were wrong in front of their boss, and that's a career cost nobody pays to save a line item. Your job on a three-month-old contract is to be memorable and get off the phone quickly. That's it.

If they signed two, three, four years ago, you have something. Long-tenured contracts are where the accumulated annoyances live. Multi-year deals also mean the pricing is stale, the rep who sold it is probably gone, and the product they bought is not the product that exists today.

If they can't remember when they signed, that's the best answer of all. It means nobody's paying attention to it internally, which means nobody's defending it either.

Question two: what made you pick them?

"What was the thing that made you go with them over the alternatives?"

This question feels like flattery of the incumbent. It's actually reconnaissance. You are asking them to state their original buying criteria out loud, and buying criteria is the whole game.

What you'll hear back is one of three things. Sometimes it's a genuine capability — "they were the only ones who integrated with our TMS." That's real and you need to know if you clear that bar. Sometimes it's a process artifact — "honestly, our old VP knew the guy." That's an incumbent with no moat, and when that VP leaves, so does the relationship. And sometimes it's price, which tells you exactly which lever you'll be pulling later.

The other thing you learn is whether the person you're talking to actually made the decision. If they say "I wasn't here yet" or "that was procurement," you now know you're talking to an inheritor, not an owner. Inheritors have no ego investment in the incumbent. They are the easiest people in the world to switch, and they will tell you things a champion never would.

Question three: what would you change?

"If you could change one thing about how it works today, what would it be?"

Note the framing. I'm not asking what's wrong with the vendor. I'm asking what they'd change about the workflow. Those sound similar and they are not. "What's wrong with them" invites a defense, because criticizing a vendor is implicitly criticizing the decision to buy them. "What would you change" is a wish, and people love saying their wishes out loud.

Almost everyone answers this. Even happy customers answer it. And the answer is your entire follow-up strategy, because now you know what to send them, what to reference in eight months, and what to lead with when the renewal comes around.

If they genuinely say "nothing, it's great" — believe them, and say so. "That's rare, good for you." Then ask one more: "Who else in the org uses it? Same experience?" Headquarters is often thrilled with a tool the field hates.

Why trashing the incumbent costs you the deal

There's a version of this call where the rep hears "we use Competitor X" and immediately goes: "Oh, X. Yeah, we take a lot of business from them. Their reporting is a mess and their support is offshore."

I have listened to reps do this and I have watched the call die in real time.

Here is what the buyer hears. They do not hear "this rep has market knowledge." They hear "this rep thinks I'm an idiot for having bought X." Because a person made that decision. Maybe the person on the phone. Maybe their boss. Maybe their friend two desks over. Attacking the product is attacking the judgment of somebody in the building, and buyers close ranks around their own.

The second thing they hear is insecurity. Confident products don't need to name competitors. When a rep leads with what's wrong with the other guy, the unspoken message is "I can't win on my own merits so I'm going to try to lower yours." Everyone recognizes that move because everyone's seen it in politics and in dating. It reads as weakness, every time.

And the third thing, which is practical: you don't actually know. You know the version of the incumbent that shows up in your win/loss notes, which is a filtered sample of accounts where they lost. You don't know what their product does at this account, on this contract, with this configuration. Confidently describing a product you haven't used to someone who uses it every day is how you get corrected on a cold call, and once you've been corrected on a fact, nothing else you say carries weight.

Language that separates you without smearing anyone

The skill here is describing a real difference in a way that lets the buyer conclude the incumbent is weaker, without you ever having said it. Three patterns I use.

Talk about your design choices, not their flaws. "We built ours around the dispatcher rather than the back office, so most of the workflow lives on mobile." You've said nothing about the competitor. But if the competitor is a desktop tool, the buyer just did the math themselves. Conclusions people reach on their own stick; conclusions you hand them get argued with.

Talk about the type of company you fit. "We tend to land with fleets running under a couple hundred power units, where the ops manager is also the guy answering the phone. If you're bigger than that we're usually not the right call." Disqualifying yourself out loud is the single most credible thing you can do on a cold call. And it forces the buyer to place themselves on one side of the line, which is real information for you either way.

Ask about the thing rather than assert it. Instead of "their onboarding is brutal," try "how long did implementation take you?" If it was brutal, they'll say so, and now it's their complaint instead of your attack. You can build a whole follow-up sequence on a complaint the buyer authored.

This is the same muscle that makes hostile-open cold calls work in general — the freight and 3PL market is the extreme version, where every dispatcher has heard four pitches this week and the freight and 3PL cold call script exists mostly to handle people who are already sick of your category. Same in the field trades, where the construction and trades cold call script has to survive a general superintendent who's standing on a job site and does not care about your platform. In both cases the winning move is the same: fewer claims, more questions.

"Call me in eight months"

This is the outcome you should be aiming for on a fresh-contract account, and most reps handle it terribly. They say "great, I'll reach out then," set a task, and let the account go cold for eight months. Then they call back with "hey, you told me to call you now!" — which is a terrible opener, because the buyer doesn't remember and it puts the burden of the meeting on a promise they don't recall making.

Do this instead. Before you hang up, pin the date. "When you say eight months — is that when the contract's up, or is that just when you'll have bandwidth?" Those are wildly different answers. Contract-up means there's a decision event on the calendar. Bandwidth means there isn't, and eight months from now they'll be just as busy.

Then get permission for the in-between. "I'm not going to chase you. But I run into a lot of teams doing the same thing you are — if I see something worth forwarding, can I send it over? One email, no follow-up sequence." Almost everyone says yes, because you've just described the opposite of what they expect.

Then actually do it. Two or three times over those eight months, send one short email with one useful thing and no ask. No "just checking in." No "circling back." The thing you send should reference what they told you in question three — the thing they'd change. That's why you asked.

And then, six to eight weeks before the renewal date, not on the day, you call back. Renewal decisions are not made on the renewal date. They're made in the window before it, when procurement starts asking questions and somebody has to justify the line item again. Show up on the day the contract expires and you're too late; the auto-renew already fired.

Finding the renewal date without asking for it

Sometimes they'll just tell you. Ask, plainly: "When does that contract come up?" A surprising number of people answer. But when they won't, there are other roads.

Fiscal year is the biggest one. A lot of contracts get signed at the end of a quarter or the end of a fiscal year because that's when the vendor's rep needed the deal. If you know the company's fiscal calendar, you can guess the anniversary within a quarter and be right often enough to matter.

Public sector, education, and anything touching government procurement will often have the contract sitting in a public record — award notices, board minutes, RFP archives. It's tedious and almost nobody does it, which is exactly why it works.

Job postings tell you more than people think. A company hiring for a role that names the incumbent tool just told you they're doubling down. A company hiring for a role that names your category generically may be in evaluation. Press releases and case studies from the incumbent will often say when the partnership started, and start date plus typical term length gets you close.

And the cheapest source: ask a second person. The end user who doesn't own the budget has no reason to protect the renewal date, and often knows it, because their team's been told to get their feedback in before the review.

Know what the other rep is doing right now

This is the part most sellers never think about. While you're building a case to displace the incumbent, the incumbent's rep is building a case to keep them — and if they're any good, they know the account is at risk before you do.

Go read a save-call playbook from the other side of the table. The SaaS renewal save call script is written for the rep who's six weeks from losing an account, and the insurance renewal script for a carrier that's halfway out the door covers the same dynamic in a longer, heavier buying cycle. Read them as intelligence. They'll tell you exactly what will be said to your prospect after your meeting — the concession offer, the exec sponsor who suddenly appears, the roadmap slide with the missing feature now marked "Q3," the switching-cost math.

Once you know those moves are coming, you can pre-empt them. "At some point in this process they're going to offer you a discount to stay. That's fine, and honestly you should take it if the product's right. The question I'd ask is whether the thing that's bothering you gets fixed by a lower price." Say that early and you've inoculated the deal against the most common save play in existence, without insulting anybody.

Run the reps before you need them

All of this collapses under pressure. You know the three questions right now, reading them. On the phone, at 3:40pm, on your nineteenth dial, when someone says "we already use someone for that" in a tone that says go away — you will default to whatever you've said a hundred times before, which for most reps is "no problem, I'll follow up."

So the thing I'd actually do next is not read more about this. It's say it out loud until it's boring. Take the agreement line, the three questions, and one separation statement about your product, and run them against a voice that pushes back the way a real buyer does — flat, impatient, occasionally rude. That's what we built DrillCall for: live voice roleplay where the objection lands before it costs you a real account. Twenty minutes of that beats a week of reading scripts you never say aloud.

The incumbent objection isn't the end of the call. It's the first honest thing the buyer has said. Treat it that way and you'll find your best pipeline is sitting inside accounts you've been marking as closed-lost for years.