Your marketing team's monthly review opens with a slide showing 847 marketing qualified leads generated in October, comfortably above target. Thirty seconds later, the sales lead pulls up their own dashboard and reports that sales qualified only 68 of them, roughly 8%, well below the 25% baseline the two teams agreed to twelve months ago. Marketing pushes back: the agreed definition says engagement plus ICP fit, and 847 is correct against that definition. Sales pushes back harder: the leads they received were "box-tickers, not buyers," and the real intent threshold is nowhere near where marketing is setting it.
Both teams are right, which is exactly the problem.
The MQL versus SQL conversation is almost never, in practice, a definitional one. The internet is full of clean definitions, "an MQL has demonstrated interest, an SQL has demonstrated intent", and every marketing leader can recite them in their sleep. What breaks the handoff is not that the two teams do not know the definitions. It is that they are both quietly negotiating the definitions in their favour, every week, in Slack, in forecast meetings, and in the margins of CRM configuration tickets. Marketing optimises for MQL volume because that is what the team's goals look like. Sales optimises for a high SQL-to-opportunity conversion rate because that is what their forecast depends on. Finance picks whichever definition makes CAC look worse this quarter. The glossary that was written and signed off eighteen months ago is being re-litigated in real time, and nobody has formally reopened it.
A marketing qualified lead is a prospect marketing has evaluated against two criteria and confirmed meets both: a reasonable fit with the ideal customer profile (industry, company size, role, geography, and whatever other firmographic signals your team uses), and a meaningful level of engagement with your marketing (content downloads, event attendance, repeated site visits to pricing or product pages, or similar behavioural signals). The MQL stays with marketing for nurturing until it crosses the threshold where it is ready for direct sales attention.
A sales qualified lead is a prospect that sales has independently vetted and formally accepted as ready for direct outreach, usually by confirming some version of BANT (Budget, Authority, Need, Timeline) through either an inbound conversation or an outbound discovery call. The crucial word is "independently"; the SQL is sales' judgement, not marketing's handoff. An MQL becomes an SQL only when sales says so.
In between sits the Sales Accepted Lead, or SAL, which is increasingly standard in mature B2B teams. The SAL is the formal handoff moment: marketing passes the MQL to sales, and sales formally accepts it as worth working. Not every MQL becomes an SAL (some get rejected back to marketing for more nurturing), and not every SAL becomes an SQL (some get disqualified after the first conversation). The SAL exists precisely because the handoff needs a checkpoint; without it, marketing counts MQLs that sales never touched, sales counts rejections against marketing's quality score, and both teams end up in a definitional dispute at quarter-end.
The MQL-to-SQL conversion rate is often the single most-watched metric in the marketing-sales relationship, and it is being renegotiated constantly in ways nobody is tracking. If your MQL-to-SQL rate drops from 28% to 19% quarter over quarter, three completely different things could be causing it: your lead quality has genuinely degraded, sales has quietly tightened their SQL criteria, or the agreed definitions have drifted without anyone writing the change down. Each of those requires a different response, and if you cannot tell them apart, you will end up solving the wrong problem.
The downstream cost of definitional drift is substantial. Marketing budget decisions get calibrated to the MQL target. Sales headcount decisions get calibrated to the SQL volume. Both get calibrated to the handoff rate between them. When the definitions are drifting, every forecast built on top of them is drifting too, and the first time anyone notices is usually six weeks into a quarter when the pipeline number does not match what both teams were reporting. A clear KPI reporting cadence around the handoff is one of the most consequential governance investments a marketing leader can make, because it is the artefact that catches drift before it becomes a budget conversation.
If your business runs enterprise or complex B2B sales, you are almost certainly dealing with buying groups rather than individual decision-makers. The data on this is consistent across sources: typical B2B buying committees now average eight to ten stakeholders, and the person who fills in the form is rarely the person who signs the contract. In that environment, a traditional MQL, scored on one person's engagement with one piece of content, is a crude signal. The individual form-fill tells you less than the account-level pattern of three different roles from the same company engaging with product content over a four-week window, which is what buying-group signals actually look like.
This is why mature B2B teams are increasingly operating with a Marketing Qualified Account (MQA) alongside or instead of the traditional MQL. The handoff conversation shifts from "here is a lead for you to call" to "here is an account showing buying activity across multiple stakeholders, the person who filled the form is one of them, but the real intent signal is at the account level."
Where your team sits on this spectrum shapes almost every reporting conversation you have. Be honest about which stance you are actually in, not the one you tell leadership you are in.
Marketing and sales each operate with their own private definition of what qualifies a lead. The two definitions have never been formally written down or signed off. Weekly handoffs happen through CRM automation that was configured eighteen months ago and nobody fully remembers.
Marketing and sales have a shared qualification document, written at some point in the past, sitting in a shared drive. It gets referenced during onboarding and during quarterly disputes, and nowhere else in between.
Marketing, sales, and finance meet quarterly to review the agreed MQL, SAL, and SQL definitions, update them if the sales motion or market has shifted, and publish the updated glossary with a version number and effective date.
The team has moved beyond individual-lead qualification to account- or buying-group-level qualification. Marketing passes qualified accounts to sales, not qualified individuals, and the handoff rules account for multi-stakeholder engagement patterns rather than single form-fills.
Most teams describe themselves as sitting in the living-definition stance. Most are honestly closer to written-but-stale, with a document that has not been reviewed since the last reorg.
Teams that hold the MQL/SQL definition line over time tend to run the handoff on a written compact between marketing and sales, reviewed on a fixed cadence. We call this the qualification compact, and it has four components that together prevent the political drift that undoes most lead qualification systems.
Without all four components, the handoff tends to degrade into whichever team has the louder voice in that quarter's leadership meetings. With all four, the handoff becomes an operational discipline that holds up under budget scrutiny.
You cannot manage what you do not accurately measure, and the handoff between marketing and sales has a specific set of metrics worth tracking consistently. Industry benchmarks are directional (your mileage will vary by industry, sales motion, and ICP), but they give a useful calibration point against which to measure your own performance.
The reason the rejection reason distribution matters so much is that it is diagnostic. If 60% of MQL rejections are "bad fit," your ICP targeting needs work. If 60% are "bad timing," your lead scoring is firing too early. If 60% are "bad contact," your form or data enrichment is passing wrong information. Each diagnosis points to a different fix, and without the rejection reason breakdown, teams tend to default to "the MQL quality is bad" as a general complaint and spend six months on the wrong solution.
For B2B teams whose sales motion genuinely involves committee buying, the individual-lead MQL is becoming an increasingly weak signal, and the operational shift is toward Marketing Qualified Accounts (MQAs) or buying-group-level qualification. This does not mean abandoning the MQL overnight, individual engagement is still an input signal, but it does mean changing what gets passed to sales and how it gets evaluated.
The practical shift looks like this. Instead of qualifying one person based on their engagement, you aggregate engagement across every known and inferred contact at the account. When three different roles from the same company engage with product content over a four-week window, that is a buying-group signal, and it is a materially stronger indicator of real buying intent than any single form-fill. The handoff to sales becomes an account briefing rather than a lead handover: here is the account, here are the stakeholders showing engagement, here is the pattern of their activity, and here is the recommended next step.
A note of honest caution: buying-group qualification works well for high-ACV B2B with multi-stakeholder buying processes. It works less well for lower-ACV, individual-decision-maker purchases where the person who fills the form really is the buyer. If your sales motion is more transactional, the traditional MQL remains the right primary signal, the lesson is not that MQLs are dead universally, it is that they need to match the buying behaviour of your actual market.
Three governance practices separate a qualification compact that holds up over time from one that quietly degrades into private interpretations.
Publish the compact and the change log. The agreed definitions, SLAs, and acceptance protocols should live in a single document that marketing, sales, and finance can all reference, with a visible version number and change log. When someone asks "what counts as an SQL today," the answer is "version 3.2 of the compact, effective since September 1st, see the change log for the two changes from version 3.1." The alternative, definitions scattered across tribal knowledge and ad hoc Slack decisions, is exactly how drift happens.
Review the compact on a fixed quarterly cadence. Not when there is a dispute. Not when a quarter has gone wrong. Fixed cadence, agenda published in advance, decisions documented. The review covers the previous quarter's numbers against each metric in the compact, discusses whether any definitional drift has emerged, and formally updates the compact if the sales motion or market context has shifted. Fixed-cadence reviews catch drift before it becomes a crisis; reactive reviews only catch it after the budget conversation has already gone wrong.
Track rejection reasons as a first-class metric. The breakdown of why sales rejected MQLs over the quarter is the single most useful diagnostic signal in the handoff system. It should be visible on every weekly operational dashboard, reviewed quarterly as part of the compact review, and treated as the primary input into any decision to adjust the MQL definition or scoring model. Teams that treat rejection reasons as noise end up making qualification-model changes based on vibes; teams that track them properly make changes based on diagnostic evidence.
Two operational patterns quietly undermine most lead qualification systems, regardless of how good the initial definitions are.
Four moves worth making immediately, whether your qualification system is new or has been running for years.
Everything above assumes marketing and sales can agree on a shared view of the handoff numbers in the first place. For most teams, that is exactly where the process breaks.
Your MQL volume lives in your marketing automation platform. SAL acceptance lives in your CRM. SQL conversion lives in a different CRM view that sales has configured to match their workflow. Pipeline sourced sits in a finance tool nobody in marketing has permissions for. Producing a unified view of the handoff requires exporting all four, reconciling the definitions, and rebuilding the picture every week, which is both time-consuming and one tag misconfiguration away from showing something misleading.
The real barrier to a defensible MQL/SQL discipline is not knowledge. It is clarity.
Hurree is the unifying analytics intelligence layer that solves this.
By centralising your scattered sources into one environment, Hurree lets the handoff conversation stop being a reconciliation exercise and start being an operational one. We provide:
Don't wait for the next quarterly review to discover that marketing and sales have been quietly working from different definitions. Turn the MQL/SQL handoff from a political negotiation into the operational discipline it was always meant to be.
The MQL versus SQL conversation looks like a definitional problem and operates like a political one. The teams that handle it well are not the ones with the cleverest definitions. They are the ones who have accepted that definitions drift under incentive pressure, built a written compact to document the current agreement, and committed to reviewing it on a fixed cadence so drift gets caught early. For businesses whose sales motion has evolved into committee buying, the same discipline applies to the shift from MQL to MQA. In both cases, the handoff holds up not because the definitions are perfect but because the governance around them is honest.
An MQL (Marketing Qualified Lead) is a prospect marketing has qualified based on fit with the ideal customer profile and meaningful engagement with marketing content. An SQL (Sales Qualified Lead) is a prospect sales has independently vetted and confirmed is ready for direct outreach, typically by confirming budget, authority, need, and timeline. The crucial distinction is who makes the judgement: marketing qualifies an MQL based on engagement signals; sales qualifies an SQL based on confirmed buying readiness.
A SAL (Sales Accepted Lead) is the formal handoff checkpoint between an MQL and an SQL. When marketing passes an MQL to sales, the SAL is sales' formal acceptance (or rejection) of the lead as worth working. Not every MQL becomes a SAL, and not every SAL becomes an SQL. The reason the SAL matters is accountability, without it, marketing counts MQLs that sales never touched, and sales dismisses lead quality without the data to prove it. Introducing a SAL stage usually fixes handoff disputes within a quarter.
Industry benchmarks typically sit between 25% and 40% for well-aligned B2B teams. Enterprise sales motions often sit lower (15-25%) because of longer, more complex buying cycles. A conversion rate below 15% almost always signals a definitional or quality problem rather than a volume problem, meaning your MQLs are not being qualified against criteria that match what sales actually accepts. The right first response is to review the rejection reason breakdown, not to generate more MQLs.
B2B buying increasingly happens in committees averaging eight to ten stakeholders rather than through single decision-makers. In that environment, qualifying one individual based on their form-fill is a weak signal compared to tracking engagement across an entire account. Mature B2B teams are increasingly operating with a Marketing Qualified Account (MQA) alongside or instead of the traditional MQL, scoring engagement at the account level rather than the individual level. The traditional MQL still works for transactional or individual-decision purchases; for high-ACV committee buying, MQAs produce materially higher conversion rates.
Both teams own the definitions, which is exactly why a formal qualification compact matters. Marketing cannot unilaterally set the MQL criteria without sales input, because sales is the team working the leads. Sales cannot unilaterally set the SQL criteria without marketing input, because that affects what marketing is targeting with its programmes. The right model is co-ownership with revenue operations (or marketing operations, if that function exists) running the quarterly review process and holding the published change log. Finance should observe but not drive, since their incentives can skew the definitions in cost-focused rather than growth-focused directions.
Quarterly is the right default cadence for most B2B teams. Monthly is too frequent and creates definitional instability. Annually is too infrequent and lets drift accumulate for months before anyone catches it. The quarterly review should be scheduled in advance (not reactive to a dispute), should cover previous quarter's numbers against each metric in the compact, and should produce either a confirmation that no change is needed or a new version of the compact with a documented change log.
Letting the definitions drift without a formal review process. Both teams know what the definitions were supposed to be; both have slowly adjusted their operational interpretation to match their own incentives; nobody has written down that the drift has happened. Every quarterly review becomes a dispute because there is no versioned baseline to compare current performance against. The fix is a written, versioned qualification compact reviewed on a fixed quarterly cadence, unglamorous but disproportionately high-leverage.