How to tell a competitor is in a deal before the rep does: signals in CRM, calls and email

Why "the rep will tell me" fails

The competitor field is the last place the truth shows up. It records what the rep knew and chose to type, usually while writing the loss reason, well after the buyer first asked how you compare. HubSpot has no competitor field at all: the default deal properties include "Closed lost reason" and "Closed won reason" and nothing about competitors, so each team creates a custom property (checked October 7, 2026). Salesforce can hold competitors on an opportunity, filled in by hand the same way (check your org's page layout).

This article covers finding out mid-deal. Choosing which competitors to track is in a competitor list has four buckets; checking the CRM loss reason against the buyer afterwards is in CRM loss reasons and buyer feedback.

Eight signals, and what each one misses

The strength column is our judgement; no source we found quantifies the false-positive rate of any of these signals.

G2 defines a Compare signal as "A buyer viewed a G2 comparison page including your product and at least one competitor" and a Competitive signal as a buyer viewing "a pricing, profile, or compare page for a competing product in a shared category" (G2 Buyer Intent data reference, read October 7, 2026). Its fields identify the buyer organisation and the visitor's region and country; no field names a person. For web visits, the visitor-identification vendor Knock2 states that "IP matching only works well for people on corporate networks. Remote workers, VPN users, and anyone connecting from a residential ISP don't show up as their company", which is why the row is rated low.

The two inference rows rest on thinner material. A bid-writing blog advises reading RFP requirements as signals of an incumbent's weakness (River Editor, November 2025); that is advice to a bidder, not evidence that a named competitor is active. Drew University's purchasing policy requires three quotes between $25,001 and $49,999 and a formal competitive process above $50,000, and lists recurring purchases that may be solicited on a multiyear basis. One institution, but it shows that a request for a competing quote can be a rule about the price band rather than a rival in the room.

What a Gong tracker can and cannot see

Gong's help centre describes two tracker types. Keyword trackers "detect specific words or phrases when they appear in a conversation"; AI trackers "detect concepts and intent rather than exact words" (About trackers, updated October 6, 2026). Competitor names are a keyword tracker, and Gong's win/loss analytics reads a pre-built competitors tracker created during setup.

The configuration settles whether the rep or the buyer said the name. When you create a keyword tracker, "Track when mentioned by" offers "Anyone (default), People at your company, and People not at your company"; the last makes the count buyer-side. The same page lets you include related word forms, restrict to phrases said as part of a question, choose calls only or calls and emails, and keep a separate keyword list per language.

Four documented limits belong in your report's footnote:

• "Calls without transcripts produce no tracker results" (Troubleshoot trackers).
• "Email tracker results are not currently available through the standard Salesforce tracker push. Only call-based results push to Salesforce" (same page). Email keyword results appear only in the deal activity panel and the account page.
• "When your company runs out of credits, published AI trackers are automatically paused and must be manually republished after credits are added" (About trackers). Nothing in the report shows the pause.
• Deals with no calls at all are excluded from the win/loss competitor insight (Review win/loss analytics).

The docs say nothing about a competitor whose name is also an ordinary word, or about a mis-transcribed name. We expect over-matching for the first and under-matching for the second; if a competitor's name is a common word, read a sample of matches before you trust the count.

Read a mention as named, compared or evaluating

A mention is not an evaluation. Gong's AI tracker docs draw the same line: "not just whether a competitor was mentioned, but whether it was framed as a competitive evaluation". For your report, sort each buyer-side mention into named (the competitor came up), compared (the buyer asked how you differ) or evaluating (the buyer said they are running both). Only the last two belong in a "competitor in the deal" count.

Timing matters as much as the label, and the only numbers on it are Gong's own. Gong Labs reported in January 2025 that "an early competitive mention increases the odds of winning an enterprise deal by 32% over not discussing the competition" and that "since 2022, the average number of competitive mentions increased by 57%" (The best sales insights of 2024). A 2017 Gong study put the early-mention lift at 49% and found late mentions slightly less likely to close than greenfield deals (Win competitive deals). Both are vendor figures with no stated sample size. Cite them with their dates or leave them out; the direction, early beats late, is the useful part.

One competitor no tracker lists is the status quo. A MEDDPICC guide includes it: competition "includes the status quo (doing nothing) and internal builds" (exec.com, February 2026). A buyer who never names a vendor may still be weighing you against their own engineers or against doing nothing.

If there are more tracker hits than you can read, Claude can do the first sort in a plain chat on an anonymised export: strip names and company identifiers, paste the snippets, ask for one of the three labels per snippet with the sentence that justifies it, then read every snippet it labels evaluating yourself. This is our suggestion, not a documented Gong or Claude workflow, and each label is a hypothesis until a person confirms it.

Three ways a mention-rate report misleads

A competitor mention rate is the number leadership asks for, and it is easy to produce one that is wrong in the direction of your choosing. Each trap below comes from a documented limit above.

1. Counting mentions or calls instead of deals

   A deal with five calls and one competitor is one competitive deal, not five. Gong's own insight shows how the double count creeps in: "Unlike other insights, a deal can appear in more than one graph bar if more than one competitor is mentioned." Report "deals with at least one competitor" as its own figure and keep "mentions per call" separate.

2. A denominator that is not all deals

   Gong's win/loss analysis excludes deals with no calls at all. Trackers see only transcribed calls and emails, the CRM list only deals a rep filled in, a paused AI tracker nothing, and email results do not reach Salesforce through the standard push. A rate whose denominator is "deals with a recording" overstates presence. No source quantifies that bias, so print the denominator and let the reader judge.

3. Treating a mention as an evaluation, and ignoring when it was said

   A rep who name-drops a rival on the first call produces a mention; a buyer who asks for a side-by-side on the fourth produces an evaluation. Collapse the two and the rate rises. Ignore the date and the early-versus-late split that Gong's figures turn on disappears.

A good report states the denominator, counts deals, splits early from late and named from evaluating, and footnotes which deals were invisible to each source. A bad report is one percentage with no denominator.

A rule for "competitor present", and an alert that asks to be confirmed

Write the rule down before the first report, so the number means the same thing every month. Our recommendation: a deal is "competitor present" when a buyer-side signal shows a comparison or an evaluation (a tracker hit labelled compared or evaluating, a comparison request in email, or an RFP grid that names the rival), or when the CRM field is filled. Record the date and source of the first signal on the deal. A rep-side mention, a web visit or a G2 intent hit is a prompt to look, not a count.

Then route the signal to the person who can confirm it. The wording below is ours, invented for this article, and it is a question on purpose:

Competitor signal on [Deal]: [Competitor] named by the buyer on the [date] call. Source: call tracker. Not yet confirmed in CRM. Owner: [AE]. Confirm or dismiss.

The AE either fills the field, which turns the signal into a record, or dismisses it, which teaches you which signals over-match. Once a month, reconcile the tracker's deal list against the CRM field: deals the tracker caught and the field missed are your lag, and deals the field holds and the tracker never saw are your transcript gap.

Where Steve fits

Everything above runs on Gong, a CRM, a spreadsheet and one person who does the reconciliation. The competitor is in the CRM only when a rep remembers to enter it, and the remedy, a buyer-side tracker plus a monthly reconciliation, stops the month that person is busy. It also never sees the status quo.

Steve's Intelligent Deal Detection works inside HubSpot and Salesforce. As the site describes it, Steve suggests the competitor on each new deal and you approve it, one at a time or in bulk; every recorded call Steve imports is matched to its deal by participant email and linked on the record; a battle-card link is written onto the deal or opportunity; and deals sync every night and whenever you click Sync. Steve connects to Gong and scans your call transcripts for competitor mentions, tags each insight with its transcript context, and lets you approve, edit or reject it before it reaches a battle card.

The tradeoffs, as of October 2026, are on the same pages. A person approves each suggestion; nothing is tagged automatically. Sync runs nightly or on demand rather than in real time. Its inputs are the CRM deal, recorded calls from the recorders it connects to, and, on HubSpot, linked Gmail threads; you can also attach an RFP to a deal and ask Steve about it. The site does not claim that Steve detects a competitor from email wording, RFP wording, procurement behaviour, web visits or review-site intent, nor a Slack alert on a mention. It works with HubSpot and Salesforce only. If your gap is the CRM field and the call-to-deal match, that is the job it does; if your gap is the other five rows of the table, keep the rule and the reconciliation above.