Discovery Caller

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

Qualification Frameworks

Stakeholder Mapping

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

Discovery Output Metrics

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

1. Discovery Preparation (preparation)

Impact: CRITICAL Description: Pre-call research, hypothesis building, agenda setting, and account intelligence. The work before the call determines the call's success.

2. Question Frameworks (questions)

Impact: CRITICAL Description: SPIN methodology, situation/problem/implication/need-payoff questions, and techniques for going deeper.

3. Active Listening (listening)

Impact: HIGH Description: Listening techniques, clarification methods, note-taking, and reading between the lines.

4. Qualification (qualification)

Impact: CRITICAL Description: Budget, timeline, authority, and need qualification. Identifying deal-breakers early.

5. Discovery & Mapping (discovery)

Impact: HIGH Description: Pain point identification, stakeholder mapping, competition discovery, and buying process understanding.

6. Documentation (documentation)

Impact: MEDIUM-HIGH Description: CRM notes, call summaries, handoff documentation, and next steps tracking.

Next Steps and Commitment

Impact: CRITICAL

Every discovery call must end with a clear next step and commitment. "I'll send you some info" is not a next step - it's a dead deal walking.

The Next Step Hierarchy

STRONGEST COMMITMENT:
┌──────────────────────────────────────────────────────────────┐
│ Calendar invite sent and accepted for specific next meeting │
└──────────────────────────────────────────────────────────────┘
                           ↓
┌──────────────────────────────────────────────────────────────┐
│ Verbal agreement to specific date/time for next meeting     │
└──────────────────────────────────────────────────────────────┘
                           ↓
┌──────────────────────────────────────────────────────────────┐
│ Agreement to specific next action with timeline             │
└──────────────────────────────────────────────────────────────┘
                           ↓
┌──────────────────────────────────────────────────────────────┐
│ Vague agreement to "follow up next week"                    │
└──────────────────────────────────────────────────────────────┘
                           ↓
WEAKEST COMMITMENT:
┌──────────────────────────────────────────────────────────────┐
│ "Send me some info" / No specific next step                 │
└──────────────────────────────────────────────────────────────┘

Strong vs. Weak Next Steps

The Commitment Close

Reserve 5 minutes at the end of every call for closing.

Framework: Summarize → Confirm → Propose → Lock

SUMMARIZE:
"Let me make sure I captured everything. You're dealing with [pain 1]
and [pain 2], which is costing roughly [quantified impact]. Your
priority is [goal] and you're looking to have something in place
by [timeline]. Does that capture it?"

CONFIRM:
"Does it make sense to keep this conversation going?"
[If yes, continue. If hesitation, address it.]

PROPOSE:
"Based on what you shared, I think a good next step would be
[specific next step] with [specific people]. How does that sound?"

LOCK:
"Great. I have availability on [Day 1] at [Time] or [Day 2] at [Time].
Which works better for you?"
[Send invite while still on call if possible]

Next Step Options by Stage

Getting Calendar Commitment

The Live Calendar Technique:

"I have my calendar up right now. I see I have Tuesday at 2pm or
Thursday at 10am available. Which works better for your schedule?"
[Wait for response]
"Great, I'm sending the invite right now. Can you confirm you received it?"

The Assumptive Close:

"It sounds like a demo would be valuable. Let me pull up my calendar -
what does your availability look like next Tuesday or Wednesday?"

The Alternative Close:

"Would it work better to do the technical deep-dive first, or would
you rather bring in your VP for a higher-level conversation?"

Handling Next Step Objections

The Mutual Action Plan

For complex deals, establish a mutual action plan:

MUTUAL ACTION PLAN: [Company Name]

Goal: [Customer] implementing [Product] by [Date]

DATE        | ACTION                  | OWNER       | STATUS
------------|-------------------------|-------------|--------
Jan 15      | Discovery call          | Both        | Complete
Jan 22      | Technical deep-dive     | [Tech Lead] | Scheduled
Jan 29      | Demo with VP Eng        | [Rep]       | Pending
Feb 5       | Trial kickoff           | Both        | Pending
Feb 19      | Trial review            | Both        | Pending
Feb 26      | Proposal review         | [Rep]       | Pending
March 1     | Contract review         | [Legal]     | Pending
March 15    | Go-live                 | [Customer]  | Pending

Dependencies:
- Trial requires security review (scheduled Jan 25)
- VP approval needed before proposal

Risks:
- Budget approval timeline unclear

Testing Commitment

Commitment tests during the call:

"If what you see in the demo addresses your concerns, what would
be the next step from there?"

"Assuming this looks like a fit, what would the decision
process look like?"

"What would need to happen for you to move forward this quarter?"

"Is there anything that could prevent this from happening?"

Reading commitment signals:

Ending the Call Strong

Good call endings:

"This was really valuable. Here's what we agreed to:
1. I'll send the case study by end of day
2. You'll share with your security team
3. We're meeting Tuesday at 2pm with the broader group
4. I'm sending the invite now - please accept when you get it.
Sound right?"

Bad call endings:

"Okay, well, let me know if you have questions."

"I'll send you some stuff."

"Good chatting, talk soon."

"Let me know when you're ready to move forward."

Follow-Up Cadence

Recap Email Template:

Subject: Recap: [Company] + [Your Company] Discovery Call

Hi [Name],

Thanks for the great conversation today. Here's what I captured:

KEY TAKEAWAYS:
- [Pain point 1 with quantified impact]
- [Pain point 2 with quantified impact]
- [Timeline/urgency driver]

AGREED NEXT STEPS:
- [Action 1] - Owner: [Name] - By: [Date]
- [Action 2] - Owner: [Name] - By: [Date]
- [Meeting scheduled] - [Date/Time] - Attendees: [Names]

ATTACHED:
- [Relevant document 1]
- [Relevant document 2]

Please let me know if I missed anything. Looking forward to
[next step] on [date].

Best,
[Name]

Anti-Patterns

• No close attempt — Ending call without asking for next step
• Accepting vague answers — "Let's talk next week" without specifics
• Not sending invite live — Losing momentum after call
• Single-action next step — "I'll send info" without follow-up meeting
• No recap email — Verbal agreements get forgotten
• Chasing instead of leading — "Let me know when you're free" vs proposing times

Competitive Discovery

Impact: HIGH

Knowing your competition in a deal changes everything - your positioning, urgency, and strategy. Discover early, differentiate strategically.

Why Competitive Discovery Matters

WITH COMPETITION:                  WITHOUT COMPETITION:
- Faster decision timeline         - Slower, less urgent
- Forced comparison               - Evaluated in isolation
- Higher risk of loss             - Lower risk
- Differentiation critical        - Features focus
- Price pressure                  - Value conversation

Questions to Uncover Competition

Direct questions:

"Are you evaluating any other solutions alongside us?"

"Who else is on your shortlist?"

"What alternatives have you looked at?"

"Is there an incumbent solution you're comparing us to?"

Indirect questions:

"What does your research process look like so far?"

"What other approaches are you considering for solving this?"

"How did you hear about us and who else came up in your research?"

"Have you seen any demos or had conversations with other vendors?"

Timing questions:

"Where are you in conversations with other vendors?"

"When are you looking to make a final decision?"

"Are you at a similar stage with other solutions?"

Competitive Landscape Framework

Competition Response Matrix

                    KNOWN COMPETITOR?
                    YES              NO
                ┌─────────────┬─────────────┐
EARLY IN        │ COMPETE     │ DISCOVER    │
EVALUATION      │ Differentiate│ Ask questions│
                │ early        │              │
                ├─────────────┼─────────────┤
LATE IN         │ DEFEND      │ SUSPICIOUS  │
EVALUATION      │ May be       │ May be      │
                │ behind       │ hiding info  │
                └─────────────┴─────────────┘

When They're Evaluating Competitors

Discovery questions:

"What criteria are you using to evaluate solutions?"

"What's most important to you in making this decision?"

"Where do you see the biggest differences between options?"

"What would make one solution stand out over another?"

"What concerns do you have about each option you're considering?"

Positioning questions:

"Based on what you've seen so far, where do you think we might
have an advantage?"

"Is there anything you've seen elsewhere that you wish we had?"

"What would you want to see to feel confident in choosing us?"

Competitive Differentiation Conversation

Framework: Acknowledge → Bridge → Differentiate

Acknowledge: "Yes, [Competitor] is a solid company and I understand
why they're on your list."

Bridge: "The key difference I've seen with customers who choose
us over them..."

Differentiate: "Is that [specific differentiator] matters when
[specific use case]. How important is that for you?"

Good differentiation:

"Where we see customers choose us over [Competitor] is when they
need [specific capability]. For example, [Customer X] came to us
specifically because [reason]. How relevant is that to your situation?"

Bad differentiation:

"They're not as good as us." (No specifics)

"Their product is buggy." (Negative, unsubstantiated)

"We're the market leader." (Irrelevant to their needs)

"Let me tell you everything wrong with them." (Comes across desperate)

Handling the "We're Looking at Others" Response

Positive framing:

Prospect: "We're also looking at HashiCorp and AWS Secrets Manager."

Rep: "That makes sense - both solid options. I'm curious, what drew
you to include us in the evaluation? Understanding that helps me
focus on what's most relevant for you."

Going deeper:

"What criteria matter most to you in comparing these options?"

"Have you had a chance to see demos of both yet?"

"Where do you see the biggest differences so far?"

"Is there a front-runner at this point, or are you still
gathering information?"

Status Quo Competition

Often the biggest competitor is "doing nothing."

Discovery questions:

"What happens if you don't solve this in the next 6 months?"

"What's keeping this from being a higher priority?"

"What would need to change for this to become urgent?"

"Have you tried to solve this before? What happened?"

Creating urgency:

"Based on the $150K annual cost we calculated, every month you
wait is roughly $12K. What would need to be true for this to
become a priority this quarter?"

DIY Competition (Build vs. Buy)

Discovery questions:

"Is building a solution in-house on the table?"

"What would it take to build this internally?"

"Have you estimated the time and cost to build?"

"Who would maintain it long-term?"

Build vs. Buy Comparison:

Positioning against DIY:

"Some companies do consider building. What we typically see is that
the initial build takes 6+ months, then requires 1-2 engineers
maintaining it forever. When you factor in opportunity cost -
what else those engineers could build - it's usually 3-5x the
cost of buying. Have you done that calculation?"

Competitive Intelligence Tracking

After every call, document:

COMPETITIVE INTEL: [Company Name]

Competitors mentioned: [HashiCorp Vault, AWS Secrets Manager]

Stage with competitors:
- HashiCorp: Had one demo, scheduling technical deep-dive
- AWS: Researching, no demo yet

Decision criteria shared:
1. Ease of use
2. Integration with existing stack
3. Price

Differentiators that resonate:
- Our developer experience
- Faster implementation

Concerns about us:
- Less known brand than competitors

Next steps:
- Send competitive one-pager
- Prep for technical deep-dive against HashiCorp

Competitive Battlecard Template

COMPETITOR: [Name]
Last updated: [Date]

OVERVIEW:
- What they do: [Description]
- Target market: [Who they sell to]
- Pricing model: [How they charge]

WHERE THEY WIN:
- [Strength 1]
- [Strength 2]

WHERE WE WIN:
- [Our advantage 1]
- [Our advantage 2]

COMMON OBJECTIONS:
- "[Competitor] is bigger" → Response
- "[Competitor] is cheaper" → Response

LANDMINE QUESTIONS:
- Ask about [their weakness area]
- Ask about [their limitation]

CUSTOMER PROOF:
- [Customer X] chose us over them because [reason]

Anti-Patterns

• Ignoring competition — "We don't have competitors" (unrealistic)
• Badmouthing competitors — Makes you look insecure
• Not asking — Assuming you know who they're evaluating
• Generic differentiation — "We're better" without specifics
• Competing on price alone — Race to the bottom
• Late discovery — Finding out about competitor in negotiation

Discovery Call Structure and Flow

Impact: CRITICAL

A well-structured discovery call feels like a conversation, not an interrogation. The right flow builds rapport, uncovers insight, and earns the next step.

The Discovery Call Arc

TIME:    0min        5min        15min       30min       40min       45min
         │           │           │           │           │           │
         ▼           ▼           ▼           ▼           ▼           ▼
     ┌───────────────────────────────────────────────────────────────────┐
     │ OPEN │ SITUATION │   PROBLEM/PAIN   │ IMPLICATION │ CLOSE       │
     │      │           │                  │ NEED-PAYOFF │             │
     └───────────────────────────────────────────────────────────────────┘
         │           │           │           │           │           │
         ▼           ▼           ▼           ▼           ▼           ▼
      Rapport     Context    Deep Dive    Quantify    Next Steps
      Agenda      Current    Challenges   Impact      Commitment
      Time        State      Pain Points  Vision

Phase-by-Phase Breakdown

Phase 1: Opening (5 minutes)

Goals:

• Build rapport
• Set agenda and expectations
• Confirm available time

Script framework:

"Hi [Name], thanks for making time today. Before we dive in,
I wanted to confirm - we have 45 minutes, is that still good?

[Confirm time]

Great. Here's what I'd like to accomplish today:
1. Learn about your current situation and what prompted this conversation
2. Understand your key challenges and priorities
3. Determine if there's a fit and discuss potential next steps

Does that work for you? Is there anything specific you'd like to
make sure we cover?"

[Get their input]

"Perfect. To kick things off, I'm curious - what prompted you to
take this meeting today?"

Rapport builders:

• Reference something from research (genuinely)
• Find common ground (mutual connection, shared experience)
• Show genuine curiosity
• Keep it brief - 1-2 minutes max

Phase 2: Situation (10 minutes)

Goals:

• Understand current state
• Establish context for pain
• Identify key players and processes

Key questions:

"Walk me through how your team currently handles [relevant area]."

"What tools and systems are you using today?"

"Who on your team is involved in this process?"

"How long have you been doing it this way?"

Transition to problems:

"That's helpful context. Now I'm curious - what's working well
with your current approach, and what's not working as well?"

Phase 3: Problem/Pain (15 minutes)

Goals:

• Surface specific challenges
• Understand depth and breadth of pain
• Capture emotional indicators

Key questions:

"What's the most frustrating part of your current approach?"

"If you could wave a magic wand and fix one thing, what would it be?"

"What happens when [specific scenario] occurs?"

"Where do things fall through the cracks?"

Deepening techniques:

"Tell me more about that."

"What do you mean by [their term]?"

"Can you give me a specific example?"

"How often does that happen?"

"Who else is affected by that?"

Phase 4: Implication & Need-Payoff (10 minutes)

Goals:

• Quantify impact of problems
• Create urgency
• Have them articulate value of solving

Implication questions:

"When that happens, what's the downstream impact?"

"How much time does your team spend dealing with this?"

"What's at risk if this doesn't get solved?"

"What's the cost to the business?"

Need-payoff questions:

"If you could solve this, what would change for your team?"

"What would it mean for the business to have this fixed?"

"How would that affect [their stated goal]?"

Phase 5: Closing (5-10 minutes)

Goals:

• Summarize understanding
• Confirm fit
• Secure specific next step

Framework:

"Let me make sure I captured everything correctly.

[Summarize situation]
You're currently [situation], and the main challenges are
[pain 1] and [pain 2].

[Summarize impact]
This is costing roughly [quantified impact] and is driving
urgency because of [critical event].

[Summarize need]
What you're looking for is [need/vision].

Did I get that right? Is there anything I missed?

[Confirm]

Based on what you've shared, I think there's a strong fit.
The logical next step would be [specific next step] with
[relevant people].

I have availability [Day 1] at [Time] or [Day 2] at [Time].
Which works better for you?"

Call Time Allocation by Length

Transition Phrases

Opening → Situation:

"To make sure I ask the right questions, can you give me some
context on your current setup?"

Situation → Problems:

"Thanks for that overview. I'm curious - what's working well
and what's challenging about your current approach?"

Problems → Implications:

"That sounds frustrating. Help me understand the impact - when
that happens, what's the ripple effect?"

Implications → Need-Payoff:

"Given the impact you described, what would it look like if
this was completely solved?"

Need-Payoff → Close:

"Based on everything you've shared, here's what I'm thinking..."

Handling Common Flow Disruptions

Pacing Indicators

Going too slow if:

• You're 20 minutes in and still on situation
• Prospect seems impatient or checking time
• Answers becoming shorter

Going too fast if:

• Surface-level answers only
• Haven't uncovered quantified pain
• Prospect seems confused about direction

Adjust by:

• Checking in: "Are we covering the right things?"
• Summarizing: "Let me make sure I've got this right..."
• Redirecting: "I want to make sure we have time for [important area]"

Discovery Call Checklist

Before you close, verify you have:

□ Clear understanding of current situation
□ 2-3 specific pain points identified
□ At least one pain quantified (time, money, risk)
□ Understanding of decision process
□ Key stakeholders identified
□ Timeline and urgency drivers
□ Budget context (if appropriate)
□ Competition awareness
□ Specific next step committed
□ Calendar invite sent

Example Full Call Flow

0:00 - OPEN
"Thanks for making time, Sarah. We have 45 minutes - still good?
Great. I'd love to learn about your situation, understand your
challenges, and see if there's a fit. What brought you to take
this meeting?"

5:00 - SITUATION
"Can you walk me through how your team manages secrets today?"
"What tools are you using?"
"Who's involved in the process?"

15:00 - PROBLEM
"What's the most frustrating part of your current approach?"
"Tell me more about that rotation process."
"What happens when someone leaves the team?"

30:00 - IMPLICATION
"When that happens, what's the business impact?"
"How much engineering time does that consume?"
"What's at risk from a compliance perspective?"

35:00 - NEED-PAYOFF
"If this was solved, what would change for your team?"
"What would that mean for your audit confidence?"

40:00 - CLOSE
"Let me summarize what I heard... does that capture it?"
"Based on this, I think a demo with your security lead makes sense."
"I have Tuesday at 2pm or Thursday at 10am - which works?"

45:00 - END
"Great, sending the invite now. I'll also send a recap email
today. Thanks for your time, Sarah."

Anti-Patterns

• Skipping the open — Diving straight into questions
• Spending too long on situation — 20 minutes of context, no pain
• Not quantifying — Pain points without numbers
• Weak close — "I'll send you some info" instead of next meeting
• Rigid adherence — Following structure over conversation
• No time check — Running over or getting cut off

Pain Point Identification and Quantification

Impact: HIGH

Pain without quantification is just complaining. Quantified pain becomes a business case that drives deals forward.

Pain Discovery Framework

IDENTIFY → EXPLORE → QUANTIFY → VALIDATE

"What's hard?" → "Tell me more" → "What does it cost?" → "Did I get that right?"

Types of Business Pain

The Pain Quantification Ladder

Level 1: AWARENESS
"We have a problem with X"
↓
Level 2: ACKNOWLEDGMENT
"It's frustrating and takes time"
↓
Level 3: QUANTIFIED IMPACT
"It costs us 40 hours/month and $15K"
↓
Level 4: BUSINESS CONSEQUENCE
"We missed our launch deadline because of it"
↓
Level 5: PERSONAL STAKE
"My job depends on solving this"

Goal: Get every key pain point to Level 3 or higher.

Quantification Questions by Pain Type

Time Pain:

"How many hours per week does your team spend on this?"
"Walk me through the process - how long does each step take?"
"If you had to assign a percentage of someone's time to this, what would it be?"
"How many people are involved?"

Money Pain:

"What's the dollar impact when this happens?"
"Have you calculated the cost of [problem]?"
"What are you spending on the current solution/workaround?"
"If an engineer costs $150K loaded, what does 40 hours/month represent?"

Risk Pain:

"What's the worst case if this doesn't get fixed?"
"What happened last time this went wrong?"
"What would a breach/incident/failure cost you?"
"What's at stake from a compliance perspective?"

The ROI Calculation Framework

Quantification Worksheet:

PAIN POINT: Manual secrets rotation

TIME COST:
- Hours per rotation event: 5 hours
- Events per month: 8
- People involved: 2 engineers
- Hourly cost (loaded): $100
- Monthly time cost: 5 x 8 x 2 x $100 = $8,000/month

RISK COST:
- Incidents in last 12 months: 2
- Average incident cost: $25,000
- Annual risk cost: $50,000

TOTAL ANNUAL COST: ($8,000 x 12) + $50,000 = $146,000

→ "So this problem is costing roughly $150K per year between
   time and incidents. Does that align with your estimate?"

Pain Exploration Techniques

The Peel-Back Method:

Surface: "We need better security."
Peel 1: "What specifically about security?"
→ "Secrets management is a mess."

Peel 2: "What do you mean by 'a mess'?"
→ "Engineers are storing credentials in .env files."

Peel 3: "What problems does that cause?"
→ "We've had two leaks this year."

Peel 4: "What happened when those leaks occurred?"
→ "40 hours of emergency rotation, plus stress."

Peel 5: "What did that cost the business?"
→ "About $25K per incident in engineering time alone."

The "What Else?" Technique:

Rep: "What other challenges does this create?"
Prospect: "Well, there's also the audit issue."
Rep: "Tell me about that."
Prospect: "Our auditors flagged it last year..."
→ Uncovered a second pain point

Pain Validation

Confirm understanding:

"Let me make sure I have this right. You're saying [pain] is costing
roughly [amount] and it's created [X] incidents. Is that accurate?"

Prioritize pain:

"Of the challenges you mentioned - [A, B, C] - which is the most
urgent to solve and why?"

Test commitment:

"If you could solve [pain] in the next 30 days, would that be
worth investing time in evaluation?"

Good Pain Discovery Examples

Rep: "What happens when a developer leaves the company?"
Prospect: "It's a nightmare."
Rep: "Tell me more about that."
Prospect: "We have to manually rotate every credential they had access to."
Rep: "How long does that process take?"
Prospect: "Usually a full weekend for two engineers."
Rep: "How often does someone leave?"
Prospect: "About twice a month with our turnover."
Rep: "So roughly 4 engineering-days per month on rotation. At your
engineering cost, that's probably $15-20K monthly. Does that sound right?"
Prospect: "Actually, yeah. I never did that math."

→ Quantified: ~$20K/month in time cost
→ Frequency: Twice monthly
→ Impact: Full weekends of engineering time

Bad Pain Discovery Examples

"Do you have security problems?" (Yes/no, no depth)

"That sounds expensive." (Tells, doesn't ask)

"Let me show you how we solve that." (Jumped to solution)

"Yeah, everyone has that problem." (Dismissed their specific pain)

Pain Documentation Template

PAIN POINT #1: [Title]
- Description: [What's happening]
- Impact: [Quantified cost - time, money, risk]
- Frequency: [How often it occurs]
- Who's affected: [Roles/teams]
- Quote: "[Exact words from prospect]"
- Business consequence: [Downstream effects]
- Current workaround: [How they cope today]

Example:

PAIN POINT #1: Manual Credential Rotation
- Description: Engineers manually rotate secrets when employees leave
- Impact: $20K/month (160 engineering hours @ $125/hr)
- Frequency: 2x monthly
- Who's affected: DevOps team (2-3 engineers each time)
- Quote: "It's a nightmare every time someone leaves"
- Business consequence: Weekend work, risk of incomplete rotation
- Current workaround: Spreadsheet tracking, manual process

Anti-Patterns

• Accepting surface pain — "It's frustrating" without quantifying
• Skipping to solution — "We can fix that!" before understanding depth
• Assuming impact — "That must cost a lot" instead of asking
• Single pain point — Stopping after finding one; aim for 3+
• No documentation — Losing quantified pain to memory
• Leading the witness — "Doesn't that cost $100K?" (let them quantify)

Stakeholder Mapping During Discovery

Impact: HIGH

Deals are won and lost based on stakeholder mapping. Single-threaded deals die. Multi-threaded deals close.

The Buying Committee

┌─────────────────────────────────────────────────────────────────────┐
│                       BUYING COMMITTEE                               │
├─────────────────────────────────────────────────────────────────────┤
│                                                                      │
│                      ┌──────────────────┐                           │
│                      │  ECONOMIC BUYER  │                           │
│                      │  (Final sign-off) │                           │
│                      └────────┬─────────┘                           │
│                               │                                      │
│              ┌────────────────┼────────────────┐                    │
│              │                │                │                     │
│    ┌─────────▼──────┐  ┌──────▼──────┐  ┌─────▼─────────┐          │
│    │   CHAMPION     │  │  TECHNICAL   │  │   COACH       │          │
│    │ (Sells for you)│  │  EVALUATOR   │  │(Inside intel) │          │
│    └────────────────┘  └─────────────┘  └───────────────┘          │
│                               │                                      │
│                      ┌────────▼────────┐                            │
│                      │    END USERS    │                            │
│                      │  (Adopt or reject)│                           │
│                      └─────────────────┘                            │
│                                                                      │
│    ┌─────────────────┐                                              │
│    │    BLOCKER      │ ← May appear at any level                    │
│    │(Has objections) │                                              │
│    └─────────────────┘                                              │
│                                                                      │
└─────────────────────────────────────────────────────────────────────┘

Stakeholder Roles Explained

Discovery Questions for Stakeholder Mapping

Identifying the committee:

"Walk me through how decisions like this typically get made at [Company]."

"Who else would need to be involved in evaluating a solution like this?"

"If you found something you loved, who would you need to get buy-in from?"

"Is there anyone who might have concerns about making a change here?"

"Who owns the budget for initiatives like this?"

Understanding each stakeholder:

"What does [Person] care most about when evaluating new tools?"

"How would [Person] define success for this project?"

"What objections might [Person] raise?"

"What would get [Person] excited about this?"

Building multi-threading:

"Would it make sense to include [Role] in our next conversation?"

"I'd love to understand [Technical Lead]'s requirements. Would you
be open to a brief call with them?"

"What would be helpful for you to share with [Economic Buyer]?"

Stakeholder Mapping Template

STAKEHOLDER MAP: [Company Name]

ECONOMIC BUYER:
- Name: Sarah Chen
- Title: VP of Engineering
- Priority: ROI, risk reduction
- Status: Not yet engaged
- Next step: Request intro through champion

CHAMPION:
- Name: Mike Rodriguez
- Title: DevOps Lead
- Priority: Solving daily pain, looking competent
- Status: Actively engaged
- Next step: Arm with business case

TECHNICAL EVALUATOR:
- Name: TBD
- Title: Security Engineer
- Priority: Integration, compliance
- Status: Unknown
- Next step: Ask Mike for intro

END USERS:
- Team: Platform Engineering (8 people)
- Priority: Ease of use
- Status: Haven't met
- Next step: Include in demo

POTENTIAL BLOCKER:
- Name: Director of IT
- Title: Controls infrastructure budget
- Concern: "We already have Vault"
- Status: Unknown
- Next step: Understand relationship with DevOps

COACH:
- Name: Mike Rodriguez (also champion)
- Intel: Budget cycle is Q4, CTO makes final calls

Multi-Threading Strategies

The Meeting Expansion:

After discovery with your contact:
"This was really helpful. Based on what you shared about [technical
requirements], would it make sense to have [Security Lead] join our
next call? I want to make sure we address their needs too."

The Content Bridge:

"I have a case study from [similar company] that I think would
resonate with your CFO. Would it be helpful if I sent that over
for you to share, or would you prefer I send it directly?"

The Org Chart Request:

"Help me understand the landscape. Beyond yourself, who else has
a stake in solving this problem? I want to make sure we're
addressing everyone's concerns."

Champion Development

What makes a strong champion:

• Has authority/influence
• Has the problem you solve
• Is motivated to solve it now
• Will advocate internally
• Shares inside information

How to build champions:

1. Make them successful - solve their problem
2. Make them look good - arm them with content
3. Make them informed - share industry insights
4. Make them powerful - give them inside access
5. Make them confident - prepare them for objections

Arming your champion:

"Here's a one-pager you can share with your VP that summarizes
the business case."

"What objections do you expect from [Blocker]? Let me help you
prepare responses."

"Would it help if I drafted an email you could send to
[Economic Buyer]?"

Identifying and Handling Blockers

Common blockers:

Questions to identify blockers:

"Is there anyone who might be skeptical about making a change?"

"Who might see this as impacting their area of responsibility?"

"What pushback have you gotten when raising this internally before?"

"Is anyone invested in the current solution?"

Stakeholder Coverage Goals

Warning Signs

Anti-Patterns

• Single-threading — Only talking to one person throughout deal
• Bypassing champion — Going around your contact (damages trust)
• Assuming org structure — Every company is different
• Ignoring end users — They can tank adoption
• Not identifying blockers — They appear at worst times
• No champion development — Expecting them to sell for you naturally

Note-Taking and CRM Documentation

Impact: MEDIUM-HIGH

Great discovery is wasted if it's not documented. Your notes are the foundation for demos, proposals, negotiations, and handoffs.

Why Documentation Matters

DOCUMENTED DISCOVERY:           UNDOCUMENTED DISCOVERY:
- Personalized demos            - Generic presentations
- Accurate proposals            - Guessed pricing
- Smooth handoffs               - Re-discovery needed
- Deal continuity               - Lost context
- Forecasting accuracy          - Pipeline surprises

Real-Time Note-Taking

What to capture during the call:

• Direct quotes (exact words)
• Numbers and metrics
• Names and roles mentioned
• Pain points with specifics
• Decision process details
• Timeline drivers
• Competition mentioned
• Objections raised
• Commitment level

Note-taking techniques:

1. Split screen: Video + notes side by side
2. Use shorthand: P = Pain, C = Competition, Q = Quote
3. Capture quotes verbatim: Use quotation marks
4. Timestamp key moments: "23:00 - revealed budget"
5. Star (*) action items
6. Question mark (?) things to clarify

Call Notes Template

=== DISCOVERY CALL NOTES ===

DATE: [Date]
COMPANY: [Company Name]
ATTENDEES: [Names and titles]
CALL LENGTH: [Duration]

---

SITUATION:
- Company context: [Size, stage, industry]
- Current state: [Tools, process, team]
- Trigger for call: [Why are they talking to us now]

---

PAIN POINTS IDENTIFIED:

Pain #1: [Title]
- Description: [What's happening]
- Quote: "[Exact words]"
- Impact: [Quantified if possible]
- Who's affected: [Roles]

Pain #2: [Title]
- Description: [What's happening]
- Quote: "[Exact words]"
- Impact: [Quantified if possible]
- Who's affected: [Roles]

Pain #3: [Title]
- Description: [What's happening]
- Quote: "[Exact words]"
- Impact: [Quantified if possible]
- Who's affected: [Roles]

---

QUALIFICATION:

Budget:
- Status: [Allocated / Can request / Unknown]
- Range: [$X - $Y if known]
- Source: [What budget line]

Authority:
- Decision maker: [Name, title]
- Buying committee: [List roles/names]
- Process: [How decisions get made]

Need:
- Priority level: [1-10]
- Urgency: [Why now?]
- Impact of not solving: [Consequence]

Timeline:
- Target decision: [Date]
- Implementation: [Date]
- Critical event: [What's driving it]

---

COMPETITION:
- Vendors evaluating: [List]
- Stage with each: [Description]
- Decision criteria: [What matters most]
- Our differentiators that resonate: [List]

---

STAKEHOLDERS:

| Name | Title | Role | Priority | Status |
|------|-------|------|----------|--------|
| [Name] | [Title] | Champion | [What they care about] | Engaged |
| [Name] | [Title] | Economic Buyer | [What they care about] | Not yet met |
| [Name] | [Title] | Technical | [What they care about] | Scheduled |

---

OBJECTIONS / CONCERNS:
- [Concern 1]: [How we addressed / need to address]
- [Concern 2]: [How we addressed / need to address]

---

NEXT STEPS:
- [ ] [Action 1] - Owner: [Name] - By: [Date]
- [ ] [Action 2] - Owner: [Name] - By: [Date]
- [ ] [Meeting]: [Date/Time] - Attendees: [Names]

---

REP NOTES:
[Personal observations, deal strategy, risks]

CRM Field Requirements

Essential fields to update after every call:

CRM Entry Best Practices

Good CRM entry:

CALL SUMMARY:
Discovery with Mike Rodriguez (DevOps Lead) - 45 min

KEY FINDINGS:
- Managing secrets manually, costs 40 hrs/month (~$6K)
- SOC 2 audit in March driving urgency
- Also evaluating HashiCorp Vault (had one demo)
- Budget allocated: $30-50K/year
- Decision maker: Sarah Chen (VP Eng) - need to meet

PAIN QUOTES:
- "It's a nightmare every time someone leaves"
- "I can't sleep before an audit"

NEXT STEPS:
- Demo scheduled 1/22 with Mike + Security Lead
- Mike to request intro to Sarah for exec briefing
- Sent case study from similar fintech

DEAL NOTES:
Strong opportunity - clear pain, budget, timeline. Need to
multi-thread to VP level before proposal. Main risk:
HashiCorp relationship with Security team.

Bad CRM entry:

"Good call. They have interest. Following up."

Handoff Documentation

When handing off to another team member:

=== DEAL HANDOFF: [Company Name] ===

HANDOFF FROM: [Your name]
HANDOFF TO: [Their name]
DATE: [Date]

---

DEAL SNAPSHOT:
- Stage: [Current stage]
- Close date: [Expected]
- Amount: [$X]
- Probability: [%]

---

KEY CONTEXT:

Why they're buying:
[1-2 sentence summary of core driver]

What matters most:
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]

Landmines to avoid:
- [Thing that could derail deal]
- [Sensitive topic]

---

RELATIONSHIPS:

Champion: [Name] - [Notes on relationship, communication style]
Economic Buyer: [Name] - [What we know, how to approach]
Technical: [Name] - [Concerns, requirements]
Blocker: [Name] - [Why they might block, how to handle]

---

HISTORY:
[Chronological summary of key interactions]

---

OPEN ITEMS:
- [Thing that needs follow-up]
- [Question that needs answering]

---

MY RECOMMENDATION:
[What should happen next, how to win this deal]

Post-Call Workflow

Within 30 minutes of call ending: 1. Complete raw notes (fill gaps while fresh) 2. Update CRM opportunity fields 3. Write call summary 4. Send recap email to prospect

Within 24 hours: 1. Send promised materials 2. Create follow-up tasks 3. Update stakeholder map 4. Brief any team members who need context

Documentation Tools & Tips

Note-taking tools:

Time-saving techniques:

• Use text expansion for common phrases
• Create snippet library for frequently used responses
• Voice-to-text for quick post-call notes
• Calendar blocking for documentation time

Discovery Summary for Demo Prep

Before a demo, summarize discovery:

DEMO PREP: [Company Name]

TAILOR DEMO TO:
- Pain 1: [How to address in demo]
- Pain 2: [How to address in demo]
- Pain 3: [How to address in demo]

SKIP/MINIMIZE:
- [Feature they don't care about]
- [Area not relevant to them]

PROOF POINTS TO USE:
- [Similar customer reference]
- [Relevant case study]

QUESTIONS THEY'LL LIKELY ASK:
- [Anticipated question 1]
- [Anticipated question 2]

ATTENDEES TO ACKNOWLEDGE:
- [Name 1]: [What they care about, how to engage]
- [Name 2]: [What they care about, how to engage]

Anti-Patterns

• No notes — Relying on memory for complex deals
• Generic notes — "Good call, they're interested"
• CRM as afterthought — Updating days later with fuzzy recall
• No quotes captured — Losing exact customer language
• Skipping handoff docs — Expecting others to re-discover
• Unstructured notes — Stream of consciousness vs organized template
• Over-documenting — 3 pages of notes no one will read

Active Listening Techniques

Impact: HIGH

Active listening is the difference between a conversation and an interrogation. It builds trust, uncovers deeper insights, and makes prospects feel heard.

The 70/30 Rule

Target: Prospect talks 70%, you talk 30%

┌─────────────────────────────────────────────────────────────────┐
│                     TALK TIME ANALYSIS                          │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  OPTIMAL:     Prospect ████████████████████████████░░░░░░░░░   │
│               Rep      ░░░░░░░░░░░░░░░░░░░░░░░░░████████████   │
│                                    70%              30%        │
│                                                                 │
│  COMMON:      Prospect ████████████░░░░░░░░░░░░░░░░░░░░░░░░░   │
│               Rep      ░░░░░░░░░░░░████████████████████████████│
│                                    40%              60%        │
│                                                                 │
│  DISASTER:    Prospect ████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │
│               Rep      ░░░░█████████████████████████████████████│
│                                    15%              85%        │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

The LAER Framework

Active Listening Behaviors

Do:

• Maintain eye contact (on video)
• Nod and use verbal affirmations ("I see", "That makes sense")
• Take notes visibly (shows you value what they say)
• Pause before responding (process what was said)
• Paraphrase back key points

Don't:

• Interrupt
• Multitask (check email, Slack)
• Plan your response while they're talking
• Jump to solution mode
• Dismiss or minimize their concerns

Clarification Techniques

Paraphrasing:

"So if I'm hearing you correctly, [restate their point]. Is that right?"

"It sounds like the core challenge is [summary]. Am I on track?"

"Let me make sure I understand - you're saying [paraphrase]?"

Reflection:

"It sounds like that's been really frustrating for you."

"I can hear how important this is to the team."

"That seems like a significant concern."

Probing:

"Tell me more about that."

"What do you mean by [specific term they used]?"

"Can you give me an example?"

"What happened next?"

Digging Deeper: The 5 Whys

When you hit a surface-level answer, keep going:

Statement: "We need better security."

Why 1: "Why is security a priority right now?"
Answer: "We had an incident last month."

Why 2: "What happened in that incident?"
Answer: "A developer accidentally pushed a key to GitHub."

Why 3: "What was the impact?"
Answer: "We had to rotate 50+ credentials over a weekend."

Why 4: "What did that cost in terms of time and resources?"
Answer: "About 40 engineering hours plus the stress."

Why 5: "What would have prevented that?"
Answer: "Automated scanning and secrets management."

→ Now you have: quantified pain, specific use case, and stated need

Reading Between the Lines

What they say vs. what they mean:

Silence as a Tool

Strategic pauses:

• After asking a question: Wait 3-5 seconds before filling silence
• After they finish speaking: Pause before responding
• When they give a short answer: Stay silent; they often elaborate

Rep: "What's the biggest challenge you're facing?"
Prospect: "Time."
Rep: [Silence - waits 4 seconds]
Prospect: "I mean, specifically, my team is spending 20 hours a week
on manual processes that should be automated, and it's killing our
velocity."

→ The silence drew out the real answer

Note-Taking Best Practices

What to capture:

• Direct quotes (exact words they use)
• Numbers and metrics mentioned
• Names of people and tools
• Emotion indicators (frustrated, excited, worried)
• Questions to follow up on

Note structure:

CALL: Discovery - Acme Corp
DATE: 2024-01-15
ATTENDEES: Jane Smith (VP Eng), John Doe (DevOps Lead)

SITUATION:
- 80 engineers, growing to 120 by Q2
- Using HashiCorp Vault (self-hosted)
- Manual rotation process

PAIN POINTS:
- "Rotation takes 20 hours/month" (Jane's words)
- Recent audit flagged secrets management
- Two incidents in last 6 months

IMPACT:
- $15k/month in engineering time (calculated)
- SOC 2 audit at risk
- "I can't sleep before an audit" - Jane

NEXT STEPS:
- Demo scheduled for Tuesday
- John to bring Security Lead
- Send ROI calculator

Red Flags in Listening

Anti-Patterns

• Listening to respond — Planning your next question instead of hearing them
• Interrupting with solutions — "Oh, we can solve that!" before they finish
• Ignoring emotion — Missing frustration or excitement cues
• No follow-up — Accepting surface answers without exploring
• Distracted listening — Multitasking during calls
• Confirmation bias — Only hearing what supports your hypothesis

Pre-Call Research & Preparation

Impact: CRITICAL

The best discovery calls are won before they start. Thorough preparation demonstrates professionalism and enables deeper, more relevant questions.

The 15-Minute Research Framework

Company Intelligence (5 min)

• Company size, funding, growth trajectory
• Recent news, press releases, announcements
• Tech stack (use tools like BuiltWith, Wappalyzer)
• Key competitors in their space

Person Intelligence (5 min)

• LinkedIn profile, career history
• Recent posts, articles, or content they've shared
• Mutual connections
• Role tenure and scope

Hypothesis Building (5 min)

• Based on research, what problems might they have?
• What triggered this meeting?
• What's their likely buying timeline?

Pre-Call Checklist

Research Sources by Priority

Hypothesis Development

Build 2-3 hypotheses before every call:

Template:

Based on [research finding], I hypothesize that [prospect name]
is struggling with [problem] which is causing [business impact].

Research Finding: Series B startup, grew from 20 to 80 employees in 12 months
Hypothesis: Rapid growth has likely outpaced their security infrastructure.
They're probably managing secrets manually or with basic tools that don't scale.

Validation Question: "With your team tripling in size, how has your
approach to secrets management evolved?"

Good Preparation Examples

Before a call with a Series B fintech CTO:

Research:
- Company raised $25M 6 months ago
- CTO posted about SOC 2 compliance on LinkedIn
- Job postings show they're hiring DevOps
- Using AWS based on job descriptions

Hypotheses:
1. SOC 2 audit driving security improvements
2. Growing team means access management challenges
3. Moving fast but worried about compliance

Prepared Questions:
- "I noticed you're going through SOC 2. How is that going?"
- "With the DevOps hiring, how are you managing secrets at scale?"
- "What triggered the focus on compliance now?"

Bad Preparation Examples

Showing up with:
- "So, tell me about your company"
  (Should already know this)

- "What does your company do?"
  (Wastes their time, shows laziness)

- "I see you work at Acme Corp"
  (That's not research, that's reading)

- Generic pitch deck with no customization
  (One-size-fits-all doesn't fit anyone)

Agenda Setting

Send a brief agenda 24 hours before:

Good Agenda:

Subject: Agenda for Tomorrow - [Your Company] + [Their Company]

Hi [Name],

Looking forward to our conversation tomorrow. Here's what I'd like to cover:

1. Learn about your current [relevant area] and key priorities (15 min)
2. Understand what's working and what's challenging (15 min)
3. Determine if there's a fit and discuss next steps (10 min)

I've done some research on [Company] and have a few specific questions,
but I'd love to hear what's top of mind for you. Is there anything
specific you'd like to cover?

Best,
[Name]

Bad Agenda:

Subject: Meeting tomorrow

Hi,

Excited to tell you about our product tomorrow. I'll show you a demo
and explain our pricing.

See you then!

Pre-Call Mental Preparation

Five minutes before the call: 1. Review your hypotheses 2. Have your top 5 questions visible 3. Open note-taking tool 4. Close distractions (email, Slack) 5. Take a breath - be genuinely curious

Anti-Patterns

• Zero preparation — "So tell me about yourself" opening
• Research overload — Spending 2 hours on a 30-minute call
• Stalker vibes — "I saw you went to Hawaii last week" (creepy)
• No hypotheses — Going in without informed guesses to validate
• Generic questions — Same questions regardless of prospect
• No agenda sent — Prospect doesn't know what to expect

Budget and Timeline Qualification

Impact: CRITICAL

Qualification separates real opportunities from time-wasters. Don't invest cycles in deals that won't close.

Qualification Framework Comparison

Budget Qualification

The goal: Understand if they can afford your solution and if it's a priority for their budget.

Direct Questions:

"What budget has been allocated for solving this problem?"

"Where would funding for this come from - existing budget or new request?"

"What's the typical range you spend on solutions like this?"

"If this became a priority, what investment level would make sense?"

Indirect Questions:

"What are you currently spending on [related area]?"

"When you've invested in solutions like this before,
what was the typical price range?"

"How do you typically evaluate ROI for purchases in this area?"

Budget Scenarios:

Budget Qualification Matrix:

                    Budget Available
                    YES         NO
                ┌─────────┬─────────┐
         YES    │ IDEAL   │ HELP    │
Can              │ DEAL    │ BUILD   │
Request         │ FAST    │ CASE    │
                ├─────────┼─────────┤
         NO     │ FIND    │ NURTURE │
                │ SPONSOR │ ONLY    │
                └─────────┴─────────┘

Timeline Qualification

The goal: Understand when they need to make a decision and what's driving urgency.

Key Questions:

"When are you looking to have a solution in place?"

"What's driving that timeline?"

"What happens if this doesn't get solved by [date]?"

"Is there a specific event or deadline creating urgency?"

"Where does this sit relative to other priorities this quarter?"

Timeline Indicators:

Critical Events to Discover:

EXTERNAL (Hard deadlines):
- Compliance audits (SOC 2, HIPAA, GDPR)
- Contract renewals
- Board meetings
- Funding rounds
- Product launches

INTERNAL (Soft deadlines):
- Quarterly planning
- Budget cycles
- Headcount changes
- Strategic initiatives
- Executive mandates

Authority Qualification

The goal: Understand who makes the decision and your contact's role.

Questions:

"Walk me through how decisions like this typically get made."

"Who else would be involved in evaluating and approving this?"

"If you found a solution you loved, what would the process look like?"

"Who owns the budget for this area?"

"Have you purchased something similar before? How did that process go?"

Stakeholder Roles:

Need Qualification

The goal: Confirm the problem is real, significant, and solvable by your product.

Questions:

"On a scale of 1-10, how painful is this problem today?"

"What would happen if you did nothing for 6 months?"

"How does this compare to other challenges you're facing?"

"Is solving this a 'must-have' or 'nice-to-have'?"

"What would success look like if this was solved?"

Need Assessment Matrix:

Qualification Scoring

Simple Qualification Score:

Total Score:

• 10-12: Hot - prioritize heavily
• 7-9: Warm - active opportunity
• 4-6: Cool - qualify further or nurture
• 1-3: Cold - deprioritize or disqualify

Disqualification Criteria

Hard disqualifiers:

• No budget and no path to budget
• No authority and won't involve decision makers
• Problem you can't solve
• Timeline >12 months with no driver
• Current contract with competitor (long remaining)

When to disqualify gracefully:

"Based on what you've shared, it sounds like [problem] isn't
the top priority right now. I don't want to waste your time -
would it make sense to reconnect in [timeframe] when this
becomes more urgent?"

"It sounds like you're earlier in this journey than our typical
customers. Can I share some resources and check back in Q3?"

Anti-Patterns

• Avoiding budget conversations — Feels awkward but essential
• Accepting "we'll find budget" — Press for specifics
• Believing timeline without drivers — "This quarter" means nothing without a why
• Single-threading authority — Always ask who else is involved
• Not disqualifying — Hoping bad deals become good
• Qualification once — Should revisit throughout deal cycle

SPIN Question Framework

Impact: CRITICAL

SPIN Selling is the gold standard for discovery questions. It creates a logical flow from understanding the situation to building urgency for change.

The SPIN Progression

SITUATION → PROBLEM → IMPLICATION → NEED-PAYOFF

"What is..."  "What's hard..."  "What happens..."  "What if..."

Each question type builds on the previous, moving the prospect from awareness to urgency.

Situation Questions

Purpose: Establish context and current state When: Early in discovery (first 10 minutes) Risk: Too many = interrogation; too few = assumptions

Good Situation Questions:

"Can you walk me through your current workflow for onboarding new developers?"

"What does your tech stack look like today?"

"How many people touch this process on a weekly basis?"

"What prompted you to take this meeting today?"

Bad Situation Questions:

"What does your company do?"
(Should know from research)

"How many employees do you have?"
(Publicly available information)

"Tell me everything about your business"
(Too broad, lazy)

Problem Questions

Purpose: Surface challenges, frustrations, and gaps When: After establishing context Tip: Listen for emotion - frustration indicates real pain

Good Problem Questions:

"What's the most frustrating part of your current approach?"

"If you could wave a magic wand and fix one thing, what would it be?"

"Where do you see the biggest gaps in your current process?"

"What's broken that you haven't had time to fix?"

Bad Problem Questions:

"Do you have problems with X?"
(Leading, closed-ended)

"Wouldn't you agree that X is hard?"
(Manipulative)

"Let me tell you the problems you have..."
(Not a question)

Implication Questions

Purpose: Quantify the cost of inaction and build urgency When: After identifying problems Key: This is where deals are won or lost

Good Implication Questions:

"When a secret gets leaked, what's the incident response process?
How many people get pulled in?"

"If you estimate the engineering time spent on this monthly,
what does that translate to in dollars?"

"What happens to your SOC 2 audit if this isn't addressed?"

"How does this problem impact your ability to ship features on time?"

Bad Implication Questions:

"Isn't that a big problem?"
(Leading, doesn't quantify)

"That must be expensive"
(Assumes, doesn't discover)

"You should be worried about that"
(Telling, not asking)

Need-Payoff Questions

Purpose: Have the prospect articulate the value of solving the problem When: After implications are established Power: The prospect sells themselves on the solution

Good Need-Payoff Questions:

"If you could reduce that incident response time by 80%,
what would that mean for your team?"

"Imagine having full visibility into every secret across your infrastructure.
How would that change your security posture?"

"If this problem was solved, what could your engineers focus on instead?"

"What would it mean for your SOC 2 audit to have this fully automated?"

Bad Need-Payoff Questions:

"Wouldn't it be great if..."
(Rhetorical, not discovery)

"Let me tell you how our product solves this"
(Pitching, not questioning)

"You need a solution like ours"
(Presumptuous)

SPIN Sequencing Example

Situation:
"Walk me through how your team manages secrets today."
Response: "We use .env files and have some stuff in a shared vault."

Problem:
"What happens when someone joins or leaves the team?"
Response: "It's a mess. We have to rotate everything manually."

Implication:
"How often does that happen with your growth rate?
And what's the risk if a credential doesn't get rotated?"
Response: "Monthly. And honestly, we've had a few close calls."

Need-Payoff:
"If you had automated rotation and complete audit trails,
how would that affect your confidence in security?"
Response: "It would be huge. I'd actually sleep at night."

Question Density Guidelines

Anti-Patterns

• Skipping to Need-Payoff — Can't propose solutions before understanding problems
• All Situation — Spending entire call on context without finding pain
• No Implications — Finding problems but not quantifying impact
• Rapid-fire questions — No pauses for prospect to elaborate
• Leading questions — "Don't you think X is a problem?"
• Closed questions only — Yes/no answers don't reveal insight