When a buyer names a competitor mid-call, don't attack it and don't rush to compare features. Acknowledge the name, ask why they're looking at it, narrow the comparison to the two or three things this buyer said matter, then show proof on those. Reps who handle it well treat the mention as useful information about how the buyer is thinking. Here's the sequence, the scripts, and the one-screen battlecard that makes it repeatable.
The mention is information, not an attack
A competitor's name tells you the buyer is doing their job. They're evaluating, which means there's a real project with a real budget somewhere behind it. It also tells you what category they've put you in, who else got a meeting, and sometimes which feature list they're carrying around. Reps who hear it as a threat get defensive, and defensiveness reads as weakness to a buyer who was only asking a question.
The goal for the next three minutes is to learn why that competitor is in the room, and to reset the comparison to the buyer's problem instead of the competitor's feature grid.
Step 1: acknowledge without flinching
Say something respectful and brief. The buyer may already like the other product, may have a colleague who uses it, or may be testing how you react.
"Yes, we see them a lot, and they're a solid product for the right situation. It's worth understanding where the two of us differ for what you're trying to do."
Avoid the two reflexes: dismissing them ("they're not really a competitor") and dumping a comparison ("here's a list of twelve things we do that they don't"). The first sounds insecure, the second sounds rehearsed, and both hand control of the conversation to a company that isn't on the call.
Step 2: get curious about why
Before you compare anything, find out what put the competitor on the list. One or two questions, asked plainly:
"What drew you to them? Was it something specific they showed you, or more that they came recommended?"
"When you looked at them, what did you like most, and what was missing?"
The answers do two things. They tell you what the buyer values, often more honestly than your discovery did, and they tell you whether the competitor is a serious alternative or a box being ticked for procurement. Say a buyer answers that the other vendor "came recommended by our Salesforce admin." That's a relationship to understand, not a feature gap to close.
Write the answer down, or make sure your notes capture it. Which competitors come up, and why, is some of the most useful information your marketing and product teams will get this quarter, and most of it evaporates in the debrief.
Step 3: box the comparison to what this buyer said matters
You should already know the two or three outcomes the buyer cares about from discovery. Bring the comparison down to those and nothing else. A feature-by-feature debate is one the buyer can't judge, and the competitor's marketing team wrote the questions for it.
"Earlier you said the thing that would make this a win is reps getting answers while they're still on the call, not the next morning. Let's compare on that. I'll tell you honestly where they're stronger too."
Then do exactly that. Concede what's true. If the competitor has a better reporting module and the buyer didn't list reporting among their outcomes, say so and move on. Conceding one point you don't need buys credibility for the points you do.
Step 4: deliver proof, not claims
Once the comparison is boxed, show evidence on those points: a two-minute demo of the specific workflow, a reference customer in the same industry, a result a customer has shared publicly. Offer a reference call rather than a slide. Buyers evaluating two vendors remember who let them talk to a customer.
If you genuinely can't win on the outcome the buyer cares most about, say so and ask what else is on their list. Losing a deal honestly in week three is better than losing it in week eleven after a proof of concept.
Step 5: build the battlecard that fits on one screen
Reps freeze on competitor mentions because the battlecard is a nine-page document nobody has opened since onboarding. Cut each competitor to one screen with five sections: how they position themselves, where they genuinely win, where you win, the three questions to ask when they come up, and the proof points with links. Write the "where they win" section honestly. Reps who trust the card will use it, and reps who catch it exaggerating will ignore all of it.
Then make the card show up when it's needed. Reps won't search a content library mid-call. If the card can appear when the competitor's name is spoken, it gets used on the call that matters rather than in the debrief afterward.
What not to say
- "They're going out of business," or anything about a competitor's finances, staff, or roadmap that you can't source. It comes back to you.
- "We do everything they do plus more." Unverifiable, and it invites the feature grid you were trying to avoid.
- "Nobody uses them anymore." The buyer may have a colleague who does.
- Anything you wouldn't say if the competitor's CEO were on the call.
Where this goes wrong
- Comparing on the competitor's terms. The rep answers a feature checklist, both products start to look the same, and the buyer decides on price.
- Skipping the why. The rep launches into differentiation before learning that the competitor is only on the list because procurement requires three quotes.
- Refusing to concede anything. Buyers stop believing the claims you're right about.
- Battlecards nobody can find. Nine pages in a content library, written for a launch two years ago, are the same as no battlecard.
- Trashing the competitor. It's the fastest way to lose a buyer who respects them.
Where Aircover fits
Aircover listens for competitor names during the call and surfaces the one-screen battlecard, the approved questions, and the proof points at the moment the name is spoken, so the rep isn't reconstructing positioning from memory. After the call, managers can see which competitors came up, how often, and how each mention was handled. The objection handling page shows how battlecards surface during a call.