Business
Business

Kill Zombies Upfront vs Diffuse Bomb After

Business

Kill Zombies Upfront vs Diffuse Bomb After

A zombie is twenty feet away. You shoot it from distance. Easy kill. No damage to you.
developing·concept·2 sources··May 26, 2026

Kill Zombies Upfront vs Diffuse Bomb After

The Difference Between an Obstacle and an Objection

A zombie is twenty feet away. You shoot it from distance. Easy kill. No damage to you.

A zombie is biting your face. You shoot it. The shot kills the zombie, but it's been chewing on you for ten seconds. You won.1

In Hormozi's terminology, an obstacle is a zombie at distance — a concern raised before the price has been mentioned. An objection is a zombie chewing on your face — the same concern raised after the price has been mentioned. They are the same content. The timing changes everything about how much damage they do to the sale.

Kill the zombies upfront — handle the likely concerns before you mention the price. Diffuse the bombs that show up after you mention the price. Both work. Killing upfront is dramatically easier.

What This Actually Is

The doctrine is operational: the closer's job during the O and S sections is to surface and resolve likely BANT-related concerns before the price is on the table. After the price is on the table, the same concerns become objections that operate under much higher pressure.

Standard pre-emptive moves during O / pre-S:

  • Authority obstacle → "Is there anyone else who needs to be part of this decision?" — pre-empted decision-maker objection
  • Need obstacle → "Is this something you'd want to start now, or is it more of a future-quarter thing?" — pre-empted timing objection
  • Timing obstacle → "How much time per week could you commit to implementation?" — pre-empted time objection
  • Budget obstacle → "What's the kind of investment range you were imagining for solving this?" — pre-empted price objection2

These can be asked during the pain cycle (O section) where they feel like fact-finding, not interrogation. They surface the same information that would later become objections — except surfaced upfront, the information becomes context the closer can address gently. Surfaced after price, the information becomes resistance that has to be overcome under stakes.

Why Timing Determines Damage

The mechanism has three parts:

  1. Pre-price, the stakes are zero. When you ask "is there anyone else who'd need to be on the call?" before the price is on the table, the prospect can answer honestly without strategic positioning. They might say "actually yes, my business partner" and you say "got it, let me make sure they're on the next call." No drama. The information is collected and addressed.

  2. Post-price, the stakes are high. When the prospect says "actually I need to talk to my business partner" after you've quoted $4,500, they're using the partner as a face-saving exit. They might or might not actually need to consult the partner. The closer has to work harder to determine whether the objection is real and figure out the right overcome.

  3. Pre-empted concerns can't be used as exit ramps. If you confirmed at minute 12 that the prospect has full decision authority, they can't claim at minute 28 that they need spousal approval. You've cut off that exit ramp in advance.

The discipline is similar to how a chess player anticipates an opponent's likely moves several turns ahead and pre-empts them with their own positioning. Pre-emption isn't manipulation; it's removing predictable failure modes from the conversation before they occur.

Synergies & Handshakes

Kill-zombies-upfront is intimately connected to:

  • BANT qualification (Cluster C, Session 2) — BANT is the framework for what to pre-empt
  • The pain cycle (O section) — pre-emption questions are folded into past-pain conversation
  • The three-bucket map (Ellis Three Distortions) — pre-emption targets the most common circumstances and others bucket objections
  • The closing section (E) — post-price diffusing is the alternative when pre-emption didn't happen

The discipline operates as the front-end of objection-handling. The E section's bomb-diffusing is what handles objections that escaped pre-emption.

Analytical Case Study: The Spouse Pre-Empt

Standard scene. Minute 14 of the call, in the middle of the pain cycle. The closer has just asked "what have you tried so far?" The prospect mentions a previous business decision they made.

Closer: "Got it — and was your husband involved in that decision?"

Prospect: "Yeah, we usually decide together on this kind of stuff."

Closer notes it. Doesn't make a big deal of it. Continues the pain cycle. Minute 20, finishing O, transitioning to S:

Closer: "Just so I know — if we figure out this is the right move today, would your husband need to be on the call to make the call, or is this something you have the freedom to decide together later?"

Prospect: "Honestly, for the kind of investment I'm thinking about, I'd probably need him on the call."

Closer: "Totally fair. What if we schedule the next call for both of you — let me show you what we're talking about so you can both make the decision together rather than me trying to explain it to him through you. That fair?"

Prospect: "Yeah, that actually makes sense."

What happened: the closer surfaced the decision-maker constraint at minute 20, before any price had been mentioned. The constraint became a logistical conversation, not an objection. The next call gets scheduled with both decision-makers. No bomb to diffuse later because no bomb got loaded.

Counterfactual: closer doesn't pre-empt. At minute 28 the price is on the table ($8,000). Prospect: "I need to talk to my husband." Now the closer has to determine whether this is real or a face-saving exit, handle the AAA loop, possibly run through the four-step decision-maker overcome, possibly lose the sale because by the time they figure out the husband actually needs to be involved, the prospect has already committed publicly to thinking about it.

The pre-empted version closes (eventually, on the next call with both decision-makers). The unpremempted version may or may not close depending on how skillfully the closer handles the objection under price-stress.

Implementation Workflow

You're at minute 16. You're in the pain cycle. You've collected past-failure data. You're about to transition to the pitch.

You take a beat. You think: "What are the three or four objections most likely to come up after I mention price?"

Standard candidates:

  • Decision-maker (spouse, partner, board)
  • Time (capacity for implementation)
  • Budget (price range)
  • Fit (something specific about the product they might want different)

You ask one of these per minute, folded into the natural conversation, for the next 3-4 minutes. Each one is asked as a fact-finding question, not as a "let me check if you're qualified" question:

  • "Is there anyone else who'd typically be involved in a decision like this?"
  • "How much time per week could you realistically commit to implementing something like this?"
  • "What's the kind of investment range you were imagining for solving this?"
  • "Is there anything specific about how you'd want this delivered that I should know about?"

The answers either confirm green-light or surface the obstacle. Surfaced obstacles get addressed gently in pre-S conversation, not under post-price pressure.

By minute 22, the most likely post-price bombs have either been defused or surfaced and addressed. The pitch (S) lands on a much more committed prospect. The E section, when it begins, has fewer surprises.

The Pre-Emption Failure (Diagnostic Signs)

  • You quoted price without asking the spouse-question. First post-price objection is "I need to talk to my husband." You skipped the pre-emption. Now you're working it under stakes.
  • You pre-empted but didn't address the surfaced obstacle. You asked "is there anyone else?" — they said "yes, my partner" — you noted it and kept going. The pre-emption only works if you address what gets surfaced. Otherwise it's just data collection.
  • You ran the pre-emption like an interrogation. "I need to qualify you on decision authority before we go further." This is BANT-as-interview, not BANT-as-conversation. The prospect feels grilled. Pre-emption only works when folded into natural conversation.
  • You pre-empted but at minute 28 still got the objection anyway. You asked at minute 16, they said yes, but at minute 28 they pivoted to "actually my partner needs to weigh in." This usually means there's a deeper concern (self-bucket) using the partner as a foil. The pre-emption didn't fail; the objection isn't really about the partner. Pivot to surfacing the actual concern.

Author Tensions & Convergences

The pre-emption discipline maps onto Hughes's BOM Lens 3 (Compliance) — the idea that resistance-mechanisms surface predictably and can be pre-empted by addressing them before the high-stakes ask. Hughes's framework is more clinical (here are the compliance failure-modes; here's how to architecture around them); Hormozi's is more operational (here are the four BANT-objections; here's how to fold them into the pain cycle).

The convergence with classical military strategy is real: every credible military doctrine emphasizes pre-empting predictable opponent moves rather than reacting after the move is made. Sun Tzu's "win first, then go to war" maps onto kill-zombies-upfront — make sure the conditions for victory are in place before engagement, not improvised during engagement.

Where Hormozi diverges from BANT-as-qualifying-framework: BANT was developed by IBM in the 1950s-60s as a qualification framework — disqualify leads that don't meet B-A-N-T criteria so reps don't waste time. Hormozi uses BANT as a pre-emption framework — surface the BANT-related concerns to address them, not to disqualify. This is a meaningful re-deployment: same framework, different operational goal.

Cross-Domain Handshakes

The pre-emption doctrine operates across any domain where a practitioner faces predictable resistance and has a window to address it before the high-stakes moment.

  • Behavioral Mechanics: Six-Minute X-Ray Elicitation Suite (Hughes) — Hughes's elicitation framework emphasizes information-gathering before the commitment-ask. The structural parallel: both architectures collect information about likely failure-modes before the high-stakes moment, so the failure-modes can be addressed proactively. The insight: pre-emption is universal high-stakes-conversation craft. The intelligence officer reading a target and the closer pre-empting BANT-objections are running the same machinery — diagnose the resistance architecture before deploying the ask.

  • Military Strategy: Sun Tzu Art of War Hub / Chinese Military Theory Hub — classical Chinese military strategy is foundationally pre-emptive: shape the battlefield, secure the ground, eliminate the opponent's options before the engagement begins. The structural parallel: both architectures privilege upstream positioning over downstream improvisation. The insight: kill-zombies-upfront is military pre-emption deployed for commercial sales. The strategist arranging conditions before the battle and the closer arranging conditions before the price-reveal are operating on the same principle — the moment of high-stakes engagement is decided by the work done before it, not during it.

  • Psychology: Anticipatory Coping as Anxiety Management / Inner Child Child Psychology Hub — therapeutic frameworks for managing anxiety often emphasize pre-emptive identification of likely trigger-points and the construction of advance coping plans. The structural parallel: pre-emptive identification of failure-modes (in sales: objections; in therapy: trigger-states) and proactive addressing reduces the cognitive load when the failure-mode arrives. The insight: the kill-zombies-upfront doctrine is anxiety-management craft deployed for commercial sales. The therapist building advance coping plans for a client and the closer pre-empting BANT-objections are running the same architecture.

The Live Edge

The Sharpest Implication

If kill-zombies-upfront is correct, then most sales training is mis-prioritized in a specific way: training focuses on what to say after objections appear (E section), when it should focus equally on what to ask before objections appear (folded into O). The result is closers who are skilled at bomb-diffusing but unskilled at zombie-killing. They handle objections well under stress when they could have prevented the stress by pre-empting earlier. The implication: sales-training time-budget should be roughly equal between pre-emption questions and post-price objection-handling, not weighted 80/20 toward objection-handling as most training is.

Generative Questions

  • The four standard BANT-objections (decision-maker, time, budget, fit) are well-known. Are there other categories of post-price objections that should be pre-empted? Probably yes: risk-tolerance ("what if it doesn't work?"), prior-bad-experience ("we tried something similar three years ago"), competitor-comparison ("we're also looking at X"). Building a fuller pre-emption taxonomy is an open vault project.
  • The pre-emption questions are folded into the pain cycle. But the pain cycle is finite — typically 10-15 minutes. How many pre-emption questions can be folded in without making the cycle feel like an interrogation? Probably 4-5 maximum. Beyond that, the cycle loses its emotional character. The calibration is a craft skill.
  • When pre-emption surfaces an obstacle that can't be addressed in the current call (e.g., "I need to talk to my husband"), the right move is usually to reschedule with both decision-makers rather than to push through. But this means killing-zombies-upfront sometimes ends the current call without a close — and many closers resist this because their metrics reward closing the current call. The structural tension: pre-emption discipline implies sometimes ending calls without closing, but compensation structures don't reward that move. Designing compensation that recognizes the discipline is an open organizational-design question.

Connected Concepts

Footnotes

domainBusiness
developing
sources2
complexity
createdMay 26, 2026
inbound links9