"How Are You Different From [Competitor]?" Asked Ninety Seconds Into a Cold Call

Ninety seconds into a cold call, the prospect interrupts you and says: So how are you different from Competitor X?

Most reps hear a buying signal. They lean forward. They start talking. And by the time they come up for air, the call is over and the prospect has filed them next to the last four vendors who called about the same thing.

I have listened to a lot of cold calls, and this is one of the most reliably mishandled moments in the whole conversation. Not because the answer is hard. Because the question is not the question.

What the buyer is actually doing when they ask

Think about what has happened in the ninety seconds before. A stranger called. The stranger said a sentence about what they do. The prospect's brain did what brains do with new information: it went looking for an existing folder to put it in.

Most of the time, it found one. You said something about visibility and their brain said ah, tracking software, we looked at that. You said something about anomaly detection and their brain said AIOps, we bought that, it did not work.

The competitor comparison objection on a cold call is the sound of that filing happening out loud. The prospect is not asking you to differentiate. They are asking you to confirm the file so they can close the drawer and get off the phone politely. That is the default case, and if you answer it like a genuine question you will lose.

But it is not the only case. There are three things the question can mean, and your first job is to work out which one you are in.

One: they are filing you

The most common version. Tone is flat, slightly fast, often comes with a small sigh. They have heard a pitch shaped like yours before. They are not evaluating anything. They want a category so they can say yeah, we are happy with what we have and hang up without being rude.

The tell is that they name a competitor they are not using. If someone says how is this different from Salesforce and they are not buying a CRM this quarter, they are not comparing. They are gesturing at a shelf.

Two: there is a real evaluation in flight

Rarer, much better. They are actually looking at something, or they looked at something last quarter and it stalled, and your call landed in the middle of a live internal debate. The tone is different — sharper, more specific. They name a product, not a company. Sometimes they name a version or a module. Sometimes they say we are in a trial with.

This is the one where a comparison is genuinely useful, and it is still not the moment to give it, because you do not yet know which two or three things they care about out of the forty you could list.

Three: scar tissue

They bought something in your category and it went badly. The question is not how are you different, it is convince me you are not going to do the same thing to me again. You hear it in the phrasing. We already tried that. We have one of those. Is this another one of those tools that...

Answering a scar-tissue question with a feature comparison is like answering I got food poisoning here last year with a description of the specials.

Three meanings, three different next moves, and you have about a second and a half to pick. Which is why the answer is not an answer.

Why the feature comparison loses even when it is accurate

Say you know your competitor cold. You know where you win. You launch into it: we are faster to deploy, we do not require an agent, our data model handles multi-entity, their support is offshore.

Here is what the prospect hears. First, they hear a vendor talking about another vendor, which is the least credible source of information about that vendor on earth, and they know it. Second, and worse, every one of those claims is an answer to a question they did not ask. They asked a general question because they had a general level of interest. You gave them a specific answer, which reveals that you do not know anything about their situation, which confirms the thing they suspected when they picked up: this is a spray call.

Third, you have accepted the frame. By comparing yourself feature-for-feature to the competitor they named, you have agreed that you are in that category, and the category is where the conversation goes to die. Once you are in a category, the only remaining question is price, and you cannot win a price conversation ninety seconds into a cold call with someone who does not have a problem yet.

I have watched reps give technically flawless competitor comparisons and get sounds good, send me something every single time. Flawless and useless.

The reframe: refuse the comparison, ask for the use case

The move is to decline to answer in a way that does not sound like dodging. Something like:

Honestly, depends what broke last time. Can I ask what you are using it for?

Or, if they have not told you they use anything:

Depends entirely on what you would be using it for. What made you think of them?

Read why that works, because the mechanics matter more than the wording.

Depends what broke last time does three things at once. It concedes that the competitor is real and probably fine for some people, which immediately makes you more credible than every rep who trashed them. It implies you have seen this category fail in specific, nameable ways, which is a small claim of expertise that costs you nothing. And it plants the idea that something did break, which — if they are in category three — they are itching to tell you about.

Then the question. Short, open, about them. What are you using it for is better than what are your requirements because requirements is a procurement word and use is a work word. People will tell you what they do all day. They will not tell you their requirements to a stranger.

What you have bought yourself is another sixty seconds, and more importantly you have flipped who is talking. If they answer that question with anything longer than five words, you are in a conversation instead of a pitch.

If they give you nothing — we just use it for the standard stuff — you have still lost nothing, and you can go to your one loaded differentiator, which we will get to.

Naming the competitor without trashing them

You have to be able to say the competitor's name out loud, calmly, without your voice changing. Most reps either cannot bring themselves to say it, which reads as evasion, or say it with a little edge, which reads as insecurity. Both are worse than the truth.

The rule I use: say something true and slightly generous, then move to difference of fit, not difference of quality.

They are good. Most of the brokerages I talk to who went with them are still on them. Where I usually get called in is when someone has more than a couple of TMS integrations to keep straight, because that is where it gets manual.

Notice there is no attack. There is a boundary. You are describing the edge of their fit, not the limit of their competence. That is a much harder statement to argue with, and it makes you sound like someone who has seen deployments rather than someone who has read a battlecard.

The second rule: never be the first to bring a competitor up. If they name them, you can name them. If they have not, do not go looking. Volunteering a competitor's name on a cold call is doing their homework for them and reminding them there is an alternative to talking to you.

Third: if they ask about a competitor you genuinely lose to in their exact situation, say so. For what you just described, honestly, they are probably the better fit — the place I would be useful is if X ever becomes a problem. You will lose that deal. You will keep the relationship, and in my experience those calls come back more often than the ones you bluffed your way through.

Load one differentiator per persona, and state it as an outcome

Here is the discipline most teams never do. For every persona you dial, you should have exactly one differentiator loaded, and it should be a thing that happens to a person, not a thing that exists in your architecture.

One. Not a list. If you have five, you have none, because under pressure you will say all five badly.

And it has to be an outcome. Reps default to architecture because architecture is what they got trained on. We are agentless. We have a native connector. Our data model is entity-first. None of that lands with a buyer at ninety seconds because none of it describes anything happening to them.

Translate it. Agentless becomes nobody on your team has to touch the endpoints, so you are not waiting on a change window. Native connector becomes you do not need an integration project, which is usually the thing that kills these in month two. Entity-first data model becomes when you acquire someone, you are not rebuilding your reporting.

Same fact. One of them is a feature and one of them is a Tuesday.

The per-persona part matters because the same product produces different outcomes for different jobs. A VP of Sales and a RevOps lead do not want the same thing from the same platform, and if you are dialling both — which most reps working the SaaS motion into CROs, VPs of Sales and RevOps leaders are — you need two loaded answers, not one you shade slightly. The VP wants pipeline they can trust in the forecast. The RevOps lead wants to stop rebuilding the same report every Monday. Give the VP the RevOps answer and you sound like a tools vendor. Give the RevOps lead the VP answer and you sound like a consultant who does not understand the work.

Write them down. One line each, per persona, stated as an outcome. Then say each one out loud until it stops sounding like a sentence you wrote.

Worked example: the brokerage buyer who has heard it four times

Freight is the hardest version of this because the category is crowded and the buyer is fielding calls all day. You are on with an ops director at a mid-size brokerage. You get through the opener. Ninety seconds in:

Prospect: How is this different from [visibility vendor]?

Flat tone, no follow-up detail, no product name. That is a filing question. Category one.

Rep: Honestly, depends what broke last time. Are you running them today?

Prospect: We have had them about a year.

Rep: Okay. What are your dispatchers actually using it for day to day?

Prospect: Mostly check calls. Tracking loads for the customers who ask for it.

Rep: Got it. So the bit I would ask about — when a load goes dark on a carrier who is not on the network, what happens?

Prospect: Someone picks up the phone.

Rep: Right. That is the whole reason people call me. Their tracking is good. The gap is the tail — the carriers who never onboard. My customers stopped assigning a person to chase those.

Look at what happened. The rep never compared anything. They asked what it is used for, listened for the edge of the incumbent's fit, and then named one outcome — nobody chasing the tail — in language the ops director uses internally. No architecture. No feature. No trashing.

And critically, the rep earned the right to be specific by asking two questions first. That is the difference between differentiation and noise. If you are working this market, most of the groundwork sits earlier in the call, in the freight and 3PL opener built for buyers who have heard the pitch four times — the comparison question gets much easier when your opening line has not already put you in the category.

Worked example: the network ops leader burned by AIOps

Different shape entirely. You are on with a head of network ops. Ninety seconds in:

Prospect: Is this another AIOps thing? We already went through that with [vendor].

That is not a filing question and it is not an evaluation. It is scar tissue. Category three. The words went through are doing all the work — that is someone describing a bad experience, not a purchase.

Do not defend the category. Do not say well, we are not really AIOps — that is a semantic dodge and they will hear it as one.

Rep: Probably fair to be sceptical of it. What happened with them?

Prospect: Took nine months to tune and it still paged us for everything.

Rep: Yeah. Alert volume goes down on the slide and up in real life. Can I ask — was that a model problem or a topology problem? Most of the time when I hear that, the tool never actually knew what depended on what.

Prospect: Bit of both. It never had a decent view of the estate.

Rep: That is the only thing I would claim to be different on, and I would rather be specific than pitch you. We do not start with detection. We start with dependency. The outcome my customers care about is that when something goes, they get one page instead of forty, and they get it for the thing that broke rather than the forty things downstream of it.

The rep asked what happened before saying a single word about their own product. Then they named a failure mode — the tool did not know what depended on what — which is a credibility play, because only someone who has seen these deployments would name it. Then one differentiator, stated as an outcome: one page instead of forty.

Technical buyers punish generalities harder than anyone. If you are dialling into network organisations you have probably already found that out; the telecommunications opener for CTOs and heads of network ops goes deeper on that, but the principle holds everywhere. Ask what broke, name the failure mode, give one outcome.

When they push back and demand the comparison anyway

Sometimes the reframe does not take. No, seriously, just tell me how you are different. Fine. They have earned a straight answer and stalling twice will cost you the call.

Give them one thing, framed as fit, and hand the question back:

Shortest honest version: they are built for X, we get called in for Y. If you are mostly doing X, I am probably not worth your time. Which one is closer to you?

You answered. You did it in two sentences. You gave them a real basis for a decision instead of a battlecard, and you ended on a question that requires them to describe their own situation. If they say we are mostly X, thank them and get off the phone — you have saved you both a fortnight. If they say actually, both, you are in a conversation.

What you never do is give the full comparison. Not on a cold call, not at ninety seconds, not to someone whose use case you cannot describe in a sentence. Save it for a call where they have told you what matters, because a comparison is only useful once you know which column the buyer is reading.

Make it a reflex, not a plan

Everything above collapses under pressure unless the first four words are automatic. Depends what broke last time has to come out of your mouth before your brain has finished categorising the question, because if you pause to think, you will default to the feature list — that is what every rep does, and it is what I did too before I got sick of hearing myself do it.

So run the reps. Write your one differentiator per persona as an outcome, get someone to throw the competitor question at you at random points in a mock call, and practise the reframe until it sounds bored rather than rehearsed. If you do not have a colleague with the patience for that, this is exactly the kind of thing I built DrillCall for — take your three personas, load the competitor objection, and run it forty times until the reframe is the thing that comes out instead of the pitch. That is what I would do next, this week, before your next dial block.

The question sounds like interest. Treat it as a door closing, and answer it by asking what they are using it for. Almost every rep I have watched who makes that one swap gets a longer call out of it.