MQL vs SQL: Definitions, Handoff Criteria, SLAs, Disputes and How to Report Conversion Between Them

A marketing qualified lead (MQL) is a lead that marketing has qualified as ready for the sales team; a sales qualified lead (SQL) is one that sales has qualified as a potential customer. HubSpot uses almost those words in its default lifecycle stages. The first judgement rests on marketing signals such as fit and engagement; the second on a sales conversation or review.

The practical difference is accountability. An MQL is marketing's claim that a lead deserves sales attention. An SQL is sales accepting that claim and taking responsibility for it. If both teams treat the labels as the same thing, the stage adds no information and the funnel report loses meaning.

Some businesses use other labels or add stages such as sales accepted lead. The names are less important than the sequence of decisions behind them, and every added stage needs an owner and a rule. Check how your CRM names its stages by default, because HubSpot, for instance, treats SQL as a lifecycle stage and keeps the finer sub-stages in a separate Lead Status property.

Define each stage as an entry rule, an exit rule and an owner. An MQL rule combines fit (the right kind of company or person, location, size) with a meaningful action such as requesting a quote, booking a demo or asking a specific question. Downloading a guide may or may not qualify, depending on how your buyers behave. An SQL rule adds what only a person can check: a real need, a decision route, a plausible timeline and a conversation that confirms them.

Frameworks like BANT can supply the SQL checklist, and a lead score can inform the MQL threshold; HubSpot's scoring tool can build scores from properties and from engagement. Whatever you use, write it down in plain words and test it on ten real records. If two people disagree about where a record belongs, the criterion is not finished.

Avoid criteria that cannot be recorded. If the SQL rule says the rep must feel the lead is serious, no report can check it. Turn judgement into a field with a few options, such as need confirmed, decision route known and timeline stated, so the answer is stored and can be examined later when conversion rates move.

The handoff is the moment an MQL reaches a named person, and it needs three things: a rule for who receives it, a response time, and a required outcome. The outcome is either accept (the lead becomes an SQL) or reject with a reason from a fixed list. A lead that stays in limbo, neither accepted nor rejected, is the most expensive state in the funnel.

Set the SLA at a level the team can keep. A promise of a response within minutes that nobody keeps is worse than an honest few hours, because it teaches everyone to ignore the clock. Build the clock into the CRM: HubSpot workflows can assign an owner, notify them and create a task on a trigger, and a second workflow can alert a manager if nothing happens. Both are Professional and Enterprise features.

Measure the SLA from the moment the lead becomes an MQL to the first real attempt by a person, not to an automated email. Automated replies are useful for the prospect but they say nothing about whether sales acted. Report it weekly by owner and by source so that patterns, such as slow handling of leads that arrive on weekends, show up quickly.

Most disputes are about incentives wearing a definitional costume. Marketing is rewarded for volume, so the MQL threshold drifts down; sales is rewarded for closed revenue, so the SQL standard drifts up. Each side is acting rationally on what it is measured on. The fix is a shared measure that both can lose or win on, such as the share of MQLs that become opportunities and the revenue they produce.

Settle individual disagreements with evidence. Take a sample of rejected MQLs and look at what happened later. If some of them became customers, the rejection was too hasty or the follow-up was weak. If none did, the MQL criteria need tightening. Review the sample together, monthly, on the same screen, and agree the changes before leaving the room.

A written agreement helps, but only if it names consequences. If sales rejects more than an agreed share of MQLs with the same reason, marketing reviews the source. If marketing's leads are accepted but not worked, sales reviews capacity. Without a consequence on each side, the agreement is a document, and it will be forgotten the first busy month.

Report by cohort: take the leads that became MQLs in a given month and track what share reached SQL, and later opportunity and customer, over the following weeks. Dividing this month's SQLs by this month's MQLs mixes leads from different months and produces a number that swings whenever volume changes. Cohorts are slower to read but they do not mislead.

Also report time in stage, since a stable conversion rate can hide a lengthening delay. HubSpot records lifecycle stage history and creates calculated properties for each stage, and its custom reports can chart records by stage, which gives you the raw material. Check how your tool handles a lead that skips a stage or moves backward before trusting the totals; HubSpot's default lifecycle property, for example, only moves forward through its own tools.

Labels help when they reflect a decision that actually happens. In a business where every inbound enquiry is a request for a quote and a salesperson calls within the hour, there is no marketing-only judgement to record, and an MQL stage is just a delay. A single "new enquiry" stage and a clear accept-or-decline step may be more honest.

The reverse also happens. Larger teams, several products or an account-based motion need more stages than two. The test is whether a stage has a different owner, a different action and a different report from its neighbours. If it does not, remove it.

Revisit the question when the business changes, for example after adding a product line, a new market or a self-serve option. A definition that worked for one sales motion can quietly fail in another, and the first sign is usually that reps start keeping their own lists because they no longer trust the stage.