What is the Discovery Caller used for?

To prepare for discovery calls, guide effective questioning, qualify prospects, map stakeholders, and document findings for CRM and handoffs.

Which frameworks are used?

SPIN for questioning, BANT or MEDDIC for qualification, active listening, stakeholder mapping, and CRM-based documentation.

How does it drive next steps?

Each call ends with a defined next step or disqualification, and notes are captured for the CRM to enable seamless handoff.

discovery-caller

npx machina-cli add skill ncklrs/startup-os-skills/discovery-caller --openclaw

Files (1)

SKILL.md

6.9 KB

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:

Listen more than talk — Aim for 70/30 prospect-to-rep ratio
Quantify everything — Pain without numbers is just complaining
Map the buying committee — One champion doesn't close deals
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

Source

git clone https://github.com/ncklrs/startup-os-skills/blob/main/skills/discovery-caller/SKILL.mdView on GitHub

Overview

Discovery Caller provides strategic guidance for B2B discovery calls, from pre-call prep and SPIN-based questioning to qualification and CRM documentation. It helps identify pain points, map the buying committee, and secure clear next steps.

How This Skill Works

When used, it applies a modular set of guidelines organized into preparation-, questions-, listening-, qualification-, discovery-, and documentation- domains. It leverages SPIN framing, active listening, and budget/authority/need/timeline (BANT) or MEDDIC to drive questioning, note-taking, and CRM handoffs for next steps.

When to Use It

Before a new B2B discovery call to align objectives, agenda, and stakeholders
During prospect qualification to assess budget, authority, need, and timeline
When identifying and quantifying pain points with SPIN-style questions
When mapping the buying committee and establishing a decision-making plan
When documenting CRM notes and scheduling next steps for handoff

Quick Start

Step 1: Prepare with pre-call research, define hypotheses, and list potential stakeholders
Step 2: Run SPIN-driven discovery, actively listen, and take structured notes
Step 3: Qualify (budget/authority/need/timeline) and document findings in CRM; schedule next steps

Best Practices

Listen more than you speak (aim for a 70/30 prospect-to-rep ratio)
Quantify pain with metrics to convert qualitative complaints into business value
Lead with SPIN: Situation, Problem, Implication, Need-Payoff to uncover real needs
Map stakeholders and identify the economic buyer and influencers
Close with clear next steps and thorough CRM documentation

Example Use Cases

Open with: 'Here’s our agenda and the time we have. Is there anything you’d like added before we begin?'
Ask SPIN questions: 'Walk me through your current process for X' (Situation) followed by 'What’s the biggest friction you face?' (Problem)
Quantify impact: 'If this issue persists, what is the annual cost or risk to your business?'
Identify champions: 'Who else is involved in the final decision, and what criteria will they use?'
Document in CRM: capture pain points with numbers, stakeholders, timeline, and schedule the next meeting

Frequently Asked Questions

Add this skill to your agents