Marketing operations
MQL vs SQL: how to define lead stages sales will accept
MQL vs SQL comes down to who has qualified the lead. An MQL (marketing qualified lead) fits your target customer and has shown enough interest for sales to review it. An SQL (sales qualified lead) is an MQL that sales has reviewed or spoken with and confirmed is worth an active sales process.
MQL vs SQL: the short answer
| Aspect | MQL (marketing qualified lead) | SQL (sales qualified lead) |
|---|---|---|
| Who decides | Marketing, using rules agreed with sales | Sales, after reviewing or speaking with the lead |
| Evidence | Fit (role, company size, industry) plus engagement | Confirmed need, timing and the right contact |
| Trigger | Meets the written MQL definition or score thresholds | Rep confirms the lead is worth a sales process |
| Next action | Assign an owner and follow up within an agreed time | Create a deal and start the sales process |
| HubSpot lifecycle stage | Marketing Qualified Lead | Sales Qualified Lead |
| Measured by | Lead-to-MQL rate, time to first touch | MQL-to-SQL rate, time in stage |
| Typical failure | Rule so loose that sales stops trusting MQLs | Reps skip the stage, so it is never recorded |
What is an MQL?
A marketing qualified lead is a contact who matches your ideal customer profile and has taken actions that suggest buying interest, judged against criteria marketing and sales agreed in writing. An MQL is not sales-ready; it is ready for a salesperson to look at.
A good MQL definition is specific enough that two people looking at the same CRM record reach the same answer.
What is an SQL?
A sales qualified lead is an MQL that a salesperson has reviewed or contacted and confirmed is worth pursuing. Sales owns this call because it depends on what marketing data cannot show: real need, workable timing and a contact who can move a purchase forward.
Turn the questions reps already ask on a first call into written SQL criteria; BANT (budget, authority, need, timeline) is a common starting set. When sales rejects an MQL, the rep picks a reason from a fixed list, for example: not a buyer role, no current need, bad timing, outside our territory, existing customer or bad contact data.
How to write your MQL definition
Write the MQL definition as three lists: who fits, what engagement counts and what rules a lead out no matter what. Draft it with sales in the room; if the teams cannot agree, a neutral marketing operations consultant can run the session and turn the result into CRM rules.
Fit criteria
Fit describes who the lead is. Only use fields that are filled in on most records; a rule on a mostly empty field silently excludes good leads.
- Job function and seniority that match your buyer
- Company size range and industry you serve
- Country or region you can support
Engagement criteria
Engagement describes what the lead has done. Group actions by intent and set a time window, such as the last 60 days, so old activity stops counting.
- High intent: demo, consultation or pricing request, or a reply to a sales email
- Medium intent: pricing page visit, webinar attendance, case study download
- Low intent: newsletter signup, a single blog visit
Disqualifiers
Disqualifiers override everything else: students, job seekers, vendors pitching you, competitors, existing customers (who go to their account owner) and companies outside the size range or regions you serve.
Then combine the lists into one sentence sales can check against a record: A contact is an MQL when they have no disqualifier and have either made a high-intent request, or work at a company in our size range, hold a buyer role and have taken two medium-intent actions in the last 60 days.
Where lead scoring fits
Lead scoring applies your MQL definition automatically when there are too many leads to review by hand. A lead scoring model is the definition translated into points, not a replacement for it.
Score fit and engagement separately: one combined score hides the difference between a perfect-fit contact who has done nothing yet and a poor-fit contact who reads everything. HubSpot lead scoring can keep fit and engagement in separate score properties, though available features depend on your subscription.
A simple starting lead scoring model
Illustrative example only. These points and thresholds are invented to show the mechanics; they are not an industry benchmark. Engagement points count only actions from the last 60 days. Set yours from the traits of deals you have won, then adjust after a month of sales feedback.
| Criterion | Score type | Example points |
|---|---|---|
| Company size in target range | Fit | 20 |
| Job function matches buyer role | Fit | 20 |
| Industry in a served segment | Fit | 10 |
| Pricing page visit | Engagement | 10 |
| Case study download | Engagement | 10 |
| Webinar attended | Engagement | 10 |
| Newsletter signup | Engagement | 5 |
| Any disqualifier | Override | Not an MQL, whatever the score |
Worked example
The example MQL rule: fit of 40 or more and engagement of 20 or more. That matches the written definition above: size range plus buyer role reaches 40, two medium-intent actions reach 20, and industry adds points but cannot replace either. High-intent requests (demo, consultation or pricing requests, and replies to a sales email) skip scoring and go straight to sales, and a disqualifier overrides both paths.
- Contact A: target company size (20) + buyer role (20) = fit 40. Pricing page visit (10) + case study download (10) = engagement 20. Both thresholds met: MQL.
- Contact B: target company size (20) + served industry (10) = fit 30, because the job function is not the buyer role. Pricing page visit (10) + case study download (10) + webinar (10) = engagement 30. High engagement, poor fit: not an MQL. Contact B stays in nurture; the activity is a reason for sales to look for the actual buyer at that company.
- Contact C: target company size (20) + buyer role (20) + served industry (10) = fit 50. Newsletter signup (5) = engagement 5. Perfect fit, no recent interest: not an MQL yet; Contact C stays in nurture.
Mapping MQL and SQL to HubSpot lifecycle stages
Lifecycle stage is HubSpot's default property for funnel stage on contacts and companies. Its default values are Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist and Other. Give each stage you use a written entry rule, and set it automatically rather than by hand.
| Lifecycle stage | Example entry rule | Set by |
|---|---|---|
| Subscriber | Opted in to content only, such as a newsletter | Form or workflow |
| Lead | Shared contact details with a known source | Form or workflow |
| Marketing Qualified Lead | Meets the MQL definition or score thresholds | Workflow |
| Sales Qualified Lead | Rep confirmed qualification | Workflow on the rep's lead status update |
| Opportunity | A deal was created for the contact | HubSpot's deal lifecycle sync setting or one workflow, not both |
| Customer | A deal was closed won | HubSpot's deal lifecycle sync setting or one workflow, not both |
Lead status, recycling and cleanup
- Use lead status for the working state inside a stage (for example New, Attempted to Contact, Connected, Unqualified), so reps update one field and lifecycle stage stays clean. If your portal works leads in HubSpot's lead object instead of contact lead status, apply the same split: the lead record holds the working state, and lifecycle stage holds the funnel stage.
- Decide how recycling works. By default, HubSpot forms, imports and workflows only move lifecycle stage forward, so sending a rejected MQL back to Lead usually means a workflow clears the value first, then sets the earlier stage. Pick one rule and write it down, for example: rejected MQLs return to Lead with lead status Unqualified, and can re-qualify only on engagement after the rejection date.
- Audit before you rebuild. If stage values are already inconsistent, start with the CRM audit checklist, then rebuild stages, properties and the workflows that move them as one piece of HubSpot setup.
The marketing-to-sales handoff rule and follow-up time
The handoff rule is a short written agreement on what happens between MQL and SQL, who does it and by when.
- 01Assign. Every new MQL gets an owner automatically, with a fallback owner for leads no rule catches. See HubSpot lead routing for the rule types.
- 02Follow up. Agree a first-touch window your team can staff, shorter for high-intent requests (for example, the same business day for demo requests and two business days for other MQLs; set yours from real capacity, not a published benchmark), and create a task when the lead is assigned.
- 03Escalate. If an MQL has no logged activity when the window ends, alert the sales manager.
- 04Decide. The rep marks the lead SQL, recycled or disqualified, with a reason.
- 05Review. Monthly, look at rejected MQLs by reason and change the definition when one reason keeps appearing.
Metrics to watch: lead-to-MQL rate, MQL-to-SQL rate and time in stage
Track these by source and by month; a blended rate hides the channel sending poor leads. For MQL-to-SQL, count by cohort where you can: of the MQLs created in a month, how many became SQLs, whenever that happened. Dividing one month's SQLs by the same month's MQLs mixes cohorts and swings when sales takes weeks to qualify.
| Metric | Formula | What a change usually means |
|---|---|---|
| Lead-to-MQL rate | MQLs ÷ new leads × 100 | A sharp rise can mean the rule is too loose |
| MQL-to-SQL rate | SQLs from a month's MQLs ÷ that month's MQLs × 100 | A falling rate usually means sales distrusts the definition or follow-up is slow |
| Time to first touch | Median hours from the MQL date to the first logged call, email or meeting | A rising figure points to routing or capacity gaps; check it by owner |
| Time in stage | Median days between entering and leaving a stage | A long MQL stage means reps are not making the SQL, recycle or disqualify decision |
Illustrative calculation
Made-up numbers to show the arithmetic, not targets: if 200 new leads arrive in a month, 40 of them become MQLs and 10 of those MQLs become SQLs, the lead-to-MQL rate is 40 ÷ 200 × 100 = 20% and the MQL-to-SQL rate is 10 ÷ 40 × 100 = 25%.
HubSpot stores the date a contact entered each lifecycle stage, so time in stage is reportable. These metrics belong on your marketing KPI dashboard and feed campaign performance measurement when you want cost per MQL or SQL by campaign.
Common mistakes when defining MQLs
- Counting every form fill as an MQL. The MQL count rises, the MQL-to-SQL rate falls and sales stops opening the queue.
- A definition nobody wrote down. If the rule is not in one shared place, the CRM and the team drift apart.
- Silent rejections. Without rejection reasons, marketing cannot tell what to fix.
- Never revisiting the rule. Review it on a set schedule, for example quarterly, and after any big change in channels or offer.
Questions this guide answers
Is a demo request an MQL or an SQL?
Treat it as a high-intent MQL that skips scoring and goes straight to sales review. It becomes an SQL when a rep confirms fit and need, often on the first call. Recording both steps keeps conversion rates accurate.
What is a sales accepted lead (SAL)?
An SAL is an optional stage between MQL and SQL: sales has agreed to work the lead but has not qualified it yet. Add it only if you need to measure acceptance separately from qualification.
Do small teams need lead scoring?
Not always. If someone can review every new lead within a day, a written MQL definition and a saved CRM view do the job. Scoring earns its setup time when volume makes manual review slow or inconsistent.
What is a good MQL-to-SQL conversion rate?
There is no single standard. It depends on how strict your MQL definition is, your sales cycle and your channel mix. Track your own rate by source over several months; the trend tells you more than a published average.
Who should own the MQL definition?
Marketing owns it day to day, but sales agrees to it before it goes live. Name one person to approve changes and keep the definition in a shared document linked from the CRM.
Marketing and sales still arguing about what counts as a lead?
In 20 minutes I'll look at how leads move from form to sales today, where your MQL and SQL definitions break down, and what to change first.
Book a 20-minute funnel definitions callMichelle Ivanova runs imivs consulting, building marketing operations, CRM workflows and reporting automation in the tools a team already uses.