AIViral logoAIViral
← Back to blog

MQL vs SQL: Stop Wasting Rep Hours With SAL Handoff Rules

Sales rep reviewing a lead handoff

An MQL is a lead that fits your profile and has shown interest but still needs nurturing. An SQL adds clear buying intent and is ready for a sales conversation. Marketing manages MQLs, and sales owns SQLs, so every handoff shifts accountability. Before anything else, agree on written acceptance criteria and start measuring your MQL to SQL conversion rate.

TL;DR:

  • Require at least one explicit buying signal, such as a demo request, pricing inquiry, or procurement timeline, before a high score can trigger sales review.
  • A Sales Accepted Lead stage should require sales to accept, reject, or recycle each MQL with a logged reason and a defined response window.
  • Predictive scoring averaged about 15% lead to customer conversion versus 5% for traditional scoring, but it needs clean CRM data and enough closed deals.
  • Track acceptance time, speed to first contact, and downstream opportunity and win rates, then compare results by lead source rather than relying on universal benchmarks.
Aiviral
Prioritize Leads Ready to Talk
Aiviral uses AI-driven outreach and performance marketing to deliver pre-qualified B2B leads who actively request meetings or pricing.
Explore Aiviral

Table of Contents

What is an MQL, and which signals qualify a lead?

A marketing qualified lead is someone who matches your ideal customer profile and has engaged enough to deserve more attention, but has not said they want to buy. The definition of an MQL is deliberately loose at the edges, which is why teams need written rules. As HubSpot’s guide lays out, MQL actions tend to be low-commitment behaviors such as downloads and webinar attendance.

Two kinds of signals matter:

  • Behavioral signals: content downloads, webinar attendance, trial signups, and repeat visits to key pages.
  • Fit signals: job title, company size, industry, and geography where it affects your ability to serve the account.

Here is what that looks like in B2B. A product manager at a mid-size software company downloads your spec sheet. An operations head registers for your webinar and watches it. Both fit your profile and both showed curiosity. Neither asked for a price or a call, so both belong in nurturing, not on a rep’s call list.

Watch for the volume trap. When marketing is rewarded for the raw count of leads, the MQL bar drifts downward, and sales soon learns to ignore anything marketing sends. Fit has to carry real weight in the definition: a student who downloads five ebooks is engaged but is not a lead worth a salary hour.

A useful test is to ask whether a rep would be glad to receive this person. If the honest answer is “only if nothing else is on the list,” the MQL rule is too loose.

What is an SQL, and when is a lead sales-ready?

A sales qualified lead has crossed from interest into intent. The person fits your profile, has taken an action that signals a real buying conversation, and sales has either vetted or can quickly vet the opportunity. The distinction between the two stages, which Adobe’s guide describes as essential for managing the funnel and limiting lost opportunities at handoff, comes down to this shift from curiosity to intent.

High-intent actions that typically define an SQL:

  • A demo request or a pricing request.
  • A stated procurement timeline or a named budget.
  • A mention that they are evaluating vendors.
  • A reply to outreach that asks for a meeting or a call.

Sales then adds its own vetting on top of those actions:

  • Contact quality: you are talking to a decision-maker or someone who can credibly bring one in.
  • Authority: the person can sign off on, or strongly influence, the purchase.
  • Timeline alignment: their window to buy overlaps with how long your sales cycle runs.

A typical SQL looks like this: a VP of operations at a manufacturer fills out your demo form, mentions that their current vendor contract is ending soon, and gives a direct phone number. Reps want that context on hand before they dial: the pages the person viewed, the content they downloaded, the form fields they filled in, and any notes from earlier touches. An SQL record with an empty history forces the rep to start from zero, which wastes the very speed the handoff was meant to create.

How do MQLs and SQLs differ in practice?

The cleanest way to separate the two is by ownership and by what happens next. Salesforce’s explainer stresses that knowing when to pass a lead from marketing to sales improves sales cycle speed and win rate, so the rules for the transition deserve as much care as the definitions.

  • Ownership: marketing owns the MQL and nurtures it with content, email sequences, and retargeting. Sales owns the SQL and works it with calls, tailored outreach, and meetings.
  • Expected next step: for an MQL, the next step is more engagement and a clearer signal. For an SQL, it is a conversation, ideally promptly.
  • Timeline after handoff: agree on a response window in your service level agreement, and treat a missed window as a process failure, not a rep failure.
  • What sales expects on receipt: complete contact details, the triggering action, firmographic data, and engagement history.

Common traps are worth writing into your handoff document. Unscored leads reach sales with no explanation of why they qualified. Records arrive without a phone number or a valid email. Marketing hands off too early, chasing a volume target, and reps respond by tagging everything “not interested.”

Concrete indicators that an MQL is moving toward SQL: a pricing page visit followed by a form submission, a reply to an email that asks a buying question, a second stakeholder from the same account showing up in your analytics, or a shortened gap between visits. None of these alone makes a lead an SQL, but several together usually should trigger a review.

How do lead scoring and qualification criteria separate MQLs from SQLs?

Scoring turns a vague sense of “warm” into a number both teams can inspect. A workable model combines four kinds of input: firmographic fit, engagement actions, recency, and intent signals. Fit tells you whether the account could buy. Engagement and intent tell you whether this person is moving. Recency keeps stale activity from inflating a score.

Here is a sample point-based rule set, offered as an illustration to adapt, not a standard:

  1. Add points for a demo request.
  2. Add points for a whitepaper or guide download.
  3. Add points for decision-maker seniority, such as director level or above.
  4. Add points for a visit to the pricing page.
  5. Subtract points for inactivity after a defined period with no engagement.

Then set separate thresholds. A lower score marks an MQL and starts nurturing. A higher score, usually requiring at least one explicit intent action, marks a lead for sales review. Do not let a lead cross into SQL territory on volume of low-value actions alone; a stack of ebook downloads should never equal a demo request.

Predictive lead scoring replaces hand-set points with a model trained on your historical wins and losses, weighing many more variables than a person could. A 2023 literature review in PMC reported average lead-to-customer conversion of about 5% for traditional scoring versus about 15% for predictive scoring across the studies it examined. Consider it once you have enough closed deals to train on and a clean CRM.

Whichever approach you choose, validate it against reality. Take last year’s leads, apply the model, and check whether high scorers actually converted at higher rates. Retune the weights regularly.

Pro Tip: Run your scoring model against closed-lost deals as well as wins. If many lost deals scored high, your model rewards engagement that does not predict buying, and those weights need to drop.

How do you design the MQL to SQL handoff with a SAL stage?

A Sales Accepted Lead is the formal checkpoint between marketing’s MQL and sales’ SQL. Sales either accepts the lead or rejects it with a logged reason. That small requirement creates accountability on both sides and shows exactly where conversion stalls. We go deeper on Sales Accepted Lead intake metrics if you want to track the stage closely.

Build the handoff in this order:

  1. Write the acceptance checklist. Agree on what sales needs to see before accepting a lead.
  2. Trigger an automatic notification. When a lead crosses the MQL threshold, the assigned rep is alerted in the CRM and by message.
  3. Set a response window. Set a response window for a decision, with a shorter one for hot intent actions like demo requests.
  4. Log the decision. Accept, reject, or recycle, always with a reason code.
  5. Return rejected leads to nurturing with the reason attached, so marketing can act on it.
  6. Review reasons regularly in a joint meeting.

A practical acceptance checklist for sales:

  • The company matches the ideal customer profile.
  • At least one real intent signal is present.
  • The contact is reachable by phone or email.
  • The stated or inferred timeline fits your sales cycle.

Standardize your rejection reasons: wrong company size, wrong role, no budget, bad contact data, duplicate, competitor. Free-text notes are hard to aggregate, so give reps a dropdown with an “other” field. When “wrong role” dominates the log, tighten your targeting. When “bad contact data” dominates, fix your forms and enrichment. The log is the feedback loop that makes the next quarter’s MQLs better than this quarter’s.

How do you calculate MQL to SQL conversion, and what else should you measure?

The formula is simple: divide SQLs by MQLs and multiply by 100. For example, divide the number of SQLs by the number of MQLs in the same period, then multiply by 100 to calculate the MQL to SQL conversion rate.

A 2023 PMC review of lead scoring models reported that predictive scoring averaged roughly 15% lead-to-customer conversion, against roughly 5% for traditional scoring in the studies reviewed. Treat this as evidence that scoring method affects results, not as a target for your own funnel.

Track these alongside it:

  • Lead to opportunity rate: the share of SQLs that become open deals.
  • Opportunity to win rate: the share of deals that close.
  • Time to acceptance: the gap between an MQL being routed and sales deciding.
  • Speed to lead: how quickly a rep first contacts a high-intent lead. Our piece on speed to lead for B2B covers why the first minutes matter.

Benchmarks vary widely by channel, ideal customer profile, and deal size, which is why a single “good” number is misleading. An inbound demo request converts far better than a gated ebook download, and an enterprise buyer moves more slowly than a small business owner. Compare yourself against your own history by source first, and use external figures only as rough context. If you need to credit leads correctly across channels, our guide to lead attribution models helps.

Use the metrics to set service level agreements. If time to acceptance is longer than your target, that gap becomes a concrete goal for both teams.

Lead acceptance timeline exceeding its target

Which best practices improve MQL to SQL conversion?

Most conversion gains come from alignment, not from new tools. Start with shared definitions, then shared numbers, then shared meetings.

  • Agree on a written SLA. Marketing commits to a lead volume and quality floor, sales commits to a response window and a logged decision for every lead.
  • Share KPIs. When both teams are measured on pipeline created or revenue influenced, not just lead counts or activity, the incentive to hand off junk disappears.
  • Run speed-to-lead plays. Route high-intent leads instantly, and give reps short follow-up templates that reference the specific action the lead took.
  • Build one dashboard. Put MQL volume, acceptance rate, rejection reasons, and time to acceptance in a single view that both teams open weekly.
  • Hold calibration meetings. Once a month, review a sample of accepted and rejected leads together and argue about the borderline ones.
  • Use disqualification data. If reps keep rejecting leads from one campaign, change the targeting or the message, not just the threshold.

Sales enablement matters here too. A lead that gets a sharp, relevant follow-up converts better than one that gets a generic pitch, and interactive formats can help; Yonderly’s piece on interactive sales presentations that improve qualified lead rates is one example of how teams sharpen that conversation.

Pro Tip: Pick the three rejection reasons that appear most often and assign one owner to each. A reason without an owner is just a complaint, and it will repeat next month.

Finally, protect your definitions from drift. Revisit them every quarter, because your product, pricing, and audience change, and a rule that was right a year ago may now be admitting the wrong people.

What does the research say about predictive scoring and choosing tools?

The strongest evidence we have points one way: smarter scoring tends to help. The PMC literature review found predictive models associated with higher conversion from lead to customer than traditional point systems, with reported averages of about 5% versus about 15% in the studies it covered. Those are averages across reviewed work, so your own gain will depend on data quality, deal volume, and how well your team acts on the scores.

Gartner recommends structured vendor and tool selection for lead scoring and qualification, drawing on peer and industry best practices to avoid costly poor decisions. Source: Gartner’s Ignition Guide to Getting Started With Lead Scoring

For smaller and mid-market teams, the implication is practical. Predictive scoring needs enough historical closed deals and reasonably clean CRM data to learn from. If you are early on either count, a well-tuned point-based model with a SAL stage will give you most of the benefit at a fraction of the effort. If you have the data, compare vendors against written criteria for your use case, test on your own history before committing, and plan for the ongoing work of monitoring the model. A tool that nobody retunes decays quietly.

Why do we favor verified interest and disciplined handoffs?

Volume is easy to buy and hard to use. At AIViral, we built our work around verified interest: we only deliver a lead after a real person has replied showing genuine intent, and a human reviews each response before you pay. That discipline exists for the same reason a SAL stage does. Every low-quality lead that reaches a rep costs more than the lead itself, because it teaches sales to distrust the whole pipeline. My advice is to stop celebrating MQL counts and start measuring acceptance decisions, because the rejection log tells you more about your funnel than any top-of-funnel number does. Write the criteria down, log every decision, and retune your scoring from what the log tells you.

— Max

FAQ

What comes first, MQL or SQL?

The MQL comes first. A lead is marketing qualified once it fits your profile and shows enough engagement, and it becomes sales qualified only after showing buying intent and passing sales vetting.

What is a good MQL to SQL ratio?

There is no universal figure, because it depends on channel, audience, and deal size. Measure your own rate by source, compare it quarter to quarter, and treat external benchmarks as rough context only.

What are examples of MQL?

A typical MQL is a product manager who downloads a spec sheet, an operations head who registers for a webinar, or a returning visitor who signs up for a trial. Each fits your profile and shows interest without yet asking to buy.

How do you calculate MQL to SQL?

Divide the number of SQLs by the number of MQLs in the same period, then multiply by 100. The result is your MQL to SQL conversion rate.

Sources

← Back to blog