# Start Discovery Call Guide

> Writes a Discovery Call Guide for one person, with an agenda to agree at the start, a few situation questions and more problem, implication and need-payoff questions written for them, room for the cost of doing nothing in their numbers, who else decides and the next step to ask for. Use for "run start-discovery-call-guide", "prep my discovery call", "what do I ask on a first client call", "I have never run a sales conversation", "SPIN questions for this call", "they said they might need help", "help me run a first meeting", part of the Claude Guide for New Founders Pack by 90n.

- Skill: `polar-bear-org/start-discovery-call-guide` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/start-discovery-call-guide`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/start-discovery-call-guide/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/start-discovery-call-guide

---


# Discovery Call Guide

## When To Use
A contact says "we might need help with that", and you have never run a sales conversation. You were always the expert brought into the room after someone else had opened the door. This gives you, for one call, the few questions that let the other person say what the problem costs and what they want to be different.

## When Not To Use
If the call is a friendly catch-up with no problem on the table, use Coffee Chat Prep; bringing this guide would be heavy-handed. After the call, write it up with Discovery Call Recap before any proposal.

## Inputs
- What they said that led to this call, in their words, and how you know them
- What you already know about their situation from public sources and your own history with them
- The length of the call and who will be on it, by role
If you have none of this, I start from the person's name and the reason the call was booked, and mark the output as a first draft.

## Approach
SPIN questioning comes from Huthwaite International's research on what successful sellers ask: situation, problem, implication and need-payoff questions, in roughly that order. The judgement is in the balance: few situation questions, because nobody enjoys reciting what you could have read, and more implication and need-payoff questions, because that is where the other person builds the case in their own words. A senior expert's own failure mode is different from a seller's: you hear the problem in minute five and start solving it for free. The guide keeps you asking.

## Workflow
1. Ask at most three questions: why they agreed to the call, in their words; what you already know; and what you want to be true when the call ends.
2. Draft the opening to agree: the purpose, the time available, and what happens at the end (for instance, deciding together whether a next conversation makes sense). You propose it and ask if they want to add anything.
3. Situation: two or three questions only, on what you could not find out beforehand. If you worked there, cut what you already know and ask what has changed since you left.
4. Problem: three or four questions that surface what is difficult or unsatisfying today. Each is written around what this person is likely to face and marked as your hypothesis.
5. Implication: questions that let them trace the consequences (time, money, risk, people, missed chances) and put the cost of doing nothing in their own numbers. The figure is left blank for the call; I never estimate it.
6. Need-payoff: questions that let them say what solving it would be worth. Then who else is involved in a decision like this, by role, and the next step you will ask for, with a date.
7. Add a "listen for" list and a "do not" list: do not solve it on the call, do not name a price yet, do not agree to "send something" without a date to talk it through.

## Output Format
```markdown
# Discovery Call Guide
With: [name, role] | Date: [date] | Length: [minutes] | How this call came about: [their words]
## Opening to agree
- Purpose: [one line] | At the end: [what we decide together]
## Questions
| Type | Question for this person | Why I ask it (hypothesis or gap) |
|---|---|---|
| Situation | [question] | [what I could not find out] |
| Problem | [question] | [my hypothesis] |
| Implication | [question] | [consequence to explore] |
| Need-payoff | [question] | [value they could state] |
## Cost of doing nothing, in their numbers
[Left blank for the call: what it costs, over what period, by their own figure]
## Who else decides
[Roles to ask about]
## Listen for / do not
- Listen for: [words that show a real priority; signs the decision sits elsewhere; doing it with AI as an alternative]
- Do not: [solve it on the call / name a price / promise a document without a date]
## Decision
[Your name] decides on the call which next step to ask for, and agrees a date with them before it ends.
```

## Done When
- No situation question can be answered from public sources or your own history.
- Implication and need-payoff questions outnumber situation questions.
- The cost of doing nothing is left for the other person to state.
- A next step to ask for is written down.

## Quality Bar
- Questions are written for this person, never a generic list, and asked one at a time.
- Hypotheses are marked as yours, so you test them, not assert them.
- No qualification grid and no rating of the person; this is one conversation.
- Recording a call needs consent, and the rules vary by place: check with a qualified adviser.
- Claude prepares the questions; you run the conversation yourself, and nothing about them is invented.

## Next
Run start-discovery-call-recap (Discovery Call Recap) the same day, to play the call back before you write anything else.

## About the makers

This 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).

