A prospect asks: "How many days a week are you open?"
You answer "seven." They wanted four. Sale dies.
You answer "five." They wanted seven. Sale dies.
You answer "we're open as much as you need." They wanted a number. Sale stalls.
The problem is that the moment you give a blind answer — any blind answer — you've rolled dice on whether your answer matches what they wanted. You never wanted to be in the position of answering. You wanted them to tell you what they were looking for first, and then frame your answer to fit.1
Hormozi's rule: never answer a question you don't already know the answer to. The way you find out is to ask a question about their question. "What days were you looking for?" or "What's the reason behind that question?" Their answer tells you which version of the truth to deploy. Now your answer lands.
This is the lawyer rule: lawyers cross-examining a witness never ask a question they don't already know the answer to. Same discipline applies in sales. You never give an answer you don't already know is the right one.2
Details-are-death-traps is a discipline rule for the E section. It says: when a prospect asks a specific factual or technical question (price, hours, features, integrations, certifications, timeline), the closer's first move is not to answer — it's to ask a question about their question.
The standard reformulations:
Once they answer, you have two options:
The discipline is consistent across both videos: never let the prospect pull you into a detail-comparison where they get to evaluate your answers against their criteria. Always understand the criteria first, then answer.
Three mechanisms operate when a closer slips into detail-answering:
You don't get to pick whether your answer is right. The prospect has criteria you don't know. Your answer is judged against those criteria. If you don't know the criteria, you're guessing — and guessing is a coin flip.3
You shift authority to the prospect. When they ask questions and you answer, they are running the conversation. The questioner controls the frame (Questions Not Statements). Detail-answering is statement-mode; it cedes control.
A detail objection is actually a preference objection. When a prospect drills into a detail, they're usually expressing "I want your outcome but I want it my way." The detail is the surface; the preference is the substance. Answering the detail doesn't resolve the preference; chunking up does.4
The mechanic close and the secretary close are escape hatches when the prospect insists on a detail answer you can't safely give: "I can't ethically answer that without bringing your car into the shop first" / "It would be like asking a heart surgeon's secretary about your heart condition before you've actually seen the surgeon." Both moves appeal to the authority of the business while declining to commit to a specific answer.5
Details-are-death-traps is one of the most direct deployments of Questions Not Statements. It's also the practical defense for Sell-the-Vacation — when a prospect tries to pull you into plane-flight talk by asking about specific features, the question-about-the-question move keeps you in vacation talk.
The discipline also enables Value Overcome — Resourceful Not Resources — when a prospect drills into price-detail, the chunk-up move surfaces the value comparison they're actually making.
A prospect at a personal-training consult asks: "What certifications do your trainers have?"
Detail-answer (kills sales): "We have CPT certifications, CES certifications, some have CSCS, the head trainer has a Master's in kinesiology..." — now the prospect can compare your specific list against their preferred specific list. If their gym down the street has more impressive credentials, you lose. If your list is impressive but lacks the specific cert they were looking for, you lose.
Question-about-the-question close:
The closer never named a specific certification. The closer chunked up from "certifications" to the reason behind the question ("safety") and addressed the underlying concern with a concrete proof point (no injuries in two years). The detail evaporated because the underlying preference got addressed.
The case is load-bearing because it shows that the chunk-up move isn't evasion — it's addressing the prospect's actual concern more directly than the literal answer would have. The prospect didn't really want a list of certifications; they wanted reassurance about safety. The closer's job was to surface what they actually wanted and respond to that.
Minute 18 of the call. Prospect asks a detail question: "What's your platform's uptime guarantee?"
You take a breath. You don't answer.
You ask: "What kind of uptime are you used to working with right now?"
They answer: "Our current vendor is at 99.5%, but we've had three outages this year that cost us money."
Now you know:
You answer: "Got it. So the real concern is making sure you don't have those outage incidents again. We're at 99.95%, but more importantly, our SLA includes financial compensation if we drop below that — which means we have direct skin in the game on your uptime. Does that sound like the kind of vendor commitment that would solve the outage-cost problem?"
You shut up. They affirm or refine. You move on.
The question-about-the-question converted a detail trap into a value comparison the closer could win. The specific number (99.95% vs the prospect's previous 99.5%) is now in context: it's not just "higher number" — it's "higher number plus financial commitment that aligns interests."
The doctrine is empirically defensible — every consultative-selling tradition (SPIN, Sandler, Challenger) emphasizes question-asking during discovery and concern-resolution. The specific lawyer-on-the-stand framing is rhetorical (lawyers don't strictly never ask unknown questions; they minimize unknown answers in high-stakes cross-examination).
The unresolved tension is between this discipline and the prospect's legitimate need for technical information. Enterprise software buyers genuinely need to know about integrations, compliance certifications, deployment models. Pure question-about-the-question can read as evasion when the prospect has a list of technical fit criteria they need to check off.
The resolution Hormozi offers (escape hatches like the mechanic close) is partial. For complex B2B, the more honest move is often: "Let me get our technical team on a call with your engineers — that's the right venue for the technical fit-check. For this call, I want to understand your business goals so I know whether the technical fit-check is even worth scheduling." This redirects without evading.
The open question Hormozi doesn't fully address: when should a closer give a direct answer? The implicit answer is "when you already know the answer is the right one for the prospect's criteria." But this requires either pre-call research or a question-about-the-question first. Pure direct answering is justified only when the closer is in a position to know with high confidence that the answer lands. Most early-call detail questions don't meet that bar.
Details-are-death-traps and Hughes's Behavioral Table of Elements (BOM) Lens 3 (Compliance) operate on the same principle: when a counterparty is pulling you into a specific commitment, redirect to surface the underlying interest before committing. Hughes frames this as "reveal the want behind the ask"; Hormozi frames it as "chunk up from detail to reason."
The convergence is striking — two completely unrelated lineages (one from behavioral intelligence, one from gym sales) have surfaced the same principle: a specific request usually masks a more general interest, and addressing the general interest is more effective than addressing the specific request.
Where Hormozi diverges from consultative-selling traditions: he gives explicit escape-hatch moves (mechanic close, secretary close) that consultative traditions rarely name explicitly. Those traditions assume the closer can handle technical questions through expertise; Hormozi assumes the closer often can't and provides verbal off-ramps that preserve authority while declining to commit.
The doctrine operates across any domain where a practitioner faces requests for specific commitments that mask underlying interests.
Behavioral Mechanics: Six-Minute X-Ray Elicitation Suite (Hughes) — Hughes's needs-cluster work identifies the gap between what subjects ask for (surface request) and what they actually need (underlying motivation). The question-about-the-question move is the elicitation technique for surfacing the gap. The structural parallel: both architectures recognize that specific requests are surface phenomena and that operators who address the surface miss the underlying interest. The insight: details-are-death-traps is the sales-specific deployment of a universal interview principle — when you address what they're literally asking, you miss what they're actually after.
Psychology: Inner Child Child Psychology Hub — therapeutic clarifying questions ("What about that is most painful for you?" / "When you say X, what do you mean specifically?") operate on the same chunk-up mechanism. A client's specific complaint usually masks a deeper concern; the therapist's job is to chunk up from surface to substance without dismissing the surface. The structural parallel: both practitioners (closer and therapist) face surface-level statements that don't reveal the actual concern. Both use clarifying questions to surface the substance. The insight: details-are-death-traps is the commercial deployment of therapeutic chunk-up technique. Different goal (close sale vs facilitate insight), same mechanism.
Eastern Spirituality: Sadhana Practice Hub specifically the guru-disciple inquiry tradition — when a disciple asks a specific doctrinal question, advanced gurus often respond with a question that surfaces what the disciple actually needs to learn (which is rarely what they asked). The structural parallel: both teachers (guru and closer) recognize that surface questions don't reveal the actual learning need. Both redirect through inquiry. The insight: the chunk-up move is one of the oldest pedagogical techniques in human teaching — disciples and prospects alike ask the wrong questions, and the master practitioner's job is to surface the right ones.
The Sharpest Implication
If details-are-death-traps is correct, then most product-marketing copy is structured to defeat itself. Most product copy answers detail questions: "How many features?" "What integrations?" "What's the SLA?" The doctrine says these answers should never be given without first knowing the reader's criteria. But product copy can't ask back. So product copy that pre-emptively answers detail questions is creating loss-surfaces (every answer is a comparison point against the reader's unknown criteria). Better copy answers questions about underlying interests rather than surface details. This is a structural challenge for product-marketing teams that most never solve. The companies that solve it look more like consultants in their copy than like product vendors.
Generative Questions