What is a trap-setting question? A practical definition

Glossary · sales · 4 min read · last verified 2026-07-21

What a trap-setting question is

A trap-setting question is a discovery or qualification question designed so that any answer the prospect gives is informative — it either confirms a real, specific pain, or it exposes that a claimed pain isn't actually being addressed as described. Unlike an open-ended discovery question, which invites a broad answer you then have to interpret, a trap-setting question is built around a specific, checkable claim.

The name describes the mechanism, not the intent — it isn't about tricking anyone. It's about designing a question narrow enough that a vague or evasive answer is itself the useful signal.

One caveat on the term before going further: it is not standardized, and a competing usage is at least as established. In competitive-selling literature, a "trap-setting question" — frequently called a landmine question — usually means something else entirely: a question that plants a requirement into the buyer's evaluation criteria which the incumbent or a named competitor cannot satisfy. That is a competitive-positioning move aimed at shaping the shortlist, not a verification move aimed at testing a pain. This article uses the other sense throughout: a discovery question built so that any answer is informative about whether a stated pain is real. Both senses are in circulation, and neither has a canonical owner, so when you use the phrase with a colleague it's worth saying which one you mean.

The mechanism, with a labeled example

Example (illustrative, not a script to copy verbatim): a prospect claims their current process for handling a specific workflow — say, contract redlines — is "working fine." An open question ("how's that going?") invites a vague, reassuring answer. A trap-setting version asks something specific and checkable: "Walk me through the last redline that took more than a week to close — what happened at each step?"

If the process is genuinely working, the prospect can answer specifically and quickly, because there's a recent, minor example. If it isn't, one of two things happens: they can't produce a specific recent example (revealing the "working fine" claim was general reassurance, not a checked fact), or they produce an example that contradicts "working fine" once they walk through it out loud. Either outcome gives you more real information than the original claim did.

Why the specificity is the whole mechanism

A trap-setting question only works because it's concrete. "Are you happy with your current vendor?" is easy to answer with a reflexive "sure" regardless of the truth. "What's the last thing you had to work around because your current vendor couldn't do it?" requires either a specific recent memory or an admission that nothing comes to mind — and both of those are more useful than "sure."

This only works as a genuine qualification tool if you're prepared to accept and act on either answer. If the prospect gives a solid, specific answer that shows the process is actually fine, that's real disqualifying information about the pain you assumed existed — not something to argue past.

Where it's used

• Testing a stated pain point before building a proposal around it — confirming the pain is real and specific, not a polite answer to "what are your biggest challenges."
• Competitive displacement discovery — asking about a specific recent failure mode of the incumbent tool, rather than a general satisfaction question the prospect can answer diplomatically.
• Surfacing an anti-sponsor's real motive — see what is an anti-sponsor — a specific question about what changes for that stakeholder personally if the deal goes through often reveals more than a general "any concerns?"

How it differs from a leading question

A leading question smuggles the answer you want into the question itself ("you'd agree faster turnaround would help, right?") and mostly produces agreement, useful or not. A trap-setting question doesn't smuggle in an answer — it's neutral on the outcome and specific on the details, which is what makes a vague or contradictory response diagnostic rather than just unhelpful.

Two more examples

A naming note, to be explicit about provenance: the term "trap-setting question" is not part of MEDDIC, BANT, or Challenger, and none of those frameworks coined the term or owns it. "-adjacent" below means only that the example maps onto an element those frameworks already name — budget authority in the MEDDIC case, timing in the BANT case — not that the framework is the source of the technique.

MEDDIC-adjacent example (see what is meddic): instead of asking "is there budget for this?" — which invites an optimistic yes regardless of reality — ask "which specific budget line would this come from, and who approved spend from it last quarter?" A prospect who can answer immediately has actually checked; one who can't is describing hoped-for budget, not confirmed budget.

BANT-adjacent example (see what is bant): instead of "is this a priority for you?" ask "what were you doing about this problem before we started talking, and what changed to make it worth revisiting now?" A specific trigger event is a much stronger timeline signal than a general statement of interest.

What to do with the answer

• A confident, specific answer that holds up under a follow-up "walk me through that" is a real signal — treat the pain (or its absence) as established.
• A vague or generalized answer to a specific question is itself information — it usually means the stated pain hasn't actually been tested against a real recent event, and needs more discovery, not a proposal built on top of it.
• Use it once per topic, not as an interrogation style — the value comes from the specificity of a well-chosen question, not from stacking pressure with a string of them.