home / skills / ncklrs / startup-os-skills / discovery-caller

discovery-caller skill

/skills/discovery-caller

This skill guides you through B2B discovery calls, framing questions, quantifying pain, mapping stakeholders, and documenting outcomes to accelerate

npx playbooks add skill ncklrs/startup-os-skills --skill discovery-caller

Review the files below or copy the command above to add this skill to your agents.

Files (12)
SKILL.md
6.9 KB
---
name: discovery-caller
description: Expert discovery call strategist for B2B sales. Use when preparing for discovery calls, qualifying prospects, asking effective questions, identifying pain points, mapping stakeholders, or documenting findings. Covers SPIN selling, active listening, budget/timeline qualification, competition discovery, and CRM documentation. Use for sales qualification, needs analysis, and discovery call execution.
---

# Discovery Caller

Strategic discovery call expertise for B2B sales teams — from preparation and question frameworks to qualification and documentation.

## Philosophy

Discovery isn't about pitching. It's about **understanding deeply** before you ever propose a solution.

The best discovery calls:
1. **Listen more than talk** — Aim for 70/30 prospect-to-rep ratio
2. **Quantify everything** — Pain without numbers is just complaining
3. **Map the buying committee** — One champion doesn't close deals
4. **Earn the next step** — Every call ends with commitment or disqualification

## How This Skill Works

When invoked, apply the guidelines in `rules/` organized by:

- `preparation-*` — Pre-call research, agenda setting, hypothesis building
- `questions-*` — SPIN framework, situational, implication questions
- `listening-*` — Active listening, note-taking, clarification techniques
- `qualification-*` — Budget, authority, need, timeline (BANT) and modern alternatives
- `discovery-*` — Pain identification, stakeholder mapping, competition
- `documentation-*` — CRM notes, next steps, handoff

## Core Frameworks

### The Discovery Call Arc

```
┌─────────────────────────────────────────────────────────────────────┐
│                         DISCOVERY CALL ARC                          │
├─────────────────────────────────────────────────────────────────────┤
│                                                                     │
│  OPEN (5 min)         BUILD RAPPORT                                 │
│  ─────────────        Set agenda, confirm time                      │
│                                                                     │
│  SITUATION (10 min)   UNDERSTAND CONTEXT                            │
│  ─────────────────    Current state, tools, process                 │
│                                                                     │
│  PROBLEM (15 min)     UNCOVER PAIN                                  │
│  ─────────────────    Challenges, frustrations, gaps                │
│                                                                     │
│  IMPLICATION (10 min) QUANTIFY IMPACT                               │
│  ─────────────────    Cost of inaction, business impact             │
│                                                                     │
│  NEED-PAYOFF (5 min)  VISION OF SUCCESS                             │
│  ─────────────────    Ideal future state, ROI potential             │
│                                                                     │
│  CLOSE (5 min)        NEXT STEPS                                    │
│  ─────────────        Commitment, stakeholders, timeline            │
│                                                                     │
└─────────────────────────────────────────────────────────────────────┘
```

### SPIN Question Framework

| Type | Purpose | Example |
|------|---------|---------|
| **Situation** | Understand current state | "Walk me through your current process for..." |
| **Problem** | Surface challenges | "What's the biggest frustration with that approach?" |
| **Implication** | Quantify impact | "When that happens, what's the downstream effect on...?" |
| **Need-Payoff** | Envision solution | "If you could solve that, what would it mean for...?" |

### Qualification Frameworks

| Framework | Components | Best For |
|-----------|------------|----------|
| **BANT** | Budget, Authority, Need, Timeline | Transactional, lower ACV |
| **MEDDIC** | Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion | Enterprise, complex |
| **SPICED** | Situation, Pain, Impact, Critical Event, Decision | Modern SaaS |
| **CHAMP** | Challenges, Authority, Money, Prioritization | Customer-centric |

### Stakeholder Mapping

```
                    ┌─────────────────┐
                    │ ECONOMIC BUYER  │
                    │ (Signs check)   │
                    └────────┬────────┘
                             │
              ┌──────────────┼──────────────┐
              │              │              │
     ┌────────▼────────┐     │     ┌────────▼────────┐
     │   CHAMPION      │     │     │   TECHNICAL     │
     │ (Internal sell) │     │     │   EVALUATOR     │
     └─────────────────┘     │     └─────────────────┘
                             │
                    ┌────────▼────────┐
                    │    END USERS    │
                    │  (Day-to-day)   │
                    └─────────────────┘
```

### Discovery Output Metrics

| Metric | Target | Why It Matters |
|--------|--------|----------------|
| **Talk ratio** | <30% rep time | Prospect should talk more |
| **Questions asked** | 10-15 per call | Enough depth without interrogation |
| **Pain points quantified** | 2-3 minimum | Numbers drive urgency |
| **Stakeholders identified** | 3+ roles | Multi-thread the deal |
| **Next step commitment** | 100% | Every call earns an outcome |

## Anti-Patterns

- **Feature dumping** — Pitching before understanding pain
- **Single-threaded** — Only talking to one person
- **Surface-level discovery** — Accepting first answer without going deeper
- **Unquantified pain** — "It's frustrating" without business impact
- **Assumptive qualification** — Guessing budget/timeline instead of asking
- **Weak close** — "I'll send you some info" instead of next meeting booked
- **No preparation** — Showing up without researching the prospect
- **Interrogation mode** — Firing questions without building rapport

Overview

This skill is an expert discovery call strategist for B2B sales reps and teams. It prepares reps to run disciplined, outcome-focused discovery calls that qualify prospects, uncover quantified pain, map stakeholders, and earn clear next steps. Use it to structure conversations, choose questions, and capture CRM-ready findings.

How this skill works

When invoked, the skill guides preparation, live questioning, active listening, qualification, stakeholder mapping, and documentation. It applies SPIN questioning, implication-focused follow-ups, modern qualification frameworks (BANT, MEDDIC, SPICED, CHAMP), and a repeatable call arc to drive consistent outcomes. It also produces CRM-friendly notes and next-step recommendations.

When to use it

  • Preparing for a B2B discovery call or qualification meeting
  • Designing call agendas and pre-call research checks
  • Uncovering and quantifying customer pain and ROI levers
  • Mapping buying committees and identifying champions
  • Determining budget, timeline, decision process, and competition

Best practices

  • Aim for a 70/30 prospect-to-rep talk ratio; ask 10–15 targeted questions per call
  • Quantify pain: capture metrics, costs, frequency, and business impact
  • Map at least 3 stakeholder roles (economic buyer, champion, technical evaluator)
  • Close every call with a clear next step or qualified disqualification
  • Avoid feature-dumping; surface implications before discussing solutions

Example use cases

  • Prepare a tailored call agenda with hypotheses and research prompts
  • Run a discovery call using the Discovery Call Arc: Open → Situation → Problem → Implication → Need-Payoff → Close
  • Qualify opportunities with BANT for transactional deals or MEDDIC/SPICED for enterprise deals
  • Create CRM notes that summarize pains, metrics, stakeholders, risks, and agreed next steps
  • Train new reps on active listening, clarifying questions, and quantifying impact

FAQ

What if the prospect avoids giving numbers for impact?

Use layered implication questions: start with frequency and scope, then translate qualitative pain into operational or financial terms (time lost, error rates, revenue at risk). Offer ranges to help them approximate.

How many stakeholders should I aim to identify on the first call?

Target identifying roles for at least three stakeholders (champion, economic buyer, technical evaluator) and who influences timeline and budget. If you can’t, make stakeholder mapping an explicit next step.