MQL vs SQL: One Card for the B2B Handoff
Or: stop calling every interested click a sales-ready lead.
Source: /Users/nitishchauhan/Downloads/gemini-code-1784786284904.html
Phase: final
Status: draft
Index: Index - B2B Marketing Funnel MQL vs SQL Card
Trajectory: Trajectory - Inner Map
Pipeline: CONSTITUTION - Publishable Asset Pipeline
Master: 00 - Master Index
Slug folder: Work/b2b-marketing-funnel-mql-vs-sql-card/
How this one actually started
It started with a vocabulary failure that wastes pipeline meetings.
Marketing says “we have leads.” Sales says “these are not leads.” Both are often right, because they are not talking about the same object. One side is counting early interest. The other side is waiting for buy intent. The funnel jargon gets longer. The handoff stays muddy.
So the useful move was not another multi-slide GTM deck. It was a one-screen teaching card: MQL at the top, SQL at the bottom, and one bridge in the middle called lead scoring and qualification.
What follows freezes that card as a short authority piece. The visual is the spine. The prose only names what the card already forces you to see.
The distinction that pays rent
If you only keep one sentence:
MQL is marketing-ready interest. SQL is sales-ready intent after scoring.
Everything else is staging and signals.
1. Top of funnel: MQL
TOFU (Awareness)
MQL means Marketing Qualified Lead.
From the card:
- Downloads a whitepaper.
- Views the blog.
- Not ready to buy yet.
That last line is the point. Engagement is real. Purchase readiness is not. Marketing owns the relationship here: educate, nurture, score, and refuse to dump every form fill on a closer.
If a team calls every whitepaper download “pipeline,” the MQL label has already failed.
2. The bridge: lead scoring and qualification
Between the two stages the card prints one transition, not five:
↓ Lead Scoring & Qualification ↓
This is where marketing and sales either agree on rules or invent silent resentment.
Scoring answers a practical question:
- Which interest signals are strong enough to become a conversation with sales?
- Which still need nurture?
The card does not invent a points model. It forces the architecture: interest is not automatic eligibility for sales time. Qualification is the gate, not a courtesy label.
3. Bottom of funnel: SQL
BOFU (Conversion)
SQL means Sales Qualified Lead.
From the card:
- Requests a demo.
- High buy intent.
- Passed directly to the sales team.
SQL is not “a better MQL by vibes.” It is a lead that cleared the shared criteria and now belongs in a sales motion: discovery, demo, proposal, close.
If demo requests sit in a marketing nurture drip for two weeks, the SQL label has failed the other way.
4. Content ops pairing (what the card implies)
The teaching graphic is also a content map in disguise.
| Stage | Typical asset / signal | Job of content |
|---|---|---|
| MQL / TOFU | Blog, whitepaper, light education | Create and capture interest without forcing a buy conversation |
| Bridge | Scoring rules, form fields, behavior thresholds | Decide when interest is ready for hand-off |
| SQL / BOFU | Demo request, high-intent CTA, sales-ready page | Convert intent into a sales-owned conversation |
Use this when planning a content calendar:
- Which pieces are built to create MQLs?
- Which pieces or CTAs are built to create SQLs?
- Where is the scoring rule written so marketing does not ship noise and sales does not starve?
That pairing is how the card stays useful outside a design file.
5. How to use the card
- Teach the handoff, not the whole funnel. Awareness → scoring → sales-ready is enough for most first explanations.
- Anchor with behaviors. Whitepaper/blog vs demo request. Abstract stage names alone invite debate theater.
- Write the bridge down. If scoring is “we’ll know it when we see it,” you do not have a funnel. You have a mood.
- Seed a larger Visual Wiki later. This card is a primitive. Fuller maps (channels, nurture loops, attribution) can hang off it without replacing it.
Close
The card is small on purpose.
It does not claim to be a full B2B strategy. It freezes the one distinction that keeps pipeline language honest: interest is not intent, and the path between them has a name - lead scoring and qualification.
Keep the navy/orange one-screen layout as the teaching surface. Keep this article as the verbal twin. When someone blurs MQL and SQL in a meeting, you do not need a textbook. You need this handoff, said once, clearly.
Authority teaching card. Provenance: Gemini HTML export → Gemma 14 Index → trajectory map → Final.