Which question should I ask to test a rep’s understanding of the competitor landscape in 2026?

The outcome you should expect

When you replace the generic "who are our top three competitors?" prompt with a recall-and-evidence question, the thing you are measuring changes fundamentally. The first question tests whether a rep sat through onboarding. The second tests whether a rep processes losses, listens in discovery, and carries competitive context into live opportunities. Those are different skills, and only the second one predicts anything about how the rep will behave when a deal turns competitive in month four.

The immediate outcome you should expect from asking the recall question is a sharp bimodal split across your team. Roughly speaking, in most teams you will see three clusters. A small group answers instantly and in detail — they name the account, the competing vendor, the stage the deal was in when the competitor appeared, and they can quote or closely paraphrase what the buyer said. A middle group names accounts and competitors but goes fuzzy on the buyer's actual words, substituting their own interpretation ("they went cheaper," "they liked the incumbent"). A third group cannot get past the vendor names at all and starts describing the competitor's product instead of the deal.

That split is the real deliverable. You are not looking for a score; you are looking for a diagnosis that tells you what coaching each rep needs. The first cluster needs to be mined — their recalled buyer language is the raw material for your battlecards, and they should be running the loss-review sessions rather than sitting in them. The second cluster needs a discovery habit change: they are hearing competitive signals and not writing them down, which means the intelligence dies in their heads at the end of every call. The third cluster needs structural help — a real competitive brief, a joined loss review, and probably a manager sitting in on their next three competitive calls.

The second outcome, which matters more over a quarter, is that asking the question repeatedly changes rep behavior. Reps optimize for what they are asked about. If your one-on-one always includes "what did the buyer say about the alternative," reps start listening for it, start asking about it in discovery, and start logging it. Within a few cycles you get competitive field notes flowing into your CRM as a side effect of the coaching cadence rather than as a compliance chore nobody does. That is the quiet RevOps win here: a coaching question that doubles as a data-collection mechanism.

You should also expect the question to surface gaps in your own enablement rather than just rep weakness. If every rep on the team fumbles the same competitor, that is not five rep problems — that is one content problem. If reps consistently recall buyer objections your battlecard does not address, your battlecard was written by someone reading the competitor's website instead of listening to your own call recordings. Treat a team-wide miss as a signal about the enablement supply chain, not the reps.

Finally, expect the answer quality to depend heavily on how long the rep has been in seat and what segment they sell. A rep six weeks into an SMB territory with two-week cycles may genuinely not have three competitive losses to recall, and grading them against an enterprise rep with an eighteen-month book is a category error. Calibrate the ask to the pipeline the rep actually has — one deal for a new rep, three for a tenured one — but keep the shape of the question identical so answers stay comparable across the team.

What drives that outcome

The reason a recall question works better than a knowledge question comes down to where competitive understanding actually lives. There are three distinct layers, and most testing only touches the shallowest one.

Layer one is vendor awareness. The rep can name the companies they run into. This is table stakes and it is also nearly worthless as a signal, because it is the easiest thing to memorize and the least connected to deal outcomes. Any rep who has read the competitive folder can recite the list. Asking for it tells you almost nothing.

Layer two is positioning fluency. The rep can articulate where each competitor is genuinely stronger and where you are, in language a buyer would recognize. Note the word *genuinely*. A rep who says the competitor has no strengths has not thought about it; they have absorbed marketing. Real fluency includes an honest map of where you lose on the merits — smaller partner ecosystem, thinner reporting, no native integration with a platform the buyer already runs. Reps who can name your real weaknesses tend to handle competitive deals better, because they steer toward ground where those weaknesses do not decide the outcome instead of getting ambushed on ground where they do.

Layer three is deal-level pattern recognition. The rep knows which competitor tends to appear at which stage, what triggers their appearance, and what the buyer typically says right before the deal tilts. This is the layer that changes behavior in live deals, and it is only built by processing losses. It cannot be transferred by a deck. A rep who has this layer will tell you things like "when procurement gets involved before technical validation, the incumbent usually wins on switching cost, so I try to get the technical win locked before the paper goes over."

The recall question reaches layer three because it asks for something only layer three can produce: specific buyer language attached to a specific deal. You cannot bluff a quote you never heard. A rep operating at layer one will substitute a generalization, and the substitution is instantly audible.

There is a second driver worth naming: the incentive structure around loss reporting. In many organizations, closed-lost reasons are a dropdown a rep clicks on their way out of a deal, and "price" is the top option because it is fast and blameless. If your CRM says forty percent of losses are price, you probably do not have a price problem — you have a loss-coding problem. Reps who know their loss reasons will be read back to them in a QBR as evidence of poor execution will code defensively. That directly starves layer three, because the raw material for pattern recognition is honest loss data.

So the question works partly by routing around your own broken data. You are asking the rep directly, in a low-stakes setting, rather than trusting a field they had every reason to fill in carelessly. If you want the question to keep working, make it explicit that the recall exercise is not performance review input. The moment reps suspect it is, the quality of the answers collapses and you are back to reading dropdowns.

Benchmarks and realistic ranges

Rather than inventing precise statistics, here are the practical calibration ranges most revenue teams can sanity-check against their own numbers.

How many competitive deals a rep should be able to recall. Take the rep's closed-lost count over the trailing two quarters and the share of deals where a competitor was present. In most B2B segments a meaningful minority to a majority of losses involve a named alternative — including "do nothing" and "build it internally," which are competitors even though they never appear on a battlecard. If a rep closed twenty opportunities and lost twelve, and none of those twelve involved an identifiable alternative, either the market is uncontested or the rep is not asking. The second is far more likely.

Time to answer. This is a surprisingly clean signal. A rep with layer-three understanding starts talking within about five seconds and does not need to open Salesforce. A rep who needs thirty seconds and a CRM tab is reconstructing rather than recalling. Do not treat the delay as disqualifying — treat it as a marker of whether competitive context is loaded in working memory during live calls, which is the only place it helps.

Named-account specificity. Set the bar at the account name plus the deal stage where the competitor surfaced. "We lost Northwind in late-stage after security review pulled in their existing vendor" is a passing answer. "We lost a few manufacturing deals to the incumbent" is not.

Buyer-language recall. The highest-value component. Ask directly: "What words did they use?" Accept a close paraphrase, but the paraphrase should sound like a buyer, not like a marketer. "They said their ops team had already built reporting on top of the other tool and rebuilding it was three months they didn't have" sounds like a buyer. "They preferred the competitor's superior analytics capabilities" does not.

Honest weakness recall. Ask the rep to name one thing the competitor does better. A rep who cannot is either not credible with buyers or not paying attention. Buyers reward reps who concede real ground and lose trust in reps who claim none.

Reasonable cadence. Monthly in one-on-ones is enough. Quarterly if your cycles are long. Weekly turns it into a ritual reps game rather than a diagnostic.

Segment adjustment. Transactional SMB reps with dozens of deals per quarter will have shallower recall per deal but wider pattern coverage — ask them for the top two competitors by frequency and what the recurring objection is. Enterprise reps with a handful of deals should have near-total recall of each, including who on the buying committee advocated for the alternative and why.

What "good" looks like as a team distribution. If more than half your team lands in the vendor-awareness cluster, the problem is enablement and loss-review process, not hiring. If you have a healthy spread with a clear top cluster, you have a coaching problem you can solve rep by rep. If your top performers are also your best recallers, that correlation is worth surfacing to the team — it makes the coaching land better than any framework will.

One caution on benchmarks: resist the urge to turn this into a numeric score in a spreadsheet. The moment a rep sees a "competitive fluency score" in their file, they will prepare for it, and preparation defeats the entire mechanism. The value of the question is that it catches unrehearsed recall. Keep it conversational.

Risks, edge cases, and failure modes

The rehearsal problem. Once reps know the question is coming, they prepare three stories and deliver them smoothly forever. This is the single biggest threat to the mechanism. Mitigate it by varying the frame each time: ask for the last three *wins* against a competitor instead of losses, or ask about a specific competitor, or ask about a specific quarter, or ask what the buyer said about a competitor in a deal that is still open. Same underlying test, different surface, harder to pre-load.

Using it as a gotcha. If you ask the question in a group setting and let a rep fail publicly, you have taught the whole team to fear the question and to prepare defensively. Ask it privately first. Bring it to the group only when you have a rep whose answer is genuinely instructive and who is comfortable sharing.

Punishing honest losses. Related and more damaging. A rep who says "we lost because their integration with the buyer's existing warehouse was native and ours required middleware" has just given you the most useful sentence in the meeting. If the response is a lecture about handling objections, they will never say anything that specific again. Reward the honest answer visibly, or the mechanism dies within two cycles.

Confusing memory with judgment. Some reps have excellent recall and terrible strategy. They can tell you exactly what the buyer said and still have no idea what to do about it. The question diagnoses knowledge, not skill. Pair it with a second question — "knowing that, what would you do differently in the deal you have open right now with the same competitor?" — to test whether the understanding converts to action.

The new-rep edge case. A rep in their first sixty days has no competitive losses to recall. Do not ask this question of them and conclude anything. Instead ask what they have heard on calls so far and whether any prospect mentioned an alternative. You are establishing the habit early rather than measuring an outcome that cannot exist yet.

The territory edge case. A rep in a greenfield territory with an unpenetrated market may genuinely be competing against "nothing" — the buyer's status quo of spreadsheets and manual process. That is still a competitor landscape and the question still applies, but the answers will sound different: no vendor names, lots of internal-alternative language. Do not mark that as a fail. Ask what the buyer's current process is and why they decided it was good enough.

Stale intelligence. Competitor positioning moves. A rep whose recall is entirely from deals eighteen months old may be confidently wrong about what the competitor does today. Ask when the deal closed. Weight recent recall much more heavily, and treat old recall that contradicts current reality as a coaching moment rather than a credential.

Over-indexing on one competitor. A rep with deep understanding of one rival and none of the others looks strong in a spot check and is fragile in practice. Rotate which competitor you probe, or ask them to rank the competitors by how often they appear and how much they hurt.

The rep who blames product. Some answers will be accurate and uncomfortable: "we lose to them because we don't have the feature." Verify it before dismissing it. If three reps independently report the same gap in the same buyer language, that is product feedback with a sample behind it, and routing it to the roadmap is a better use of the finding than coaching the reps to overcome it.

Manager consistency. If different managers ask the question differently, you cannot compare answers across teams and you will make bad calibration decisions. Write down the exact wording, the follow-ups, and what counts as a passing answer, then have managers use it verbatim. This is a small piece of enablement discipline with an outsized effect on whether the data means anything.

A practical rollout plan

Rolling this out is a four-week exercise, not a memo. The sequence matters because the trust conditions have to exist before the answers are worth anything.

Week one — write the question and the rubric. Fix the exact wording. Write the three follow-ups: who was the competitor, what stage did they appear, what did the buyer say. Write the three-tier answer definition from the section above so every manager grades the same way. Keep it to one page. If it needs more than one page, it will not get used.

Week two — managers ask it privately, and record nothing formal. Every manager runs the question in their next one-on-one. No scores, no CRM field, no spreadsheet. Managers take notes for themselves only. Announce this framing to the team explicitly: this is coaching input, not evaluation. The single most common way this rollout fails is that reps assume otherwise and start managing their answers.

Week three — aggregate the gaps, not the scores. Managers bring their notes to a RevOps or enablement review. Look for the patterns that cross reps: a competitor everyone fumbles, an objection nobody has a good answer to, a buyer phrase that keeps recurring. Those patterns are your content backlog. Ship the two highest-frequency gaps as updated battlecards or a short competitive brief — and write them in the buyer's language you just collected, not in marketing's.

Week four — close the loop visibly. Send the updated material back to the team and say plainly where it came from: "three of you told me buyers keep raising the migration-effort objection, so here is how we're handling it." This is what converts the exercise from an audit into a system. Reps who see their input come back as a tool will feed it next time.

Ongoing — make it a standing item. Add the question to the one-on-one template so it happens without anyone remembering to schedule it. Rotate the frame monthly using the variations listed earlier. Once a quarter, run one deep competitive loss review as a group, using the rep with the strongest recall as the presenter rather than the manager.

A note on tooling. You do not need a new system for this. If you already run conversation intelligence over your calls, you likely have a competitor-mention search that can validate rep recall against what was actually said — a useful cross-check, and a fast way to find the buyer quotes your battlecards should be built from. If you do not have that tooling, a shared doc with a row per competitive loss works fine and costs nothing. The mechanism is the coaching cadence; the tooling only makes the collection cheaper.

The last piece is deciding who owns it. Left to individual managers, the practice decays within a quarter. Assign the ownership to whoever owns enablement or RevOps, give them the aggregation step as a recurring calendar item, and give them a way to route product gaps to the roadmap. The question itself takes ninety seconds to ask. Everything that makes it worth asking happens in the two hours a month someone spends on what the answers add up to.

Related questions

Should I ask this in an interview or only with existing reps?

Both, with different expectations. A candidate cannot know your competitor landscape, so ask them to walk through competitive dynamics at their last company instead. You are testing whether they process losses at all — a habit that transfers — rather than testing product knowledge you have not taught them yet.

What if the rep's recall contradicts our CRM loss reasons?

Trust the recall and fix the CRM. Dropdown loss reasons are filled in quickly and often defensively. If reps consistently describe losses differently than the field says, your closed-lost taxonomy needs rewriting — probably in the buyer language the reps just gave you.

How is this different from a battlecard quiz?

A quiz tests whether the rep read the card. This tests whether competitive context reaches live deals. A rep can score perfectly on a quiz and still never bring competitive positioning into a call. The recall question only rewards knowledge that has already been used.

Can I use the same question for sales engineers or CSMs?

Yes, with a shifted frame. Ask SEs about the last three technical evaluations where an alternative was in play and what the technical buyer said. Ask CSMs about the last three renewals where a competitor was mentioned. The structure holds; the deal moment changes.

What if we genuinely have no direct competitors?

You do — status quo, internal build, and budget going elsewhere. Reframe the question as "the last three deals where the buyer chose not to move, and what they said about why." The diagnostic value is identical.

FAQ

What exactly do I say, word for word?

"Tell me about the last three deals where you were up against someone else. Who was it, what stage were they in when the competitor showed up, and as close as you can remember, what did the buyer actually say about why they were considering them?" Then stop talking and let the silence work.

How long should the whole exercise take in a one-on-one?

Five to ten minutes for the ask and follow-ups. The temptation is to turn it into a coaching session on the spot, but that changes what you are measuring. Take the answer, note the gap, and schedule the coaching separately so the next time you ask, you are still getting unrehearsed recall.

Is it fair to ask about losses when reps are already sensitive about them?

It is fair if you have established that loss discussion is not performance review input, and unfair if you have not. If your culture currently punishes lost deals, fix that first or ask about competitive *wins* instead — the recall test works nearly as well and carries none of the defensiveness.

What if the rep gives a great answer but I know the deal was lost for a different reason?

That is a valuable finding in itself. It means the rep has a confident but incorrect model of why they lose, which will misdirect their behavior in every similar deal. Walk the deal back together with whatever evidence exists — call recordings, the buyer's own emails — rather than simply correcting them.

Should the answers go into a shared system?

The aggregated patterns should; the individual answers should not. Publishing rep-level responses converts a coaching tool into a scoreboard and destroys the candor that makes it work. Keep the notes with the manager and share only the cross-rep themes.

How do I know the question is working?

Watch for competitive detail showing up unprompted — in deal reviews, in forecast calls, in the notes reps write after discovery. If reps start volunteering what the buyer said about the alternative without being asked, the habit has taken hold and the question has done its job.

Sources

• Gartner — Sales Insights and Research
• Harvard Business Review — Sales and Marketing
• McKinsey — Growth, Marketing and Sales Insights
• Gong Labs — Sales Research
• Salesforce — Sales Blog
• HubSpot — Sales Blog
• SaaStr
• Winning by Design — Resources
• MIT Sloan Management Review — Strategy

Related on PULSE

• [What specific question can you ask a new sales rep in their first week to assess their understanding of your product's top three differentiators?](/knowledge/q14388)
• [Top 10 questions to gauge a rep's understanding of buyer personas](/knowledge/q14401)
• [What question would you ask to test if a salesperson truly understands their buyer's industry trends and challenges?](/knowledge/q14422)
• [How do I run a win/loss review that reps actually tell the truth in?](/knowledge/q14430)
• [What should a competitive battlecard contain to be useful on a live call?](/knowledge/q14435)