# Frac Discovery Questions

> Prepares a one-page question guide for the scoping call of a fractional engagement, covering the outcome, what it is worth in the company's own figures, the cost of waiting, the alternatives and who decides what today, with a "listen for" column, an answer grid left blank for the CEO's words and the gaps to follow up. Use for "run frac-discovery-questions", "what should I ask on the scoping call", "discovery call questions for a fractional role", "they said send me a proposal", "find out who decides", "what is this seat worth to them", "questions before I scope the engagement", part of the Claude for Fractional Leaders Pack by 90n.

- Skill: `polar-bear-org/frac-discovery-questions` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/frac-discovery-questions`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/frac-discovery-questions/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/frac-discovery-questions

---


# Engagement Discovery Questions

## When To Use
The scoping call ends with "send me a proposal" and you still do not know the outcome or who decides. You leave with a clear picture of their org chart and no idea what the seat is worth to them, what they would do without you, or whether the founder will let go of a single decision. Run it before the call, and again after it to sort what the CEO said from what you assumed.

## When Not To Use
If the engagement is signed and you are interviewing the team, run First 30 Days Diagnostic. If you already have the outcome, its worth and the decision rights in the CEO's words, go straight to Good-Better-Best Engagement Options.

## Inputs
- What you know so far: the CEO's message, the role description if one exists, notes from earlier calls, each with where you heard it
- Who will be on the call, by role, and how long you have
- After the call: your notes, with the CEO's answers as they gave them
If you have none of this, I start from the function and the five question blocks below, and mark the guide as a first draft.

## Approach
SPIN question types from Huthwaite International (situation, problem, implication, need-payoff), with one pricing idea described generically: a seat is worth what the company's next-best alternative costs, plus the value of the difference. The lesson of SPIN for a prepared senior person is to ask few situation questions and spend the call on implications. The failure this prevents is a scoping call that feels warm, ends with "send me something", and leaves you pricing days because you never learned the outcome.

## Workflow
1. Ask, all at once: how long is the call and who is on it; what has the CEO asked for so far, in their words; what do you already know about who decides what in this function today?
2. Draft five blocks in this order, because each rests on the one before: the outcome and how they would measure it; what it is worth in their figures; the cost of waiting another quarter; the alternatives (full-time hire, agency, adviser, in house with AI, nothing) and what each would cost them; who decides what today, and which decisions the founder would hand over.
3. Keep situation questions to what you could not read beforehand. Write more implication questions than any other type: what the gap affects, who feels it, what happens if it continues. Ask for their figure and unit; never offer one.
4. Make every question open and neutral. Strip leading ones. The question about their own AI is asked with curiosity, never as a trap.
5. Add a "listen for" entry under each question: the words that would confirm the outcome, and the signs to take seriously before signing (no single outcome, every decision still with the founder, full-time responsiveness expected on part-time days).
6. Lay out the answer grid with the CEO's words column blank. After the call you paste your notes and mark each line stated, inferred or unknown; I sort it and list the gaps worth one follow-up message.

## Output Format
```markdown
# Engagement Discovery Questions
Client: [name or code] · Call: [date, length] · On the call: [roles]
## Questions for this call
| Block | Question | Listen for |
|---|---|---|
| Outcome and measure | [open question] | [their words for done] |
| Worth in their figures | [open question] | [their figure and unit] |
| Cost of waiting | [open question] | [what slips, who feels it] |
| Alternatives, their own AI included | [open question] | [what they tried, what it would cost them] |
| Who decides what today | [open question] | [decisions the founder keeps; signs to take seriously] |
## Answer grid (filled by you after the call)
| Topic | The CEO's words | Their figure, if given | Stated / inferred / unknown |
|---|---|---|---|
| [topic] | [left blank for you] | [left blank for you] | [your mark] |
## Gaps to follow up
1. [question still open] · ask [role]
## Decision
[You] decide by [date] whether there is enough stated to shape options, or which follow-up to send first.
```

## Done When
- The five blocks are covered in order, and implication questions outnumber situation questions
- Every question has a "listen for" entry
- The CEO's words column is blank, or filled only from your notes
- The guide fits on one page and leaves room for the CEO to lead

## Quality Bar
- No question suggests a number, a range or a conclusion
- The company's own AI and a full-time hire are asked about as fair alternatives
- Notes record what was said, never a judgment of the person who said it
- Nothing learned at another client is used to frame a question here
- Answers are the CEO's own words; Claude never fills one in, and you run the call

## Next
Run frac-engagement-options (Good-Better-Best Engagement Options) to turn the answers into three real shapes of the seat.

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

