MQL vs SQL and the Qualification Gate

Day 13 of 30 · B2B Sales 2026 Masterclass

Decide fast: when to say no and when to open discovery.


Learning Goal

  • Draw a clear line between MQL and SQL.
  • Write a 5-question qualification gate.
  • Create 3 fast “no” templates.

Why It Matters

  • Bad leads waste time and hurt win rate.
  • Fast “no” boosts focus and pipeline quality.
  • Without a gate, the team works on opinion.

Explanation

MQL

  • Marketing signal: download, signup, event.
  • Not yet validated for ICP/problem.

SQL

  • ICP + problem + reachable decision maker/gatekeeper.
  • Trigger or pain validated.

Gate

  • 5 questions: ICP? pain? decision maker? trigger? timing?
  • Yes = discovery; No = quick close or nurture.

Examples

Bad: Every signup is invited to discovery.

Good: Only ICP + problem + decision maker → discovery.


Guided Exercise (10–15 minutes)

  1. Write 5 gate questions.
  2. Write 3 polite, value-adding “no” templates.
  3. Mark which MQLs go to nurture.

Independent Exercise (5–10 minutes)

Take 10 leads, apply the gate, note how many become SQL.


Self-check

  • MQL/SQL definitions set.
  • 5-question gate written.
  • 3 “no” templates ready.
  • Applied to 10 leads and logged results.

Optional Deep Dive