Section 1
Key takeaways
• A discovery call has one job: replace adjectives with facts. "Churn is rough" is an adjective; "we're losing $40k a month and it's getting worse" is a fact you can write a proposal against. • The deal you think you're losing to a rival, you are usually losing to the buyer's own inaction, 60% of pipeline dies in "no decision" , 40–60% of intending buyers stall out . • Five line items make a deal qualified: the quantified problem, the decision process, budget reality, the timeline trigger, and success criteria. Each must be a sentence with a number, a name, or a date in it. • Leave with all five filled and you write a proposal. Leave with four and you book a second call to fill the blank, you don't write the guess. • The checklist is an indecision detector: every blank line is a place the deal will stall later, found while you can still ask a question instead of three weeks into a silent pipeline.
Section 2
The "good call" is the most expensive lie in services
Here's the trap. Rapport feels like progress. It isn't. A call where everyone nods is exactly the call that produces a polite "let me think it over" two weeks later, and then silence. Matthew Dixon and Ted McKenna put numbers on that silence in HBR: "anywhere between 40% and 60% of deals today end up lost to customers who express their intent to purchase, but ultimately fail to act" . Read that slowly. The deal you think you're losing to a rival, you are usually losing to the buyer's own inaction. Forrester's read on the pipeline is the same shape from a different angle, 60% lost to no decision, not to a rival's better pitch . Put those next to a 10–30% discovery-to-sale conversion band and the picture is blunt: the average services proposal is a guess dressed up as a plan, and most of them die not in a bake-off but in the prospect's own stall. The honest move on a half-qualified deal is to name the maybe and force a real decision rather than nurse it. You cannot fix that downstream. You cannot email your way out of an unqualified deal. The leak is on the call, and it's a leak of information you needed and didn't collect. There's a structural reason this keeps happening, and it shows up on the recordings. Mindtickle's 2024 analysis of recorded discovery calls found that reps talk 57% of the time, meaning the prospect, the one person whose problem you are supposed to quantify, speaks less than half the call . Read that again. The person with the budget, the pain, and the veto is in the passenger seat for most of the conversation. Of course the proposal is a guess. The seller spent the call talking instead of extracting, which is exactly why keeping the prospect talking more than you do is the precondition for everything below. And it's not that asking questions is hard, it's that most people ask the wrong volume of the wrong things. Gong analyzed more than 519,000 B2B sales calls and found a sweet spot: 11–14 targeted questions on a winning discovery call . Fewer and the problem stays under-defined, you never get past the adjective. More and it stops being a conversation and becomes an interrogation, which kills the trust you need for honest answers. The skill isn't "ask a lot." It's "ask the right dozen, then stop talking and let them fill the half of the call you've been hogging."
Section 3
What you're actually mining for
Strip away the script and a discovery call has exactly one job: replace adjectives with facts. "Churn is rough" is an adjective, churn being the rate at which customers cancel. "We're losing about $40k a month to churn and it's getting worse each quarter" is a fact. You write proposals against facts. You can't write anything against adjectives, you just project your own assumptions onto a stranger's business and hope. This is the difference between running discovery as a diagnosis rather than a pitch: a doctor who skips the exam and writes the script is guessing too. So before the framework, the standard: a fact is something the prospect said out loud, with a number or a name or a date attached. Not something you inferred. Not something you'd "circle back on." Said out loud. If you find yourself filling a gap with "they probably mean…", that gap is a missing line item, and the proposal you build on top of it is fiction. That's the whole game. Five facts. Get them and you write a proposal. Get four and you write a guess.
Section 4
The BGA framework: The Exit Receipt
The Exit Receipt is minimum-viable discovery, five line items you must be holding before you hang up. Run it as a literal checklist. If you can't write the answer in a sentence with a number, a name, or a date in it, the line is blank, and a blank line means you book a second call, not a proposal. 1. The Quantified Problem, a number, not an adjective. Get the cost of the problem in the prospect's own words and units. Money, hours, headcount, lost deals, whatever they measure. "We're losing roughly $40k a month to churn" passes. "Retention is a headache" fails. Action: Ask "what is this costing you right now?" and then "how did you get to that number?" The follow-up matters more than the first answer, because it tells you whether the figure is real or a shrug, the same discipline behind quantifying the problem in the prospect's own units. A prospect who built the number can defend it; a prospect who guessed will backpedal, and now you know how soft the pain actually is. Rule of thumb: If you can't state the problem's cost in one sentence with a unit attached, line 1 is blank. A solution priced at $5k against an unstated problem has no anchor, and an unanchored price is the thing prospects "think over" forever. 2. The Decision Process, who signs, who can veto, how many bodies are in the room. "I'll run it by the team" is not an answer. It's a checklist item you haven't filled in. B2B buying decisions routinely involve a group, not a person, so you need to know how many, who they are, and what each one cares about. The economic buyer who signs the check, the user who lives with the thing day to day, and the skeptic who can quietly kill it on a Slack thread you'll never see. This is the work of mapping the buying committee before you propose into it. Action: Ask "walk me through how a decision like this actually gets made here, who else weighs in, and what would each of them want to know?" Map names to roles. You are not being nosy; you are building the list of people your proposal has to win, because a proposal only ever persuades the person reading it. Rule of thumb: If you can't name the person who signs and at least one person who could veto, line 2 is blank. This is the line that prevents the most common death, the deal that "everyone loved" and then evaporated because one unseen stakeholder said no and nobody told you. 3. Budget Reality, a range they said out loud, not one you hallucinated. You need a number the prospect spoke, or at minimum a band they confirmed when you floated it. Not a figure you backed into from their headcount and prayed about. Establishing budget before the proposal, not after, is what turns pricing into a conversation instead of an ambush. Action: Anchor and check. "Most engagements like this land between $X and $Y depending on scope, does that fit how you've thought about it?" Watch the reaction. A flinch is data. A nod is data. A "we haven't budgeted for this at all" is the most valuable answer you'll get all call, because it tells you the work ahead is justifying spend that doesn't exist yet, not winning a slice of spend that does. Rule of thumb: If the only budget number in your notes is one you invented, line 3 is blank. Writing a proposal priced at a number nobody confirmed is how you generate a "too expensive" you could have caught on the call for free. 4. The Timeline Trigger, the event forcing action by a date. This is the line most sellers skip, and it's the one that determines whether the deal ever closes. There has to be an event, a renewal, a product launch, an audit, a funding round, a new hire, a contract expiring, that makes doing nothing more painful than doing something, by a specific date. No trigger means no urgency. No urgency means "no decision," which is where 60% of pipeline goes to die and where 40–60% of intending buyers quietly stall out . Surfacing the timeline and triggers that make inaction expensive is how you separate a buyer from a browser. Action: Ask "what happens if this is still unsolved in six months, and is there a date on the calendar that makes it worse?" If the honest answer is "nothing really changes," you've found a prospect, not a buyer. Note the difference and price your time accordingly. Rule of thumb: If you can't name the event and roughly when it lands, line 4 is blank. A deal with no trigger isn't qualified, it's a "someday," and someday doesn't sign. 5. Success Criteria, the specific outcome that makes them call it a win in 90 days. What does "this worked" look like to them, measured, by a date? Tie it back to line 1. If the quantified problem was $40k/month of churn, success might be "cut it to $20k within a quarter." Now you have a before, an after, and a clock. Action: Ask "if we do this and it goes great, what's specifically different 90 days from now, and how would you measure it?" Get their metric, not yours. The number they pick is the number they will judge you against at renewal, so you want it on the record now, in their words, not invented by you later. Rule of thumb: If the success definition is "we'd be happy" with no number and no date, line 5 is blank. Vague success means an un-renewable engagement and a case study you can never write. Five lines. Here's the discipline that makes it a framework instead of a wish list: leave with all five filled and you write a proposal. Leave with four and you write a guess, so you don't write it. You book the second call to fill the blank. That single rule, held honestly, does more for your close rate than any amount of follow-up cleverness, because it stops you from spending hours proposing into a void.
Section 5
A worked example: the fractional CMO who almost wrote a guess
Make it concrete. A fractional CMO, an outsourced marketing leader hired part-time, takes a discovery call with a Series A SaaS founder. Great rapport. The founder says growth has "stalled" and they "need help with demand gen." Old playbook: write a $12k/month retainer proposal that weekend. Run The Exit Receipt instead. • Quantified Problem: "We were growing 15% month over month, now it's 3%, and our payback period blew out to 14 months." Number, units, direction. Line 1 filled. • Decision Process: "I decide, but our board lead has opinions and our head of sales has to buy in or it won't stick." Three names, one signer, one veto. Line 2 filled. • Budget Reality: The CMO floats "$10–14k/month." Founder: "We were thinking closer to $8k, but if it moves payback we'd stretch." A real band, spoken aloud. Line 3 filled. • Timeline Trigger: "We're raising our A extension in Q4, the metrics have to look right by October." A date, an event, real teeth. Line 4 filled. • Success Criteria: "Payback back under 10 months and month-over-month growth above 8% by the raise." Tied to line 1, with a clock. Line 5 filled. Now the proposal writes itself, and it's not a guess, it's priced against a confirmed budget, aimed at a board-credible metric, timed to a raise, and structured to win over a specific skeptical head of sales. Compare that to the weekend retainer built on "growth has stalled." Same call, same rapport. One produces a document the founder can say yes to without three weeks of "thinking it over." The other joins the no-decision pile . Notice what the receipt didn't require: more time. The difference between the guess and the plan isn't a longer call, it's what gets extracted in the minutes you already have. The right dozen questions , the prospect talking more than you do , and five facts in hand by the end.
Section 6
Why this beats "build rapport and follow up"
Rapport is necessary and worthless on its own. It opens the door to the five answers; it is not a substitute for them. The reason the Exit Receipt works is that it attacks the actual failure mode in the data. Deals don't mostly die because someone out-pitched you. They die because the buyer was never qualified to act, no quantified pain, no clear signer, no real budget, no trigger, no defined win, and so when the meeting ends, the path of least resistance is inaction . A checklist that forces those five facts onto the table is, functionally, an indecision detector. Every blank line is a place the deal will stall later. You'd rather find the blank on the call, while you can still ask a question, than three weeks into a silent pipeline when your only move is a follow-up email nobody answers. If you want the deeper diagnostic of why qualified-looking deals stall, it traces back to a blank line nobody filled on the first call. And it reorders your effort. Instead of pouring hours into beautiful proposals for half-qualified deals and converting at the bottom of a 10–30% band , you spend the expensive hours only on deals where all five lines are full, and you let the four-line deals earn a second call before they earn a document. That's not working harder on the call. It's refusing to do free work after it. Over a quarter, that single reallocation is usually the difference between a calendar full of "thinking it over" and a calendar full of signed work.
Section 7
You're running The Exit Receipt right when…
You're running The Exit Receipt right when you can end any discovery call and, without checking your notes, recite five things: what the problem costs in their words, who signs and who can kill it, the budget band they said out loud, the dated event forcing a decision, and the measured outcome that means "win" in 90 days. If you can recite all five, write the proposal, it's a plan. If you go quiet on any one of them, you don't have a deal. You have a guess with good rapport, and you book the second call to turn the blank into a fact before you write a single word. Stop pitching solutions to problems nobody has put a number on. Earn the receipt first. The full checklist, the exact question scripts for each of the five lines, and the second-call sequence live in the LeadOS playbook. If you want the five lines as a ready-to-run worksheet with the exact question scripts for each, the Template Pack gives you the receipt to fill in on your next call.