# MQL vs SQL: define and hand off leads

> Align marketing and sales qualification with shared criteria, an acceptance process and clear reasons to return a lead.


**Marketing-qualified leads (MQLs) and sales-qualified leads (SQLs) are qualification stages teams can use to agree when marketing should send a contact for review and when sales should accept it for follow-up.** MQL usually describes a record marketing considers ready for review; SQL describes one sales reviewed and accepted under shared criteria. Each company needs definitions that fit its offer and sales process.

Salesforce Mexico also recommends that marketing and sales agree on what MQL and SQL mean and when a contact is ready for sales as part of their service-level agreement. That is CRM vendor guidance, not a universal taxonomy. Read its explanation of [MQL and SQL](https://www.salesforce.com/mx/blog/mql-sql/?bc=OTH).

## Example criteria a team could agree on

Imagine a fictional company selling a content-planning service to small teams. The team documents its own rule:

- The contact provides valid details and works for a business in the service area.
- Their role contributes to content planning or the purchase decision.
- They request a demo or reply that they want to discuss the service.

If the contact meets those points and marketing records the evidence, the team can mark the lead as an MQL and send it to sales. Sales reviews it. If the team confirms there is a need the business can serve and agrees on a next step with the contact, it accepts the lead as an SQL. These criteria belong to the fictional business; another company may need different rules.

A submitted form or download alone does not require a team to call a record an MQL. The interaction is a signal to review alongside fit and available details. An SQL is not a closed opportunity or a customer; evaluation, a proposal and a purchase may still be ahead.

## Put the handoff in writing

| Point in the handoff | Owner | Minimum record |
|---|---|---|
| Marketing prepares the handoff | Marketing | Criteria met, supporting evidence, date and details needed to continue. |
| Sales reviews | Sales | Accepted or returned, review date and selected reason. |
| Both teams review the process | Marketing and sales | Accepted leads, repeated returns and agreed changes to the definition. |

The review time belongs in the team's agreement. Set it based on service capacity and the business's buying cycle; there is no universal response time that guarantees better results. If sales returns a lead, use reasons the team can act on, such as “outside service area” or “missing details to assess the need.” Avoid a vague label like “poor quality” when it does not explain what failed.

## Read acceptance with its denominator

In the same fictional case, marketing sends six unique contacts as MQLs during the month. By month-end, sales has reviewed all six: four are accepted as SQLs and two are returned. The calculation follows that same handoff cohort; it excludes acceptances of contacts sent earlier. The acceptance rate for that month, using the agreed rule, is:

**4 accepted SQLs ÷ 6 MQLs sent × 100 = 66.7%.**

That calculation describes the handoff in the fictional sample. Report the counts and the two returned leads too. The rate does not measure closed sales or prove that a campaign caused revenue. If a company records repeat contacts as separate rows or changes its criteria between months, the comparison no longer uses the same base.

To make the calculation reviewable, keep the lead ID, handoff date, sales decision, reason and version of the criteria. Also agree how to handle duplicates, contacts sales already opened and leads sent back to marketing for more information.

## A monthly review that leads to a decision

Marketing and sales can review a sample of accepted and returned leads and ask what evidence established fit, which details were missing and whether both teams applied the agreement consistently. If they change a criterion, record the date and compare each version separately. The number of MQLs alone does not show whether the process works.

Cost per lead answers how much each lead cost under a stated cost and counting rule. The [cost per lead guide](/en/guides/cost-per-lead/) explains that metric. This article focuses on the handoff between teams and their shared definition of a record sales accepts.

*The company, criteria and counts are fictional. MQL and SQL definitions are agreements an organisation needs to set; this example is not an industry standard or benchmark.*

The cover is an AI-generated illustration.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
