“What changed to make solving this now matter?” is the single question that separates a real B2B deal from polite curiosity. Nearly every operational problem a founder sells into has existed inside the account for years, so the buyer’s existing workaround is proof it was survivable. Unless something recent shifted — a leadership change, a budget reallocation, a competitive threat, a compliance deadline — the workaround stays good enough and the deal ends in no decision. Ask it on the first call, and a quarter of dead pipeline disappears from your forecast in an afternoon.
You run discovery. The prospect is engaged, says the right things, and asks for a follow-up next quarter. Your calendar looks like a healthy pipeline. Across 300+ founder conversations in 40+ countries on six continents, I have watched founders read that calendar as traction when what they had collected was polite curiosity.
The instinct is to blame the product or the demo. It is usually neither. It is that nobody established why today.
Why doesn’t BANT work for early-stage founders anymore?
BANT fails because it assumes a buyer who already knows they have a problem and has budget set aside to fix it — a description of a stable buying process that mostly no longer exists. Budget, Authority, Need, Timeline works fine when the prospect arrives pre-convinced. Early-stage founders rarely meet that buyer. They meet someone who has lived with the problem for three years, has no line item for your category, and whose real alternative is not a competitor but doing nothing at all.
The trap is that BANT is answerable by someone who will never buy. Ask about budget and you get “we’d find it for the right solution.” Ask about timeline and you get “probably next quarter.” Both are true, neither is a commitment, and the checklist comes back clean.
| What BANT assumes | What’s actually true early-stage |
|---|---|
| A budget exists for your category | Money has to be pulled from something else already funded |
| One executive can decide | Consensus is needed across a committee with no shared urgency |
| The buyer is actively searching | The buyer is coping, and coping is cheaper than switching |
| A deadline drives the decision | Nothing forces a date, so the deal slips indefinitely |
This is the mechanism behind the ghosting pattern: your competition isn’t a rival vendor, it’s inertia and noise. As Matthew Dixon and Ted McKenna document in The Jolt Effect, a large share of lost B2B deals go to indecision rather than to another vendor — buyers who wanted to move and couldn’t. The related point is that your biggest competitor is noise, not “do nothing”: these buyers aren’t inactive, they’re taking meetings and running pilots and still not deciding.
What does a real trigger actually look like?
A real trigger is a specific, recent, external-to-you event that made the status quo cost something it didn’t cost before. Not a general frustration — a dated change with a name attached. Four kinds show up repeatedly:
- A leadership change. A new VP or exec arrives hired to fix a named bottleneck, with a mandate and a window to establish their own stack.
- A budget or fiscal shift. A missed target, a new cost mandate, or a consolidation push that forces the team to find efficiency this quarter rather than eventually.
- A competitive threat. A rival moved, and the manual workaround the team tolerated is now a visible liability someone will be asked about.
- A regulatory or compliance deadline. An external date that makes the current process untenable regardless of anyone’s preference.
If the buyer can name one of these, the conversation changes character — they start asking about implementation and internal cost rather than features. If they can’t, you are looking at a problem the organization has already proven it can live with. That’s the same distinction I draw between curiosity and purchase intent, arrived at from the buyer’s side rather than the seller’s.
Why do technical founders mistake activity for a sales motion?
Technical founders mistake activity for a motion because meeting volume is measurable and buyer urgency isn’t. Sequences go out, meetings get booked, the number climbs — and none of it is evidence that anyone is in-market. It compounds when the founder runs the call: having built the thing, the natural move is to show how it works, which produces a warm reaction and no information about whether this buyer has a reason to act.
The correction is cheap. Before the demo, ask what changed. If nothing has, you have learned in ninety seconds what would otherwise take six weeks and four follow-ups to discover.
| Signal | Polite curiosity | Real purchase intent |
|---|---|---|
| Motivation | Keeping up with what’s out there | An active bottleneck with a named owner |
| Questions asked | How it works, what it integrates with | Implementation timeline, rollout cost, who owns it internally |
| The trigger | None they can name | A specific, recent, dateable event |
| What a pilot means | Curiosity with a budget code attached | A step inside a project that has a date |
What does this mean before you hire a Founding AE?
Document your triggers before you hire, because the trigger list — not the ICP — is what makes a first sales hire effective. A seller handed a demographic profile will target companies that look right and fill the calendar with the same polite conversations you were having. A seller handed a list of what changed in the world of every customer who actually bought knows which accounts are live right now.
This is the concrete, writable core of a repeatable sales process. Go through your closed-won deals and, for each one, write the sentence: in the weeks before they engaged, this changed. If you can’t answer it for most of them, that gap is the thing to fix — long before it becomes a new seller’s problem. Working out whether you’re ready to hire a Founding AE starts here rather than with a job description.