MQL vs SQL: What Separates Them and How to Hand Off
An MQL is a lead worth nurturing. An SQL is ready for a sales conversation. Here is how to define both, plus SAL, for ad-funded service businesses.
An MQL (marketing qualified lead) fits your target customer and has shown real interest. But they are not ready to talk to sales yet. An SQL (sales qualified lead) has shown clear buying intent and is ready for a sales conversation. The gap is readiness to buy. It is not how many clicks or downloads a lead has racked up.
Simple, right? In practice, most Australian service businesses running Google or Meta ads blur the two. A form fill lands in the CRM (your sales system), gets called a lead and sits there until someone has time. This guide covers the definitions, the middle stage (the SAL), how to write criteria that suit your business and what to measure so the handoff stops leaking.
MQL vs SQL at a glance
HubSpot puts it simply. MQLs need more nurturing. SQLs meet set criteria for direct sales contact. Adobe's explainer covers the same split.
| MQL | SQL | |
|---|---|---|
| Who decides | Marketing, using preset fit and engagement criteria | Sales, after a conversation or a clear buying signal |
| What it shows | Interest and a good match to your ideal customer | Intent to buy and a relevant problem |
| Typical signals | Ad engagement, content downloads, webinar sign-ups, repeat visits, form submissions | Demo or consultation request, pricing questions, product comparison request, a direct conversation confirming need |
| Right next step | Nurture with education and proof | A fast, direct path to a call, with commercial detail |
| Owner of the follow-up | Marketing sequences | A person (or a system acting for one) who can book and sell |
The two stages need different messaging. Early prospects need education and confidence. Sales-ready ones need a clear next step. Adobe's guide to MQL and SQL stages goes deeper on each.
One catch. The idea that marketing owns MQLs and sales owns SQLs is too tidy. Salesforce treats them as two points in the buyer's decision. A lead can be very engaged and still not ready to buy. So SQL should mean "ready for a sales conversation". It should never be a reward for marketing activity.
What is an MQL?
Salesforce explains that an MQL has shown interest in your brand. Marketing judges them likely to become a customer, using set criteria such as product-need fit and budget. Two things must be true. The person matches your target customer. And they have taken a meaningful action.
For a service business running lead campaigns, keep it simple. An MQL is a real person who matches your customer profile and has done something meaningful. Capture these fields:
- The service they want
- Their location
- Company type
- Their role
- Working contact details
Say someone downloads a checklist from a LinkedIn post and uses a generic email address. That is a lead, but maybe not an MQL. Now say a facilities manager at a 60-person company in your service area visits three pages and submits a form. That is probably an MQL.
What is an SQL?
An SQL is a lead that has passed the MQL bar and then shown clear buying intent. Salesforce's Australian site gives examples: in B2B software this often means booking a demo or starting a trial, and in other models it might be requesting a quote or asking to speak with sales.
For a service business, an SQL needs proof of a real problem and a willingness to talk. Salesforce's guidance points to the BANT checks (budget, authority, needs and timeline). These are the questions to settle:
- Urgency: when do they need this fixed?
- Current process: what are they doing today?
- Decision-maker involvement: is the person you are talking to the one who signs off?
- Budget range, where appropriate
- Agreement to a call or assessment
Notice that most of these cannot be read off a click. Someone has to ask. That is why an enquiry form submission from a Google or Meta ad is not automatically an SQL, however expensive the click was.
Where SAL fits in
Many people also search for the gap between MQL and SAL. A SAL (sales accepted lead) sits between the two. ORM's glossary lays out three stages in order. An MQL meets marketing's bar. A SAL is a lead sales has agreed is worth working. An SQL is one sales has worked and confirmed as a real opportunity candidate.
The Pedowitz Group frames it as an agreement. An MQL meets fit and intent. Sales accepts a SAL within an agreed time. A rep confirms an SQL as sales-ready.
The SAL matters because it creates a checkpoint. Without it, marketing can pass over leads that sales never touches, and nobody can say whether the problem was lead quality or lead handling. With it, you can see exactly where leads stall.
A small business may not need a formal SAL stage. If you have two salespeople and 40 enquiries a week, a simple rule such as "accepted means a rep has attempted contact" may be enough. The point is to record that the lead was received by a human or a system that can act on it.
What comes first, MQL or SQL?
The MQL comes first. The usual path is lead, then MQL, then (optionally) SAL, then SQL, then opportunity, then closed won or lost. Salesforce lays out this lifecycle with the SQL sitting after the MQL and before an active deal.
There is one important exception. Some leads skip the MQL stage entirely. Someone who clicks your ad and immediately asks for a quote or a consultation has expressed explicit purchase intent on the first touch. Treating that person as an MQL and dropping them into a nurture sequence is one of the commonest ways paid leads go cold.
The Nielsen Norman Group studied long online sales cycles. Buyers who know what they want move fast. Half the conversions in its study (mostly consumer sites) happened within 28 minutes of arriving from a search engine. So here is the rule for a service business. Send high-intent enquiries to a person straight away. Nurture the lower-intent MQLs.
How to write your own definitions
Generic scoring thresholds are the weak point of most MQL programs. Amplitude says leads can be classified by specific, measurable behaviours, such as content downloads and demo requests. Take that one step further and base the behaviours on your own funnel. A free trial, a demo request or a pricing page visit might be an SQL in one business and only an MQL in another.
Here is a process you can run in an afternoon:
- Pull your last 30 to 50 won customers. Note the service they bought, company size, role of the first contact and how they first enquired.
- Pull a similar number of lost or stalled leads. Look for what they had in common that the winners lacked.
- Write the fit test. Combine the fields that separated winners from losers (service, location, company type, role).
- Write the intent test. List the actions that preceded wins: a consultation request, a pricing question, a call booked.
- Set the SQL gate. An SQL is a lead that passes the fit test, shows an intent action and has confirmed a relevant problem, ideally in conversation.
- Agree a response standard. Decide in writing how quickly each stage gets a human touch, and who owns the lead at each point.
- Review quarterly. Definitions drift as your offer and ad targeting change.
The Salesforce guide makes the same point. Qualification is fit plus buying intent. It is not a generic score.
A worked example for a service business
Say you run a commercial cleaning company and advertise on Google. Three enquiries land on the same morning:
- Enquiry A downloads a pricing guide, has a personal email address and gives no company name. Fit is unclear and intent is mild. This is a lead, probably not yet an MQL. Send it to a nurture sequence and watch for more activity.
- Enquiry B is an office manager at a company in your service area who has read several service pages and filled in a contact form with no specific question. Fit is good, intent is moderate. This is an MQL. Nurture it, but with a short, human-sounding reply that invites a conversation.
- Enquiry C is an operations manager who asks for a quote for a 1,200 square metre office starting next month. Fit is good and intent is explicit. This should go straight to a person, be confirmed as a SAL and, once the rep confirms need and timing, become an SQL.
The same ad produced all three. Only one of them should reach a salesperson's phone in minutes. This is the practical value of the MQL and SQL split: it tells your team which enquiries need speed and which need patience.
What is a good MQL to SQL rate?
There is no honest universal figure. Be wary of any article that gives you one with no study behind it. The research we reviewed sets no Australian benchmark for MQL to SQL conversion. Rates shift with your industry, price point, traffic source and how strictly you define each stage.
A better question is whether your rate is moving, and why. LeadSpot's 2026 B2B pipeline report looked at teams in the top quartile for MQL to SQL conversion. They define lead quality at the point of qualification, not after delivery. In short, the best teams agree what good looks like before the lead moves.
Set your own baseline from the last two or three months of data, then improve against it.
What to measure beyond MQL volume
MQL volume alone rewards cheap, shallow leads. Amplitude says to measure and track both MQLs and SQLs. Track a fuller set of numbers than volume:
- MQL to SAL acceptance
- SAL to SQL conversion
- SQL to opportunity conversion
- Opportunity to won conversion
- Speed to first response
- Revenue or pipeline by lead source
Read them as diagnostics:
| What you see | Likely cause | Where to look |
|---|---|---|
| Many MQLs rejected by sales | Targeting, form quality or a definition sales never agreed to | Ad audiences, form fields, the shared definition |
| SALs accepted but rarely become SQLs | Response quality, qualification, offer fit or follow-up | First-contact speed, the questions asked, follow-up cadence |
| Plenty of SQLs but few opportunities | Sales process or proposal stage | Call quality, pricing conversation |
Judge ad spend by the downstream stage
If you buy leads through Google or Meta, chasing the lowest cost per lead pulls the platform toward people who fill in forms. Not people who buy. Look further down. How many leads became SQLs? How many of those closed? An NYU Stern study found paid and organic search together converted better than organic alone (an 11.7% rise in combined conversion rate). It is not an Australian benchmark. But it backs the idea of judging the whole journey, from ad to qualified opportunity.
If your ads bring volume but few SQLs, paid ads management built around your sales pipeline starts from that downstream view.
Why the handoff breaks
The handoff usually breaks for one of five reasons:
- No shared definition. Marketing counts a form fill as a win. Sales counts only booked calls. Both are right by their own measure.
- No response standard. Leads sit in a queue because nobody owns the clock.
- Everything is nurtured. High-intent enquiries get the same email sequence as someone who downloaded a guide.
- Qualification happens too late. The first real question is asked days after the enquiry, when the prospect has moved on.
- Nothing is written back to the CRM. The stage a lead is in does not match reality, so reporting is fiction.
The last point deserves attention. If stage changes are not recorded as they happen, none of the metrics above can be trusted. Njin's CRM Agent is built to update records automatically from call transcripts, which keeps stages honest without relying on reps to type notes.
Automating qualification without losing the human call
The gap between MQL and SQL is mostly a question gap. Someone has to find out urgency, current process, decision-maker involvement and budget. Doing that manually for every ad lead is slow, and slow is expensive when you are paying for each click.
This is where AI qualification helps. A system can reply to an enquiry in seconds and ask the SQL questions in a chat. Then it either books a call with a salesperson or puts the lead into nurture.
Our guides on real-time lead qualification and chatbot lead qualification guide show how it works. The AI Orchestrators guide to AI lead qualification covers founder-led firms. AI lead routing then sends confirmed high-intent leads to the right person straight away.
Automation should serve your definitions, not replace them. Write the MQL and SQL criteria first, then build the system to apply them.
Keep automated follow-up lawful
If your qualification and nurture involve email, SMS or instant messages, the Spam Act applies. The ACMA says you must have consent from the recipient, identify yourself as the sender and make it easy to unsubscribe. It also says it is up to you to prove you have consent, so keep a record of who gave it, when and how.
Business Victoria's guidance covers the same rules for small business. An enquiry does not mean the lead agreed to unrelated promotions. Make sure every automated message traces back to a lead source and a consent record.
Where Njin fits
Njin is an Australian AI sales agency. Your business already pays for Google or Meta ads. We build systems that answer every enquiry in seconds, ask the SQL questions, book the call and follow up. All of it plugs into your existing CRM.
The Lead Qualification Agent is $8,400 to set up and $2,200 a month. If you want a faster first step, the Instant Reply Agent is $900 to set up and $400 a month. The full range is on our services page.
Common questions
What is the difference between an MQL and an SQL in HubSpot?
In HubSpot, MQL and SQL are lifecycle stages on a contact record. HubSpot describes an MQL as a contact who has shown interest but is not ready to buy, and an SQL as one ready for direct sales engagement. The labels only help if your team agrees the rules for moving a contact from one to the other.
How can I convert an MQL to an SQL?
Give the lead a fast, direct path to a conversation. Ask the questions that confirm need and timing. Early-stage prospects need education. Sales-ready ones need commercial detail and a clear next step, as Adobe's guide covers. Speed matters most for leads who ask about pricing, availability or a consultation.
What is the difference between MQL and SAL?
A SAL is a lead that sales has formally accepted as worth working. It sits between the MQL and the SQL, so an MQL is marketing's judgement, a SAL is sales agreeing to take it on and an SQL is sales confirming it is a real opportunity. Tracking the SAL stage shows whether a stalled lead is a quality problem or a handling problem.
Is a form submission from a Google or Meta ad an SQL?
Not automatically. A form fill shows interest, but an SQL needs evidence of a relevant problem and willingness to talk to sales. Treat it as an MQL unless the person has asked for a quote, price or consultation, in which case route it to a person straight away.
Not sure where your leads leak? Take the AI readiness assessment to find out. Know what you need? Book a call.
