MQL vs SQL: Definitions, Differences, and the Handoff

Ask marketing why pipeline is thin and you may hear that sales ignores their leads. Ask sales and you may hear the leads are junk. Both teams are usually describing the same missing artifact: a shared definition of a qualified lead.

MQL and SQL are the two definitions that do this work in most B2B organizations. When they are precise, the handoff is smooth and the pipeline math is legible. When they are vague, every revenue meeting turns into an argument about lead quality. The definitions are cheap to write and expensive to skip.

This guide defines both terms, lays out the criteria that separate them, covers lead scoring basics, and shows how to design the handoff, the SLA, and the recycle loop that make the model actually work.

MQL and SQL, defined

Marketing qualified lead (MQL)

An MQL is a lead that marketing judges ready for direct sales attention, based on fit and behavior. They resemble your ideal customer profile and have engaged deeply enough to signal genuine interest: picture an operations manager at a mid-market company who attended your webinar and then visited pricing twice.

The key word is judges. MQL status is a prediction that this person is worth a seller's scarce time, not a promise that they will buy. Treat the bar as a budget decision: it should rise and fall with how much qualified attention your sales team actually has to spend.

Sales qualified lead (SQL)

An SQL is a lead that sales has accepted and confirmed as a genuine opportunity through an actual conversation. Someone verified a need you can solve, a person with authority or influence, and a timeline worth pursuing.

The difference is evidence. An MQL is inferred from behavior, while an SQL is confirmed by a human. Many teams also name the step between them: the sales accepted lead, or SAL, which marks sales agreeing a lead is worth working before qualification has happened.

A hypothetical makes the ladder concrete. Say you sell payroll software: a controller who downloads your year-end checklist is a lead, becomes an MQL after she requests a demo, and becomes an SQL once the call confirms her team is replacing its provider this year.

The criteria that separate them

The exact triggers vary by company, but the dimensions are stable. This is the table to rebuild with your own definitions and have both teams sign.

The most important row is the first. The MQL call belongs to marketing and the SQL call belongs to sales, which is exactly why the definitions must be written together: each team is making a promise the other depends on.

Revisit the table whenever either side stops trusting it. Definitions drift as products, pricing, and audiences change, and a definition nobody believes gets silently ignored long before anyone proposes updating it.

Lead scoring basics

Lead scoring is how MQL judgment scales past the point where a human can review every signup. Score on two axes.

• Fit measures how closely the person and company match your best customers: industry, company size, role, geography.
• Engagement measures what they do: pricing page visits, email engagement, webinar attendance, content depth, and how recently all of it happened.

A few rules keep the model honest:

1. Weight intent unevenly. One pricing page visit outweighs ten blog visits.
2. Decay scores over time, so last quarter's activity cannot create this quarter's false positive.
3. Subtract for negative signals: students, competitors, and careers page visitors.
4. Set the MQL threshold jointly with sales, then revisit it quarterly against which leads actually converted.

Start embarrassingly simple. A five-rule model both teams understand and trust beats a sophisticated model nobody believes.

You also do not need special tooling to begin. A spreadsheet over your form fills and email engagement is enough to test whether the first thresholds predict anything, and automating the scoring only makes sense once the rules themselves are proven.

Designing the handoff and the SLA

A handoff without a service level agreement is a suggestion. The SLA makes the exchange explicit in both directions.

• Marketing commits to the MQL definition and a rough monthly volume, so sales can plan capacity.
• Sales commits to a first-touch window and to dispositioning every lead: accepted, working, recycled, or disqualified, always with a reason.
• Both commit to a recurring review where dispositions feed back into the scoring rules.

Two operational details decide whether the SLA holds. Speed first: interest decays in hours, so measure time to first touch as a core metric. Routing second: the fewer hops between the MQL trigger and a named owner, the fewer leads evaporate in the gap.

Concretely, a starter SLA can be three lines. Say marketing commits to fifty MQLs a month matching the signed definition, sales commits to a first touch within one business day, and both commit to a thirty-minute monthly review of every recycled and disqualified lead.

The recycle loop for not-ready leads

Most MQLs will not become SQLs this quarter, and that is not a failure of the model. Not ready is a timing state, not a verdict.

Build the loop deliberately. A recycled lead returns to marketing with a reason code, enters a lead nurturing track that matches the reason, and can re-qualify later on fresh signals. Wrong timing earns a patient drip. Wrong person triggers a search for the right contact at the same account. No budget gets revisited around planning season.

Teams that run this loop treat their existing database as a pipeline source, which is almost always cheaper than generating the same volume of net-new leads.

Measure the loop like a channel. Track how many recycled leads re-qualify and how many convert downstream, because that number justifies nurture investment better than any engagement statistic.

When the MQL model breaks down

The MQL model assumes a volume business with a relay from marketing to sales. Several situations break that assumption.

• Product-led motions. When people use the product before ever talking to sales, product activity qualifies leads far better than content engagement does.
• Account-based motions. In account-based marketing, target accounts are chosen up front, so person-level MQL counts distract from account-level engagement.
• Very small sales teams. With two reps, shared judgment and a fast channel beat any scoring model.
• Committee purchases. Person-level scoring misses buying groups; three mid-score contacts at one account can matter more than a single high scorer.

The pattern behind the exceptions: MQL is a tool for allocating scarce sales attention under lead volume. When the motion, the volume, or the unit of purchase changes, change the tool. The mistake is not having an MQL model or lacking one; it is keeping a model that no longer matches how your customers actually buy.

Making the handoff run itself

Definitions and SLAs live or die in execution. Someone has to route each lead within minutes, start the follow-up, and keep nurturing everyone who was not ready, indefinitely.

That operational layer is what Tented automates. Contacts and their behavior live in the audience CRM, and automated journeys handle the plumbing: instant follow-up when a lead crosses your threshold, recycle tracks matched to disposition reasons, and re-engagement when a cold lead warms back up. The AI writes the emails for each track, so adding a new path never waits on production. Every touch is logged against the contact, so the next scoring review argues from one shared record instead of two exports.

The definitions stay yours. The execution stops depending on anyone's memory.

Final thoughts

MQL and SQL are not standards handed down from anywhere. They are names for a promise between two teams, and they work exactly as well as that promise is kept. The companies that get this right do not have smarter definitions; they have definitions both teams actually use.

Write the definitions together, score simply, respond fast, recycle deliberately, and rebuild the model when your motion outgrows it. Then let a platform like Tented run the handoff mechanics, so your team's time goes where it belongs: into the conversations that actually qualify deals.