Discovery Call Questions
When To Use
You come off the call knowing how the client's process works today and nothing about why they would pay to change it. Nobody mentioned a consequence, an owner or a date. Run this before the call to decide which questions, in which order, reach the cost of the problem and the way the decision gets made within the time you have.
When Not To Use
If the client has already given figures and you need to lay out what waiting costs, use Cost of Inaction. If you need the note the client reads beforehand, use Discovery Call Agenda.
Inputs
- The questions from your brief reading and your pre-call hypotheses, if you have them
- The length of the call and who attends, by role
- What you already know, with where you heard it
If you have none of this, I start from the client's name, the subject and the call length, and mark the page as a first draft.
Approach
SPIN questions come from Huthwaite International (huthwaiteinternational.com/spin-selling): Situation, Problem, Implication, Need-payoff. The lesson for someone who has prepared is to ask very few situation questions, since research answers most of them and senior buyers tire quickly, and to spend the call on implications. The failure it prevents is the call that ends in "send me a proposal" with no cost, no owner and no reason to act. I prepare the page; you run the conversation and follow the client, not the paper.
Workflow
- Ask, in one go: how long is the call, and how much of it is yours? Which hypothesis or gap matters most? Who will be there, by role?
- Start with the gaps the brief left open (budget, decision owner, deadline, what was tried), asked plainly. Without these nothing later can be scoped.
- Situation: only what research could not tell you. Keep it to two or three, and delete any that their website already answers.
- Problem: one per hypothesis, asked about difficulty and not about existence. "Where does [process] slow down today?" opens more than "is [process] a problem?"
- Implication: for each problem, what it touches, who feels it, what it costs, what happens if it carries on. Write more of these than of any other type; urgency comes from here. Ask for their figure and its unit, and never offer one.
- Need-payoff: what solving it would make possible, in their words; the answer becomes the opening of the proposal. Then the decision block (who else decides, how a similar decision went last time, what could stop this) and a "listen for" line under every question. One page; you pick and adapt.
Output Format
# Discovery Question Page
Client: [name] · Call: [date, length] · In the room: [roles]
## Open gaps first
| Question | Listen for |
|---|---|
| [gap question] | [what would answer it] |
## Situation, problem, implication, need-payoff
| Type | Question | Listen for | Tests hypothesis |
|---|---|---|---|
| Situation | [only if research could not answer] | [fact] | [n] |
| Problem | [question] | [their words for the difficulty] | [n] |
| Implication | [question] | [their figure and unit, who feels it] | [n] |
| Need-payoff | [question] | [the value in their words] | [n] |
## Decision process
| Question | Listen for |
|---|---|
| [who else decides / last time / what could stop this] | [role, step, date] |
## Decision
[You] choose which questions to take into the call by [call date]; what goes into the proposal comes from [client role]'s answers, not from this page.
Done When
- Implication questions outnumber situation questions
- Every question has a "listen for" line and the decision block is there
- It fits one page and leaves room for the client to lead
Quality Bar
- A situation question with a public answer does not make the page
- Questions are open and neutral, and none carries a figure or a range inside it
- Nothing about anyone's private life or personality
- The page is preparation only; I put no answer in the client's mouth, and you run the conversation.
Next
Run firm-cost-of-inaction (Cost of Inaction) to set up how you will capture what staying put costs them.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: firm-discovery-call-questions3description: Prepares a one-page question guide by SPIN type, with few situation questions, more problem, implication and need-payoff ones, the brief's open gaps asked first, a decision process block and what to listen for under each question. Use for "run firm-discovery-call-questions", "what do I ask on the discovery call", "write my discovery questions", "SPIN questions for this client", "how do I find out who decides", "my calls never reach what the problem costs", "questions for the first client meeting", part of the Claude for Consultants · Team in Claude Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/firm-discovery-call-questions6---78# Discovery Call Questions910## When To Use11You come off the call knowing how the client's process works today and nothing about why they would pay to change it. Nobody mentioned a consequence, an owner or a date. Run this before the call to decide which questions, in which order, reach the cost of the problem and the way the decision gets made within the time you have.1213## When Not To Use14If the client has already given figures and you need to lay out what waiting costs, use Cost of Inaction. If you need the note the client reads beforehand, use Discovery Call Agenda.1516## Inputs17- The questions from your brief reading and your pre-call hypotheses, if you have them18- The length of the call and who attends, by role19- What you already know, with where you heard it20If you have none of this, I start from the client's name, the subject and the call length, and mark the page as a first draft.2122## Approach23SPIN questions come from Huthwaite International (huthwaiteinternational.com/spin-selling): Situation, Problem, Implication, Need-payoff. The lesson for someone who has prepared is to ask very few situation questions, since research answers most of them and senior buyers tire quickly, and to spend the call on implications. The failure it prevents is the call that ends in "send me a proposal" with no cost, no owner and no reason to act. I prepare the page; you run the conversation and follow the client, not the paper.2425## Workflow261. Ask, in one go: how long is the call, and how much of it is yours? Which hypothesis or gap matters most? Who will be there, by role?272. Start with the gaps the brief left open (budget, decision owner, deadline, what was tried), asked plainly. Without these nothing later can be scoped.283. Situation: only what research could not tell you. Keep it to two or three, and delete any that their website already answers.294. Problem: one per hypothesis, asked about difficulty and not about existence. "Where does [process] slow down today?" opens more than "is [process] a problem?"305. Implication: for each problem, what it touches, who feels it, what it costs, what happens if it carries on. Write more of these than of any other type; urgency comes from here. Ask for their figure and its unit, and never offer one.316. Need-payoff: what solving it would make possible, in their words; the answer becomes the opening of the proposal. Then the decision block (who else decides, how a similar decision went last time, what could stop this) and a "listen for" line under every question. One page; you pick and adapt.3233## Output Format34```markdown35# Discovery Question Page36Client: [name] · Call: [date, length] · In the room: [roles]37## Open gaps first38| Question | Listen for |39|---|---|40| [gap question] | [what would answer it] |41## Situation, problem, implication, need-payoff42| Type | Question | Listen for | Tests hypothesis |43|---|---|---|---|44| Situation | [only if research could not answer] | [fact] | [n] |45| Problem | [question] | [their words for the difficulty] | [n] |46| Implication | [question] | [their figure and unit, who feels it] | [n] |47| Need-payoff | [question] | [the value in their words] | [n] |48## Decision process49| Question | Listen for |50|---|---|51| [who else decides / last time / what could stop this] | [role, step, date] |52## Decision53[You] choose which questions to take into the call by [call date]; what goes into the proposal comes from [client role]'s answers, not from this page.54```5556## Done When57- Implication questions outnumber situation questions58- Every question has a "listen for" line and the decision block is there59- It fits one page and leaves room for the client to lead6061## Quality Bar62- A situation question with a public answer does not make the page63- Questions are open and neutral, and none carries a figure or a range inside it64- Nothing about anyone's private life or personality65- The page is preparation only; I put no answer in the client's mouth, and you run the conversation.6667## Next68Run firm-cost-of-inaction (Cost of Inaction) to set up how you will capture what staying put costs them.6970## About the makers7172This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).