Sales Ops Glossary · Pipeline & Forecast
A Marketing Qualified Lead (MQL) is a prospect that a marketing team has identified — through behavioral signals, firmographic fit, or lead scoring — as sufficiently interested and well-matched to the ideal customer profile to be worth passing to sales for follow-up. An MQL is not yet sales-ready; it is a candidate for sales qualification.
The MQL is where marketing's responsibility ends and sales development's begins. Before reaching MQL status, a contact is simply a name in the database — someone who has given their email in exchange for a piece of content, attended a webinar, or been added to a cold outreach sequence. Once they hit the MQL threshold — typically a combination of firmographic fit and behavioral engagement — they're surfaced to the SDR team for outreach. The MQL is marketing's deliverable to sales.
MQL definitions vary widely across organizations, which is a significant source of misalignment between marketing and sales teams. In a well-functioning operation, the MQL definition is co-owned: marketing agrees to deliver leads that meet a specific quality bar, and sales agrees to follow up within a defined SLA. Without a shared definition — written down, agreed upon, and reviewed quarterly — marketing optimizes for MQL volume while sales complains about lead quality, and neither team has enough data to resolve the disagreement.
Without an MQL framework, marketing and sales operate as disconnected silos. Marketing generates leads and throws them over the wall; sales complains the leads are bad; marketing defends their numbers; no one improves anything. The MQL framework creates a contractual accountability point: marketing commits to delivering a minimum volume of leads that meet a defined quality bar, and sales commits to following up within a defined SLA. When conversion rates are measured at every handoff — lead to MQL, MQL to SQL, SQL to close — both teams have the data to identify where the problem actually lives.
MQL volume and quality are two of the most important leading indicators of future pipeline. Because sales cycles typically run 30–120 days, the MQLs generated today directly determine how much pipeline will exist next quarter. RevOps teams that model MQL-to-pipeline conversion can forecast pipeline shortfalls 60–90 days in advance — early enough to intervene with campaign investment, event participation, or outbound prospecting to fill the gap. Organizations without an MQL tracking process are essentially flying blind on future pipeline visibility.
Evaluating pipeline & forecast tools?
Browse software →Lead scoring models degrade over time if they aren't maintained. A scoring model built two years ago may weight actions that no longer predict buying intent — an old whitepaper that everyone downloads but few buyers act on, or a job title that the ICP has shifted away from. RevOps teams should audit lead scoring models quarterly, comparing MQL-to-SQL conversion rates for leads from different sources and score ranges. Leads scoring above the MQL threshold but converting to SQL at under 5% are a sign the scoring model needs recalibration.
The biggest practical mistake in MQL programs is treating all MQLs as equal. A contact who requested a demo and works at a company that matches the ICP exactly is a very different MQL from a contact who downloaded a top-of-funnel ebook from a company that is 10× too small. Segmenting MQLs by quality tier — and routing them to different SDR workflows — allows teams to allocate follow-up resources based on lead potential. Tier 1 MQLs get an immediate personal call; Tier 3 MQLs enter an automated nurture sequence.
MQL definitions should be a joint agreement between marketing and sales leadership, revisited every six months. The most effective process: marketing and sales ops review the previous two quarters of MQL-to-SQL conversion data together, identify the firmographic and behavioral attributes that most strongly predict SQL conversion, and update the scoring model accordingly. This feedback loop — close data informing lead scoring — is the mechanism that makes an MQL program progressively more accurate over time.
When marketing is measured solely on MQL volume, teams optimize for quantity by lowering the threshold — more leads, more MQLs, lower quality. SDRs end up spending 60–70% of their time on leads that will never convert, pipeline generation stalls, and the downstream effect is a pipeline shortage that marketing can plausibly deny responsibility for because their MQL numbers look fine.
If SDRs don't document why MQLs failed to convert to SQL — no budget, wrong persona, no active project, competitor already selected — marketing has no signal to improve lead quality. Without disposition data flowing back into the scoring model, the same low-quality lead profiles keep hitting the MQL threshold quarter after quarter, wasting SDR capacity and distorting funnel metrics.
Research consistently shows that lead conversion rates drop sharply after the first five minutes. An MQL who filled out a demo request form and received an SDR email 48 hours later has likely moved on, engaged a competitor, or lost the urgency that drove the original action. Teams without an MQL follow-up SLA and enforcement mechanism routinely see 30–40% lower conversion rates than teams that follow up within the hour on high-intent MQLs.
MQL processes are orchestrated through marketing automation platforms (HubSpot, Marketo, Pardot) for scoring and routing, and managed in a CRM for handoff and disposition tracking. Revenue operations tools like LeanData and Chili Piper automate routing logic. Sales engagement platforms (Outreach, Salesloft) run the SDR follow-up sequences that convert MQLs into SQLs.
An MQL is a lead that marketing has scored as ready for sales outreach based on behavioral and firmographic criteria — it's a signal of potential interest and fit, not confirmed buying intent. An SQL is a lead that has been personally qualified by a sales development rep and confirmed to meet specific criteria: a real problem, budget availability, decision-maker access, and a defined timeline. MQLs are machine-scored; SQLs are human-verified. The MQL-to-SQL process is the qualification step between the two.
A good MQL definition combines firmographic fit (company size, industry, job title match your ICP) with behavioral signals that indicate active interest or urgency (pricing page visit, demo request, trial signup, or multiple high-intent content downloads). It should be specific enough that any SDR can evaluate a lead against it consistently, and it should be calibrated against real conversion data — the percentage of leads meeting the definition that actually convert to SQL should be 15% or higher. Definitions based purely on email opens or generic page views produce too many low-quality MQLs.
For B2B SaaS, a conversion rate of 15–20% is considered healthy. Below 10% typically indicates a lead quality problem — either the scoring model is too loose or marketing is optimizing for volume over fit. Above 25–30% can mean the threshold is too strict and some qualified prospects are being filtered out before SDR outreach. The most important thing is to track the rate consistently and understand the trend — a rate that was 18% and is now 10% is a more urgent problem than a steady 12% rate.
Quarterly reviews are best practice, with a deeper annual recalibration. Each quarterly review should compare the firmographic and behavioral attributes of leads that converted to SQL against those that didn't — and adjust point values accordingly. Annual recalibration should align the scoring model with any ICP shifts, new product capabilities, or changes in the buyer journey. Scoring models that go more than 18 months without review typically drift significantly out of alignment with current buyer behavior.
Every non-converted MQL should be dispositioned with a documented reason — not just marked as 'no response.' Common dispositions include: not a fit (wrong company size, wrong persona), timing issue (no active project, budget cycle mismatch), already a customer, or competitor already selected. These disposition codes feed back into the lead scoring model to reduce future false positives. Leads with a 'timing issue' disposition should be recycled back to a marketing nurture track with a re-engagement trigger date, not discarded permanently.