mcpField
D
discovery-caller

discovery-caller

github.com/ncklrsMarketing & growth53195 installsUpdated 35w ago
Repository

About discovery-caller

A sales skill for B2B teams that structures discovery calls around preparation, questioning, qualification, and documentation. It emphasizes understanding prospect needs before proposing a solution.

Key features

  1. 01Pre-call research and agenda setting
  2. 02SPIN question frameworks
  3. 03BANT, MEDDIC, SPICED, and CHAMP qualification
  4. 04Pain quantification and stakeholder mapping
  5. 05CRM notes and next-step documentation

Use cases

  1. 01Preparing for a prospect discovery call
  2. 02Probing and quantifying business challenges
  3. 03Qualifying complex opportunities
  4. 04Recording outcomes and arranging next steps

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ncklrs/startup-os-skills --skill discovery-caller

After installing, type/discovery-callerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
_sections.md
closing-nextsteps.md
discovery-competition.md
discovery-flow.md
discovery-pain.md
discovery-stakeholders.md
documentation-crm.md
listening-active.md
preparation-research.md
qualification-bant.md
questions-spin.md

Details

From the project README

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
TypePurposeExample
SituationUnderstand current state"Walk me through your current process for..."
ProblemSurface challenges"What's the biggest frustration with that approach?"
ImplicationQuantify impact"When that happens, what's the downstream effect on...?"
Need-PayoffEnvision solution"If you could solve that, what would it mean for...?"
Qualification Frameworks
FrameworkComponentsBest For
BANTBudget, Authority, Need, TimelineTransactional, lower ACV
MEDDICMetrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, ChampionEnterprise, complex
SPICEDSituation, Pain, Impact, Critical Event, DecisionModern SaaS
CHAMPChallenges, Authority, Money, PrioritizationCustomer-centric
Stakeholder Mapping
                    ┌─────────────────┐
                    │ ECONOMIC BUYER  │
                    │ (Signs check)   │
                    └────────┬────────┘
                             │
              ┌──────────────┼──────────────┐
              │              │              │
     ┌────────▼────────┐     │     ┌────────▼────────┐
     │   CHAMPION      │     │     │   TECHNICAL     │
     │ (Internal sell) │     │     │   EVALUATOR     │
     └─────────────────┘     │     └─────────────────┘
                             │
                    ┌────────▼────────┐
                    │    END USERS    │
                    │  (Day-to-day)   │
                    └─────────────────┘
Discovery Output Metrics
MetricTargetWhy It Matters
Talk ratio<30% rep timeProspect should talk more
Questions asked10-15 per callEnough depth without interrogation
Pain points quantified2-3 minimumNumbers drive urgency
Stakeholders identified3+ rolesMulti-thread the deal
Next step commitment100%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

Comments

Markdown supported