Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component...
npx skills add ncklrs/startup-os-skills --skill "discovery-caller"
Install specific skill from multi-skill repository
# 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.
# SKILL.md
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 buildingquestions-*β SPIN framework, situational, implication questionslistening-*β Active listening, note-taking, clarification techniquesqualification-*β Budget, authority, need, timeline (BANT) and modern alternativesdiscovery-*β Pain identification, stakeholder mapping, competitiondocumentation-*β 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
# Supported AI Coding Agents
This skill is compatible with the SKILL.md standard and works with all major AI coding agents:
Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.