Claude Skill

Discovery Call Prep

Generates a 1-page brief for a B2B discovery call — pain hypothesis, buying committee, opening questions.

Download skill (.zip)Or download whole pack

What it does

Given a prospect company and your context, this skill produces a structured pre-call brief: their likely pain, who else matters in the buying committee, the first 3 questions to ask, and disqualifiers that mean it's not a fit. Designed to fit on one printed page.

When to use

✓You have a discovery call within 24 hours and haven't prepped
✓You're entering a vertical or company size you don't know well
✓You want to walk into the call with a hypothesis to test, not a blank slate

When not to use

✗You already know the customer well — this is for first-touch discovery
✗It's a follow-up call, not initial discovery

Install

Download the .zip, then unzip into your Claude skills folder.

mkdir -p ~/.claude/skills
unzip ~/Downloads/discovery-call-prep.zip -d ~/.claude/skills/

# Restart Claude Code session.
# Skill is now available — Claude will use it when relevant.

SKILL.md

---
name: discovery-call-prep
description: Generates a structured 1-page pre-call brief for B2B discovery calls — pain hypothesis, buying committee, first questions, disqualifiers.
---

# Discovery Call Prep

When the user has a discovery call coming up and provides company + role context, generate a structured brief they can read in 90 seconds.

## Required input

- **Prospect company** (name + 1-line description or URL)
- **Prospect role** (title + how senior — IC, manager, director, exec)
- **What the user sells** (1 sentence)
- Anything they already know about the prospect

## Output structure

Format as a clean 1-page brief. Use these sections in order:

### 1. Likely pain (1 paragraph)
Based on the company stage, role, and any signals, what's the probable problem? Be specific. Avoid generic "they want to grow."

### 2. Buying committee (3-5 people)
Who else likely matters in this decision? For each:
- Title
- Their probable concern
- How they'd block or champion the deal

### 3. First 3 questions to ask
Open-ended. Get them talking about THEIR problem, not pitch-prep about your solution.
Number them. Order matters — start broad, narrow as you learn.

### 4. Disqualifiers
2-3 signals during the call that mean "this isn't a fit." So the user can exit gracefully instead of forcing it.

### 5. What NOT to do on this call
Behaviors that kill discovery — premature pitching, leading questions, "are you the decision-maker?"

## Constraints

- Total output should fit on one printed page (~400 words)
- No vague advice ("listen actively")
- If the user gives weak input (no role specified, no company info), ask for it before drafting
- If the prospect is clearly out of ICP, say so and recommend they reschedule strategically

Example prompts

Once installed, try these prompts in Claude:

Discovery call tomorrow with VP Engineering at Datacore (mid-market data infrastructure). We sell observability. Help me prep.

Related prompts

Don't want to install a skill? These prompts in /prompts cover similar ground for one-shot use:

sales prompts