The post-trust era prospect doesn't want to commit to anything that feels final. Standard sales questions ("when would you like to start?") imply commitment and trigger the defensive schema. The pretend question architecture solves this by framing every commitment-tier question as hypothetical: "If you were to go ahead with this, when would you do that?"1 The construction is engineered to be easy to answer because answering doesn't commit the prospect to anything — they're just imagining.
The book anchors the architecture to Mr. Rogers: "Pretending doesn't require expensive toys."2 Small reframe; large operational consequence.
Three rules govern the construction3:
Rule 1: Use Conditional Language. The decision has to be conditional. The opening structure: "If you were to go ahead with..." Then the question follows: "...when would you do that?" / "...where would you...?" / "...what kind would you...?" / "...how many would you...?"
The pattern: hypothetical lead-in + specific decision-question. The hypothetical lead-in removes commitment-pressure. The specific decision-question elicits useful information for the operator. The prospect can answer freely because the answer doesn't bind them to anything.
Rule 2: Remove the Salesperson. No "I" or "my" in the construction. Operator-centric language reads as self-absorbed; neutral language reads as collaborative.
Wrong: "If I could get you to agree that my investment opportunity is a good idea..." / "When could I get you to sign the contract?"
Right: "If there was a way that we could help you get a much higher rate of return than what you currently have, is that something you might be looking for?"
The "I/my" removal is small structurally and large in effect. The prospect's defensive schema is calibrated against operator-self-references; removing them fails to activate.
Rule 3: Remove the Company and Product Name. Don't name your specific offering in the pretend question. Specific product-naming implies the operator has assumed the prospect will buy that product; the assumption activates the schema.
Wrong: "If you go with our XYZ Internet Service Program..."
Right: "If you were to start a new internet service program..."
The product-name removal keeps the question generic enough that the prospect can engage with the hypothetical without committing to the operator's specific solution.
The mechanism: the prospect's defensive schema is calibrated to detect commitment-pressure. Standard sales questions ("when can we start?") embed a commitment-assumption that the schema flags as pressure. The defensive frame activates and the prospect's response compresses to defensive minimums.
Pretend-question construction removes the commitment-assumption. The hypothetical lead-in ("if you were to...") signals to the schema that no commitment is being requested. The schema doesn't activate. The prospect's response can be honest and elaborated rather than defensive and compressed.
The information the operator gets is therefore higher-quality. The prospect's hypothetical answer ("if I were to go ahead, probably in Q3") gives the operator more usable information than the defensive answer ("we'd need to discuss it internally first") that a standard question would have produced.
The page is the operational engine inside Solution Awareness Stage 4 and the closing-question architecture in Cluster I. Pretend questions sit at multiple points in the methodology — wherever decision-content needs to be surfaced without triggering commitment-pressure.
Pairs with Hard Words vs Soft Words (the broader soft-language discipline), Possibly Tactical Tension Diffuser (the single-word version), and Schema Activation (the cognitive substrate).
3:14pm on a Thursday call with a SaaS prospect. The operator needs to know when the prospect would implement if they bought.
Standard frame: "When would you want to start implementation?" The prospect's brain processes the question as commitment-assumption. Response: "We'd have to evaluate internally first, get budget approval, talk to legal..." The defensive cascade. The operator gets nothing useful.
Pretend frame: "If you were to go ahead with this, when would you actually want to start? I'm not trying to commit you to anything, just trying to understand your timeline if it made sense." The prospect's brain processes the question as hypothetical. Response: "Honestly, probably late Q2 — we have a project ending May 15 that would free up the team to focus on it, and we'd want about three weeks of setup time before the busy season." The operator has a specific timeline, specific dependencies, and specific decision-context. All from one reframed question.
Same decision-information requested. Different cognitive frame. Different quality of response.
Saturday afternoon. You sit with your notebook and a list of every commitment-tier question you typically ask on sales calls. The list is probably 10-15 items: when would you start, who would be involved, what budget would you allocate, how many users, when would you renew, who would champion this internally.
For each question, you reconstruct it as a pretend-question using all three rules. "If you were to go ahead with something like this, when would you start?" / "If this were to happen, who would be involved on your end?" / "If a solution like this fit, what would you typically allocate to it?"
You read each new construction out loud. Your tongue resists slightly — the standard cadence is trained-default. You practice each construction five times until it sounds natural.
Monday morning. Your first call. You hit the moment where you'd typically ask "when would you start?" Instead you ask "if you were to go ahead, when would you start?" The five-word addition feels small to you. The prospect's response is dramatically different. They give you specific dates, specific context, specific dependencies. The hypothetical frame produced material the standard question wouldn't have.
By Friday, the pretend-question construction is your default. Your call notes have changed shape — you now have specific timeline-information on most calls, where before you had defensive-minimum-answers.
The architecture is practitioner-derived. The cognitive-mechanism (hypothetical framing reduces reactance) has empirical support in the broader psycholinguistic literature; the specific three-rule sales construction hasn't been A/B tested.
A tension: hypothetical framing can read as wishy-washy in contexts where the prospect expects direct language (some C-suite buyers, some technical contexts). The construction has to be calibrated to the buyer-register; the book treats it as universal.
Unambiguously Miner's coinage (the three-rule structure, the Mr. Rogers anchor). Acuff's contribution is more about the underlying detachment-stance that makes pretend-questions honest rather than manipulative.
Cross-source with Hormozi: Hypothetical Perfect Program Close is the parallel construction. Hormozi uses hypothetical framing for objection-surfacing ("if this were perfect, would you do it?"); Acuff/Miner use it for decision-extraction across the call. The two methodologies converge on hypothetical framing as a load-bearing tool.
The plain-sentence version: hypothetical framing recurs across influence professions as a tool for surfacing real preferences without triggering defensive responses.
Psychology — MI Evocative Questions: clinical MI uses hypothetical framing extensively to elicit change talk without triggering client defensiveness. "If you were to make a change, what would it look like?" — structurally identical to NEPQ's pretend-question. The clinical literature has decades of validation; sales is the applied form.
Behavioral Mechanics — Conditional Elicitation and Reactance Bypass: the influence literature treats conditional framing as a reactance-bypass mechanism. The three-rule structure operationalizes the principle for sales contexts.
Creative Practice — Screenwriter "What If" Construction: screenwriters use hypothetical framing as a story-generation tool — "what if a character did X?" surfaces story possibilities that wouldn't otherwise emerge. The same mechanism in a different domain.
Sharpest Implication. The pretend-question architecture is the methodology's solution to a problem most sales training doesn't recognize: that decision-tier questions trigger the schema regardless of the rest of the call's discipline. Without pretend-framing, even well-executed NEPQ calls collapse at the decision-tier moments. With it, the methodology runs cleanly from connecting through commitment.
Generative Questions.