MQL vs SQL: Definitions, Criteria and Handoff Rules

Avinash Gujje

CEO of ZUUZ. He scaled Cloud Box Technologies from 0 to $25M ARR in IT services and distribution before building ZUUZ. Connect on LinkedIn

MQL vs SQL comes down to who qualified the lead and on what evidence. A marketing qualified lead (MQL) is a contact marketing judges ready for sales, based on fit and engagement. A sales qualified lead (SQL) is a contact a salesperson has vetted, usually in conversation, as a potential customer with a real need.

Picture a regional MSP's Monday pipeline review. Marketing reports MQLs from a security webinar; sales says none were real. The month's two real deals came from a reply to an old proposal and a distributor rep's forward, and neither ever had an MQL date (an illustration, not a client story).

Both teams are right; the stage model is wrong. Scoring models are in the lead scoring matrix guide.

What Is the Difference Between an MQL and an SQL?

The difference is the qualifier and the evidence. Marketing qualifies an MQL from signals observed at a distance, such as fit, downloads and repeat visits. Sales qualifies an SQL from direct contact that confirms a need, a buyer and rough timing.

HubSpot's documentation on contact and company lifecycle stages draws the same line. It defines an MQL as "a contact or company that your marketing team has qualified as ready for the sales team," and an SQL as "a contact or company that your sales team has qualified as a potential customer."

Typical signals on each side

MQL signals are observed: ICP fit plus engagement such as a webinar or a second pricing page visit. SQL signals are confirmed: the buyer describes a project, names a date, says who else is involved and agrees to a meeting. BANT (budget, authority, need, timeline) helps structure that, but demanding all four excludes real deals whose budget is still forming.

A demo request sits in between: route it to sales at once, and let sales still reject it on fit.

Salesforce's MQL vs SQL explainer puts MQLs near the top of the funnel and SQLs near the bottom, and its Trailhead module on lead qualification builds the marketing side from a score and a grade. Weighting is covered in ICP scoring criteria, tools in lead scoring software.

Where the sales accepted lead fits

Many teams add a sales accepted lead (SAL): sales has agreed to work the MQL but not yet qualified it. HubSpot has no default SAL stage; it keeps SQL sub-stages in Lead Status (New, Open, Connected and others).

MQL vs SQL Compared Stage by Stage

This table compares each stage by what RevOps has to configure.

The standard funnel leaves out the last row, which is where IT channel deals often begin.

What Handoff Criteria Move an MQL to an SQL?

Good MQL vs SQL handoff criteria can be checked by someone who was not in the conversation: a named person at a fitting account, a need in the buyer's words, a dated first signal, an owner with a running clock, and an exit if sales says no. The test below puts that in five lines.

Failing line 1 or 2 means not ready for sales. Failing line 3 means the lead can be worked but not measured.

Run it on real history: score the last 20 MQLs and 20 SQLs from the CRM record alone. Many line 2 failures point to a loose MQL rule; SQLs failing line 3 often started in someone's inbox.

How to Write an MQL-to-SQL SLA

The SLA is the written half of MQL vs SQL: an agreement on how fast sales accepts or rejects each MQL, what counts as a valid rejection, and what marketing delivers in return, reviewed monthly against the CRM.

1. Acceptance window. How long sales has to accept or reject a new MQL. Start with a window the team can meet, then tighten it.
2. First-touch standard. Attempts and channels before a lead is marked unresponsive. Routing and speed to lead are covered in inbound lead management.
3. Reject reasons. A short picklist, such as wrong size, existing customer or no need stated. Free text cannot be reported on.
4. Recycle rule. Rejected or stalled leads return to nurture with a re-check date.
5. Marketing's commitment. Measured by acceptance rate, not MQL count.

The Fields That Make the Handoff Measurable

An MQL vs SQL handoff is measurable when every transition leaves a timestamp, an owner and a reason. HubSpot covers most of it by default.

HubSpot's default contact properties define Lead response time as the time the owner took to do the first qualifying engagement. Per the lifecycle documentation, automated tools only move the stage forward, and calculated "Date entered" values survive a backward move.

Four reports then carry the handoff: conversion by channel, days from MQL to SQL, acceptance time and rejections by reason. The return calculation is in measuring ROI from lead qualification automation.

Where MQL vs SQL Breaks in IT Channel Selling

Almost every MQL vs SQL guide assumes the first signal is a form fill or a download. In IT channel and MSP selling it is often an email that already states a need:

• A reply to an old thread. The budget came through, months after the proposal.
• A vendor or distributor forward. Their client needs a local partner for a rollout.
• A partner introduction on CC. A peer MSP introduces a customer outside its region.
• A question to the sales address. Does the team support a specific migration?

Each passes lines 1 and 2 at first read, yet under a form-based model none becomes an MQL. The conversion report undercounts the inbox and partner-sourced pipeline goes unproven.

The fix: add reply, forward and partner introduction to the first signal channel field, and let a lead that passes the test enter at SQL. Credit for introductions is in partner attribution, qualifying email in email lead qualification automation, and capture outside forms in lead capture software for IT services.

A Worked Example From an IT Services Inbox

An illustration, not a client story: a 30-person MSP runs HubSpot with a form-based MQL rule.

1. The signal arrives. A distributor's account manager forwards a thread: an accounting firm wants its firewalls replaced before support ends in March, with its IT manager on CC.
2. Old rules do nothing. No form fired, so no MQL exists.
3. Run the test. Named person, stated need and a dated first signal (Tuesday, partner introduction): yes. Owner: not yet.
4. Skip the MQL on purpose. Create the contact and company, set the stage to SQL manually and assign an owner, which starts the SLA clock.
5. Work it. The rep replies the same day and books a discovery call; once scope is confirmed, a deal makes it an Opportunity.
6. Check the report. The SQL shows no MQL date, which is accurate, and sits under partner introduction, so the distributor gets credit.

By contrast, a webinar attendee who downloaded a patching checklist becomes an MQL, then fails line 2 and returns to nurture. An existing client asking about forty more seats is account expansion, not a new lead.

From an operator's seat. In IT services sales, the handoff rarely breaks at the MQL definition; it breaks in the hours between a forward landing in a shared inbox and someone owning it, because no stage rule applies to an email nobody has logged. Give every inbox-originated lead an owner and a date on arrival, and the report finally shows where SQLs came from.

The part teams do not plan for is the reject reason. An MQL that sales quietly ignored leaves no data, so a dispute about it has nothing to check. Once every rejection carries a reason, the review becomes a count, not an opinion.

MQL vs SQL Handoff: How ZUUZ Writes the Evidence to the CRM

ZUUZ is revenue intelligence for the IT channel: MSPs and the vendors, distributors and resellers they work with. It is an AI layer on the CRM the team already runs, not a CRM. It connects to the sales inbox, calendar and meeting tools, finds deal signals, and updates the CRM and ConnectWise PSA automatically, with full change history and one-click rollback.

For the handoff, the empty inbox row fills: contact, account and thread land in the CRM, scored and enriched from what the buyer wrote. The team's rules still decide MQL and SQL.

RA Technologies, a US IT services company, ran ZUUZ on the HubSpot instance it had used for two years, with the same team.

At Cloud Box Technologies, a UAE cloud and IT services business, inbound email turns into leads and renewals, leadership sees live pipeline, and 10 to 12 renewals are tracked in minutes. ZUUZ does not send nurture email or set the MQL threshold.

When a Separate MQL Stage Is Not Worth Having

Not every team needs the full MQL vs SQL split. A small MSP where the owner reads every inquiry can run Lead then SQL, with the handoff test at first read. A team with high form volume should keep its MQL rule and add the inbox entry point beside it.

ZUUZ does not fit a team that cannot connect a mailbox, though the test works by hand. Moving an account between reps after the SQL is a separate process, covered in the sales handoff guide.