Competitor Mentions in Sales Calls: What They Actually Signal

By Ahmet Ozcelik, Product Marketing Leader & GTM Engineer — Published 2026-08-06

Quick answer: Competitor mentions in sales calls are a leading indicator of deal outcome, not just a moment reps need to navigate gracefully — Gong's own research found deals with early-cycle competitor mentions close 49% more often than deals without them. The harder problem isn't how to respond in the moment; it's that most teams only count how often a competitor's name comes up, when what actually matters is the specific claim, sentiment, and deal stage attached to each mention. Analyzing mentions at the claim level, across every call and segmented by won/lost outcome, turns an anecdotal signal into a structured competitive intelligence feed.

Most advice on competitor mentions in sales calls is written for the rep in the room, not the person building the battlecard. That's a gap, because the two questions — "what do I say right now" and "what does this mean across 400 deals" — have almost nothing in common.

What Competitor Mentions Actually Signal About a Deal

Start with the research everyone in this space eventually cites, because it's genuinely good and worth taking seriously. Gong Labs — the research team long associated with Chris Orlob's work at Gong — analyzed thousands of recorded sales calls and found that customers who mention your competitors early in the sales cycle are 49% more likely to close than those who don't.

That number gets repeated a lot, but the mechanism behind it matters more than the headline. Gong's researchers found that when your competitors are mentioned early in the sales cycle, you have a greater chance of winning the deal than if they were not mentioned at all — but the same isn't true late in the cycle. An early mention usually means the buyer has done homework, formed a real evaluation criteria, and is engaging seriously rather than kicking tires. A late mention often means the reverse: something is unresolved, and the deal is reopening rather than closing.

That's the correct starting frame. A competitor mention is not, by default, bad news. It's data about where the buyer is in their thinking, and it correlates with outcome in a direction most reps don't expect.

The problem is that almost everything written about this treats it as a single-call skill question — how to respond gracefully, when to bring up a competitor first, how not to sound defensive. Those are legitimate rep-coaching questions. But if you own battlecards or a win/loss program, the question you actually need answered isn't "how did that one call go." It's "across every deal this quarter, which competitor claims are winning and which are costing us," and no amount of in-the-moment coaching advice answers that.

Why Isn't Counting Competitor Mentions the Same as Understanding Them?

Most teams' answer to "how are competitors showing up in our deals" is a number from a competitor mention tracker: Gong, like most call platforms, will flag every instance a competitor's name gets said and hand you a count. Competitor X got mentioned 34 times this month, Competitor Y got mentioned 12 times. That's the extent of what a tracker tells you, and it's the reason competitive intelligence work built on trackers alone stalls out.

A count has no direction. "Competitor X mentioned" could mean the buyer is afraid to leave them, is comparing per-seat pricing, is worried about a missing integration, or is actively praising their onboarding. All four register as the identical tracker hit. Two calls that mention the same competitor by name can carry opposite implications for whether you win the deal, and a frequency count treats them as indistinguishable.

This is the same failure mode that shows up in objection analysis, and it's worth naming directly: reps under-log competitive context in CRM fields the same way they under-log objections. Discera's own analysis across customer call data found a median of 6.2 objections surfaced per call by structured analysis, versus 1.1 logged manually in CRM by reps. Competitive context follows the same pattern — the call has far more signal in it than the CRM field a rep fills out after the fact, because reps are optimizing for moving the deal forward, not for building your competitive intelligence dataset.

Here's how the three common approaches actually stack up once you need this at the scale of a real pipeline, not a handful of calls:

If you want the deeper version of this argument — how Gong's native analysis differs from a purpose-built layer built to extract structured findings rather than just flag keywords — that's the mechanical reason trackers plateau where cross-call analysis doesn't.

The Three Things Worth Extracting From Every Mention

If a count isn't the unit of analysis, what is? Three things, extracted per mention, not per call:

Claim. What specifically did the buyer say about the competitor? Pricing comparison, a feature gap, a switching reason, an implementation fear, a preference for the other vendor's onboarding — the claim is the actual content of the mention, and it's what a keyword tracker throws away.

Sentiment. Was the mention favorable to you, favorable to the competitor, or neutral and exploratory? "They're worried Competitor X doesn't do SSO" and "they like Competitor X's onboarding" both trigger the same tracker hit, but they're opposite signals for the deal and for your battlecard.

Stage and outcome. The deal stage the mention occurred at, and — once the deal closes — whether it was won or lost. This is the piece that turns a single mention into a pattern. One instance of "they're comparing our pricing to Competitor X" is an anecdote. Forty instances of that same claim, disproportionately present in calls that ended in closed-lost, is a finding you can act on in your next battlecard revision.

This is the identical extraction logic that makes objection analysis useful instead of anecdotal — pull the specific instance out of the transcript, tag it, and aggregate. Applied to competitor language specifically, it's what separates a mention tracker from an actual competitive intelligence process, and it's the same discipline good win/loss analysis already applies to loss reasons more broadly.

The Lost-Deal View Is a Filter, Not a Separate Report

Competitive loss analysis gets treated in most sales orgs as its own project — a separate initiative with its own interview cadence, its own spreadsheet, its own quarterly ritual of pinging AEs for anecdotes about why a deal went to a competitor. It doesn't need to be. If you're already extracting claim, sentiment, and stage from every competitor mention, the lost-deal view is just that same dataset filtered to a closed-lost outcome.

That reframe matters because it means you don't need a second workflow to answer "how are we losing to Competitor X specifically." You need to segment the same extraction by CRM stage or closed-lost reason and read the claims that cluster there. This is a natural extension of win/loss analysis on Gong calls — the mechanics are the same, you're just narrowing the filter to one competitor and one outcome.

Be honest about what this view can and can't tell you. It surfaces which claims and which competitors show up disproportionately in losses — real pattern visibility you can act on in a battlecard. It does not hand you a single root-cause percentage ("Competitor X caused 23% of our losses") unless you've validated that number against a real, cited methodology. Resist inventing that precision. The value here is in seeing where a specific claim about a specific competitor clusters by segment, not in producing a false-confidence statistic. To do that segmentation well, you'll want to segment Gong calls by deal stage and by CRM outcome field, so the claims you're reading are actually grouped by what you're trying to learn.

Aggregating Competitor Mentions Across Gong Calls

If your team runs sales and customer conversations through Gong, this is the concrete version of everything above.

Instead of pulling a sample of calls each quarter to spot-check how competitors are coming up, you run one prompt across every call in a Gong workspace for a given date range — not a sample, the full set. Discera connects to Gong read-only; it doesn't record calls or write anything back, it analyzes what Gong has already captured.

A workflow I'd set up for this: filter to Gong calls from the last two quarters, restricted to calls where a HubSpot deal record shows stage equal to Closed Won or Closed Lost, and further restricted to calls where a named competitor keyword tracker already fired. Then run a prompt like:

"For every call where a named competitor is mentioned, extract: the competitor name, the specific claim the buyer made (pricing, feature gap, switching reason, fear, or preference), the sentiment of the mention, the deal stage it occurred at, and the final deal outcome. Group findings by competitor and summarize the top three claims associated with losses and the top three associated with wins."

Discera's competitive analysis template runs that extraction across the full set — up to 30 parallel jobs, so a workload of around 1,000 calls typically finishes in roughly 5 minutes, not the days a manual pull would take. The output is a per-competitor breakdown: which claims are winning deals, which are costing them, and how that's trending by segment.

Schedule the same prompt to rerun monthly and land in a #competitive-intel Slack channel, with the full breakdown exported as a DOCX for the quarterly battlecard refresh. The competitive intelligence lead stops manually stitching together anecdotes from Slack threads before every battlecard update, because the per-competitor view is already sitting in the channel, refreshed automatically, before anyone asks for it.

One caveat worth stating plainly: this entire workflow depends on Gong being the call source. Discera doesn't generate the underlying signal — it reads and structures what Gong has already recorded. If your team isn't on Gong, the claim-level extraction methodology above still applies; you'll just need a different way to get transcripts into a structured analysis layer.

FAQ

Is it a bad sign when a prospect mentions a competitor?

No — Gong Labs research shows the opposite when the mention happens early. Early mentions correlate with higher win rates because they signal an educated, engaged buyer who's already comparing options seriously. Late-cycle mentions are the pattern worth watching, since they often indicate the deal is reopening rather than closing.

Should sales reps bring up competitors first in a call?

There's a legitimate rep-skill argument for it, but it's a different question from the one this article is built around. Whatever a rep does in the moment, the larger opportunity for a competitive intelligence or product marketing lead is capturing what gets said about the competitor across every call — not just coaching the single conversation.

How do you track competitor mentions across sales calls at scale?

A native competitor mention tracker, built into most call platforms including Gong, flags when a competitor's name gets said but only reports frequency. Tracking it meaningfully at scale means running an analysis layer over every flagged call that extracts the claim, sentiment, and deal stage per mention, then rolls that up by competitor.

What's the difference between a competitor mention tracker and competitive analysis?

A tracker counts occurrences; competitive analysis extracts meaning from each one. A count tells you a competitor's name came up 34 times this quarter — competitive analysis tells you which specific claims about that competitor are actually costing you deals, and which are helping you win them.

If your team runs deals through Gong and HubSpot, start a free trial at discera.ai and run the competitive intelligence template against your own last two quarters of calls.