MQL to SQL: How to Define the Handoff Between Marketing and Sales

An MQL is a marketing-owned lead that meets agreed fit and engagement criteria. A sales-accepted lead is one sales has reviewed and agreed to work. An SQL is a lead sales has qualified against a real problem and buying context. Those definitions are a practical operating model, not universal standards. Write your own entry and exit rules so a dashboard stage actually predicts work and progress.

The argument between marketing and sales usually starts when one team counts “leads” as form submissions while the other expects people ready for a sales call. A shared definition, an acceptance window and a rejection taxonomy resolve more than a new scoring formula.

Define stages around evidence and ownership

Inquiry: someone raised a hand or became identifiable. They may be a buyer, student, vendor or existing customer. MQL: the company and role fit a target segment, and behavior suggests a reason to investigate. Sales-accepted lead (SAL): a named sales owner has reviewed the record and committed to a next action. SQL: sales has confirmed a relevant problem or initiative, appropriate stakeholder and a plausible next step. Opportunity: there is a sales-accepted deal with an agreed commercial process in the CRM.

Your business may use different labels. The important questions are who owns each stage, what evidence is required and what happens next. Salesforce's qualification training describes MQLs as fit prospects who are not yet ready to buy; treat that as one vendor's framing, then define the transition for your team.

Set a clear acceptance rule

A lead should not become SAL merely because a notification reached a sales inbox. Give it an owner, a deadline to review, and three available decisions: accept, return for nurture with a reason, or reject as out of scope. Rejection reasons might be wrong company type, wrong geography, invalid contact, existing opportunity, no relevant problem, or duplicate. Those reasons improve future targeting.

For an inbound demo request, review may need to happen during the recipient's business hours as a priority. For a lower-intent content inquiry, an immediate sales call may be inappropriate. Set different service levels by intent and market, then measure actual response time rather than promising one universal rule.

Do not use budget, authority, need and timeline as a rigid form gate in every case. A strong early-stage buyer may not know the budget; a vendor comparison may have a timeline but no clear problem. Capture what you know, label what you do not, and use a conversation to fill the gap.

Make the handoff useful to a human seller

Pass the company, role, market, source, exact action taken, pages or assets relevant to the request, known account history, reason for fit, potential problem and any opt-out status. Avoid dumping a long behavioral log without context. A salesperson should be able to answer: Why is this lead in my queue, what do they know about us, and what would be a respectful next action?

If marketing claims that a whitepaper download is buying intent, sales should be allowed to challenge that assumption with actual outcomes. If sales rejects every MQL with “not ready,” marketing needs a more informative reason to improve the system. Hold a regular review of accepted, rejected and later-converted cohorts.

Measure stage quality, not just stage volume

Report inquiries, MQLs, SALs, SQLs and opportunities as distinct counts with denominators. Track MQL-to-SAL acceptance, SAL-to-SQL qualification, SQL-to-opportunity conversion, rejection reasons and time spent in each stage. Cohort by source so a paid lead magnet is not compared blindly with a referral or a direct demo request.

An illustrative month generates 120 MQLs, 72 accepted by sales, 30 qualified as SQLs, and 12 opportunities. MQL-to-SAL acceptance is 60%; SAL-to-SQL is about 42%; SQL-to-opportunity is 40%. These numbers are an example of the arithmetic, not benchmarks. The rejection reasons and the sales-cycle timing determine what the team should change.

Our qualified-meeting definition addresses a later appointment outcome. A lead can be sales-qualified before a meeting is held, but a booked meeting should not be counted as a held qualified meeting.

Frequently asked questions

Should every MQL be contacted by sales?

Only if the agreed entry criteria and service model call for it. Some strong-fit, low-intent leads are better placed in relevant nurture until there is a reason to start a conversation.

Who decides what counts as an SQL?

Sales and marketing should agree on the criteria, with sales confirming the evidence in the actual conversation. RevOps can maintain the definitions and reporting rules.

Can a lead skip stages?

Yes. A direct request from a well-qualified buyer may enter an opportunity quickly. Preserve the source and timestamp rather than forcing an artificial journey through every label.

The next step

Take five recently rejected leads and five accepted ones. If the difference cannot be explained by your written criteria, rewrite the handoff. Leadsify focuses on leads that can become real sales conversations, with shared definitions of quality. Talk to the team.