Quick Answer
- An MQL (marketing qualified lead) is a prospect marketing has determined shows enough engagement to be worth continued outreach.
- An SQL (sales qualified lead) is a prospect sales has independently vetted and accepted as ready for a direct buying conversation.
- The handoff between them is where most B2B revenue leaks.
- Lead scoring is the mechanism that automates and standardizes that handoff.
- A formal SLA (service-level agreement) between marketing and sales is what makes the handoff stick.
- Tracking conversion rates at each stage tells you whether your definitions are calibrated or need fixing.
What Makes an MQL and an SQL Different?
An MQL is a lead marketing believes is worth engaging; an SQL is a lead sales has accepted as ready to buy.
The distinction sounds simple. In practice, it is the source of more inter-departmental friction than almost any other definition in B2B marketing.
Marketing looks at a lead and sees signals: the contact visited the pricing page twice, downloaded a case study, and opened three emails in the last two weeks. That pattern looks like interest. Marketing marks the lead as an MQL and passes it to sales.
Sales picks it up, calls the contact, and finds out the person is a student writing a research paper. They reject it. Marketing says sales is too picky. Sales says marketing is sending garbage. Both are partly right, and the root cause is that nobody agreed on what "qualified" means before the first lead ever came in.
That definitional gap is expensive. Every dollar your paid media campaigns spend generating leads that sales will never work is money that did not compound into revenue. Getting the MQL and SQL definitions right is not a semantic exercise. It is a budget decision.
Where Each Stage Sits in the Funnel
A lead moves through stages, and the naming convention reflects how much the business knows about that lead and how ready they appear to buy.
Subscriber or contact: Someone who opted in for a resource or is in your database. No qualification yet.
MQL: Marketing has scored or reviewed this contact and concluded they match your target profile and have shown enough behavioral signals to be worth nurturing or handing off.
SQL: Sales has spoken with or reviewed the MQL and confirmed the contact has a real need, real budget or authority to spend, a defined timeline, and no disqualifying factor. The BANT framework (Budget, Authority, Need, Timeline) is still a common structure for this vetting, though many teams adapt it to their own sales cycle.
Opportunity: The SQL has entered a formal sales process. A proposal, quote, or demo has been initiated.
Customer: Closed.
Most marketing tracking systems can count contacts at each stage. Most sales CRMs can count opportunities and customers. The gap where data goes dark is almost always the MQL-to-SQL handoff and the SQL-to-opportunity conversion. That is exactly where you want measurement.
How to Define MQL and SQL Criteria Your Team Will Actually Agree On
The failure mode here is letting marketing define both stages alone. When that happens, sales has no ownership of the criteria and no incentive to work every lead marketing sends.
A better process brings both teams into a single working session to answer four questions together.
1. Who is our ideal customer? Build a concrete profile: company size, role, industry, problem they are trying to solve. Any lead who does not match this profile is not an MQL no matter how many pages they visited.
2. What behaviors signal real interest? Page visits, content downloads, webinar attendance, email clicks, demo requests, pricing page views. Rank these by how strongly they correlate with eventual purchase. A demo request ranks higher than a single blog visit.
3. What behaviors signal sales-readiness? A contact who requests a proposal, books a meeting, or responds to a direct outreach saying "yes, let's talk" is behaving differently from one who just downloaded a guide. Sales-readiness signals go into the SQL criteria.
4. What immediately disqualifies a lead? Wrong company size, wrong geography, a competitor's email domain, a student email address. These are explicit disqualifiers. Define them so your scoring model can filter them out automatically.
Document the answers. Put them somewhere both teams can see. Review them quarterly, because what qualifies a lead this quarter may not qualify one next quarter if your market or product changes.
Lead Scoring: The Bridge Between MQL and SQL
Lead scoring is the bridge between MQL and SQL, it turns subjective judgment calls into a repeatable, data-driven handoff process.
Lead scoring assigns point values to a contact's attributes and behaviors. When a contact crosses a threshold you set, they become an MQL. When they cross a higher threshold or trigger a specific high-intent action, they become an SQL.
A basic model looks like this:
Demographic fit (added at contact creation):
- Matches target company size: +10
- Matches target role: +10
- Outside target geography: -20
Behavioral signals (added as they occur):
- Visited pricing page: +15
- Downloaded a case study: +10
- Opened three or more emails in 30 days: +5
- Attended a live webinar: +20
- Requested a demo: +40
A contact who requests a demo and matches the target profile may cross your MQL threshold instantly. A contact who has been reading blog posts for six months may accumulate points slowly and graduate to MQL status over time. Both paths are valid. The scoring model handles both without a human having to review every contact individually.
Score decay matters too. A contact who visited your pricing page eight months ago and has done nothing since is not as warm as they were. Most marketing automation platforms support time-based score decay so old signals do not keep a stale lead artificially inflated.
Your conversion tracking setup needs to feed behavioral data into the scoring model. If your site events are not firing correctly, or if your CRM and your marketing automation platform are not synced, your scores will be wrong and your handoffs will be wrong. Tracking accuracy is not optional here. It is the foundation the whole model runs on.
The Handoff: SLAs Between Marketing and Sales
A service-level agreement between marketing and sales defines how fast sales must contact a new SQL and what feedback loops marketing gets in return.
A lead scoring model that delivers an SQL to sales means nothing if sales takes three days to follow up. Speed matters in B2B lead response. The difference between contacting a prospect within minutes versus hours produces measurably different connect rates, though exact figures vary widely by industry and channel. The principle is consistent: faster response wins more conversations.
An SLA between marketing and sales formalizes the expectations on both sides.
What marketing commits to:
- A minimum volume of MQLs per period (tied to budget and channel mix).
- A defined quality bar that MQLs must meet before handoff.
- Ongoing updates to ICP (ideal customer profile) and scoring criteria based on sales feedback.
What sales commits to:
- A maximum response time for new SQLs (commonly 24 hours for inbound, though teams set this based on their sales cycle).
- A minimum number of follow-up attempts before a lead is disqualified.
- A feedback loop: for every SQL that sales rejects, a reason code is logged so marketing can improve the scoring model.
That feedback loop is the piece most teams skip. Without it, marketing keeps sending the same profile of leads, sales keeps rejecting them, and nobody learns anything. With it, the model improves each quarter.
Why Bad Definitions Create Finger-Pointing and Wasted Spend
Poor MQL and SQL definitions do not just cause friction, they cause wasted ad spend, because marketing keeps funding campaigns that generate leads sales will never work.
Imagine a home services company running paid search campaigns for HVAC installation. The campaigns generate a solid volume of form fills. Marketing counts them as MQLs and hands them to sales. Sales calls them and finds that half the contacts were renters who cannot authorize the purchase, and another quarter were in a service area the company does not cover. The MQL count looks strong. The pipeline does not grow. The ad budget keeps running.
The fix is not to spend less on ads. The fix is to tighten the qualification criteria so the campaigns are optimized for contacts who actually match the buyer profile. That means adding geography and homeowner signals to the landing page form, adjusting the scoring model to filter out disqualifiers before the handoff, and feeding sales rejection data back into the campaign targeting.
When you can trace a bad SQL back to a specific campaign, keyword, or audience, you can fix the upstream source of the problem. That is the practical value of clear definitions. They make your attribution data actionable.
Tracking Conversion Rates at Each Stage
Tracking conversion rates at each funnel stage tells you whether your qualification criteria are calibrated correctly or need tightening.
Three conversion rates tell you most of what you need to know about the health of your lead pipeline.
Lead to MQL rate: What percentage of raw contacts graduate to MQL status? If this rate is very high, your MQL bar is too low. If it is very low, your scoring model may be too aggressive or your campaigns may be attracting the wrong audience.
MQL to SQL rate: What percentage of MQLs that go to sales get accepted? This is the most important leading indicator of marketing-sales alignment. A persistently low rate means the MQL definition is wrong, the scoring model needs recalibration, or sales is applying a different standard than marketing. A healthy rate varies by industry and sales cycle, but the trend over time matters more than any single benchmark.
SQL to close rate: What percentage of SQLs become customers? This is primarily a sales metric, but a sudden drop can indicate that the SQL criteria have gotten too loose, or that a campaign is bringing in contacts who match the profile on paper but not in intent.
Review these three rates together at least monthly. A drop in MQL-to-SQL conversion in the same month that ad spend increased on a new channel is a clear signal: the new channel is bringing in leads that do not convert. That is data you can act on immediately.
If you want to build this kind of pipeline visibility and connect it to your actual ad spend, our tracking and automation services are the starting point. Most teams are missing this layer, and the absence of it is what keeps marketing and sales in a cycle of blame instead of improvement.
Frequently Asked Questions
What is the difference between an MQL and an SQL?
An MQL (marketing qualified lead) is a prospect that marketing has determined shows enough interest and profile fit to be worth engaging. An SQL (sales qualified lead) is a prospect that sales has reviewed and accepted as genuinely ready for a buying conversation. The MQL is marketing's judgment. The SQL is sales's confirmation. Both judgments need to be based on agreed-upon criteria, or the handoff breaks down.
What qualifies a lead as an MQL?
A lead qualifies as an MQL when they meet two conditions: they match your ideal customer profile (right company size, role, industry, geography), and they have demonstrated behavioral signals of interest (visiting high-intent pages, downloading content, attending a webinar, opening emails consistently). Most teams encode these criteria into a lead scoring model so the qualification happens automatically rather than through manual review.
Who owns MQLs vs SQLs?
Marketing owns MQLs. The marketing team is responsible for generating, nurturing, and scoring contacts until they reach MQL threshold, then handing them off. Sales owns SQLs. Once a contact crosses into SQL status and sales accepts it, sales is responsible for follow-up, vetting, and advancing the contact through the pipeline. The handoff moment, and the SLA that governs it, is jointly owned.
How do you convert an MQL to an SQL?
An MQL converts to an SQL when sales reviews the contact and confirms they meet the agreed SQL criteria, usually some version of Budget, Authority, Need, and Timeline (BANT). Practically, this happens when the MQL takes a high-intent action (books a demo, responds to outreach, requests a proposal) or when sales makes outbound contact and the conversation confirms readiness. A well-configured lead scoring model can automatically flag when an MQL's score crosses the SQL threshold, prompting sales to initiate contact.
How often should we review our MQL and SQL definitions?
Quarterly is a good starting cadence. Review the MQL-to-SQL conversion rate, pull the rejection reason codes from sales, and look at which campaigns are producing MQLs that convert versus ones that do not. If your product, pricing, or target market has shifted, your qualification criteria need to shift with it. Annual reviews are not frequent enough for most B2B companies running active paid campaigns.
What happens to MQLs that sales rejects?
A rejected SQL (a lead sales reviewed and declined to work) should be logged with a reason code and returned to a marketing nurture sequence, not deleted. Some rejected leads will become buyers in six or twelve months when their situation changes. The reason code is what matters most: it tells marketing whether the rejection was a scoring model failure (the wrong profile got through), a timing issue (the contact was not ready yet), or a permanent disqualifier (wrong company size, competitor). That data is what makes the next quarter's model more accurate.
Can a lead skip the MQL stage and go straight to SQL?
Yes. When a contact comes in through a high-intent channel, such as a direct demo request, a referral from an existing customer, or an inbound call where they state a specific need and budget, sales can accept them as an SQL without the contact going through the standard MQL scoring process. These are sometimes called "sales accepted leads" or fast-tracked SQLs. The key is logging them correctly so your conversion rate data stays accurate.
Ready to connect your lead stages to real revenue data? A 30-minute strategy call is the fastest way to identify where your pipeline is leaking. Book a call with RGDM.