Why Marketing's Leads Die in Sales: Closing the MQL-SQL Gap
What is the difference between an MQL and an SQL? Writing handoff criteria, the rejection reason list, why response time beats lead quality, and a route back.
Marketing reports 200 leads at the end of the month. Sales says none of them were any good. Both sides believe they are right, neither can prove it, and the same argument restarts next month. The root cause is usually not lead quality — it is that the handoff process was never written down.
What is the difference between an MQL and an SQL?
An MQL is a record marketing believes has shown intent: downloaded content, attended a webinar, visited the pricing page. An SQL is a record sales has judged worth a conversation.
If those two definitions do not live in the same document, marketing generates leads against its own yardstick, sales filters against a different one, and the gap turns into conflict every month. The first step in fixing the handoff is writing both definitions in one sentence each.
Write the handoff criteria together
If marketing writes the criteria alone, sales will not accept them. If sales writes them alone, they become impossible to hit. Both sides need to sit down and answer four questions:
- Which company attributes are mandatory? Size, industry, country.
- Which behaviour is a sufficient signal? A demo request, or a content download?
- What role must the person hold? Decision maker, or is an influencer enough?
- When is a record never handed over? Students, competitors, job applicants, existing customers.
Those four answers should fit on one page. Criteria that run longer do not get applied.
The handoff has to be visible in the CRM
Even written criteria will not end the argument if the CRM does not track them. At minimum you need these fields:
- Date the record became an MQL
- The behaviour that triggered it
- Date it was handed to sales
- Date sales made first contact
- Accepted or rejected
- Rejection reason, from a closed list
Those six fields turn a months-long argument into data within two weeks.
The rejection reason list is the critical field
Sales saying "low quality" carries no information. Tie rejection to concrete causes: wrong company size, no budget, not a decision maker, bad timing, already a customer, could not reach them.
After a few weeks that list gives marketing a clear direction. If "could not reach them" dominates, the problem is response time, not lead quality. If "wrong company size" dominates, targeting needs adjusting. Those are entirely different jobs, and without a closed list you can never tell which one you have.
Response time matters more than quality
The later a handed-over lead is contacted, the lower the conversion. The same lead called two hours later performs markedly better than one called two days later.
So measure response time before you enter the lead-quality debate. On most teams a meaningful share of records labelled "bad leads" are simply records that were contacted late.
Build a route back
The biggest waste is a rejected lead going in the bin. A record sales rejects should return automatically to a marketing nurture list.
A record rejected for bad timing may be your best opportunity three months from now. If you do not capture it, you will find the same company again six months later from scratch and at a higher cost.
Agree on a service level
Both sides should make a written commitment. Marketing: how many MQLs per month, against which criteria. Sales: how many hours until a handed-over record is contacted, how many attempts, and when a decision is made.
Keep the numbers achievable rather than ambitious. A commitment that is missed costs more trust than no commitment at all.
One monthly meeting, one table
Once a month, both teams should spend half an hour looking at the same table. Four numbers are enough: MQLs handed over, acceptance rate, average response time, and deals won from MQLs.
The purpose of that meeting is not to assign blame but to update the criteria. An acceptance rate above 80 percent means the criteria are too narrow and marketing is leaving opportunities behind; below 40 percent means they are too loose.
Where to start
This week's job: take the last 50 handed-over leads and work out by hand how many were rejected and on what grounds. Even without a closed list, that one table shows for the first time which side needs to fix what.
Closync lets you track the MQL handoff process and rejection reasons on a single screen.
