The Playbook · Chapter 1: Cold calls · Lesson 3 of 5

How to respond to “we already have something for that”

We already have something for that.

No idea if we do. It usually works.

Don't argue with the incumbent. “Makes sense, most teams I call have something. What would have to break for you to look again?” You're not selling against their tool, you're locating the gap it leaves.

The read

Why they say it

Sometimes it's true. Often the buyer genuinely doesn't know, and the sentence works as a call-ender either way, because disputing it means questioning their judgment moments into a cold call.

The mistake is hearing it as a competitive situation. On a cold call it's a reflex, and a reflex carries no information about the tool, the contract, or how anyone feels about it. You have to ask for that.

The move

Don't argue with the incumbent, in practice

Legitimize it first. “Makes sense, most teams I call have something” tells them you're not about to argue, which is the only thing that keeps the call alive past the sentence.

Then ask about the gap, not the tool: “What would have to break for you to look again?” or “What's the part it still doesn't cover?” Every incumbent leaves a remainder, and the remainder is your entire pitch surface.

Never compare features here. A cold call can't win a bake-off, and trying signals that you need them to be unhappy. You don't. You need them to be curious.

Same exit, other doors

Variations you'll hear

We're under contract with someone. Real information. Ask when it renews, log it, and be the first call they get that quarter.

We built something internally. The gap question still works. Internal tools freeze at version one; ask what's still on the wishlist for it.

That's another team's thing. A redirect, not a rejection. Ask who owns it and whether they'd make the intro.

Hear this objection handled

A sample call against an AI buyer who leads with it, scored and broken down

Charles Whitaker
9

Sarah excellently bypassed the legacy-software gate by validating the existing setup first, then pivoting to a major manual pain point (last-minute routing changes) to successfully earn a 15-minute discovery call.

0:00/0:00

Your turn against the same buyer

Same persona, same objection, same scorecard

Charles Whitaker

Cold Call to Apex Logistics: Navigating the Existing Software Objection

Your objective is to secure a brief, 15-minute discovery call to evaluate if RouteFlow's dynamic dispatch engine can reduce Apex's fuel costs. When Charles raises the objection that they 'already have something for that,' do not argue with the incumbent software or try to prove RouteFlow is better. Instead, acknowledge and validate his current setup: 'Makes sense, most teams I call have something. What would have to break for you to look again?' Your goal is not to sell against their existing tool, but to locate any gaps, manual workarounds, or blind spots that their current system leaves behind.

Uses your mic. Hang up anytime. Scorecard at the end.

Practice it until it stops working on you.

Start practicing