blackroad-os-sales-playbook/02-methodology/DISCOVERY_FRAMEWORK.md

# 🔍 Discovery Framework

**PROPRIETARY & CONFIDENTIAL**

---

## Philosophy

**Discovery is the most important phase of the sales cycle.**

**Why?**
- Poor discovery = generic demo = no value = no close
- Great discovery = personalized solution = clear ROI = easy close

**Golden Rule:** Spend 2x more time on discovery than demo.

**Discovery is where deals are won or lost.**

---

## Discovery Objectives

By the end of discovery, you must know:

1. **Pain Points:** What problems are they facing? (and why it matters)
2. **Current State:** How are they solving it today? (and what's broken)
3. **Desired Outcome:** What does success look like? (quantified)
4. **Decision Process:** Who decides? What's the timeline? What's the budget?
5. **Competitive Landscape:** What alternatives are they considering?
6. **Success Criteria:** How will they measure if this worked?

**If you can't answer all 6, you haven't finished discovery.**

---

## The SPIN Framework (Extended)

SPIN = Situation, Problem, Implication, Need-Payoff

This is the foundation of consultative selling.

---

### 1. Situation Questions

**Purpose:** Understand their current state

**Goal:** Build context (but don't spend too much time here—they know their situation)

**Questions:**

```
"Walk me through your current infrastructure setup."

"What cloud providers are you using? (AWS, Azure, GCP?)"

"How many microservices or applications are you running in production?"

"How big is your DevOps/infrastructure team?"

"What tools are you using today for deployment, monitoring, and security?"

"How often do you deploy to production?"

"What's your tech stack? (Languages, frameworks, databases)"

"Do you have compliance requirements? (SOC 2, HIPAA, ISO 27001?)"
```

**Time Allocation:** 10-15% of discovery call

**Red Flag:** If you spend >20 minutes here, you're wasting time. Move to Problem questions.

---

### 2. Problem Questions

**Purpose:** Identify pain points and gaps

**Goal:** Uncover specific problems (this is where value lives)

**Questions:**

```
"What are the biggest infrastructure challenges you're facing right now?"

"What's not working well with your current setup?"

"How often do deployments fail or need to be rolled back?"

"What percentage of engineering time goes to infrastructure vs. product features?"

"What keeps you up at night about your infrastructure?"

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

"What's slowing you down the most?"

"Where are you spending money you wish you weren't?"

"What incidents or outages have you had recently?"
```

**Time Allocation:** 30-40% of discovery call

**Technique: The "Peel the Onion" Method**

When they mention a problem, dig deeper:

**Customer:** "Deployments are slow."
**You:** "How slow? What's the impact of that?"
**Customer:** "3-4 hours per deployment."
**You:** "How often do you deploy?"
**Customer:** "We want to deploy daily, but we can only do weekly because of how long it takes."
**You:** "What's the business cost of deploying weekly instead of daily?"
**Customer:** "We're losing competitive advantage. Features take 10x longer to ship."

---

### 3. Implication Questions

**Purpose:** Explore consequences of inaction

**Goal:** Make the pain acute (create urgency)

**Questions:**

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

"How does slow deployment velocity affect your ability to compete?"

"What's the cost of downtime or outages to your business?"

"How does lack of SOC 2 certification limit your sales opportunities?"

"If infrastructure stays a bottleneck, what can't you do?"

"What's the opportunity cost of having your team focused on infrastructure instead of product?"

"How is this affecting team morale? (burnout, turnover?)"

"What deals have you lost because of this problem?"
```

**Time Allocation:** 20-30% of discovery call

**Technique: The "Future Pain" Projection**

Help them see the future if they don't act:

**You:** "You mentioned deployments fail 20% of the time today. If you 10x your traffic next year, what happens?"
**Customer:** "It would be a disaster. We'd need to hire 10 more DevOps engineers just to keep up."
**You:** "At $200K per engineer, that's $2M/year. Does that fit in your budget?"
**Customer:** "No. We need a better solution."

---

### 4. Need-Payoff Questions

**Purpose:** Quantify value of solving the problem

**Goal:** Get them to articulate the ROI (so they convince themselves)

**Questions:**

```
"If you could deploy 10x faster, what would that enable?"

"What would it be worth to reduce infrastructure costs by 40%?"

"If you could achieve SOC 2 compliance 6 months faster, what's the business impact?"

"If you could redeploy 3 DevOps engineers to product work, what would they build?"

"How much revenue could you unlock if infrastructure wasn't a bottleneck?"

"What's the value of preventing the next major outage?"

"If onboarding took 2 weeks instead of 6 months, what's the cost savings?"
```

**Time Allocation:** 20-30% of discovery call

**Technique: The "Dream Scenario"**

Paint the picture of success:

**You:** "Imagine it's 12 months from now. Infrastructure is no longer a bottleneck. What does your business look like?"
**Customer:** "We're deploying daily instead of weekly. We've launched 3 new features that were stuck in the roadmap. We closed 5 enterprise deals that required SOC 2. Revenue is up 40%."
**You:** "What's that worth to the business?"
**Customer:** "$10M+ in revenue."

**Now you have a $10M value prop to justify a $180K investment.**

---

## Discovery Call Structure (60-90 Minutes)

### Minutes 0-5: Build Rapport

**Goal:** Make them comfortable

**Script:**
```
"Thanks for making time today. Before we dive in, tell me a bit about yourself.
How long have you been at [Company]? What's your background?"
```

**Why:** People buy from people they like. Build connection first.

---

### Minutes 5-10: Set Agenda

**Goal:** Align on expectations

**Script:**
```
"Here's what I'd like to cover in the next hour:
1. Understand your current infrastructure setup
2. Identify challenges and pain points
3. Discuss your goals and what success looks like
4. If there's a fit, talk about next steps

Sound good?"
```

**Why:** Clear agenda = efficient call. They know what to expect.

---

### Minutes 10-20: Situation Questions

**Goal:** Understand current state

**Focus:**
- Infrastructure setup
- Tech stack
- Team size
- Current tools

**Transition:** "Thanks for that context. Now let's talk about what's working and what isn't..."

---

### Minutes 20-50: Problem + Implication Questions

**Goal:** Uncover pain and urgency

**Focus:**
- Specific problems
- Business impact (cost, time, risk)
- Consequences of inaction

**Take Notes:** Document every pain point (you'll use this in demo and proposal)

---

### Minutes 50-70: Need-Payoff Questions

**Goal:** Quantify value of solving

**Focus:**
- Dream scenario (what does success look like?)
- Quantified outcomes ($X saved, Y% faster, Z hours/week freed)
- Business impact (revenue, growth, competitive advantage)

---

### Minutes 70-80: BANT++ Qualification

**Goal:** Assess deal viability

**Script:**
```
"Let me ask a few logistical questions:

1. Budget: Do you have budget allocated for infrastructure improvements?
2. Authority: Who else needs to be involved in this decision?
3. Timeline: When do you need this solved by?
4. Competition: What other solutions are you evaluating?"
```

---

### Minutes 80-90: Next Steps

**Goal:** Advance the deal

**Script:**
```
"This has been super helpful. Based on what you've shared, it sounds like BlackRoad OS
could solve [pain 1], [pain 2], and [pain 3].

Here's what I recommend as next steps:

[Option A: Strong Fit]
Let's schedule a demo where I'll show you exactly how we address these challenges.
I'll tailor it to your use cases. Does [specific date/time] work?

[Option B: Need More Discovery]
I'd like to bring in our Solutions Architect for a deeper technical discussion.
We can map out your architecture and show you how BlackRoad OS integrates.

[Option C: Not a Fit]
Based on what you've shared, I'm not sure we're the right fit right now. You might
be better served by [alternative]. If things change, happy to reconnect."
```

---

## Discovery Question Bank

### Technical Discovery

```
"What's your deployment process today? (Manual, automated, CI/CD?)"

"How do you handle scaling? (Manual, auto-scaling?)"

"What monitoring and logging tools are you using?"

"How do you handle secrets management?"

"What's your disaster recovery strategy?"

"How do you manage infrastructure as code? (Terraform, CloudFormation?)"

"What CI/CD tools are you using? (GitHub Actions, Jenkins, GitLab?)"

"How do you handle security vulnerabilities?"
```

---

### Business Discovery

```
"What are your company's top 3 priorities this year?"

"What metrics do you report to the board?"

"What's driving your growth right now?"

"What's your biggest competitive threat?"

"If you had unlimited budget, what would you invest in?"

"What keeps your CEO up at night?"
```

---

### Financial Discovery

```
"What's your current cloud spend? (Monthly/annual)"

"What's your DevOps budget? (Headcount + tools)"

"What does downtime cost you? (Per hour or per incident)"

"What's your customer acquisition cost (CAC)?"

"What's your runway? (Months of cash)"

"Are you profitable or growing toward profitability?"
```

---

### Compliance Discovery

```
"Do you have compliance requirements? (SOC 2, HIPAA, ISO 27001, PCI?)"

"Have you been through a compliance audit before?"

"What's your timeline for achieving compliance?"

"What's blocking you from getting certified?"

"Do you have a dedicated compliance officer or team?"
```

---

### Competitive Discovery

```
"What tools or vendors are you using today?"

"What do you like about them? What frustrates you?"

"Have you evaluated other solutions?"

"What would make you switch from your current vendor?"

"What would you never give up in a new solution?"
```

---

## Discovery Red Flags

🚩 **No Clear Pain**
- "Everything is working fine, just exploring options."
- **Action:** Politely disengage or plant seed for future.

🚩 **Can't Quantify Impact**
- "It's a problem, but I don't know how much it costs."
- **Action:** Help them quantify (or move on).

🚩 **No Timeline**
- "We'll figure it out eventually."
- **Action:** Create urgency or disqualify.

🚩 **No Budget**
- "We have $0 allocated and can't get more."
- **Action:** Disqualify.

🚩 **Can't Access Decision-Maker**
- "I'll present to my boss, but I can't introduce you."
- **Action:** Low probability deal. Pursue cautiously.

---

## Discovery Mistakes to Avoid

### Mistake 1: Pitching Too Early

**Problem:** You jump to solution before understanding problem

**Fix:** Resist urge to pitch. Ask questions first.

**Rule:** 80% questions, 20% talking about product

---

### Mistake 2: Superficial Discovery

**Problem:** You ask surface-level questions and don't dig deeper

**Fix:** Use "peel the onion" technique. Ask "why" 3 times.

**Example:**
> Customer: "Deployments are slow."
> You: "Why is that a problem?" (1st why)
> Customer: "We can't ship features fast enough."
> You: "Why does that matter?" (2nd why)
> Customer: "We're losing competitive advantage."
> You: "What's the business impact of that?" (3rd why)
> Customer: "We lost 3 deals to competitors who ship faster. $2M in ARR."

**Now you have quantified pain.**

---

### Mistake 3: Talking About Features

**Problem:** Customer asks about features, you monologue for 20 minutes

**Fix:** Answer briefly, then return to discovery.

**Example:**
> Customer: "Do you support Kubernetes?"
> You: "Yes, BlackRoad OS is Kubernetes-native. Why is that important to you?"

---

### Mistake 4: Not Taking Notes

**Problem:** You forget details, can't personalize demo/proposal

**Fix:** Take detailed notes during call. Use template (see below).

---

### Mistake 5: No Next Step

**Problem:** Great call, but no clear follow-up

**Fix:** Always schedule next step before hanging up.

---

## Discovery Notes Template

Use this template in HubSpot CRM:

```
**Discovery Call Notes - [Company Name]**
Date: [Date]
Attendees: [Names + Titles]

**SITUATION (Current State)**
- Infrastructure: [Summary]
- Tech stack: [List]
- Team size: [X DevOps engineers]
- Tools: [Current tools]

**PROBLEMS (Pain Points)**
1. [Pain 1] - [Impact]
2. [Pain 2] - [Impact]
3. [Pain 3] - [Impact]

**IMPLICATIONS (Consequences of Inaction)**
- [What happens if they don't solve?]
- [Cost/risk/opportunity cost]

**NEED-PAYOFF (Value of Solving)**
- [Quantified benefit 1]: $[X] savings or [Y]% improvement
- [Quantified benefit 2]: $[X] savings or [Y]% improvement
- [Dream scenario]: [What does success look like?]

**BANT++ ASSESSMENT**
- Budget: [Yes/No, $X allocated or to be justified]
- Authority: [Decision-makers identified]
- Need: [Critical/Important/Nice-to-have]
- Timeline: [Date or timeframe]
- Competition: [Alternatives being evaluated]
- Champion: [Internal advocate identified]
- **Score: [X/125]**

**NEXT STEPS**
- [ ] [Action 1] - [Due date] - [Owner]
- [ ] [Action 2] - [Due date] - [Owner]

**SENTIMENT**
🟢 Positive / 🟡 Neutral / 🔴 Negative

**CONFIDENCE**
High / Medium / Low (that this will close)
```

---

## Multi-Call Discovery (Enterprise Deals)

For large, complex deals, discovery may span multiple calls:

### Call 1: Executive Discovery (30-45 min)
**Attendees:** CEO, COO, or VP-level
**Focus:** Business strategy, priorities, budget

### Call 2: Technical Discovery (60-90 min)
**Attendees:** CTO, VP Eng, DevOps Lead
**Focus:** Infrastructure, tech stack, pain points

### Call 3: Compliance/Security Discovery (45-60 min)
**Attendees:** Chief Compliance Officer, CISO
**Focus:** Regulatory requirements, security concerns

### Call 4: Finance Discovery (30-45 min)
**Attendees:** CFO, Finance lead
**Focus:** Budget, ROI, payment terms

**Schedule all 4 within 2-3 weeks to maintain momentum.**

---

## Discovery Metrics

| Metric | Target | Why |
|--------|--------|-----|
| **Discovery-to-Demo Rate** | >80% | Quality of discovery (are you qualifying well?) |
| **Discovery Call Length** | 60-90 min | Too short = superficial, too long = inefficient |
| **BANT++ Score Post-Discovery** | >80 | Are you qualifying effectively? |
| **Questions Asked** | 20-30 | Enough depth? |
| **Customer Talk Time** | >60% | Are you listening or pitching? |

---

## FAQs

**Q: What if they won't answer budget questions?**
A: Say: "I'm not trying to extract a number. I just want to make sure we're aligned on investment range—are we talking $10K, $100K, or $1M?"

**Q: What if I can't get to the decision-maker?**
A: Ask your contact: "Who else should be involved? Can you introduce me?"

**Q: How do I know when discovery is done?**
A: When you can answer all 6 discovery objectives (pain, current state, desired outcome, decision process, competition, success criteria).

---

**Version:** 1.0.0
**Last Updated:** January 4, 2026
**Owner:** Joaquin, Sales Master

*Discovery is where deals are won. Ask better questions. Close more deals.*