What is the practical difference between an MQL and an SQL?
An MQL appears after an interest signal: a decision-maker replies to an email, requests material, asks a question or passes you to a colleague. That does not yet mean the company is selecting a supplier. A lead becomes an SQL after a short qualification confirms who is involved, what task is under discussion and what happens next. See how this fits into a complete process in our full-service outreach guide.
| Check | MQL | SQL |
|---|---|---|
| Interest | There is a reply or another signal | The subject of the conversation is confirmed |
| Contact | May not be the decision-maker | A decision-maker is involved or the route to one is clear |
| Next step | "Send information" | A call, proposal or estimate is agreed |
Which replies move a lead from marketing to sales?
For cold outreach, record facts from the reply rather than an abstract impression of interest. For example, “We may change our integration provider in the autumn; please send examples” is an MQL while the budget, scope and buying group remain unknown. If you ask who evaluates the technical side and whether they can discuss requirements this week, a reply with the project lead’s contact details and a call time moves the lead to SQL.
- Match the company against your ICP: industry, size, geography and type of need.
- Confirm the contact’s role: decision-maker, influencer or route to the decision-maker.
- Record the need in the prospect’s own words, not in a sales manager’s formula.
- Agree a specific next action and pass the full context into the CRM.
Do not send sales a screenshot of a reply without the thread behind it. The CRM record should include the original message, the reason for contact, any objection and what was promised. This is the basis of disciplined reply handling and qualification and CRM integration.
Why does “send a proposal” not automatically make a contact an SQL?
A common mistake is treating every proposal request as buying intent. In Russian and CIS B2B outreach, “Send it to the general inbox” can be a polite way to end the exchange or route a message to procurement without an active task. The useful response is to clarify the context, not to send a long presentation.
An equipment supplier writes: “We understand you are expanding your packaging area. Is line automation already under consideration?” The production manager replies: “Send a proposal.” Sending a catalogue with dozens of options is not qualification. A better reply is: “We will prepare it. To keep it relevant: are you replacing an existing line or equipping a new area, and who confirms the required throughput?” If the answer brings parameters and a buying participant into the conversation, it is an SQL; otherwise it remains an MQL for a careful follow-up.
The quality of the first question determines how many replies can be qualified at all. For the underlying message structure, see our guide to cold email and follow-up emails.
When MQL and SQL are not the right fix
Two statuses will not solve the problem if you cannot explain your offer through one specific business question. When one email tries to sell development, marketing, support and training at once, the recipient does not know what to respond to. Start with one hypothesis and one segment, particularly when you are testing an ICP.
- This is not for you if nobody can contact a replying lead promptly.
- It is not enough if sales and marketing have not agreed what a target customer looks like.
- It should not be used for reporting that treats MQLs as revenue or closed sales.
The operating rule matters more than the label. Your CRM can use different statuses, but the handoff rule must answer three questions: who replied, what need they named and what happens next.