01Two Lists in the Same Company
Before the acronyms: two lists that never match
The Short Version
Marketing has a list of inquiries it says it delivered. Sales has a list of inquiries it says it received. The two lists never have the same number of rows, and nobody has ever put them side by side.
It shows up in the monthly meeting like this. Marketing reports 62 leads sent. The sales manager says they got about 30 that were worth anything. Both are looking at real numbers from the same CRM. The gap is not a lie — it is that "sent" and "received" were never defined as events with a timestamp and a name attached. Marketing counts the moment it changed a field. Sales counts the moment a rep decided the lead was worth their afternoon. Between those two moments the lead sits in a place with no owner, and that place is where the argument comes from.
The two names for those two lists are MQL and SQL. Naming them is useful only because it makes the transfer between them a thing that can be timed, counted and assigned. Adopting the acronyms without defining the transfer event changes nothing: you get the same argument with better vocabulary.
02What Each Label Means in Practice
What each label means on a plant floor
Three labels, and the middle one is the one most manufacturing operations skip — which is exactly why the handoff has no audit trail:
MQL
Marketing Says It Is Worth a Call
The inquiry meets the written criterion on paper: real company, plausible application, volume in range, a deadline. Marketing owns it, and marketing is accountable if the facts on the form turn out to be wrong. It is a hypothesis, not a commitment — nobody has spoken to this person yet. In a plant this is the engineer who downloaded the load table and filled in the four fields.
Marketing Owns
SAL
A Named Rep Accepted It
The step almost nobody implements, and the one that ends the argument. A named rep looked at the lead and clicked accept, or refused it with a written reason, within 2 business hours. It is a receipt. Without this event there is no way to prove whether a lead was delivered or dropped, and the monthly meeting stays a matter of opinion forever.
The Missing Step
SQL
Talked To and Confirmed
The rep spoke to the person and confirmed by voice what the form claimed: the application is real, the volume holds, the deadline exists, and this person can move the purchase forward. From here it is a pipeline opportunity with a value and a date. Sales owns it and sales is accountable for the outcome. A lead that was never called is not an SQL, no matter what the score says.
Sales Owns
Note what is not in any of the three definitions: a points total. Scoring is a tool for prioritising the MQL queue, never for granting the SQL label — a machine cannot confirm by voice that the volume holds. The scoring mechanics themselves are covered at lead scoring in RD Station for manufacturers. The written criterion the MQL label is checked against is at how to define a qualified lead in manufacturing.
03The Five Breaking Points
The five points where the transfer breaks
All five are observable in the CRM export in a single afternoon. Find yours before changing the funnel stages:
Diagnosing the Break
Break 1: No Named Owner
The MQL is routed to a shared inbox or to "sales team". Three people see it and each assumes another one took it. Signature in the export: leads with the owner field empty or set to a group. This is the most common break and the cheapest to fix.
→
Break 2: No Acceptance Event
There is no SAL step, so nobody ever signs for the lead. Marketing counts delivery at the moment it changed the field; sales counts it when someone got round to it. Signature: the two departments report different totals for the same month and both can prove theirs.
→
Break 3: Silent Refusal
The rep decides the lead is not worth it and simply does not act. No refusal, no reason, no return. Marketing never learns what to stop generating. Signature: MQLs that stay in the same stage for more than 14 days with no activity logged against them.
Breaks 4 and 5:
Break 4 — the machine promotes the label. An automation moves the lead to SQL when the score crosses a threshold, so the pipeline fills with opportunities nobody has ever spoken to, and the forecast becomes fiction. Signature: SQLs with no call or e-mail logged. Break 5 — a rep skips the queue. Whoever prospected the account themselves marks their own lead as SQL directly, so inbound MQLs go to the back of the line and the conversion rate of the marketing channel looks worse than it is. Signature: SQLs created with no prior MQL record.
A lead sitting between two departments for six days is not being qualified. It is being stored. The buyer, meanwhile, is on the phone with whoever answered first.
04How to Fix the Handoff
Four mechanics that fix the handoff
None of the four requires new software. All four are configuration in the CRM you already pay for, plus one agreement written on one page:
The Four Mechanics
One name, one clock, one written refusal, one number both departments are measured by.
One — every MQL gets a named owner at the moment it is created, by round robin or by territory, never a group. Two — a 2-business-hour clock on the acceptance, with automatic escalation to the manager when it expires; the escalation is what makes the clock real. Three — refusal requires a reason from a closed list of at most five options, and the weekly count by reason goes to marketing in a single message, not a report nobody opens. Four — both departments are measured by the same number: SQLs accepted and worked, not leads sent and not deals closed. As long as marketing is paid on volume sent and sales on deals closed, the handoff is nobody's metric and it will keep breaking.
What to expect once the four are running: the MQL to SQL conversion rate becomes visible for the first time, and in a manufacturing operation with a written criterion it settles between 20 and 40 percent. Below 15 percent the MQL criterion is too loose or the leads are arriving cold. Above 60 percent the criterion is so tight that marketing is only forwarding leads it is certain about, which means demand is being thrown away upstream and never counted.
The two-department blame loop that surrounds all of this — and how to end it without a meeting — is at marketing blames sales, sales blames the lead. If the MQLs themselves are arriving wrong in the first place, start at why marketing generates unqualified leads.
05FAQ
FAQ
What is the difference between MQL and SQL in manufacturing? +
An MQL is an inquiry that meets the written criterion on paper and that marketing owns — nobody has spoken to the person yet. An SQL is one a named rep has called and confirmed by voice: the application is real, the volume holds, the deadline exists. The difference is accountability for the next step, not a points total.
What is a SAL and do I need that stage? +
SAL is the receipt: a named rep accepted or refused the MQL within a deadline. You need it precisely because without it nobody can prove whether a lead was worked or dropped, which is what keeps the monthly meeting stuck on opinion. It is one extra field and one clock in the CRM, not a new process.
Who changes a lead from MQL to SQL? +
The rep who owns it, and only after speaking to the person. Marketing can create and prioritise MQLs but must never be able to write the SQL label, because the label means "I confirmed this by voice and I am accountable for it". If marketing can set it, the pipeline fills with opportunities nobody has talked to and the forecast stops being usable.
Can lead scoring promote an MQL to SQL on its own? +
No. A score measures observed behaviour — pages visited, e-mails opened, material downloaded — and none of that confirms that the volume is real or that this person can move a purchase forward. Use the score to sort the MQL queue so the rep calls the most promising one first. Promotion to SQL always requires a human conversation.
What percentage of MQLs should become SQL in a manufacturing company? +
Between 20 and 40 percent with a written criterion and a working handoff. Below 15 percent the MQL criterion is too loose, or the leads are being called too late and arriving cold. Above 60 percent marketing is only forwarding what it is certain about, which means demand is being discarded upstream and never counted — a tighter funnel that hides lost revenue.
What should happen when a rep refuses an MQL? +
The refusal is legitimate, but it must be explicit and carry a reason from a closed list — never a silent non-action. The refused lead goes back to marketing, which either enriches the two missing facts and resubmits it once, or files it against the reason count. Refusals with no written reason are the single biggest cause of a criterion that never improves.
Do I need MQL and SQL if my sales team is only two people? +
You need the transfer event, not the vocabulary. With two reps, one field with three values — new, accepted, confirmed — plus a name and a timestamp does the whole job. What you must not skip at any team size is the named owner and the written refusal reason. The acronyms are optional; the receipt is not.
How do I set up MQL and SQL as stages in the CRM? +
Do not make them pipeline stages — make them a status field on the lead, separate from the deal stages. Pipeline stages should describe the negotiation (contact, quotation sent, in approval, closed); MQL and SQL describe whose responsibility the lead is. Mixing the two is why reports stop making sense after the third month.
Want to see where your handoff is losing leads?
We pull your CRM export, look for the five signatures described above and show you which break is yours — with the count of leads sitting between the two departments right now.
