After the operator has surfaced and started to address one concern, there's a structural question — are there others lurking that haven't been articulated yet? Most operators don't ask, which means they only solve the surfaced concern while the unsurfaced ones kill the deal anyway. The book's suppose-question architecture is a three-line construction engineered to surface all remaining concerns before the operator attempts to resolve any of them.1
The full construction2:
"Let's suppose we were able to resolve that issue with you. I know it's not resolved right now, but let's just pretend we could. Are there any other issues you might have that you would want to see resolved?"
Three lines, each doing specific work:
Line 1 — The Hypothetical Frame + "With You" Linguistic Partnership. "Let's suppose we were able to resolve that issue with you." The hypothetical frame ("let's suppose") removes commitment-pressure. The "with you" rather than "for you" signals collaborative resolution rather than operator-fixing-prospect-problem. Both small constructions, both load-bearing.
Line 2 — The Acknowledgment. "I know it's not resolved right now, but let's just pretend we could." The acknowledgment serves two purposes: it confirms the operator hasn't forgotten the original concern (the prospect doesn't have to worry the operator is dodging it), and it explicitly invites the imaginative move (let's pretend) that lets the prospect engage with the hypothetical without committing.
Line 3 — The Other-Concerns Surface. "Are there any other issues you might have that you would want to see resolved?" The question separates the first concern from any others. If the operator skips this question, they end up resolving the first concern and discovering the second one at the close moment — too late to address effectively.
The construction's specific word-choice "with you" (rather than "for you") is the book's deliberate phrasing3. "With you" frames the resolution as collaborative — both parties working on it. "For you" frames it as operator-action-on-prospect. The collaborative framing produces engagement; the operator-action framing produces passivity.
The book's commentary: "It's a team effort; hence the wording 'with you' and not 'for you.' Here, both you and your customer are coming up with solutions to resolve their concern together."
The two-word difference signals operator-stance to the prospect's brain. Operators who say "for you" position themselves as authorities providing solutions; operators who say "with you" position themselves as collaborators working alongside. The trusted-authority position is built through the collaborative framing, not through the authority-framing.
The mechanism exploits two distinct cognitive features:
Feature 1: Hypothetical framing reduces commitment-pressure. Same as the pretend-question architecture (Pretend Question Architecture) — when the prospect is asked to imagine rather than commit, they can engage with the content honestly.
Feature 2: Acknowledging the first concern frees attention for additional ones. The prospect's working memory was holding the first concern in focus. Until the operator acknowledges that the first concern is on track to be addressed, the prospect can't easily think about other concerns. The acknowledgment frees the cognitive space; the question then directs attention to any remaining issues.
The combination produces complete-concerns surfacing — the operator now has a full picture of what's blocking the deal before attempting any resolution. The full picture is structurally what makes resolution possible; partial pictures produce partial resolutions that the unaddressed concerns later kill.
The page sits inside the broader objection-handling apparatus of Cluster G. Pairs with Pretend Question Architecture (the related hypothetical-framing discipline), Concerns Not Objections Reframe (the framing-shift the construction operates within), and Clarifying Questions (the deeper-probe mechanism for the surfaced additional concerns).
A B2B operator is on a presentation call. The prospect has raised one concern: implementation timeline conflicts with their current quarter's commitments. The operator has acknowledged the concern and started working through how implementation could accommodate the timing.
Old-model operator: continues working the timing concern, eventually finds a solution that works, asks for the close. The prospect says "well, there's also the question of integration with our existing platform" — concern #2 surfaces at the close moment. The operator has to back out of the close-attempt to address the new concern. The momentum is lost; the deal stalls.
Suppose-question operator: before resolving the timing concern, deploys the construction. "Let's suppose we were able to resolve that timing issue with you. I know it's not resolved right now, but let's just pretend we could. Are there any other issues you might have that you would want to see resolved?" The prospect surfaces concerns #2 (integration) and #3 (training requirements) that they were holding back. The operator now has the complete map.
The operator resolves all three concerns sequentially. The close-attempt then lands cleanly because every concern has been surfaced and addressed. No backing out, no momentum loss.
The case shows the construction's leverage. Two minutes of suppose-question architecture prevented thirty minutes of fragmented objection-handling.
Saturday afternoon. You sit with your notebook. You write out the three-line suppose-question construction in your own voice — keeping the "with you" / "let's just pretend" / "are there any other issues" structure but adjusting the phrasing to sound natural for your industry and your verbal register.
You read it aloud three times. The construction feels slightly awkward at first because it's longer than the constructions you're used to. By the fourth reading it starts to feel natural.
Monday morning. Your first concern-handling moment. After the prospect articulates their concern, you pause. Instead of immediately working to resolve it, you deploy the construction. "Let's suppose we were able to resolve that with you. I know it's not resolved right now, but let's just pretend we could. Are there any other issues you might have that you would want to see resolved?"
The prospect pauses. You can hear the thinking. Then: "Well... yeah, actually, there's also the question of [second concern]." The construction just surfaced a concern that would have hit you at the close moment.
You repeat: "And anything else?" The prospect surfaces a third concern. You now have all three. You can address them in sequence with full context. The close-moment, when it comes, has nothing left to surface.
The construction is practitioner-derived. The cognitive-mechanism (hypothetical framing + acknowledgment + other-concerns surfacing) has support in the broader clinical-interview literature but the specific three-line architecture hasn't been A/B tested.
A tension: in transactional contexts with short calls, the construction can feel disproportionately long. The book treats it as universal; in practice the construction shines in complex sales with multiple potential concerns and feels heavy in single-concern transactional contexts.
Joint Acuff/Miner; the construction reads more Miner (specific tactical wording, behavioral-science grounding).
Cross-source with Hormozi: less explicit treatment of multi-concern surfacing. Hormozi's framework tends to assume one-concern-at-a-time handling within the broader ask-again loop architecture. The two methodologies optimize for different sales contexts (NEPQ for complex-multi-concern, CLOSER for transactional-single-concern).
Psychology — Agenda-Setting and Comprehensive Disclosure: clinical-interview literature treats agenda-setting at the start of a session as the equivalent move — surface all concerns the patient has before working any of them. The structural identity is precise. The clinical version has decades of training material; sales is the applied form.
Behavioral Mechanics — Elicitation Comprehensive Mapping: intelligence-elicitation tradition uses hypothetical framing to surface complete pictures rather than partial ones. Same mechanism, different ends.
Creative Practice — Scene Planning and Conflict Mapping: screenwriters map all the conflicts in a scene before writing the dialogue because partial conflict-maps produce shallow scenes. Same architectural discipline in a different domain.
Sharpest Implication. The construction is a small operator-investment with significant deal-protection. The 90 seconds spent on the suppose-question architecture prevents the multiple-hours of backing-out-and-addressing that fragmented objection-handling produces. The construction is structurally one of the methodology's highest-leverage moves.
Generative Questions.