Sales Discovery Questions

Discovery Questions

Build the sequenced question set a rep carries into a sales discovery conversation, plus the follow-up ladders and branch logic to adapt it live.

Four questioning frameworks with a publicly documented structure converge on one spine:

• SPIN (Rackham, 1988)
• Sandler's Pain Funnel
• MEDDPICC's Three Whys
• GAP Selling's Problem / Root Cause / Impact chart

The spine: isolate a real problem, dig to its root cause, quantify the impact, then establish why now. This skill encodes that convergence, not any one acronym. Vendor question-count and talk-ratio benchmarks are directional at best - never set a number to hit.

Interview

Ask before drafting. One question per message; offer multiple-choice answers when possible; skip anything the user already answered or that their notes make obvious.

• B2B, or B2C? (B2C here means considered, high-ticket consumer sales - coaching, remodeling, financial advice - not impulse retail.)
• Who is the persona, and how senior? (End user, manager, executive - seniority changes question count and depth.)
• What does the product do, and what problem does it solve, in one sentence each?
• What call is this: SDR qualification (15-30 min), AE deep discovery (30-45 min), persona-specific follow-up in a running deal, or a single B2C consultation? How long?
• Deal size and cycle complexity? (Transactional single-buyer / mid-market few stakeholders / enterprise buying committee.)
• Inbound or outbound origin? (Inbound buyers arrive with intent to confirm and deepen; outbound buyers need problem awareness built first.)
• What is already known from prior touches - outreach replies, notes, a prior call, a deal record?
• Does the team mandate a methodology (SPIN, MEDDPICC, Sandler, GAP, other)? If so, the set must map to its vocabulary.
• Is the buyer in a regulated context (healthcare, finance, government)? (Adds decision-process and procurement questions; constrains what can be asked about data and finances.)
• What pain does the rep already suspect? (Becomes the hypothesis to test - never a fact to confirm.)
• What next step would make this call a success? (The set must close toward it.)
• By what date must this call have produced a booked next step? (A hard date promotes the impact triad - a figure won on this call is what a dated ask is argued from - and demotes decision-context coverage, which pays back across the cycle, not today.)
• One-off win or compounding asset: a sheet for this one call, or a reusable persona template the team reruns? (Compounding promotes decision-context coverage and the full follow-up ladder, since both amortize across calls and personas; one-off keeps the bare spine.)
• Effort ceiling: how many of the call's minutes are yours to spend on questions, how much rehearsal will the rep actually do, and how much of the buyer's patience can you spend? (A low ceiling deletes the decision-context stage outright and caps every ladder at two rungs.)

Workflow

1. Run the Interview; collect every answer before writing a question.
2. Gather context. If you can browse the web, research the company and persona; otherwise work from the user's notes. Never fabricate account facts - research answers situation questions so the call doesn't have to.
3. Write 2-3 candidate pain hypotheses from the inputs, each stated as a hypothesis to test on the call. Confirm with the user which to prioritize.
4. Pick the coverage lens layered on the spine below. Call minutes are the budget every lens is priced in, and the buyer's patience is spent alongside them - a lens that costs more goodwill is expensive even though it is free to the rep.

• efficiency: GAP > Sandler > SPIN > MEDDPICC
• value: GAP > MEDDPICC > Sandler > SPIN
• effort: MEDDPICC > Sandler == GAP > SPIN
• Default GAP: about an hour of per-deal rehearsal and two impact questions - buys the figure in the prospect's own words that the close, the recap, and every downstream deal skill run on.
• Sandler: costs the same hour and the same handful of minutes inside a stage already open, the genuine tie on effort with GAP - buys depth on one pain instead of a number, so it ranks second.
• SPIN: near-zero on both axes - it only re-sequences questions already written, and the spine has absorbed its ordering. Take it free, never budget for it.
• Starved: MEDDPICC's decision context. High value in a real buying group, highest effort - a whole extra stage, re-gathered per persona across the cycle - so efficiency buries it, and reps ship sheets that quantify a pain nobody can approve. Promote it to first whenever the buying group runs past a single economic buyer, or the buyer is regulated. Gather its elements as questions only; scoring belongs to the scorecard skill.
• Delete, never demote:
• A mandated methodology removes the other three from the sheet and maps every stage to its own vocabulary.
• A transactional or B2C deal removes the decision-context stage outright.
• A ruled-out lens parked at the bottom reappears as scope mid-call.
• Re-rank before writing a question - this order is a default, not a law, and it moves with who runs the call and who answers:
• Fifteen SDR minutes leave only the top of the line.
• An hour with a practitioner promotes Sandler to par.
• An executive promotes whichever lens reaches a figure fastest and deletes the rest.

1. Size the set to the call: roughly one substantive question plus its follow-ups per 3-4 minutes of questioning time; fewer and deeper for executives. Spend those minutes in step 4's order - the lens at the head of the efficiency line gets its questions first, and whatever the budget cannot fund is cut from the tail, never trimmed evenly across all four. Published "ideal question counts" are correlational and internally inconsistent, so size by call length, never a magic number.
2. Draft from references/question-bank.md, sequenced per the spine, one stage at a time. Attach a 2-3 rung follow-up ladder and a listen-for note to each primary question.
3. Add branch triggers (below) and the do-not-ask list from the question bank.
4. Assemble into the call sheet from references/call-sheet-template.md.
5. Run the Quality gate; iterate - rewrite and re-check - until every item passes.
6. Deliver, and remind the user: the sheet is a map, not a script - follow the prospect's answers, use the branches.
7. If your harness has persistent memory, memorize the persona, the hypotheses that proved true, and which questions produced signal - the next set for the same persona starts warmer. Otherwise hand the user a short recap to keep.

The pain → impact → urgency spine

Every question belongs to a stage. Every stage has an exit condition. Movement is one-way - never retreat to logistics before the spine is walked.