The Definitions That Actually Matter
A Marketing Qualified Lead (MQL) is a prospect who has demonstrated enough interest through their behavior and profile to warrant sales follow-up, but has not yet been validated by a salesperson. A Sales Qualified Lead (SQL) is a prospect that a salesperson has personally vetted and confirmed as a genuine opportunity worth pursuing. The key distinction is who does the qualifying: marketing qualifies MQLs based on data and automation, sales qualifies SQLs based on conversation and judgment.
This sounds simple, but in practice the MQL-to-SQL handoff is where most B2B pipelines break down. Marketing complains that sales ignores their leads. Sales complains that marketing sends them garbage. The argument has been raging since the terms were coined in the early 2000s, and it persists because most companies never agree on precise definitions. Without shared criteria for what constitutes an MQL and an SQL, the two teams are operating from different playbooks.
Let us fix that. This guide provides the exact framework for defining, measuring, and optimizing the MQL-to-SQL lifecycle. Whether you are a startup defining these stages for the first time or an enterprise trying to fix a broken handoff process, the principles are the same.
The Complete Lead Lifecycle
Before we dive into MQL and SQL specifically, it helps to understand the full lead lifecycle. The standard stages are: Anonymous Visitor (someone browsing your website), Known Lead (someone who has provided their email, typically through a form fill or content download), MQL (a lead that meets marketing's qualification criteria), SQL (a lead that sales has accepted and validated), Opportunity (an SQL that has entered a formal sales process with a defined deal size and timeline), and Customer (a closed-won deal).
Some companies add intermediate stages like 'Sales Accepted Lead' (SAL) between MQL and SQL, which represents the moment sales acknowledges the lead but has not yet qualified it. Others add 'Product Qualified Lead' (PQL) for product-led growth companies where the product itself generates qualification signals. The specific stages matter less than having clear, agreed-upon definitions and a process for moving leads between them.
The critical transition points are Lead to MQL (automated, based on scoring), MQL to SQL (human judgment from sales), and SQL to Opportunity (formal deal creation in CRM). Each transition should have explicit criteria, a defined SLA for response time, and metrics tracking conversion rates and velocity.
How to Define MQL Criteria
MQL qualification should combine two dimensions: demographic fit (who the person is) and behavioral engagement (what the person has done). Both matter. A VP of Sales at a mid-market SaaS company who visited your pricing page once is a different lead than a marketing intern at a Fortune 500 who downloaded 10 whitepapers. The VP is high fit, low engagement. The intern is low fit, high engagement. Neither is a strong MQL on its own.
Demographic Fit Criteria
Demographic fit measures how closely a lead matches your Ideal Customer Profile (ICP). Typical criteria include: job title or seniority (Director+, VP+, C-suite), department (Sales, Marketing, Revenue Operations), company size (50-500 employees, or $10M-$100M revenue), industry (SaaS, financial services, healthcare), and geography (North America, UK, DACH). Assign point values to each criterion. For example: C-suite title = 20 points, VP = 15, Director = 10, Manager = 5, Individual Contributor = 0. Company in target size range = 15 points. Target industry = 10 points. Use firmographic enrichment tools like Clearbit, Apollo, or Clay to automatically score these attributes when a lead enters your system.
Behavioral Engagement Criteria
Behavioral scoring measures what a lead has done to indicate purchase intent. Common scoring actions include: visited pricing page (20 points, the single strongest intent signal), requested a demo (50 points, immediate MQL), attended a webinar (10 points), downloaded a case study (10 points), downloaded a whitepaper (5 points), opened 3+ emails (5 points), visited 5+ pages in one session (10 points), and returned to the site 3+ times in 30 days (15 points). The key principle is that actions closer to a purchase decision should carry more weight. Visiting the pricing page is worth more than reading a blog post because it signals active evaluation, not passive learning.
Setting the MQL Threshold
Most lead scoring systems use a threshold approach: when a lead's total score (demographic + behavioral) crosses a certain number, they become an MQL. The right threshold depends on your volume and sales team capacity. If you set it too low, you flood sales with unqualified leads and waste their time. If you set it too high, you miss good opportunities. A common starting point is 50 points to MQL, with the expectation that a lead needs both reasonable fit and meaningful engagement to cross the line.
Review your MQL threshold quarterly. Pull the data on MQL-to-SQL conversion rates and adjust. If less than 20% of MQLs convert to SQLs, your threshold is too low, meaning marketing is sending leads that sales does not find qualified. If more than 50% convert, your threshold might be too high, meaning you are leaving leads on the table that sales would have wanted to pursue. The sweet spot for most B2B companies is a 25-35% MQL-to-SQL conversion rate.
How to Define SQL Criteria
While MQLs are qualified by algorithms, SQLs are qualified by humans. When a salesperson follows up on an MQL, they need a clear framework for deciding whether to accept it (convert to SQL) or reject it (send back to marketing for further nurturing).
The BANT Framework
BANT (Budget, Authority, Need, Timeline) is the oldest and most widely used SQL qualification framework. A lead qualifies as an SQL if they have Budget allocated or allocatable, Authority to make or influence the purchase decision, a Need that your product solves, and a Timeline that suggests they will buy in the foreseeable future (typically within 6 months). BANT is straightforward but has limitations. In modern B2B sales, budget is often created rather than pre-allocated, and buying decisions involve committees rather than single authorities. Use BANT as a baseline, not a rigid checklist.
The MEDDIC Framework
MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) is a more sophisticated qualification framework used by enterprise sales teams. It goes beyond BANT by asking: What metrics will the prospect use to measure success? Who is the economic buyer with budget authority? What criteria will they use to evaluate solutions? What is the internal decision process (committee, board approval, procurement)? What specific pain are they experiencing? And do you have a champion inside the organization advocating for your solution? MEDDIC is more thorough but requires deeper discovery conversations, making it better suited for high-value enterprise deals.
Regardless of which framework you use, the SQL definition should be documented, agreed upon by both marketing and sales leadership, and revisited quarterly. Write it down in a shared document. Make it part of your sales onboarding. If you cannot point to a written SQL definition that both teams signed off on, you do not have a real definition.
The MQL-to-SQL Handoff Process
The handoff is where deals are won or lost, not in a metaphorical sense, but literally. Research from InsideSales.com (now XANT) found that responding to a lead within 5 minutes makes you 21x more likely to qualify that lead compared to responding after 30 minutes. Harvard Business Review published a similar study showing that companies responding within an hour were 7x more likely to have a meaningful conversation with a decision maker. Speed matters enormously.
Establishing an SLA
A Service Level Agreement between marketing and sales defines the commitments each team makes. Marketing commits to delivering a certain number of MQLs per month that meet the agreed-upon qualification criteria. Sales commits to following up on every MQL within a defined time window, typically 4 hours during business hours. The SLA should also define what happens when an MQL is rejected: sales must provide a reason (wrong persona, no budget, bad timing, etc.) and marketing must route the lead back into nurturing.
Track SLA compliance rigorously. Build a dashboard that shows: percentage of MQLs contacted within the SLA window, average response time, MQL acceptance rate, MQL rejection reasons (categorized), and MQL-to-SQL conversion rate by source, campaign, and sales rep. Reviewing this data weekly keeps both teams accountable and reveals optimization opportunities.
The Technical Handoff
In HubSpot, the typical handoff flow is: lead score hits MQL threshold, which triggers a workflow that changes the lifecycle stage to MQL, assigns an owner based on territory or round-robin rules, creates a task for the owner, and sends a Slack notification. In Salesforce, the equivalent is a lead score trigger that updates the lead status, assigns via lead assignment rules, and creates an activity. The key is automation. If the handoff depends on a human manually checking a list, leads will fall through the cracks.
Common Problems and How to Fix Them
MQL Inflation
MQL inflation happens when marketing games the scoring system to hit their MQL targets. This can be intentional (lowering the threshold, adding low-value scoring actions) or unintentional (a viral blog post drives massive form fills from non-ICP visitors). The result is the same: sales gets flooded with weak leads, follow-up rates drop, and trust between teams erodes. The fix is to tie marketing's KPIs not just to MQL volume but to downstream metrics: MQL-to-SQL conversion rate, pipeline generated, and revenue influenced. When marketing is measured on lead quality, not just quantity, inflation disappears.
SQL Rejection Without Feedback
When sales rejects an MQL without explaining why, marketing cannot improve. Require sales reps to select a rejection reason from a predefined list (not ICP, no budget, bad timing, already a customer, duplicate, etc.) whenever they disqualify an MQL. Analyze rejection reasons monthly. If 40% of rejections are 'not ICP,' your demographic scoring is off. If 30% are 'no budget,' you might be targeting companies that are too small. These patterns are gold for improving lead quality.
The Definition Debate
If marketing and sales cannot agree on MQL/SQL definitions, bring revenue leadership (CRO, VP Revenue, or CEO) into the conversation to arbitrate. Present data: what is the current conversion rate, what are the most common rejection reasons, and what would the pipeline impact be under different threshold scenarios? Data-driven definitions end political debates. If you do not have the data yet, agree on provisional definitions and commit to revisiting in 90 days.
Key Metrics and Benchmarks
Here are the metrics every B2B company should track across the MQL-SQL lifecycle, along with benchmarks from industry data compiled by Implisit (Salesforce analytics), SiriusDecisions, and Forrester.
MQL-to-SQL Conversion Rate: The percentage of MQLs that sales accepts as SQLs. Benchmark: 13-25%, with best-in-class companies hitting 30%+. If you are below 13%, your MQL criteria are too loose. SQL-to-Opportunity Conversion Rate: The percentage of SQLs that become formal pipeline. Benchmark: 50-65%. If below 50%, your SQL criteria may need tightening. MQL-to-Customer Conversion Rate: The end-to-end conversion from MQL to closed deal. Benchmark: 2-5% for mid-market, 5-15% for enterprise with named accounts.
Average time from MQL to SQL: Benchmark is 1-3 days. If it takes more than a week, your handoff process is broken. Average time from SQL to Opportunity: Benchmark is 7-14 days, reflecting the time needed for discovery calls and qualification. Cost per MQL: Varies enormously by channel, but typical ranges are $30-$100 for content marketing, $50-$200 for paid search, $100-$300 for events. Cost per SQL: Typically 3-5x cost per MQL due to the conversion drop-off.
Modern Alternatives to the MQL/SQL Model
The MQL/SQL framework has been the standard since HubSpot and Marketo popularized it in the 2010s, but growing numbers of B2B companies are moving beyond it. Here are the alternatives gaining traction in 2026.
Signal-Based Qualification
Instead of scoring leads based on their interactions with your marketing, signal-based qualification identifies buying intent from third-party data. Tools like Bombora, G2, and 6sense track when companies are researching topics related to your product across the broader internet. If a target account suddenly has 15 employees reading articles about 'CRM migration,' that is a stronger buying signal than one person downloading your whitepaper. Signal-based qualification shifts the focus from 'who engaged with our content' to 'who is actively in-market for our category.'
Product Qualified Leads (PQLs)
For product-led growth companies, PQLs have replaced MQLs as the primary qualification mechanism. A PQL is a user who has taken specific actions within your product that correlate with conversion to paid. For example: created a workspace, invited 3+ team members, used a key feature 5+ times, or hit a usage limit. PQLs are powerful because they are based on actual product usage rather than content engagement, which is a much stronger predictor of purchase intent. Companies like Slack, Dropbox, and Figma built their growth engines on PQL-based qualification.
Account-Based Qualification
In Account-Based Marketing (ABM), the unit of qualification is the account, not the individual lead. An account becomes 'qualified' when multiple contacts at the target company show engagement signals, when buying committee members are identified, and when intent data confirms the account is in an active buying cycle. This approach eliminates the MQL-SQL debate entirely by focusing both marketing and sales on the same target accounts from the start.
How to Set This Up in HubSpot and Salesforce
HubSpot Setup
In HubSpot, use the built-in lead scoring tool (Marketing Hub Professional or Enterprise) to create a scoring model. Go to Settings, then Properties, then HubSpot Score. Add positive scoring criteria for demographic fit (job title contains 'VP' or 'Director,' company size 50-500) and behavioral engagement (visited pricing page, submitted demo form, opened 5+ emails). Set the MQL threshold as a workflow trigger: when HubSpot Score crosses your threshold, the workflow updates Lifecycle Stage to MQL, assigns a contact owner via round-robin, creates a task, and sends a Slack notification. For SQL tracking, create a custom property called 'SQL Date' and train reps to update the lifecycle stage to SQL after their qualification call.
Salesforce Setup
In Salesforce, lead scoring is typically handled by a marketing automation platform (Pardot, Marketo, or HubSpot) that syncs scores to Salesforce. Create a custom lead field called 'Lead Score' and sync it from your automation tool. Build a lead assignment rule that routes leads above the MQL threshold to the appropriate sales rep based on territory, account ownership, or round-robin. Track the MQL-to-SQL transition using Lead Status picklist values (New, MQL, Working, SQL, Disqualified) and create reports showing conversion rates and cycle times between each stage.
How GTME Builds MQL/SQL Systems for Clients
At GTME, we help B2B companies design and implement their entire lead qualification infrastructure. This includes defining ICP-based scoring criteria, building automated scoring in HubSpot or Salesforce, setting up the MQL-to-SQL handoff with SLAs and Slack notifications, creating dashboards that track conversion rates across every stage, and running quarterly reviews to optimize thresholds based on actual conversion data.
Most companies we work with see a 20-40% improvement in MQL-to-SQL conversion rates within the first quarter, simply by implementing clear definitions and automated handoffs. If your marketing and sales teams are fighting over lead quality, we can help. Visit gtmeagency.com/services to learn about our RevOps packages.
The Bottom Line
MQL and SQL are not just labels in your CRM. They are the operational backbone of your revenue engine. When defined correctly, they create alignment between marketing and sales, accountability for both teams, and a measurable pipeline that you can optimize over time. When defined poorly, or not defined at all, they create finger-pointing, wasted effort, and a pipeline that feels like a black box.
Start by writing down your MQL and SQL definitions. Get marketing and sales leadership to agree on them. Build the scoring, handoff, and tracking infrastructure. Measure conversion rates. Optimize quarterly. It is not complicated, but it requires discipline and cross-functional collaboration. The companies that get this right build predictable revenue. The ones that do not spend every quarter wondering why they missed their number.