MQL vs SQL: Define the Hand-Off Between Teams

Few arguments between marketing and sales are as old as the one about lead quality. Marketing says it delivered plenty of qualified leads; sales says most of them were not ready to talk. Usually both are right, because they are using different definitions. The MQL vs SQL distinction exists to settle that. A marketing qualified lead (MQL) has shown enough fit and interest to be worth sales attention; a sales qualified lead (SQL) has been checked by sales and confirmed as a real potential deal. This guide explains how to define each stage, set the criteria, run the hand-off and recycle leads that are not ready.

MQL vs SQL: the core difference

The difference is who decides and on what evidence:

• An MQL is decided by marketing criteria, usually a lead score that combines fit, such as industry and role, with interest, such as content downloads and page visits.
• An SQL is decided by sales after direct contact, based on whether there is a real need, a suitable buyer and a reasonable path to a purchase.

An MQL is a promising signal. An SQL is a confirmed opportunity in the making. Treating every MQL as sales-ready overloads reps; treating none of them that way wastes marketing's work.

Define an MQL

A useful MQL definition is specific enough that anyone can check it. It typically includes:

• A minimum fit level, such as target industry, company size and role
• A minimum interest level, such as a score threshold or a specific action
• Exclusions, such as competitors, students, existing customers handled by account managers, or regions you do not serve

Some actions, such as a demo or quote request from a lead with acceptable fit, may make a lead an MQL immediately regardless of score. Write these fast-track rules down too.

Define an SQL

Sales defines the SQL, often using a short qualification checklist. Common elements:

• A confirmed business problem the product addresses
• Contact with someone who can influence or make the decision
• A realistic timeframe
• No obvious blocker, such as a contract locked in for years with a competitor

Keep the checklist short. If reps must complete a long form before accepting a lead, they will avoid the step or fill it in carelessly. Three or four yes-or-no questions, recorded in CRM fields, are usually enough to show why a lead was or was not qualified, and they make later reporting far easier than free-text notes. Review the questions with the sales team after the first month and drop any that nobody answers consistently.

Design the hand-off

The hand-off from MQL to SQL is where most leads go cold. Agree on:

• Routing: who receives each MQL, based on territory, segment or a rotation. Our guide to CRM lead routing covers assignment rules in detail.
• Response time: how quickly sales will make first contact after a lead becomes an MQL
• Outcomes: the decisions sales can record, such as accepted as SQL, rejected with a reason, or returned to nurture
• Context: what information the rep sees, such as recent activity, score breakdown and source

Response time matters because interest fades. Our guide to speed to lead explains how to measure and improve it.

Recycle leads that are not ready

Many MQLs are interested but not yet ready to buy. Without a recycle path, they either clog sales queues or disappear. Define:

• Rejection reasons, such as no budget yet, wrong contact or timing too early
• What happens next for each reason, such as return to nurture, find the right contact, or follow up in a set number of months
• How a recycled lead can become an MQL again, for example only after new activity

Rejection reasons also feed back into scoring. If many MQLs are rejected for the wrong role, the role criteria need work.

Worked example: MQL vs SQL definitions in one table

The table below shows a hypothetical set of definitions for a B2B software company. Thresholds and timings are illustrative and should be agreed between your own teams.

StageWho decidesCriteriaTarget timingNext stepLeadSystemAny new contact with valid emailImmediateScore and nurtureMQLMarketing rulesFit score 40+ and interest score 30+, or demo request with fit 25+Recalculated on activityRoute to salesSales acceptedSales repRep reviews and agrees to work the leadWithin 1 business day of MQLFirst contactSQLSales repConfirmed need, decision influencer reached, timeframe under 6 monthsAfter discovery callCreate opportunityRecycledSales repRejected with reasonAt rejectionNurture; re-qualify on new activity

Some teams add the "sales accepted" step, shown here, to measure whether reps are actually picking up MQLs before qualifying them.

Common MQL vs SQL mistakes

• Setting the MQL threshold so low that reps stop trusting the label
• Counting form fills as MQLs without checking fit
• Letting sales reject leads without a reason, so nothing can be learned
• Measuring marketing on MQL volume alone, which rewards quantity over quality
• Having no agreed response time, so good MQLs wait for days
• Changing definitions without telling the other team or updating reports

Each of these mistakes creates the same symptom: two teams reporting different numbers about the same leads. Fixing them is mostly about agreement and discipline, not new software.

Measure the funnel together

Shared definitions need shared measures. Track, by source and segment:

• MQL volume and the share that sales accepts
• MQL to SQL conversion rate
• SQL to opportunity and win rates
• Time from MQL to first contact
• Rejection reasons, ranked by frequency

Review these together each month. When the MQL to SQL rate drops, look at both sides: has lead quality changed, or has follow-up slowed?

Make the definitions stick

Write the definitions in one short document, store it where both teams can find it, and build them into the CRM:

• Lead status values that match the agreed stages
• Required rejection reasons
• Automatic timestamps for each stage change
• Reports that show stage conversion and timing

Revisit the definitions when products, markets or team capacity change. A definition agreed two years ago for a smaller sales team may now send too many or too few leads.

Frequently Asked Questions

What is the difference between an MQL and an SQL?

An MQL meets marketing's criteria for fit and interest and is ready for sales attention. An SQL has been confirmed by sales, after contact, as a real potential deal.

Who should define MQL and SQL criteria?

Both teams, together. Marketing usually owns the MQL rules and sales owns the SQL checklist, but each should agree to the other's definition and the hand-off terms.

What should happen to rejected MQLs?

They should be recorded with a reason and recycled, for example into nurture or a later follow-up, rather than left in a queue or deleted.

How do you improve MQL to SQL conversion?

Review rejection reasons, tighten fit criteria that let poor leads through, speed up first contact and make sure reps see the activity that made each lead an MQL.

Align marketing and sales on lead quality

We help teams agree MQL and SQL definitions, build the stages, routing and reports into the CRM and score leads to match. See our AI automation solutions, or talk to us about your lead hand-off.

About the Author

Manav Sharma is the founder of Insyrge and a CRM solutions architect. He works across Zoho, Salesforce, HubSpot, Odoo and more, designing the CRM setups, integrations and automations that keep sales and operations teams working from the same data.