Top 3 Discovery Call Mistakes (ft. Chris Orlob)

Top 3 Discovery Call Mistakes (Sales Execution Focus)

1) “Hammer and nail syndrome” (jumping to solutions too early)

• Mistake: You quickly identify a problem and try to “smack the nail in” (solve immediately) instead of understanding it first.
• What to do instead (process change):
  • Hang back and uncover what’s really going on before proposing solutions.
  • Stew on the problem to better diagnose the real need.

2) “Cheesy” impact questions too early

• Mistake: Asking overly personal-impact prompts such as:
  • “How does this impact you personally?”
• Why it fails: Buyers may feel uncomfortable unless there’s strong rapport, which can reduce engagement.
• What to do instead (question framework):
  • Avoid personal-impact questions early in the sales cycle.
  • Use business-oriented “ripple effect” questions, for example:
    • “What ripple effects is this challenge having throughout the business?”

3) Not diagnosing the root cause (treating symptoms vs causes)

• Mistake: Focusing on the surface problem instead of uncovering the underlying root cause.
• Core principle: Products don’t solve problems— they solve root causes.
• Concrete example (car breakdown):
  • The buyer may be in pain regardless of the issue, but you can’t sell effectively until they agree on the cause, such as:
    • transmission failure
    • engine failure
    • blown tire
    • running out of gas
  • The identified cause determines what they purchase.
• Actionable recommendation: During discovery, probe how the buyer thinks about the cause so you can align the offering to the correct root cause.

---

Frameworks / Tactics Highlighted

• Discovery sequencing
  • Investigate first → only later “pounce” with solutions.
• Question selection framework
  • Early-cycle: business-oriented impact → “ripple effects throughout the business”
  • Avoid: personal-impact questions without rapport
• Root-cause diagnosis
  • Identify cause category (symptom vs root cause) before prescribing a product solution.

---

Metrics / KPIs / Targets

• No explicit quantitative KPIs, targets, timelines, or numbers were provided in the subtitles.

---

Examples / Case-Style Illustration

• Car breakdown analogy: Demonstrates that the buyer’s root cause determines the right purchase.
• Ripple effects question: A more sophisticated alternative to personal-impact questions.

---

Presenters / Sources

• Chris Orlob (Apollo “crew” / master class context; Apollo referenced as the platform/partner)