MQL vs SQL for Outbound: How to Qualify Cold Email Replies

A reply to a cold email is not a deal — it is a signal that needs classification before anyone acts on it. Teams that treat every positive reply as a hot lead burn their closers' time on tire-kickers, while teams that nurture everything lose buyers who were ready to talk this week. This guide gives you a working MQL vs SQL framework built specifically for outbound replies, not inbound form fills.

Why inbound MQL/SQL definitions break on outbound replies

The classic definitions come from inbound marketing: an MQL is someone who engaged with your content enough to cross a scoring threshold, and an SQL is someone sales has vetted as worth a real conversation. That model assumes the lead came to you and left a trail of behavior — page visits, downloads, webinar signups — that you can score.

Outbound flips the situation. You picked the company because it matched your ideal customer profile, you found the decision-maker, and you emailed them directly. Fit is largely established before the first message goes out. What you do not know is intent — and a reply is the first real intent signal you get. So for outbound, the MQL/SQL split is less about scoring accumulated behavior and more about reading one or two replies correctly.

This matters operationally. If you dump every reply into the same pipeline stage marked qualified, your account executives will open the CRM to find a mix of people asking to be removed, people asking a vague question, and people asking for pricing. All three need completely different next steps, and mixing them destroys trust in the pipeline data.

Working definitions for outbound teams

Here is a set of definitions that holds up in address-based B2B outreach, where every prospect is a named person at a company you deliberately targeted.

An outbound MQL is a reply that confirms fit and shows problem-level interest, but not purchase-level intent. The person acknowledges the pain you described, asks a clarifying question, requests materials, or says the timing is wrong but the topic is relevant. They are worth continued conversation, not yet worth an AE's calendar slot.

An outbound SQL is a reply that shows purchase-level intent from a person with real influence: they ask about pricing, implementation, comparison with a competitor, or directly request a call or demo. Alternatively, a reply that forwards you to the actual buyer with a warm note also qualifies — the intro itself is the intent signal.

Everything else — unsubscribes, polite declines, out-of-office chains, wrong-person replies with no forward — is neither. It gets processed (stop list, contact correction, re-target to another role) but never enters the qualified pipeline.

• MQL signals: asks what exactly you do, requests a case study or one-pager, says come back next quarter, engages with a follow-up after silence
• SQL signals: asks for pricing or a call, mentions an active project or budget cycle, introduces a colleague who owns the decision, asks how you differ from a named competitor
• Neither: automated replies, remove-me requests, wrong person with no referral, one-word negatives

The two-axis check: fit and intent

Before labeling a reply, run it through two quick questions. First, fit: does the company still match your ICP now that you have more information? Cold lists always contain a percentage of mismatches — the company turned out to be too small, in the wrong segment, or a services shop when you sell to product companies. A high-intent reply from a bad-fit company is not an SQL; it is a polite no you have not sent yet.

Second, intent: is the person asking about the problem or about the purchase? Problem-level questions (how does this work, who is this for, what results do others get) mark an MQL. Purchase-level questions (what does it cost, how long is onboarding, can we start with a pilot) mark an SQL.

Also check the person, not just the company. In B2B outreach you often reach an influencer rather than the economic buyer. A strongly interested analyst is an MQL until a budget owner enters the thread. Do not inflate your SQL count with enthusiastic people who cannot sign anything — track the role explicitly in the contact record.

Realistic conversion benchmarks

Numbers vary by market and offer, but healthy ranges for targeted B2B cold email look like this: a reply rate of 3–8% on a well-personalized campaign to a clean list, of which roughly 30–50% of replies are positive or neutral rather than declines. Of those positive replies, expect 10–30% to qualify as SQL on the first exchange; the rest start as MQL.

The MQL pool is where patient teams win. With structured follow-up — a relevant case study, a check-in tied to their stated timeline, a note when something changes in their industry — a meaningful share of outbound MQLs convert to SQL within one to three months. Teams that discard everything that did not book a demo immediately are typically leaving half their pipeline on the table.

Watch one ratio closely: SQLs accepted by sales versus SQLs handed over. If AEs bounce back more than about 20% of your SQLs as unqualified, your criteria have drifted and the SDR-to-AE handoff needs recalibration before anyone argues about individual leads.

Routing rules: what happens in the CRM after classification

Classification is useless without routing. Every label must trigger a concrete, time-bound action in your CRM, ideally automatically. In LDM, replies land in the dialogs inbox linked to the contact and campaign, so the classification happens where the conversation lives — but the logic applies to any stack.

The core rules: an SQL creates a deal in the sales pipeline immediately and notifies the owner; speed matters, because reply-driven interest decays within days. An MQL stays with the SDR, gets a follow-up task with a date, and optionally enters a light nurture sequence. A wrong-person reply triggers contact research on the same account rather than closing it. A decline or unsubscribe goes to the stop list so no future campaign touches that address again — this is both hygiene and legal compliance under GDPR and CAN-SPAM.

Log the classification itself as a field, not just as a pipeline stage. When you can report on how many replies of each class a campaign generated, you can finally compare campaigns by pipeline contribution instead of raw reply count — and that changes which segments and messages you invest in.

• SQL: create deal, assign AE, first touch within 4–24 business hours
• MQL: SDR keeps ownership, scheduled follow-up task, add to nurture track
• Wrong person, warm referral: create new contact, restart thread with context
• Wrong person, no referral: research account for correct decision-maker
• Decline or unsubscribe: stop list, close contact, exclude from all future sends

Common mistakes that poison the pipeline

The most expensive mistake is labeling by enthusiasm instead of evidence. A long friendly reply feels like an SQL but often contains zero purchase signals; a curt send pricing feels cold but is the strongest intent you will get in writing. Train the team to classify on signals, not tone.

The second mistake is letting MQLs rot. An outbound MQL without a dated next action is a lead you already paid for and then abandoned. Every MQL should carry a follow-up date, and your weekly pipeline review should surface MQLs whose date passed.

Third, skipping disqualification records. When a company turns out to be a bad fit, record why — segment, size, tech stack, whatever the reason. That data feeds back into list building and stops you from re-targeting the same bad-fit profile in the next campaign.

Finally, do not let the definitions live in one person's head. Write the MQL and SQL criteria into a one-page document that both SDRs and AEs sign off on, and revisit it quarterly. Most handoff friction is not a people problem; it is two teams using the same words for different things.

A minimal checklist to implement this week

You do not need a scoring model to start — you need agreed definitions and routing rules. Here is the shortest path to a working system.

If you run outreach through LDM, most of this maps onto built-in mechanics: reply classification in dialogs, automatic lead creation from a reply, pipeline stages with automation rules, and stop-list enforcement across all campaigns. If you use another stack, the checklist still applies — the tooling just does less of the work for you.

• Write one-line definitions of outbound MQL and SQL and get sales to approve them
• Define the five routing rules above as CRM automations or explicit SDR playbook steps
• Add a reply-class field to your contact or deal object for reporting
• Set an SLA: SQL first touch within one business day, MQL follow-up within one week
• Review the AE rejection rate on handed-over SQLs monthly and adjust criteria
• Audit MQLs with overdue follow-ups every week

FAQ