Competitor and price mentions in calls: who is the customer comparing you to?

Thursday, 3:40 p.m. A sales manager at a B2B software company is walking through the eight deals that failed to close this quarter. In the CRM, the lost-reason field says the same thing on all eight: “price too high.” Then she opens the call recordings, and the picture falls apart. In three of them the buyer never discussed money at all — they named two different vendors and asked about the integration list. In two, a number came up, but the sentence was “there’s no budget left this quarter.” Only three involved an actual argument about unit price. Eight conversations had been flattened into one dropdown value, and the quarter’s decision was being made from that dropdown: widen the discount authority. The counts are illustrative; the situation is not.

This article is about turning competitor and price mentions from an impression into something you can count. We will work through it in order: why a call that names a competitor is a different kind of call, what different objections hide underneath the word “expensive,” what rule you need before you can count a mention at all, what happens in the first day after a warning badge lights up, how to read the breakdown by competitor and segment, whether a rise in price mentions calls for a price change or a positioning change, how mentions relate to closing and to call scores, what a lost deal’s recording says that the lost-reason field never will, how the findings get shared and on what rhythm, and the most common ways teams misread this data.

Why is a call that names a competitor a different kind of call?

When a buyer names a competitor, two things happen at once. First, the question on the table changes. It is no longer “should I solve this problem” but “which vendor solves it” — the decision frame has shifted from a single seller to a comparison. Second, the agenda leaves your slide order and moves into the comparison grid the buyer is holding in their head. Every question after that moment is an attempt to fill a blank cell in that grid. The questions stop being random and start moving column by column.

In practice, that moment is left entirely to the rep’s instinct. One rep pivots straight into a comparison story, another politely moves past it, a third does not even write it down. What lands in the CRM afterwards is usually a free-text line like “evaluating alternatives” — and free text never rolls up into a report. Pooled together, though, these mentions are the cheapest market data a company owns. No survey, no purchased panel, no analyst subscription: it comes out of conversations you were already having.

It helps to keep this internal signal separate from what you gather externally. Watching a rival’s pricing page, job postings and release notes is its own discipline, and an honest competitive intelligence practice tells you what the competitor is doing. Call recordings tell you what your buyers think about that competitor, which words they use, and which column they are comparing. Those are not the same thing, and most teams only ever do the first one.

What different objections hide underneath the word “expensive”?

Price is the most mislabeled objection in sales. When a buyer says “that’s expensive,” the sentence can carry at least four different meanings, and each one calls for a different move. The first is a budget constraint: the problem is the calendar, not the number, and the money exists in another cycle. The second is comparative pricing: the buyer is holding someone else’s quote and reading yours against it. The third is a value gap: the number is not high in itself, but what it buys was never made clear. The fourth is a negotiating reflex — underneath the sentence there is no objection at all, just a habit.

These four leave different fingerprints on a recording. A budget constraint brings dates into the conversation: fiscal year, approval, next cycle. Comparative pricing brings a feature list or a vendor name; the buyer usually puts two line items side by side. A value gap turns the question from “how much is it” into “why are we doing this at all.” A negotiating reflex shows up at the very end, right after the closing sentence, and comes with no reasoning attached. Anyone reading a handful of transcripts starts separating those four patterns quickly. Anyone filling in a dropdown puts all four in the same bucket.

The third case often originates in the document rather than the conversation. A quote that collapses everything into one line, with scope and term left vague, forces the reader to look only at the total. How the quote itself is built shapes how the number is perceived; the same figure draws far fewer objections when scope is broken out. If your recordings show “what exactly is included?” arriving right after every price mention, the problem is the document, not the price.

What rule do you need before you can count a mention?

If you want a countable signal, you have to write the counting rule first — otherwise everyone counts with their own definition and the totals never reconcile. Start with two separate columns: competitor mentions and price mentions. They often appear together, but they are not the same event, and they say far more when read apart. In Rocketly’s Voice of Customer dashboard that split is built into the record itself: the call detail shows competitor mentions and price mentions as two separate badges, and if a competitor came up at all the badge turns a warning color so it stands out in the record list. The counting rule does not depend on a rep’s note-taking discipline; it comes out of the call.

The second rule is normalizing labels. An analysis engine can tag the same concept with different words in different languages, and if “objection” and its local-language equivalent are counted as two rows, your ranked list splits and the most frequent topic no longer looks the most frequent. AI theme extraction folds those tags into one concept, so even a mixed-language team reads a single list. The table below covers the edge cases that come up most often when a team first writes its rule set.

What the buyer said	Competitor mention	Price mention	Why
“We trialed Vendor A’s dashboard too”	Yes	No	Another provider is on the evaluation list
“There’s no budget left this quarter”	No	Yes	A calendar constraint, but still on the price axis
“Vendor B quoted us lower”	Yes	Yes	Both axes intersect in one sentence
“We used to work with another agency”	Yes	No	A previous provider is also a reference point
“Any room on the number?”	No	Yes	A negotiation opener with no stated reason

What happens in the first day after a warning badge lights up?

A signal is worth exactly as much as the work attached to it. A badge that turns a warning color because a competitor came up is, on its own, a line in a report; if nothing follows it, nobody remembers it by Friday. A workable rule: the owner of that call leaves a two-sentence note the same business day — which competitor was named, and which capability was being compared. It takes thirty seconds, and it is the raw material for everything downstream.

The second step is seeing which column of the comparison you keep losing. If the same rival is named against the same capability for three months, that is not a coaching problem, it is a missing-asset problem. Teams that update their competitive battle cards from mention frequency rather than from hallway opinion cut down fast on the number of times a rep hears a question for the first time in front of a prospect. What goes on the card is decided by what was actually compared last quarter.

The third step is setting a threshold. Not every competitor mention is urgent. But a call that carries a competitor mention and a low score is a different animal. When an analysis carries a red flag or the call score drops below forty, managers get an in-app notification tied to that record. The calls where both conditions overlap are the ones to open the same day, rather than waiting for the weekly review.

How do you read the breakdown by competitor and segment?

A single total is indecisive. “Competitor mentions are up this period” triggers no action at all; “Vendor B is up in mid-market, always on the integration list” suggests one immediately. You need at least three axes: which rival, which segment, which topic. Because you can click a critical-moment type or a needs heading on the dashboard and drop into the paginated record list behind it — and from there into a single analysis detail — moving between those three axes stops being a reporting project. You click the number and the calls underneath it open.

The example breakdown below is constructed to show how one total splits into three different stories; the entries are illustrative.

Segment	Most-named rival	Topic compared	Move it argues for
Small business	Vendor A	Time to first value	Put the onboarding promise in writing in the quote
Mid-market	Vendor B	Integration list	Position the missing connector on the roadmap
Enterprise	Vendor B	Permissions and audit trail	Move the security pack ahead of the demo
Renewal calls	No incumbent named	Depth of usage	Present the value review before renewal comes up

It also pays to check the outside world against this breakdown. When one rival’s name climbs noticeably in your calls, something visible usually changed on their side: a new tier, a new campaign page, a reworded promise. Catching a change on a competitor’s site the day it happens lets you confirm the cause instead of theorizing about it in a Monday meeting.

Does a rise in price mentions call for a price change or a positioning change?

A rise in price mentions triggers one reflex in most companies: widen the discount authority. That is the most expensive way to misread the signal, because a discount lowers your margin and your future negotiating floor in the same motion. The better question is which sub-pattern the rise is coming from. Budget timing calls for payment terms. Comparative pricing calls for changing the columns of the comparison. A value gap calls for work on the quote and the demo. Discounting is only the right answer in the fourth pattern — genuine negotiation — and even there it should buy you something in return.

Packaging belongs in this picture too. The same product sounds expensive over and over when the tiers are drawn badly, because buyers are forced to look at a tier built for someone else. A round of packaging and tiering work resolves part of these objections before they ever reach a call. Once the tiers are clean, the price mentions that remain really are about price, and the measurement starts to mean something.

When you do decide to discount, the record of that decision matters. If it is not written down who can discount, on what grounds and up to what level, every price mention opens a fresh negotiation. Customer-specific price lists and a discount matrix turn a rep’s in-call judgement into a company decision, and the price mentions in your recordings become the feedback loop showing where that matrix is under strain.

How do mentions relate to closing and to call scores?

A competitor mention is not bad news by itself. A buyer running a comparison is an engaged buyer; the prospect who never compares anything is often not really buying. What matters is what the mention does to the rest of the conversation. The period’s average call score sits on its own card on a zero-to-one-hundred scale, and reading the score average of competitor-mention calls against the overall period average tells you whether comparison strengthens your pitch or pushes your reps into defence.

The time axis decides a lot here. Because the daily count of positive and negative calls is drawn as an area chart across the selected period — including days with no recordings — you can see whether a spike is real or the artifact of a thin week. And because you can work with seven-, thirty-, sixty- and ninety-day presets or your own range of up to ninety days, the weeks before and after a campaign or an announcement sit on the same chart.

On the installed base the relationship is even clearer. Competitor mentions rising in the weeks after a price increase is an expected reaction; the question is not whether they rise but how long the rise lasts and which segment it settles in. That is also the practical route to announcing an increase without losing accounts: the recordings from the two weeks after the announcement tell you exactly which sentence of the message was misread.

What does a lost deal’s recording say that the lost-reason field never will?

A lost-reason field is a summary field, and summaries carry the mood of whoever wrote them. When a deal closes out, the rep usually picks the least contentious option on the list — and on most lists, “price” is the least contentious option. That is why so many companies conclude that most of their losses are price losses, and then change a pricing strategy to fix a problem that was never about pricing.

Recordings correct this, because a recording does not interpret. Opening the last two calls of a lost deal and looking at how objections, questions, price moments and closing attempts were sequenced usually rewrites the lost reason within minutes. One pattern comes up constantly: the price objection landed in the first third of the call, the rep immediately started negotiating, and the buyer’s real question — the integration one — never got opened. The recording shows the deal was lost on sequencing, not on price.

There is an upside to the same reading. In the deals you win, the sentences buyers use to separate you from a rival are the best raw material marketing will ever get. A comparison phrased in the customer’s own words beats any bullet you write yourself, and feeding testimonials and case studies directly from those recordings produces something far sturdier than an invented list of benefits.

Who sees the findings, and on what rhythm?

This data does not belong to one team. Sales reads where an objection lands, marketing reads which comparison column is weak, product reads which missing capability is actually costing deals — all from the same recordings. The failure mode is three teams working from three meetings and three interpretations. The practical fix is a twenty-minute shared read once a week: the period’s most-named rival, the most-compared topic, and two calls pulled from the ones whose warning badge lit up.

Keep the mechanics simple. Sentiment split, critical moments, needs headings and the trend all export to a single CSV, and the whole dashboard downloads as a PDF, so preparing for that meeting does not turn into a screenshot exercise. The selected period travels in the address bar, which means whoever opens your link — or hits the back button — lands on the same view. The discussion does not start with “which date range are you looking at?”

On existing accounts this read can attach to a meeting you already run. Checking whether a competitor was named in that account’s calls over the last ninety days changes the agenda of a quarterly business review before you walk in. A renewal conversation with an account where a rival has been named cannot be prepared the same way as one where none ever was.

What are the most common ways teams misread this data?

The first mistake is stripping the number of its context. More competitor mentions is not bad and fewer is not good; when call volume rises, mentions rise with it. Reading a rate is almost always safer than reading an absolute count. The second mistake is generalizing from a handful of calls. Two mentions of the same rival across four calls in a week is a coincidence, not a trend; calling it a trend means widening the period first.

The third mistake is treating unprocessed records as zeros. A call whose score has not been calculated is not a low-scoring call — it shows in the review list without a score and does not drag the period average down. Analyses that are queued or that failed do not enter the dashboard totals at all. A reader who does not know that distinction can mistake an incomplete data set for a drop in satisfaction and raise an alarm about nothing.

The fourth mistake is tying the finding only to new business. When a competitor is named by an existing customer, that may be a churn signal rather than a buying signal; getting those records into the early-warning list of your customer retention work is far more useful than discovering the problem two weeks before the renewal date. The fifth is assuming everyone sees the same picture: the dashboard only aggregates records your permissions cover, and a user limited to their own records will not see other reps’ analyses in this summary either. When two people read different numbers, the cause is usually scope, not a bug.

If you want to see how competitor and price mentions are distributed across your own conversations, you can create a free account and run a first analysis on a single recording.

FAQ

Is being compared to a competitor a bad sign?

Not on its own. A buyer running a comparison is a buyer doing real evaluation. What matters is how often mentions occur, which segment they cluster in, and where those calls’ scores sit against the period average. A pipeline in which no rival is ever named is usually a sign that conversations are not going deep enough, not a sign of dominance.

Does this mean reps stop taking notes?

Note-taking does not disappear; it moves. Because competitor and price mentions come out of the recording itself, the rep’s job is no longer to write down what came up but to write down what happens next. Notes get shorter and become decisions rather than transcripts.

Should I change my pricing based on this?

A pricing decision never rests on one signal. Recordings tell you what kind of objection you are facing; a pricing decision also needs win rates, discount distribution and segment margin next to it. The strongest contribution recordings make is showing how much of what gets labelled a price problem actually is one.

How many calls before I can trust the pattern?

There is no single number — volume, the number of segments and the length of your sales cycle all move it. A practical approach is to wait for the same pattern to repeat across two consecutive periods. Before turning a spike into a decision, check whether the same breakdown still holds in the following period.