The permission-to-stop-performing move is a B2B discovery tactic where the seller responds to a prospect’s claim that everything is fine by agreeing with them — “Sounds like things are working. I’m not sure I can actually help you” — and offering a transparent exit from the sales process. Removing the pressure to buy defuses the buyer’s defensive script; roughly nine times out of ten, the prospect corrects the seller and reveals what is actually broken. The move turns polite education calls into business calls built on real commercial tension.
You think you had an outstanding first meeting. The buyer was engaged, asked smart questions, and called the demo “really interesting.” They promised to loop in their team next week. Then: total silence. You spend the next month chasing a call that felt genuinely positive, wondering how enthusiasm turned into ghosting.
Across 300+ founder conversations in 40+ countries on six continents, this is one of the most common patterns in early-stage SaaS sales. It is rarely a closing problem. It starts much earlier — with founders running education calls instead of business calls, because the knowledge that actually closes deals (triggers, objections, buying patterns) has never left the founder’s head.
Why do your best discovery calls end in silence?
Your best discovery calls end in silence because they are education calls, not business calls — the buyer leaves smarter, but nothing in their world has become intolerable. An education call is a meeting where the prospect learns about your category, your features, and a helpful framework, thanks you for the free consulting, and goes straight back to their regular day job. A business call is a meeting where the buyer leaves productively uncomfortable — like a thorough doctor’s visit. They came in tolerating a specific inefficiency, and they leave realizing they can no longer live with it.
| Signal | Education call | Business call |
|---|---|---|
| What the buyer asks | High-level category questions, feature walkthroughs, requests for slides and standard pricing sheets | Questions about implementation, rollout, and what changing would actually cost their team |
| What gets acknowledged | Nothing — the status quo stays defended | The operational and financial cost of keeping the current broken system |
| How it ends | “That was very interesting” / “We’ll be in touch if something changes” | Concrete next steps, active debate, and a mapped decision-making process |
| What the buyer got | Free consulting | A problem they can no longer ignore |
Founders get trapped in this polite feedback loop because they want to be helpful and well-liked, so they default to teaching, explaining, and showing off features. Buyers are polite, so they smile and tell you the software is incredible. But curiosity is never the same as purchase intent — and mistaking one for the other is the most common reason deals stall after a strong start.
What is the buyer actually performing on a discovery call?
On most discovery calls, the buyer is performing operational competence — a rehearsed script that says “we are organized, optimized, and fully in control of our stack” — because admitting to manual chaos risks their internal reputation and budget authority. Enterprise buyers consistently describe their own purchasing process as complex and difficult, and much of that difficulty is the internal friction of maintaining this protective facade.
Standard, linear discovery cannot pierce the performance. Predictable questions about requirements, tooling, and timelines are comfortable — they let the prospect give clean, polished answers that bypass actual pain. The call feels friction-free and positive, and that is precisely the problem: no commercial tension was ever built.
| What the buyer performs | The underlying reality | The defensive driver |
|---|---|---|
| “Our existing setup handles this cleanly.” | Multiple team leads run fragmented spreadsheets and manual workarounds | Admitting there is no process risks internal status and budget authority |
| “We’re just scanning the market for minor efficiency gains.” | The current software is widely ignored and data is leaking everywhere | Protecting a previous purchasing decision and avoiding personal blame |
| “We have clear alignment across the buying committee.” | Stakeholders hold conflicting priorities with no shared goals | Concealing internal political divides from outside vendors |
The instinctive founder response — pitch harder, demo more, explain better — makes it worse, because features earn admiration while tension earns decisions. Buyers will not stop performing until they feel it is safe to do so. Which is exactly what the move is for.
How does “Sounds like things are working” actually work?
The move works by taking the deal off the table: when a prospect insists their current workflow is fine, you agree with them and offer a clean exit — “Sounds like things are working. I’m not sure I can actually help you.” This eliminates the buyer’s need to defend the status quo, because there is nothing left to defend against. It descends from the classic negative reverse, but the intent here is diagnostic, not manipulative: you are genuinely willing to walk.
Two things can happen, and both are wins. Either the prospect accepts the exit — saving you weeks of chasing a deal that was never real — or, roughly nine times out of ten, they correct you: “Well, it’s not exactly working…” and open up about what is actually broken. Buyers are pitched constantly by vendors promising the same efficiency gains in the same words; the seller who says “you might not need my software” instantly stands out and earns the credibility to run a real diagnostic. That shift — from eager educator to diagnostic partner — is the posture the SPRINT framework calls the Trust dimension: everything you say is likely being repeated by ten competitors, so the only differentiated move is the one a pitching vendor would never make.
| Moment | The pitching vendor | The diagnosing partner |
|---|---|---|
| Buyer says the manual workflow is fine | Argues why manual work is inefficient and lists features | Acknowledges the workflow and asks whether it actually holds at their scale |
| Buyer says everything is okay | Keeps pushing the value proposition, hunting for a crack | Says “sounds like things are working” and offers the exit |
| Commercial outcome | A polite follow-up loop that ends in silent ghosting | Alignment on a real problem — or an immediate, respectful close that protects founder time |
Why can’t you hire your way out of the polite feedback loop?
You can’t hire your way out because the tacit knowledge that closes deals is still locked inside the founder’s head — a new seller inherits the calls but not the magic. Early deals close because the founder acts as a sales magician: personal charisma, deep domain expertise, and the authority to promise custom features on the fly. That force of will moves initial revenue, and it creates a dangerous illusion of product-market fit. A process-driven Founding AE cannot rewrite the roadmap mid-call. Handed a motion that runs on founder authority, they are left running education calls by default — and the ghosting pattern repeats on your payroll.
The way out is not a better hire; it is extracting the motion into a repeatable sales process with structured constraints a non-founder can execute — including the permission-to-stop-performing move as a standard play, not a personality trait. If you find yourself in every deal because the message doesn’t survive call two, the constraint is in the motion, and naming it comes before any attempt to scale. Taking five days to find the real constraint — about four hours of your own time — is cheap relative to another quarter of fixing the wrong thing.