Every pipeline has a seam where leads go quiet, and it is rarely the one anyone watches. Teams pour attention into the top of the funnel and into the close. The middle, where a lead crosses from marketing to sales, gets treated as plumbing. It is not plumbing. It is the seam where the most leads are lost, and the reason is not the definitions people argue about. It is what those definitions are secretly deciding.
Start with the two labels clear, because the rest of this depends on it.
A marketing qualified lead, an MQL, is a contact who has done enough to suggest real interest. They downloaded the guide, came back three times, asked what a demo costs. Marketing has looked at that behavior and decided the contact is warm enough to hand over. A sales qualified lead, an SQL, is a contact a salesperson has looked at and judged worth active pursuit. Right problem, right size, right timing, a reason to pick up the phone this week.
So the MQL is a signal and the SQL is a commitment. The MQL says someone is paying attention. The SQL says a person on the sales team is willing to spend hours they cannot get back. The whole pipeline runs on turning the first into the second, and that single conversion is where it breaks.
The leak is not that leads vanish. It is that they stall in the gap between the two labels, and nobody notices they stalled.
Here is the pattern. Marketing marks a batch of contacts as MQLs and passes them to sales. Sales looks at the batch, decides most are not worth a call, and works the few that are. The rest sit. They are not rejected on any record and they are not pursued. They are set down. Marketing counts them as delivered and moves to next month. Sales counts them as noise and forgets them. The lead itself, a real person who raised a hand, hears nothing back and quietly moves on to whoever answered.
Multiply that by every week of the year. The pipeline is leaking its most interested prospects out of a hole neither team is looking at, because each team believes the other is holding the rope. That is the shape of the problem. Now the question is why it keeps happening, because everyone involved is competent and trying.
Ask why the batch stalled and you get a familiar fight. Marketing says the leads were good and sales did not work them. Sales says the leads were weak and marketing padded the numbers to hit a target. It sounds like a disagreement about lead quality. It is not.
It is a disagreement about who owns the risk of a bad lead. Every contact handed across the seam carries a chance it is a waste of time. Somebody eats that cost. When marketing loosens the MQL bar to pass more leads, it pushes that risk onto sales, whose hours now get spent sorting through contacts that will not close. When sales tightens what it will accept, it pushes the risk back onto marketing, whose work now gets ignored and whose numbers now look worse. The fight about quality is a fight about which team absorbs the cost of being wrong.
Until you name it that way, every meeting about lead quality is a negotiation with the real subject hidden. People argue about the leads because it is easier than saying the true thing, which is that neither team wants to be the one holding the risk when a lead turns out to be a dud.
The two teams pull in opposite directions because they are paid to.
Marketing is measured on volume. More leads, more MQLs, a bigger number at the end of the month. Every incentive pushes toward a generous definition, because a generous definition produces a bigger count and a better report. Sales is measured on closed revenue against a fixed number of selling hours. Every incentive pushes toward a strict filter, because an hour spent on a lead that will not close is an hour stolen from one that might. A salesperson who chases loose leads misses quota, so a salesperson learns to distrust the batch.
Neither instinct is wrong. Marketing is protecting reach. Sales is protecting its calendar. But a loose definition and a strict filter aimed straight at each other guarantee a pile of leads in the middle that marketing counts as sent and sales counts as unqualified. That pile is the leak, and its size is exactly the distance between the two definitions. Close that distance and you close the leak. Which is why the definitions, the thing everyone treats as paperwork, turn out to be the whole game.
The leak between marketing and sales costs you prospects who already raised a hand. We run the qualification and the handoff for you: a clear bar, a clock on every lead, and qualified meetings booked into your calendar. One call is enough to see if it fits.
The definitions are not administrative housekeeping. They are where the two teams decide, in advance, who is accountable for what.
A definition of an MQL is really a promise. Marketing is saying, if a lead clears this bar, we stand behind it as worth a call. A definition of an SQL is the matching promise from sales. If a lead clears this bar, we will work it, and if we let it rot, that is on us. When both definitions are vague, neither promise is real, and the risk floats free in the gap, which is exactly where leads stall and die.
When both are specific and shared, the risk has an owner at every step. A lead that meets the MQL bar and then gets ignored is now a sales failure, on the record, with a name attached. A lead that cleared the bar but never should have is now a marketing failure, on the record. The leak closes not because anyone tries harder or cares more, but because the ambiguity that let leads disappear without blame is gone. You cannot quietly drop a lead when dropping it lands on your name.
A definition that actually holds has three properties, and most definitions in use have none of them.
It is specific enough that two people would sort the same lead the same way. Not warm, not engaged, not a good fit, which mean nothing, but named actions and named facts. Requested pricing, company over fifty staff, buying this quarter, has the budget line. If two reps could look at the same contact and disagree on whether it qualifies, the definition is not done. Second, it is agreed by both teams rather than handed down by one, because a bar that sales did not sign is a bar that sales will quietly ignore, and then you are back to a pile in the middle.
Third, and this is the part everyone skips, it carries a rule for what happens to a lead that does not clear it. Not silence, because silence is the exact place leads die. A route back: returned to marketing for more nurture, with a reason attached. The reason is the piece that matters most, because a reason is feedback, and feedback is how the definition gets sharper next quarter instead of staying a standing source of blame.
Picture the actual moment a lead crosses the seam. It clears the MQL bar on a Tuesday. In a leaking pipeline it drops into a shared queue, sits over the weekend, and by the time a rep glances at it on Monday the person has already booked a call with a competitor who answered the same afternoon.
Now picture the seam built as a real handoff. The lead clears the bar and lands with a named owner, not a queue, and a clock starts. The rep either accepts it and works it, or returns it with a reason, inside a set window. Nothing is allowed to simply sit. That one rule, every crossed lead gets accepted or returned within a fixed time, does more to stop the leak than any wording change to the definitions, because it removes the move that kills most leads, which is the move to do nothing and let the ambiguity swallow them.
Speed is not a nicety here. The lead that raised its hand on Tuesday is comparing you to whoever called on Tuesday. A perfect definition with no clock still loses to a competitor who is merely fast.
Get all of this right and one problem survives. Two teams can agree on a definition, staff the handoff, put a clock on it, and still watch good leads slip through, because agreeing on a definition on paper is not the same as scoring leads the same way under pressure on a Tuesday afternoon.
That is the next question, and it is the one most teams reach last. Not what should an MQL be, but how do you turn the definition into a repeatable score that anyone can apply and no one can argue with mid-shift. That is the point where qualification stops being a truce between two teams and starts being a system that runs the same whether the people running it are having a good day or a bad one. It is worth building before the next leak, not in the meeting after it.
Lead Qualification Framework
Turning the definition into a repeatable score anyone can apply.
How to Qualify Leads
The questions that sort a real buyer from a warm click.
B2B Sales Funnel Stages
Where the MQL to SQL handoff sits in the wider funnel.
How to Set Up a Sales Pipeline
Building the seam so leads cannot quietly fall through it.
An MQL, a marketing qualified lead, is a contact whose behavior suggests real interest, judged by marketing as warm enough to hand to sales. An SQL, a sales qualified lead, is a contact a salesperson has judged worth active pursuit right now. The MQL is a signal. The SQL is a commitment of selling time.
Because the gap between a loose MQL definition and a strict sales filter has no owner. Leads that marketing counts as sent and sales counts as too weak to call end up in the middle, not rejected and not pursued. Nobody is accountable for them, so they sit until the person gives up and buys elsewhere.
Both teams, together. A bar that marketing sets alone will be too loose for sales to trust, and a bar sales sets alone will be too strict for marketing to hit. The point of the definition is a shared agreement on who is accountable when a lead turns out to be good or bad, so both sides have to sign it.
Make the definitions specific enough that two people sort the same lead the same way, agree them across both teams, and add one rule with a clock: every lead that crosses gets accepted or returned with a reason inside a set window. The clock matters as much as the definition, because most leaks are just leads left to sit.
Only in the marketing sense. An MQL has shown enough interest to be worth a look, but it has not been checked against fit, budget, or timing the way sales checks an SQL. Treating every MQL as ready to buy is how sales teams lose trust in the handoff and start ignoring the batch.
A fortnightly note on one shift in global business and what it means for your revenue. One idea, one move, no filler. Leave any time.
One call is enough to work out whether outsourced sales is the right fit for where your business is right now.