The practical difference between MQL and SQL is who has qualified the lead and what they know. A marketing-qualified lead meets marketing’s agreed conditions for sales review. A sales-qualified lead has been assessed by sales as a potential customer. A sales-accepted lead, or SAL, can sit between them to record that a salesperson has taken responsibility for the review.
These labels only help when they change an action. If everyone has a different definition of “qualified,” a funnel report will count disagreements as performance. This guide provides a handoff model a small service business can adapt, including evidence, ownership, and reporting rules.
MQL vs SQL: a comparison that sales can use
HubSpot's lifecycle documentation assigns MQL qualification to marketing and SQL qualification to sales. It also allows organizations to customize their stages. Your CRM may use different names, so document the operating meaning before mapping fields or building reports.
| Stage | Question it answers | Typical evidence | Owner of the decision |
|---|---|---|---|
| Lead | Is this a valid commercial inquiry? | Relevant request and usable contact details | Intake or marketing |
| MQL | Should sales review this inquiry? | Minimum fit and a meaningful buying signal | Marketing |
| SAL | Has someone accepted responsibility? | Named salesperson and acceptance timestamp | Sales |
| SQL | Is there a plausible sales opportunity? | Confirmed need, suitable scope, and next step | Sales |
| Opportunity | Are we managing a potential deal? | Defined buying process and deal record | Sales |
| Customer | Has the purchase milestone been met? | Your agreed signed or paid event | Sales or operations |
The evidence in this table is a proposed workflow, not a universal definition. Some businesses create opportunities earlier; others use an SQL stage without SAL. What matters is that two team members can examine the same record and reach the same conclusion.
What does SAL add?
SAL records operational acceptance. It means a person has agreed to work the lead, not that the buyer has agreed to buy or even answered a call. This distinction reveals leads that marketing delivered but sales never picked up.
For a two-person team with a shared inbox and immediate assignment, a separate lifecycle stage may add unnecessary administration. You can retain an accepted-at timestamp and owner instead. For a larger queue, SAL may make unclaimed work easier to see.
Do not assume SAL exists as a default field in every CRM. In HubSpot’s documented default lifecycle list it is not a separate standard stage. Decide whether to represent acceptance through a custom stage, status, or timestamp based on how your reports and automations work.
Write entry criteria before adding automation
Start with the service you sell. A consultancy might require an offered service, a supported market, and either a consultation request or a sufficiently specific project brief before creating an MQL. A newsletter subscription alone would not meet those example conditions.
An SQL rule could require sales to confirm the problem, delivery fit, a credible purchase process, and an agreed next action. Budget can be a range or a funding discussion; a missing final number does not always mean the opportunity is invalid.
Avoid criteria that merely restate the stage name. “Interested lead” is not an actionable MQL definition. “Requested a consultation about an offered service and meets the delivery-area rule” is testable. If using lead scoring, specify which fit and intent conditions trigger review and which facts sales must still verify.
Build a handoff record that reduces repeated questions
A useful handoff contains enough context for the salesperson to begin a relevant conversation. It should not require the buyer to repeat everything entered on a form.
- Contact and company details needed for the response.
- Requested service, stated problem, and the original inquiry.
- Campaign source and landing page when reliably available.
- Evidence supporting MQL status, including unknown fields.
- Assigned owner, backup, and response deadline.
- Stage-change timestamps and a link to the relevant conversation.
Keep the buyer’s exact request available to the owner. A dropdown such as “marketing services” is useful for routing but loses nuance. A prospect asking to replace an unreliable provider needs a different opening conversation from one testing advertising for the first time.
Assignment alone is not acceptance. Define whether acceptance happens automatically when a queue rule assigns a record, or only when a person acknowledges it. The first is easier to automate; the second measures actual pickup. Label the report accordingly.
Use explicit rejection and recycling rules
Sales should be able to return a lead with a specific reason. Distinguish confirmed poor fit from missing information, no response, timing, and duplicates. Combining all of them into “bad lead” makes marketing optimization difficult.
| Outcome | Example | Next action |
|---|---|---|
| Disqualified | Requests a service you do not offer | Record reason and close the inquiry |
| More information needed | Scope is unclear | Ask one focused clarification question |
| No response | Agreed contact attempts are unanswered | Move to a documented follow-up state |
| Future timing | Suitable project starts next quarter | Schedule an appropriate check-in |
| Duplicate | Existing active inquiry from the same buyer | Link records and preserve ownership |
A recycled lead should retain its history. Do not erase its first MQL date when a later conversation revives it. Store a new transition or requalification date so the team can distinguish first qualification from renewed interest.
Calculate conversion rates using the same cohort
Suppose 100 leads first became MQLs in a particular month. After a defined observation window, sales accepted 80, qualified 32 as SQLs, and won eight customers. This is an illustrative cohort, not a performance benchmark.
The MQL-to-SAL rate is 80%. SAL-to-SQL is 40%. MQL-to-SQL is 32%. SQL-to-customer is 25%. MQL-to-customer is 8%. All denominators come from the same original group and the same stated observation window.
Do not divide today’s SQL inventory by today’s MQL inventory and call the result a conversion rate. Leads may leave one stage when they enter another, and different cohorts mature at different speeds. Inventory answers “what is in the pipeline now”; transitions answer “what happened to this group over time.”
Define the counting unit as well. Five contacts from one company may represent five people, one account, or one buying opportunity. A report that switches units between stages can make a conversion rate meaningless even when every record is accurate.
Diagnose the funnel before blaming a team
Low acceptance with many unassigned records suggests a routing or capacity problem. High acceptance but low qualification may indicate weak fit criteria, an unclear offer, or missing intake information. Healthy qualification but few wins points toward pricing, competition, proposals, timing, or sales execution.
These are diagnostic hypotheses. Review actual records before concluding that a campaign or salesperson caused the change. A shift in service mix can alter rates without any deterioration in execution.
Track lead response time next to stage conversion. A high-quality inquiry that sits untouched for days is a different problem from an inquiry outside your service area. Give both a visible reason rather than letting them disappear into one rejection percentage.
Run a weekly handoff review
Choose a small sample of accepted, rejected, and stalled records. Have marketing and sales explain the decisions using the written criteria. Fix unclear rules, missing evidence, and queue ownership before adding more fields.
When definitions change, date the new version and preserve the old one with historical reports. Changing the meaning of SQL halfway through a month can create apparent growth with no improvement in buying intent.
Use practical lead qualification questions to resolve the most common evidence gaps. The handoff is working when sales can act promptly, marketing can understand rejection reasons, and the same funnel numbers describe the same business events for everyone.
Cover photo: Campaign Creators, via Unsplash.