discovery-caller
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.
What this skill does
# 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
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.