Trap Questions
Updated July 21, 2026
Strategic questions sellers suggest prospects ask competitors to expose product shortcomings or limitations.
Also known as: Landmine questions, Landmines, Trap-setting questions, Competitive trap questions
Trap questions are questions a seller coaches a prospect to ask a competitor during an active evaluation, phrased so the competitor cannot answer them well and a real product gap becomes self-evident. The tactic lives in the competitive section of a sales battlecard. Instead of the rep asserting that a rival is weak in some area, the prospect raises the question directly, hears an evasive or unconvincing answer, and reaches the negative conclusion on their own. Practitioners favor this indirection for a simple reason: a weakness the buyer discovers persuades more than one the seller declares, which can sound like fear of the competition.
The label is not owned by any single vendor or framework. Trap questions and their near-identical synonym landmine questions appear independently across sales-enablement and competitive-intelligence writing from Klue, Gong, Force Management, and others, with no source claiming to have coined the practice. It reads as organically developed practitioner jargon rather than a named methodology with a fixed origin. Usage is inconsistent enough that landmine is often the more common word for the exact same move, and trap-setting question sometimes refers to a broader discovery technique.
Today the tactic is written and maintained by whoever owns competitive enablement, whether a product marketing or competitive-intelligence function feeding sellers, or the reps themselves. Common guidance is to keep two or three well-researched trap questions per named competitor, often split by buyer persona, since an executive and a hands-on practitioner respond to different gaps. The questions are only credible when they target a genuine, defensible weakness, which is why they sit downstream of real competitor research.
How a trap question is built and deployed
A trap question starts from a documented weakness in a specific competitor: a missing feature, a hard architectural limit, a common support complaint, a hidden cost, or a capability that only works under narrow conditions. The seller reverse-engineers that weakness into a plain, reasonable-sounding question the prospect can ask the rival, worded so an honest answer exposes the gap and a dodge looks like a dodge.
Timing matters. Most sources place trap questions later in the sales cycle, once a named competitor is actively in the deal, rather than at first contact. The rep hands the prospect two or three questions to raise in their next competitor conversation, then follows up afterward to hear how the competitor responded. That follow-up is part of the tactic, not an afterthought: the competitor's answer either confirms the gap or reveals that the intelligence is stale.
Good practice keeps the set small and persona-specific. An economic buyer and an end user care about different failure modes, so the executive gets questions about total cost, security posture, or roadmap risk, while the practitioner gets questions about workflow limits or integration coverage.
Trap questions vs. quick dismiss and objection handling
Trap questions are easy to confuse with two neighboring battlecard tactics, but they operate at different points and in different directions. Quick dismiss is an earlier-stage move meant to knock a competitor out of consideration before it gains a foothold, often a short, memorable reason not to bother evaluating them. Trap questions assume the competitor is already a live threat in the deal and work to undermine confidence from the inside.
Competitive objection handling is reactive: it supplies rebuttals for what a prospect already believes or has been told by a rival. Trap questions are proactive, seller-initiated, and aimed at the competitor rather than back at the buyer. The rep is not answering a claim; the rep is planting a question that produces a new, unfavorable data point about the competitor.
They also differ from generic discovery questions. Discovery is broad and needs-oriented and is not tied to any named rival. A trap question is a competitively targeted subset, written against one competitor's specific known weakness, which is what makes it sharp and also what makes it go out of date.
Why the label is inconsistent across the industry
There is no canonical name for this tactic, so writers should expect the vocabulary to shift between sources. Landmine question is the most common industry term for the exact same move and is used interchangeably with trap question by Klue, Gong, and others. Landmines is the shorthand.
Trap-setting question is where the confusion concentrates. Force Management uses it for a related but distinct discovery technique, meaning open-ended questions steered toward the seller's own differentiators, asked early and not framed as go ask the competitor this. Other vendors use trap-setting question as a straight synonym for the coach-the-buyer tactic described here. Because the same phrase points at two different techniques depending on who is writing, it is worth stating which one is meant rather than assuming the label carries a fixed definition. Competition-analysis frameworks such as MEDDPICC also fold the idea into their treatment of the competition element, again under varying names.
Where competitive intelligence feeds trap questions
A trap question is only as good as the weakness it targets, which puts the tactic squarely downstream of competitive-intelligence work. The raw material is documented evidence of a rival's gaps: negative reviews, feature comparisons, pricing and packaging changes, service complaints, and known limitations surfaced through research. Enablement translates that evidence into ready-to-ask questions and places them on the battlecard.
The tactic also feeds intelligence back upstream. When a rep reports how a competitor answered a trap question in a real deal, that field intel confirms, refines, or retires the question and can update the broader competitor profile. This is where continuous competitor tracking connects directly. A competitor-monitoring workflow of the kind meertrack supports, watching competitor websites, pricing pages, product changes, and job postings, surfaces the shifts that make old trap questions obsolete and new ones possible. A newly shipped feature can neutralize a question overnight; a quietly removed capability or a fresh wave of negative signal can seed the next one.
Stop looking terms up. Start tracking them.
meertrack watches your competitors' websites, pricing, and hiring, then alerts you when something meaningful changes.
Frequently Asked Questions
What are trap questions in sales?
They are questions a seller coaches a prospect into asking a competitor during an evaluation, worded so the competitor struggles to answer and a product gap becomes obvious. The point is indirection: rather than the rep claiming a rival is weak, the buyer surfaces the weakness themselves by hearing an evasive answer, which tends to land as more credible than a claim coming straight from the salesperson.
What is the difference between trap questions and landmine questions?
For most sources they are the same tactic under two names, with landmine being the more common industry term. Both mean questions a seller plants with a prospect to expose a competitor's weakness. The vocabulary is inconsistent: some vendors also say trap-setting question, which occasionally refers instead to a broader early discovery technique steered toward your own strengths, so it helps to confirm which is meant.
How many trap questions should a battlecard have?
Common guidance is two or three well-researched questions per named competitor, not a long list. Keeping the set small forces each question to target a genuine, defensible weakness rather than diluting the rep's credibility. Many teams organize them by buyer persona, since an executive worried about cost or risk and a practitioner worried about workflow limits need different questions to ask.
When should you deploy a trap question in the sales cycle?
Usually later, once a specific competitor is actively in the deal and the prospect is evaluating both options. That timing distinguishes trap questions from a quick dismiss, which aims to remove a competitor from consideration before it gains traction. The rep hands the prospect a question to raise in their next competitor conversation, then follows up to learn how the competitor answered.
Who writes trap questions?
Whoever owns competitive enablement, typically a product marketing or competitive-intelligence function, and sometimes experienced reps. The work depends on prior research into a competitor's documented gaps, such as missing features, negative reviews, or service complaints. Because that research goes stale as competitors ship changes, the questions need periodic review, and field reports on how rivals responded feed back into updating them.
Related terms
A concise sales-facing document summarizing a specific competitor's strengths, weaknesses, pricing, common objections, and recommended counter-positioning. The primary CI deliverable for sales teams.
Quick DismissA 1-2 sentence talk track allowing sellers to rapidly articulate differentiation against a named competitor.
Competitive Objection HandlingPre-built responses addressing common buyer concerns about competitive alternatives.
Competitive SellingA sales approach that proactively addresses the competitive landscape during deals.
Product GapsShortcomings or missing features in competitors' offerings that drive customer dissatisfaction and switching.
Competitor ProfileA comprehensive dossier on a single competitor covering strategy, financials, products, leadership, culture, strengths, weaknesses, and likely future moves.
Talk TrackA 15-30 second scripted response for sales reps when competitors come up during calls.
Universal Battlecard FrameworkA single competitive card per competitor covering win reasons, objection handling, and landmines. Built for lean teams.