GTM Fundamentals · intermediate · node 4.3

Lead types and qualification

Lead types are not universal categories. They are motion-specific definitions of 'ready to move.' An MQL (marketing qualified lead) is someone who raised their hand through marketing activity and meets basic fit criteria. An SQL (sales qualified lead) is someone with confirmed buying intent, budget, and authority. A PQL (product qualified lead) is someone already in your product showing high-value behavior. Which type you have determines your qualification framework, your sales motion, your cycle time, and your win rate. The funnel flows differently depending on entry point.

intermediate Last updated 2026-06-25

Prerequisites

Funnel & the bowtie (full lifecycle)Stages (awareness → advocacy)GTM motion (sales-led vs product-led)

Most founders talk about “leads” as if they are all the same thing. They are not. A lead that came in via a content download (MQL) is an entirely different animal from a lead who has already spent 20 hours in your product with a team of five people (PQL). Treating them as the same leads to spectacularly bad outcomes: you run a sales process on someone not yet ready to buy, or you send a nurture email to someone who is ready to close, or you fail to engage a product user who would expand if asked.

Lead types are not universal. They are motion-specific definitions of readiness. In a sales-led motion, you have MQLs and SQLs. In a product-led motion, you do not use these terms at all—you have PQLs instead. In a hybrid motion, you have all three, plus a routing signal that decides which path each lead takes.

The mistake is not naming and measuring these separately. When founders say “our sales team processes 200 leads per month,” what they mean is lost. 200 leads of what type? Where did they come from? How were they qualified? What is the conversion by type? Without these segments, you cannot optimize. You cannot fix something you cannot measure.

What are lead types, and why motion determines the definition

A lead type is not a universal bucket. It is a motion-specific stage in your funnel that comes with an implied readiness level and a motion appropriate to that readiness.

Sales-led motion: MQL → SQL → Opportunity → Close

MQL (Marketing Qualified Lead). Someone who expressed interest through marketing (filled a form, downloaded an asset, attended a webinar, replied to an email) AND meets basic ICP fit (right company size, industry, geography—the things you can check before a conversation). MQLs are possible customers, not yet proven customers. Conversion from MQL to SQL is typically 10–30%.
SQL (Sales Qualified Lead). Someone an AE has spoken to, confirmed they have a problem the product solves, verified they have budget and timeline, and established that they are the right stakeholder (or close to it). SQLs are probable customers. Conversion from SQL to close is typically 30–60%, depending on qualification rigor and product fit.
Opportunity. An SQL who has moved into the sales process (demo booked, discovery complete, deal in pipeline). Some teams collapse SQL and opportunity; others treat them separately.

Product-led motion: Signup → Activation → PQL → Expansion

Signup. Someone who created an account. No qualification required yet; anyone can sign up.
Activation. Someone who reached the aha moment and knows the product solves their problem. Activation is usage-based, not interest-based.
PQL (Product Qualified Lead). Someone already in the product who has shown high-value behavior (used advanced features, invited a team, hit a usage threshold, stayed past day 30, or any signal you define as “high probability of expansion or enterprise upgrade”). PQLs are confirmed customers with product fit already proven. Conversion from PQL to paying customer or enterprise sale is typically 40–70%.

Hybrid motion: Signup → Activation → Routing Signal → (MQL path or SQL path)

In hybrid, leads flow through the product first and are routed based on behavior:

Low-usage, small-account signals → self-serve upsell path (no MQL/SQL, just nurture).
High-usage, high-potential signals → routed to sales as warm leads (sometimes called “PQLs ready for sales” or warm SQLs).

The key: the lead is already product-qualified when it reaches sales, which changes the sales motion entirely. The cycle is shorter, the conversation is different, and the close rate is higher.

Lead-type by motion: a diagnostic matrix

Lead Type	Motion	How They Enter	Who Qualifies	Conversion Rate	Cycle Time	Sales Motion	Red Flags
MQL	Sales-led	Content, outreach, event, paid acquisition. Interest signal only.	Marketing by ICP criteria (company size, industry, role).	10–30% to SQL	0 days (just entered funnel)	Outbound call, email, meeting request. Lead not yet warm.	High MQL volume with low SQL conversion. Sales team complaining about lead quality.
SQL	Sales-led	Converted from MQL through sales conversation or inbound interest. Problem + budget + timeline confirmed.	Sales in discovery conversation (BANT, MEDDIC, or custom framework).	30–60% to close	30–90 days typical	Discovery → proposal → negotiation → close. Sales owns the motion.	High SQL count but long cycle or low close rate. Qualification framework is weak.
PQL	Product-led	Self-signup, reached activation, then showed high-value behavior (usage, team growth, persistence, feature adoption).	Product (usage metrics) + sometimes a human check. Signals are behavioral, not conversational.	40–70% to expansion or paid upgrade	0–30 days (already in product)	Sales motion (if needed) is warm-welcome, not convincing. Conversation is “how can we help you expand?” not “does the problem exist?”	High PQL signal but low expansion. Either wrong signal definition, or sales motion is too heavy.
Warm Lead from Hybrid	Hybrid (PLS)	Signup → activation in product → high-value behavior signal → routed to sales.	Product by signal + sales by warm conversation.	50–80% to close	14–45 days (much shorter than cold SQL)	Light sales motion: “I see you are using X feature. Want to talk about Y?” Sales is acceleration, not discovery.	Wrong routing signal sends low-value accounts to sales (waste of cost) or valuable accounts to nurture (waste of upside).

Founder mistakes: how lead-type thinking fails

Mistake 1: Treating all leads the same

The most common mistake: “We process 500 leads per month.”

What does that mean? If 400 are MQLs and 100 are SQLs, and you measure conversion as 500 → 50 customers (10%), you have masked the reality. The truth might be:

MQL → SQL conversion: 15% (excellent)
SQL → close: 50% (healthy)
But your MQL sources are weak. You are getting 400 unqualified leads and wasting time on them.

Or the opposite:

MQL → SQL conversion: 5% (bad)
SQL → close: 80% (excellent)
Your sales team is excellent, but marketing is not filtering. You need fewer, better leads.

The fix: Segment by lead type. Measure conversion by type. You will see where the real problem is.

Mistake 2: Not measuring lead-type-to-close conversion

You know your close rate: 40%. You know your SQL count: 100. But do you know:

Which SQL source converts best? (Inbound vs outbound vs channel vs event)
Which qualification framework works best? (BANT vs MEDDIC vs your custom framework)
Does SQL-to-close vary by segment? (SMB 60% close, Enterprise 30% close, or vice versa)
Do MQLs from one source convert to SQL more often than another source?

Without segmenting, you cannot optimize. You optimize “overall conversion” by accident, not by intention.

The fix: Build a cohort table. Segment every lead by source, ICP segment, and lead type. Measure conversion by each segment. You will find the winning path.

Example:

Source	MQL→SQL	SQL→Close	MQL→Close	Notes
Inbound (content)	25%	45%	11%	Long sales cycle, but good fit
Outbound SDR	8%	62%	5%	Low MQL→SQL because SDR is already pre-qualifying. SQL quality is high.
Event	18%	40%	7%	Decent MQL volume, medium conversion
Paid ads	12%	35%	4%	Lowest SQL conversion. Are we targeting the wrong accounts?

This table tells you everything. You can see that outbound has the lowest MQL volume but the highest SQL close rate—you are doing the qualification work upfront. Paid ads have the worst economics. Maybe you should shift budget.

Without this segmentation, you have no idea.

Mistake 3: Building the wrong qualification process for your motion

Sales-led mistake: You have a PQL-heavy product (users love it, activation is 70%, usage is high) but you are running a traditional sales-led motion with long discovery cycles and heavy qualification. You are qualifying leads for problems they do not have (they already know the product works because they used it). The sales motion is overkill.

Product-led mistake: You have MQLs (email signups, content downloads, webinar attendees) and you are sending them directly to sales, asking them to do a full sales-led discovery. But they do not have time to sign up for a trial. You are forcing a sales motion on buyers who want self-service. You are wasting sales time and losing deals.

Hybrid mistake: You have a routing signal (account usage > threshold), but the signal is wrong. You route $5k/year accounts to sales and lose money on CAC. You route $500k/year accounts to nurture and miss expansion. The signal decides everything. Get the signal wrong and the whole motion breaks.

The fix: Match your qualification framework to your motion.

Sales-led: Use BANT, MEDDIC, or SPICED (see 4.4). Do qualification in the discovery conversation.
Product-led: Do not use MQL/SQL terminology. Use product signals. Measure: days-to-activation, feature adoption, team growth, usage depth, account metadata (company size, growth signals). When you have a PQL signal, tell the user about the paid tier. No sales discovery needed.
Hybrid: Use product signals to route. MQL path = nurture email sequence + in-product upgrade prompts. SQL path = sales conversation (but lighter than cold sales-led, because product fit is proven).

Mistake 4: Confusing lead-type names across motions

In a sales-led motion, you can have MQLs and SQLs. But in a product-led motion, these terms do not apply. Calling a free-tier user “an MQL” is wrong—they are just a free user. Calling a power user “an SQL” is wrong—they are a PQL (or not, depending on your signal).

This confusion leads to:

Trying to apply SQL qualification frameworks to PQLs (wrong motion).
Calling all inbound leads “MQLs” and not distinguishing between tire-kickers and genuinely interested buyers.
Using MQL/SQL terminology in a product-led motion, which breaks sales team alignment.

The fix: Name lead types for your motion. In sales-led, use MQL/SQL. In product-led, use Signup/Activated/PQL. In hybrid, use both but be clear about which path each type is on.

How to qualify properly: frameworks by motion

Sales-led: MQL → SQL qualification via BANT/MEDDIC

In sales-led, qualification happens in a sales conversation. The goal is to move MQLs to SQLs by confirming:

Budget: Does the prospect have money to buy? Do not assume. Ask. If they have not budgeted for a solution, they are a 2024 prospect (or 2025 if we are in 2023). Move them to nurture. Do not sell them yet.
Authority: Who makes the decision? Is your contact the decision maker, an influencer, or a blocker? If they cannot decide, find someone who can. Or build a selling motion around influencing the decision maker through your contact.
Need: Do they have a problem your product solves? This is the easiest one to mess up. Do not tell them the problem. Ask. Let them tell you. If they do not acknowledge the problem, or they think they do not need it, they are not qualified.
Timeline: When do they need to solve it? If the answer is “sometime next year,” move them to nurture. If the answer is “next month,” they are ready to sell to. Timeline creates urgency, and urgency moves deals.

(MEDDIC adds Metrics, Economic Buyer, Decision Criteria. SPICED adds Sponsor, Problem, Irrational, Champion, Economic, Decision. See 4.4.)

The conversion from MQL to SQL depends on your qualification bar. If you ask all four BANT questions and require all four to be met before calling someone an SQL, you will have a lower conversion (10%) but a higher close rate (60%+). If you call someone an SQL after just one conversation that hints at need, you will have higher conversion (30%) but lower close rate (25%).

The right bar depends on your sales team’s capacity. If you have one AE per million in ACV, you can afford to spend time on loose qualification (lower SQL conversion, high volume). If you have one AE per ten million in ACV, you need to pre-qualify hard (higher bar for SQL).

In product-led, qualification happens via product behavior, not conversation. Define your PQL signal:

Common signals:

Activation rate: Users who hit the aha moment (activated users are 5–10x more likely to convert than non-activated).
Team size or seat growth: Users who added 3+ team members are showing multi-user need.
Usage depth: Users who used advanced features, not just the basics.
Persistence: Users who came back > 20 days, or used the product > 10 times.
Company size / growth signals: Large companies or fast-growing startups may have different willingness to pay.
Negative signals that disqualify: Users in a company with < 5 employees, users who have not signed in for 60 days, users in a geography you do not serve.

Example: A PLG finance tool defines a PQL as:

“An activated user (created 3+ transactions in the product) AND has added 2+ team members AND is from a company with 20–500 employees AND has not been inactive for 30+ days.”

This signal predicts that 60% of users meeting all four criteria will convert to paid. Users meeting 1–2 criteria convert at 15%. Users meeting zero convert at 2%.

When you identify a PQL, your motion is simple: in-product upgrade prompt + welcome email + maybe a sales development rep reaching out to say “I see you are using this feature. Want to learn about pro-tier accounts?”

The sales motion is not discovery. It is: “You already use this. Here is how to expand.”

Hybrid: Dual qualification (product + sales)

Define your routing signal clearly. Example:

“Free users who have activated AND added 2+ team members → route to sales as warm lead. Free users who have activated but are solo → send self-serve upgrade prompts. Free users who have not activated → nurture email, in-product tips.”

The sales motion for the warm lead is very different from cold sales-led. It is: “You are using this for X. You added a team. The pro plan is designed for teams. Want to see what your team is missing?”

Conversion from warm lead to paid is typically 50–70% because product-market fit is already proven.

Real examples: lead types in the wild

Example 1: Sales-led SaaS company (Zendesk-like)

They are an enterprise ticketing tool. They run outbound sales.

Leads enter as MQLs: SDRs research companies matching their ICP (1000+ employee companies), send cold emails. Some reply. Those replies are marked MQL. 300 MQLs per month.
MQL → SQL: SDR books a 20-minute exploratory call. SDR confirms: (a) they have a support problem, (b) they are not already running another ticketing system (if they are, they are a longer cycle), (c) there is a champion interested. If all three: SQL. Conversion: 15%. So 45 SQLs per month.
SQL → Opportunity: AE has a full 45-minute discovery call. Confirms budget (usually a 3-year deal = $200k+, but sometimes $50k annual). Confirms they have a procurement process. Confirms the champion can move it. If yes: Opportunity. Conversion: 80%. So 36 opps per month.
Opportunity → Close: 60% close rate (they are very selective). So 22 customers per month.

Total: 300 MQL → 22 customers. 7.3% MQL-to-close.

Key insight: Most of the math is front-loaded. The MQL → SQL conversion is the biggest drop (15%). But it has to be. An SDR cannot call 300 companies. By filtering with qualification criteria, they call 100 and book 15 conversations, of which maybe 5 are true SQLs after getting fuller information on the first call. The AE then has time to work them properly.

Example 2: Product-led SaaS (Figma-like)

They are a design tool. No sales team initially.

Leads enter as signups: Anyone can sign up. 50,000 signups per month.
Signup → Activation: They define activation as “created and shared a file.” Activation rate: 45%. So 22,500 activated users per month.
Activation → PQL: They define PQL as “shared file with 3+ collaborators.” This signal shows multi-user intent and predicts a 55% conversion to paid. PQL rate: 18% of activated (maybe they are not all multi-user yet). So 4,050 PQLs per month.
PQL → Expansion/Paid: When users hit PQL signal, they get an in-product upgrade prompt and a welcome email from the founder. 55% convert to paid or enterprise. So 2,227 paid users per month.

Total: 50,000 signup → 2,227 paid. 4.45% signup-to-paid.

Key insight: No qualification conversation needed. No sales team. The product itself qualifies the user via behavior. By the time someone is a PQL, they have already decided the product is valuable. The upgrade conversation is “yes, you are ready to expand” not “does our product solve your problem?”

Example 3: Hybrid (Slack-like in mid-market)

They sell to teams and enterprises with a hybrid motion.

Leads enter via product or sales: Signup (50k/month) + outbound-sourced leads to book free trial (2k/month).
Product path - Signup → Activation: 60% of signups reach aha (organize first channel). So 30k activated.
Product path - Activation → Warm lead for sales: 15% of activated users meet the routing signal: 5+ team members OR 500+ messages OR 30+ days active AND company > 50 employees. So 4,500 warm leads.
Sales motion for warm leads: Sales rep notes: “I see you are using 5+ channels and have a 20-person team. Want to learn about team management and SSO?” 60% convert. So 2,700 conversions.
Outbound path - Direct to sales: 2,000 outbound-sourced leads. Sales has a lighter discovery (product fit is assumed to exist in market, but prospect has not tried yet). 45% move to SQL. 900 SQLs. 50% close. 450 customers.

Total: (50k signup + 2k outbound) → (2,700 + 450) = 3,150 customers. ~5.6% conversion for product path, 22.5% for sales path (but sales path is smaller volume).

Key insight: The hybrid motion is efficient because it routes high-intent users (who are already in the product) to sales, where the sales motion is warm (not discovery-heavy) and high-converting. Low-intent users stay in product and do not waste sales time. The routing signal is everything.

Rules: name, measure, segment, route

Rule 1: Name your lead types for your motion.

In sales-led, use MQL and SQL. In product-led, use Signup, Activated, PQL. In hybrid, use both but be explicit about routing. Do not use “lead” generically in a sentence like “we processed 500 leads.” Instead: “we generated 500 MQLs and converted 75 to SQLs.”

Rule 2: Measure conversion by lead type and by source.

Build a cohort table: Lead Type × Source × Conversion to SQL/Close. You cannot optimize what you do not segment. “Overall conversion” is useless. “MQL from inbound content to SQL” is actionable.

Rule 3: Define your qualification criteria and document them.

For sales-led: Write down your BANT/MEDDIC framework. What does “budget confirmed” mean? How many budget questions do you ask? For product-led: Write down your PQL signal. What exact behavior flags a user as high-probability-to-convert? For hybrid: Write down your routing signal. What product behavior moves someone from nurture to sales?

Rule 4: Route by signal, not by guesswork.

Do not route a lead based on “the AE asked for it” or “this came in through event, so it is hot.” Route by your defined signal (qualification framework for sales, product behavior for PQL, routing signal for hybrid). This removes bias and makes the motion reproducible.

Rule 5: Do not confuse lead types across motions.

If you run sales-led, do not try to apply product-led qualification. If you run product-led, do not force a sales discovery conversation on a PQL. If you run hybrid, do not apply sales-led qualification to product-qualified users. Match the motion to the lead type.

Next: once you have qualified a lead, how do you move them through the funnel? How do you structure the conversation (for sales) or the product experience (for product) to maximize conversion? That is Qualification frameworks: BANT, MEDDIC, SPICED.

Key definition summary:

MQL: Interest + basic ICP fit. Sales-led only. 10–30% convert to SQL.
SQL: Interest + problem + budget + timeline confirmed. Sales-led only. 30–60% convert to close.
PQL: Already in product + high-value behavior signal. Product-led only. 40–70% convert to paid or expansion.
Warm lead (hybrid): Signup → activated → routed to sales by signal. 50–80% convert to close.
Lead type depends on motion. Do not use MQL in a product-led motion. Do not send cold discovery to a PQL. Match the definition to the motion.

Key takeaways

Lead types are not universal. An MQL in one motion is an SQL in another. The definition depends on your motion and what 'ready' actually means in your context.
MQL catches interest early (broad net, low conversion). SQL is high-intent (narrow net, higher conversion). PQL is already in the product (self-filtered, usage-based, highest conversion). Do not mix them.
Founder mistake: treating all leads the same. An MQL needs lead nurturing; an SQL needs sales engagement; a PQL needs a different motion entirely.
Founder mistake: not measuring lead-type-to-close conversion. You cannot optimize something you do not segment.
Founder mistake: building the wrong process. Sales-led motions need SQL qualification; product-led motions do not use the term. Hybrid motions need both and a routing signal.
Name your lead types. Measure conversion by type. Route by signal. That is qualification.

Related concepts

BANT qualificationSales-qualified lead (SQL)Marketing-qualified lead (MQL)Product-qualified lead (PQL)Lead scoringLead routing

How to cite this

@misc{shalvi_gtm_fundamentals_lead_types_and_qualification_2026,
  author = {Singh, Shalvi},
  title  = {Lead types and qualification},
  year   = {2026},
  url    = {https://shalvisingh.com/gtm/fundamentals/lead-types-and-qualification},
  note   = {GTM World Model — GTM Fundamentals}
}

Singh, Shalvi. "Lead types and qualification — GTM Fundamentals." shalvisingh.com, 2026. https://shalvisingh.com/gtm/fundamentals/lead-types-and-qualification