MQL and SQL criteria define when a lead should move from marketing qualification to sales qualification.
An MQL, or marketing qualified lead, is a lead that appears relevant enough for further evaluation based on fit, engagement, source, behavior, or declared interest. An SQL, or sales qualified lead, is a lead that sales has accepted as worth active follow-up because there is enough evidence of fit, intent, and potential commercial relevance.
The problem is that many B2B teams use these labels loosely. Marketing calls a lead “qualified” because it filled out a form. Sales rejects it because the account is not a fit, the person has no urgency, or the request is too vague. The CRM shows movement, but the business still does not know whether lead generation is producing real pipeline.
MQL and SQL should not be subjective opinions. They should be operational lifecycle stages with clear criteria, ownership, and measurement.
Key takeaways
- MQL and SQL criteria should be defined jointly by marketing, sales, and revenue operations.
- A form submission is not automatically an MQL, and an MQL is not automatically an SQL.
- MQL criteria usually focus on account fit, engagement, source, and declared interest.
- SQL criteria require stronger sales readiness: clear need, relevant company, valid contact, and accepted follow-up path.
- The handoff should include CRM data, routing rules, disqualification reasons, and service-level expectations.
- The quality of MQL and SQL definitions should be measured by sales acceptance, opportunity conversion, and disqualification patterns.
What MQL and SQL mean in B2B lead generation
An MQL is a lead that marketing considers qualified enough for the next step. It may not be ready for direct sales pursuit yet, but it has enough positive signals to move beyond a raw contact or low-intent subscriber.
An SQL is a lead that sales considers qualified enough for active sales follow-up. This means the lead has passed a higher threshold: the company appears relevant, the problem is connected to the offer, the person is reachable, and sales has a reasonable next action.
A simple distinction:
| Lifecycle stage | Main question | Owner | Typical action |
|---|---|---|---|
| Raw lead | Did someone submit information or enter the database? | Marketing operations | Store, validate, classify |
| MQL | Does this lead look relevant enough for further qualification? | Marketing | Route, score, enrich, or prepare for handoff |
| SQL | Does sales accept this lead as worth active follow-up? | Sales | Follow up, qualify deeper, create opportunity if valid |
| Opportunity | Is there a real potential deal? | Sales | Manage pipeline stage |
| Disqualified | Why should this lead not continue? | Shared | Record reason and analyze pattern |
The main point: MQL and SQL are not vanity labels. They are workflow states.
If the labels do not change routing, ownership, or reporting, they are not useful.
Why MQL and SQL definitions break down
MQL and SQL definitions usually break down when the team has no shared criteria.
🔍 Diagnostic signal: Compare the visible activity metric with qualified outcomes before changing the channel, page, or budget.
Common failure patterns include:
- Marketing defines MQL by form submission only;
- Sales defines SQL differently by rep;
- Scoring thresholds are not connected to actual sales outcomes;
- CRM fields are incomplete;
- Sales rejects MQLs without structured reasons;
- Content leads are treated as sales-ready;
- Fit and intent are mixed into one vague score;
- Lead source quality is judged only by CPL;
- Lifecycle stages are updated manually and inconsistently;
- The team does not review MQL-to-SQL conversion by channel.
This creates predictable conflict.
Marketing reports lead volume. Sales says the leads are not good. Leadership asks which channel is working. The CRM cannot answer because the MQL and SQL stages do not reflect a disciplined qualification process.
The fix is not only better scoring. The fix is a clearer handoff definition.
The difference between MQL and SQL criteria
MQL and SQL should use related but different criteria.
MQL criteria usually answer: does this lead deserve more attention from the system?
SQL criteria answer: does this lead deserve active sales follow-up?
| Criteria area | MQL threshold | SQL threshold |
|---|---|---|
| Account fit | Appears to match target segment | Confirmed or strongly likely fit |
| Contact quality | Valid enough for follow-up or nurture | Reachable and connected to the account |
| Intent | Shows relevant interest or engagement | Shows commercial or operational need |
| Urgency | May be unknown | Clear enough to prioritize or evaluate |
| Role | Relevant or potentially influential | Has buying influence or access to decision process |
| Data completeness | Enough to classify | Enough for sales to act |
| Source quality | Comes from relevant campaign, page, or channel | Source supports real sales context |
| Next action | Route, enrich, nurture, or review | Sales follow-up or discovery |
| Owner | Marketing or operations | Sales |
| Failure path | Continue nurture or review | Disqualify, recycle, or create opportunity |
This distinction prevents a common mistake: expecting MQLs to behave like opportunities.
An MQL is not a closed deal in waiting. It is a lead that has crossed a marketing-defined threshold and needs the right next step.
A practical MQL criteria framework
A lead can become an MQL when it meets enough criteria across fit, intent, and data quality.
A practical MQL framework can include five layers.
1. Account fit
The company should appear relevant based on basic characteristics.
Possible fit criteria:
- Target industry;
- Company size range;
- Business model;
- Region served;
- Market maturity;
- Relevant team or department;
- Known account type;
- Not clearly excluded by negative criteria.
Account fit does not need to be perfect at the MQL stage, but it should be plausible.
2. Contact credibility
The contact should be real enough to classify.
Possible credibility criteria:
- Valid email format;
- Work email or credible personal email with company context;
- Real name;
- Company name or website;
- No obvious spam indicators;
- Not a vendor or irrelevant inquiry.
A lead with suspicious contact data should not become an MQL only because it submitted a form.
3. Relevant intent
The lead should show interest connected to a business problem.
Possible intent signals:
- Submitted a demo or pricing form;
- Described a relevant challenge;
- Visited high-intent pages;
- Engaged with bottom-of-funnel content;
- Attended a relevant webinar;
- Downloaded a topic-specific asset;
- Returned multiple times from the same company;
- Selected a relevant problem category.
Intent should be interpreted carefully. A content download may indicate topic interest, not buying readiness.
4. Data completeness
The record should contain enough information for the next step.
Minimum data may include:
- Email;
- Company name;
- Source;
- Form type;
- Landing page;
- Country or region if needed;
- Problem or topic interest;
- Lifecycle stage;
- Consent status where relevant.
If the lead lacks essential data, it may need enrichment or review before becoming an MQL.
5. Not excluded by disqualification rules
Some leads should not become MQLs even if they engaged.
Examples:
- Vendor inquiry;
- Student request;
- Competitor research;
- Support request;
- Wrong region;
- Fake or invalid data;
- Duplicate with no new signal;
- Clearly irrelevant company type.
Negative criteria are as important as positive criteria. They protect MQL quality.
A practical SQL criteria framework
A lead should become an SQL only when sales accepts it as worth active follow-up.
SQL criteria should be stricter than MQL criteria.
A practical SQL framework includes:
| SQL criteria | What it means | Example evidence |
|---|---|---|
| Confirmed or likely fit | The account fits the target profile | Company size, industry, region, use case |
| Clear business need | The lead has a relevant problem | Form message, sales reply, page intent |
| Reachable contact | Sales can contact the person | Valid email, phone if needed, real identity |
| Relevant role | The person has influence or access | Founder, executive, head of function, operator |
| Timing or priority | There is a reason to engage now or soon | Timeline, project stage, active evaluation |
| Enough context | Sales can prepare a meaningful follow-up | Problem, source, company, form type |
| Sales acceptance | Sales agrees to own next action | Accepted status in CRM |
SQL status should not be assigned automatically only because a lead crosses a score threshold.
Scoring can suggest priority. Sales acceptance confirms ownership.
How to define the handoff between marketing and sales
The MQL-to-SQL handoff should define five things clearly.
1. Entry criteria
What must be true before marketing can pass a lead to sales?
Examples:
- Target segment or plausible fit;
- Valid contact information;
- Relevant form or engagement signal;
- No disqualifying inquiry type;
- Source and campaign data captured;
- Enough context for sales to respond.
2. Sales acceptance criteria
What must be true before sales accepts the lead as SQL?
Examples:
- Company appears relevant;
- Contact is reachable;
- Need is commercially relevant;
- Sales has a clear next action;
- No obvious disqualification reason;
- Lead is not duplicate noise.
3. Response expectation
How quickly should accepted leads be reviewed or contacted?
Speed matters most for high-intent forms such as demo, pricing, or contact requests. Lower-intent leads may follow a different workflow.
4. Rejection rules
When can sales reject an MQL, and which reason must be recorded?
Examples:
- Poor company fit;
- No relevant need;
- Vendor;
- Support request;
- Student or researcher;
- Fake data;
- Duplicate;
- No buying influence;
- Wrong region;
- Incomplete context.
5. Feedback loop
How often should marketing, sales, and operations review MQL-to-SQL outcomes?
Useful review segments:
- By source;
- By campaign;
- By landing page;
- By form type;
- By content offer;
- By disqualification reason;
- By sales owner;
- By company segment.
This turns handoff into a system, not a debate.
What should happen when sales rejects an MQL
Sales rejection is not a failure by itself. It becomes a failure when the reason is not captured.
A rejected MQL should move into one of several states:
| Rejection outcome | When to use it | Next step |
|---|---|---|
| Disqualified | Clear poor-fit or invalid lead | Record reason and stop sales workflow |
| Recycle | Good-fit but not ready | Return to nurture |
| Enrich | Promising but incomplete | Add account or contact data |
| Re-route | Wrong owner or team | Assign correctly |
| Merge | Duplicate record | Associate with existing contact or account |
| Review | Mixed signals | Manual check before final status |
The key is to preserve learning.
If many MQLs are rejected for wrong company size, the targeting or form criteria may be too loose. If many are rejected for no relevant need, the offer or page message may be attracting curiosity instead of demand. If many are rejected as incomplete, the form or enrichment layer may need improvement.
CRM fields required for MQL and SQL tracking
MQL and SQL criteria require clean CRM data.
Useful fields include:
| CRM field | Why it matters |
|---|---|
| Lifecycle stage | Shows raw lead, MQL, SQL, opportunity, customer, disqualified |
| Lead status | Shows current workflow state |
| MQL date | Measures time to marketing qualification |
| SQL date | Measures time to sales acceptance |
| Lead source | Shows acquisition origin |
| Landing page | Connects conversion to page intent |
| Form name | Identifies conversion type |
| Campaign | Supports channel-level analysis |
| Company size | Supports fit criteria |
| Industry | Supports segment analysis |
| Region | Supports routing and eligibility |
| Role | Helps assess buying influence |
| Problem category | Captures intent |
| Qualification status | Shows current evaluation result |
| Sales acceptance status | Confirms handoff |
| Disqualification reason | Explains rejection |
| Owner | Shows responsibility |
| Last activity | Helps monitor follow-up timing |
The CRM should make the handoff visible.
If a lead changes from raw lead to MQL to SQL, the system should show when it happened, why it happened, who owns it, and what happened next.
Common mistakes
Mistake 1: Treating every form fill as an MQL
A form fill is a conversion event, not automatically a qualified lead. The lead may still be spam, vendor, poor-fit, low-intent, incomplete, or not sales-ready.
⚠️ Common risk: The team may improve traffic or submissions while the real constraint sits in fit, routing, or sales follow-up.
Mistake 2: Letting sales define SQL differently by rep
If each sales rep has a private definition of SQL, reporting becomes unreliable. SQL criteria should be shared and documented.
Mistake 3: Using lead score without explaining the score
A score is useful only if the underlying criteria are clear. A lead with a high score but poor company fit may not be valuable.
Mistake 4: Ignoring negative criteria
MQL criteria should include exclusions. Vendor inquiries, support requests, fake data, and wrong-fit companies should not become MQLs just because they engaged.
Mistake 5: No structured rejection reasons
“Bad lead” is not a useful reason. Sales rejection should produce data that marketing and operations can analyze.
Mistake 6: Judging marketing only by MQL volume
MQL volume is incomplete without MQL-to-SQL rate, sales acceptance, opportunity conversion, and disqualification patterns.
Mistake 7: Making SQL status purely automatic
Automation can suggest SQL readiness, but sales acceptance should confirm that the lead is worth active follow-up.
Metrics to track
MQL and SQL performance should be measured across the full handoff.
📊 Measurement note: Use qualified conversion, sales acceptance, and opportunity movement instead of raw form volume alone.
| Metric | What it shows |
|---|---|
| Raw lead-to-MQL rate | How many leads meet marketing criteria |
| MQL-to-SQL rate | How many MQLs sales accepts |
| Sales acceptance rate | Whether sales trusts marketing qualification |
| MQL rejection rate | How often sales rejects MQLs |
| Disqualification reason mix | Why leads fail |
| Time from lead to MQL | Speed of marketing qualification |
| Time from MQL to SQL | Speed of sales acceptance |
| SQL-to-opportunity rate | Whether SQLs become real pipeline |
| Source-to-SQL rate | Which channels produce sales-accepted leads |
| Cost per SQL | Acquisition efficiency beyond CPL |
| MQL-to-opportunity rate | Whether marketing qualification predicts pipeline |
| SQL aging | Whether accepted leads are followed up |
The most important view is not total MQLs. It is MQL quality by source.
For each source or campaign, compare:
- Raw leads;
- MQLs;
- SQLs;
- Rejected MQLs;
- Disqualification reasons;
- Opportunities;
- Cost per SQL;
- Source-to-opportunity rate.
This shows whether marketing is generating activity or qualified demand.
Practical checklist
Use this checklist to define MQL and SQL criteria.
🛠 Operating fix: Review one complete path from source to CRM record to next sales action before changing spend.
- Define what counts as a raw lead.
- Define what minimum data is required before MQL status.
- Separate account fit from engagement.
- Create negative criteria for vendors, spam, support, students, and poor-fit inquiries.
- Decide which actions create strong intent and which only show light engagement.
- Map MQL criteria to CRM fields.
- Define what sales must confirm before SQL status.
- Require sales acceptance before counting a lead as SQL.
- Create structured rejection reasons.
- Track MQL date and SQL date.
- Review MQL-to-SQL rate by channel and form type.
- Compare SQLs to opportunities, not only to lead volume.
- Recycle high-fit but not-ready leads instead of deleting them.
- Review criteria regularly with marketing, sales, and operations.
- Update definitions when the ICP, offer, or sales process changes.
FAQ
What is the difference between MQL and SQL?
An MQL is a lead that marketing considers qualified enough for further evaluation or handoff based on fit, engagement, and available data. An SQL is a lead that sales accepts as worth active follow-up because it appears commercially relevant and actionable.
Is every demo request an SQL?
Not automatically. A demo request may show strong intent, but it still needs basic fit, valid contact data, relevant need, and sales acceptance. Some demo requests may be vendors, students, poor-fit companies, or incomplete submissions.
Who should define MQL and SQL criteria?
Marketing, sales, and revenue operations should define the criteria together. Marketing understands source and engagement. Sales understands buyer readiness. Operations ensures the criteria can be captured and measured in the CRM.
What should happen when sales rejects an MQL?
Sales should record a structured rejection reason. The lead can then be disqualified, recycled, enriched, merged, re-routed, or reviewed. The rejection reason should be analyzed by source, campaign, form, and landing page.
Should lead scoring determine MQL status?
Lead scoring can help identify MQL candidates, but it should not be the only rule. Fit, intent, data quality, negative criteria, and business context should also be considered.
What is the most important MQL-to-SQL metric?
Sales acceptance rate and MQL-to-SQL conversion are critical. They show whether marketing-qualified leads are actually useful to sales. SQL-to-opportunity rate is also important because it shows whether sales-accepted leads become real pipeline.
Practical summary
MQL and SQL criteria are not just terminology. They define how marketing-generated demand moves into sales ownership.
A strong MQL definition identifies leads that appear relevant based on fit, intent, engagement, and data quality. A strong SQL definition confirms that sales accepts the lead as worth active follow-up.
The handoff works best when both stages are tied to clear CRM fields, routing rules, disqualification reasons, and measurable outcomes. The goal is not to create more lifecycle labels. The goal is to reduce guesswork, protect sales capacity, and make lead generation performance visible beyond raw lead volume.
How did this article land?
Choose one reaction. You can change it anytime.
