Section 1
Key takeaways
• 40–60% of lost deals die in "no decision," not to a competitor, the prospect does nothing . Most of your "losses" are stalls. • Of those no-decision losses, 56% are driven by fear of messing up, not preference for the status quo . The buyer is frozen, not satisfied. • Arguing harder against the status quo backfires 84% of the time, it deepens the freeze instead of breaking it . • A real "why now" is external and time-bound: a renewal, a regulation, a deadline on someone else's calendar. Urgency you had to invent won't survive procurement review. • Run every deal through the Compelling Event Test before you forecast it: external trigger, one-sentence consequence, and whose urgency it actually is.
Section 2
Why do deals stall, and why is "push harder" the wrong reflex?
Start with the failure mode; it's more common than the win. In the JOLT Effect research, an analysis of 2.5 million recorded sales conversations, 40% to 60% of an average rep's lost deals were attributed not to a competitor but to indecision . The buyer didn't pick someone else; they picked nothing. That single fact reframes most pipeline reviews. When you mark a deal "lost," you look for the rival who undercut you, but the likelier culprit is a calendar that never moved. A separate tally puts roughly 60% of pipeline losses on no-decision, not competitors : the threat to your forecast is mostly internal stalling. Here's the part that should change your behavior. Of those no-decision losses, 44% came from genuine preference for the status quo, but the majority, 56%, came from indecision rooted in risk or fear of failure . The buyer wasn't happy; they were scared of moving and getting it wrong. As Matt Dixon, co-author of The JOLT Effect and The Challenger Sale, put it in an interview: "They're not concerned about missing out, what they're concerned about is messing up" . That distinction, fear of messing up, not fear of missing out, is the whole game. The standard seller reflex is built for the wrong fear: we amplify FOMO, making staying put feel painful. Against a frightened buyer, that's counterproductive. The research found an 84% probability that arguing harder against the status quo increases the odds the customer does nothing . You're pressing the gas with the parking brake on. This is why I treat manufactured urgency as a tell that a deal is weak, not strong. A fake deadline, "this pricing is only good through month-end", adds risk to a buyer already paralyzed by risk. It doesn't melt the freeze; it confirms their instinct that buying is dangerous. For where deadlines help versus backfire, urgency that isn't fake goes deeper.
Section 3
What a real compelling event actually is
A compelling event is a specific, time-bound business trigger that makes inaction measurably costly by a known date . Three properties matter, and all three have to hold: 1. It's external to your sales process. A renewal date, a regulatory deadline, a contract expiry, a board commitment, a funding milestone, a system being sunset. It exists whether or not you show up. "Our quarter ends Friday" is your event; "their compliance audit is in September" is theirs. 2. It's time-bound. There's a date. "Eventually we'll need to fix this" is a problem, not a trigger. "Our vendor's contract auto-renews on March 1 and we owe 60 days' notice" is a trigger, it has a clock. 3. The cost of waiting is concrete. Someone can name, in one sentence, what specifically breaks if nothing happens by that date. Not "things would be better." Rather: "If we don't switch by March 1, we're locked in for another 12 months at the rate that's already 30% over budget." Notice what's missing: your enthusiasm, your quota, your follow-up cadence. None are compelling events, they're pressures on you. The buyer doesn't share them, and treating them as urgency is how you build a forecast full of deals that feel hot and close at zero. A useful complement is front-end timing. Whether a deal has a clean trigger often traces back to when you engaged, most of your market isn't in a buying window at any moment, the core of the 95:5 rule. You can't conjure a trigger for someone with no buying window; you catch them when one opens. The changes that open those windows, funding, a new exec, a system migration, are the same observable triggers worth mapping before you reach out.
Section 4
A worked example: the consultant who kept "almost" closing
Make it concrete. Say you run a fractional operations consultancy, parachute in, fix a broken process, hand it back. Average engagement: $40k over three months. Pipeline looks healthy; close rate is miserable. Two deals "felt" identical on the discovery call. Deal A, the manufacturing client. The ops director says their order-to-cash process is a mess: invoices go out late, cash is tight. Real pain. You build a detailed proposal. They say it "makes total sense" and ask you to circle back next quarter. You do. Same answer. The deal is technically open eight months later, which means it's dead and you're the last to know. Deal B, the clinic group. The COO describes the same pain, almost word for word. But then: "We're onboarding two new clinics in October and our billing process can't handle the volume, it already breaks at month-end. If we go live in October on what we have, claims sit unprocessed and we miss the cash-flow targets we committed to the board for Q4." Same pain, completely different deal. Deal B has a date (October), an external trigger (two clinics already signed), and a one-sentence consequence the COO can repeat to her board ("claims sit, we miss the Q4 number"). Deal A has none of those. The pain is real in both, but only Deal B has a trigger, a reason for this quarter, not some other one. The mistake operators make is treating Deal A like a closing problem and throwing more pitch at it. It isn't a closing problem; it's a no-trigger problem, and it was one on day one. The discipline is to find that out on the call, which is what running the discovery call as a qualification tool, not a pitch is built to do, not eight months later in your win-loss review.
Section 5
The questions that surface a "why now"
You surface a trigger the way you surface anything real on a call: you ask, then you listen. The point is to find out whether a date exists and who owns it, not to lead the witness into a deadline you invented. Here's the question set I run, in order: • "Why is this a priority now, versus six months ago, or six months from now?" The single best opener. If they can't answer it crisply, there may be no trigger. Silence here is data. • "What happens on [date] if this isn't solved?" Once a date appears, anchor to it. You're testing whether the consequence is concrete or vague. "Things stay annoying" is vague. "We breach the SLA and the client can leave" is a trigger. • "Who else has this deadline on their calendar?" A real compelling event has witnesses. If only your champion cares about the date, it's not an organizational event, it's one person's preference, and one person rarely moves a budget. • "What's the cost of waiting another quarter, in your numbers?" This forces quantification. If they can't put a figure or a hard consequence on inaction, the event isn't compelling yet. (See quantifying the problem for how to make the cost of waiting undeniable.) • "What's driven other teams to finally fix something like this?" A sideways way to surface triggers they haven't volunteered, renewals, audits, a leadership change, a painful incident. Two rules while you ask. First, do not supply the urgency for them. The moment you say "so you really need this by Q4, right?" and they politely agree, you've contaminated the data, you can no longer tell their trigger from your wishful thinking. Let them say the date. Second, blank answers are a finding, not a failure: you've correctly identified a deal that shouldn't be in your committed forecast.
Section 6
The BGA framework: The Compelling Event Test
Before you forecast any deal, before you write it into the committed column, before you spend another hour on the proposal, run it through three filters. All three must pass. To pressure-test a whole pipeline this way, the free growth diagnostic walks the same filters deal by deal. Step 1, The external trigger filter. Is there a time-bound trigger outside your sales process: a renewal, a regulation, a contract expiry, a board mandate, a launch ? Write the trigger and the date on the deal record. Rule of thumb: if the only date in the deal is your quarter-end, the trigger filter fails. Step 2, The one-sentence consequence filter. Can your champion explain to the economic buyer, in a single sentence, what specifically breaks if they wait one more quarter? Make them say it, then write it down verbatim. If you can't produce that sentence, in the buyer's own words and numbers, you don't have a consequence, you have a hope. Rule of thumb: if the consequence needs a paragraph and three caveats, it won't survive procurement. Step 3, The whose-urgency filter. Is the urgency the buyer's, fear of messing up by not acting, or merely yours (quota pressure, pipeline math, end-of-month)? Be honest. This is where most forecasts inflate. If you strip away your own deadline and the deal has no pull left, the urgency was never theirs. If all three pass, you have a real compelling event. Forecast it, and tie every next step to the date. If one or more come back blank, you don't push. You do one of two things: • Surface the trigger you missed. Run the question set above. Often the event exists and simply hasn't been spoken aloud. Your job is to find it, not invent it. • Co-create the Cost of Inaction clock. If there's genuinely no external date, you can still make the cost of waiting concrete and time-bound together, quantify what each stalled quarter costs in their numbers and attach it to a real upcoming milestone. This is honest because the consequence is real; you're naming it, not fabricating it. It's where naming what "do nothing" actually costs does the work a fake deadline never could. And if both come back empty, no trigger to surface, no real cost to name, disqualify or park the deal. That's the point of the test. A deal with no compelling event isn't lost; it's just not now. Stop spending closing energy on it and put that energy where a clock is ticking. One structural reason to build this habit now: the window is shrinking. The average B2B sales cycle has stretched to 6.5 months, up from 4.9 in 2019, roughly a third longer in six years . Longer cycles give indecision more room to set in. The deals that close are increasingly the ones with a real clock; the rest drift until they die.
Section 7
You're running The Compelling Event Test right when…
You're running it right when your committed forecast only contains deals with a date and a one-sentence consequence written on the record, and you can read that sentence aloud in the buyer's own words. You're running it right when "circle back next quarter" stops your pursuit instead of triggering three more follow-ups, the no-trigger signal it usually is. And you're running it right when disqualifying a no-trigger deal feels like a win, because you just bought back the hours you'd have burned pushing a frozen buyer harder and making it 84% more likely they'd never move . You're running it wrong when your pipeline is full of deals that "feel close," every urgency in the file is yours, and your win-loss review keeps surfacing the same ghost: a calendar that never moved.