The MQL to SQL handover is the most contested process in B2B revenue operations. Marketing teams celebrate hitting MQL targets; sales teams complain the leads are unqualified; CFOs ask why marketing spend isn’t producing pipeline. Each side has its own definition of what "qualified" means. Marketing scores leads on engagement (downloaded ebook, visited pricing page, attended webinar). Sales evaluates leads on intent and fit (right title, right company size, active project, timeline). The two definitions rarely align in practice, leading to constant friction at the handover point and 40–60% of MQLs that sales considers "unqualified."
The friction isn’t a personality problem or a process problem — it’s a definition problem. When marketing’s "MQL" and sales’s "qualified" use different criteria, the handover always produces conflict. The solution isn’t to argue about whose definition is correct; it’s to build a shared definition that both teams commit to AND that the CRM enforces operationally. Companies that successfully align these definitions see 25–45% improvements in SQL-to-deal conversion within 6 months — not by changing the leads, but by changing how they’re classified and handed off.
This guide is the MQL-to-SQL alignment blueprint we deploy for Dallas B2B clients. The 4-criteria framework that defines MQL and SQL identically across teams, the handover workflow including required fields and SLA, the feedback loop that lets sales correct miscategorized MQLs, and the case study of a Lewisville-based B2B services firm that rebuilt their definitions and lifted SQL-to-deal conversion 31% in 4 months.
MQL and SQL definitions should use the same 4 criteria, weighted differently. The 4 criteria: (1) Fit — ICP match (company size, industry, role), (2) Engagement — demonstrated interest (content downloads, page views, demo requests), (3) Intent — explicit purchase signals (pricing page visits, contact form submission, "looking to buy" language), (4) Authority — decision-maker or influencer role. MQL definition: Fit ≥ minimum threshold + Engagement ≥ medium + Authority ≥ influencer. SQL definition: Fit ≥ minimum + Engagement ≥ high + Intent ≥ medium + Authority ≥ decision-maker. Handover SLA: sales contacts SQL within 4 business hours; documented reason if rejected back to marketing. Feedback loop: weekly sync where sales reports actual lead quality vs MQL/SQL designations.
Why MQL-to-SQL Handover Usually Fails
Three structural problems create the constant marketing-vs-sales friction:
Problem 1: Different measurement incentives
Marketing is measured on MQL volume. Sales is measured on deals closed. These metrics diverge: marketing’s "more MQLs" isn’t the same as "more deals." When marketing teams hit their MQL target with mostly low-fit leads, they’ve technically succeeded by their KPI while creating sales waste. The KPI structure itself drives the misalignment.
Problem 2: Definition drift over time
Most B2B orgs defined MQL and SQL once, 3–5 years ago, and haven’t revisited the definitions. Meanwhile, ICP has shifted, marketing channels have changed, lead behaviors have evolved. The definitions become increasingly disconnected from current reality. Both teams operate with stale criteria and blame each other for the results.
Problem 3: No feedback loop
Sales doesn’t consistently report back which MQLs were actually qualified. Marketing has no signal about whether their definitions are working. The gap between "marketing’s MQL list" and "sales’ actually-qualified leads" grows invisibly. Without a feedback mechanism, both teams operate on assumptions instead of data.
The most common rebuild mistake: revenue leadership rewrites MQL/SQL definitions and pushes them down to marketing and sales. Definitions imposed don’t stick. Definitions co-created in a working session between marketing managers + sales managers + revops do. Spend 4 hours of joint working time defining criteria together; expect 12–18 months of operational alignment from that investment.
The 4-Criteria Framework
Criterion 1: Fit (ICP match)
How well does this lead match your defined ICP? Common fit dimensions:
- Company size (revenue, employee count) — matches ICP bucket
- Industry / vertical — in your target verticals
- Geographic location — in your service area / territory
- Technology stack — compatible with your solution
- Funding / financial health (for B2B SaaS) — can afford your tier
Fit is binary: in ICP or out of ICP. Borderline cases (e.g., slightly under your size threshold) typically score as low-fit MQL eligible, not SQL.
Criterion 2: Engagement
How much interest has the lead demonstrated through behavior? Measured by:
- Content consumption: blog posts read, ebooks downloaded, webinars attended
- Email engagement: opens, clicks, replies
- Website behavior: session count, page depth, pricing page visits, return visits
- Social engagement: LinkedIn follows, content shares, comments
Engagement levels typically map to: Low (1 touchpoint), Medium (2–3 touchpoints), High (4+ touchpoints across multiple channels and time periods).
Criterion 3: Intent
Explicit signals of buying interest, distinct from general engagement:
- Pricing page visits — 2+ visits to pricing in a short window
- Demo / trial request — explicit "show me the product" action
- Contact form / quiz completion — explicit "talk to me" action
- Competitor comparison page visits — evaluation mode
- RFP / procurement language in conversations — active buying process
- Calendar booking — scheduled call directly
Intent is what distinguishes "interested" from "actively buying." A lead can have high engagement but low intent (researcher learning the space) or low engagement but high intent (already-decided buyer ready to talk).
Criterion 4: Authority
Lead’s role in the buying decision:
- Decision-maker: primary buyer authority (often VP, Director, C-level)
- Influencer: part of decision team (manager, senior IC)
- End-user: would use the product but doesn’t decide
- Researcher: gathering info for someone else
For low-ACV products ($5K–$25K), end-users and influencers can be acceptable SQL. For high-ACV ($100K+), only decision-makers and senior influencers qualify.
MQL and SQL Definitions: Concrete Examples
MQL definition (example for $30K–$150K ACV B2B SaaS)
- Fit: Company 50–2,000 employees AND in target industries (B2B services, SaaS, financial)
- Engagement: 2+ marketing touchpoints in past 30 days (any combination of email click, content download, webinar, multiple page visits)
- Intent: any explicit interest signal (visited pricing OR product page OR demo request)
- Authority: Manager+ role OR self-identified as influencer
Result: marketing nurtures, sends targeted content, monitors for next-stage signals. Not yet handed to sales.
SQL definition (same business)
- Fit: Company 50–2,000 employees AND in target industries (same as MQL)
- Engagement: 4+ marketing touchpoints AND at least 1 was direct intent action
- Intent: Explicit "talk to sales" action — demo request, calendar booked, quiz completed with high score, OR multiple pricing page visits within 7 days
- Authority: Director+ role OR confirmed buying-team member
Result: sales contacted within 4 business hours, structured discovery process begins.
The Handover Workflow
Step 1: CRM enforces the definitions
The CRM (Salesforce, HubSpot, Pipedrive, etc.) should automatically calculate lead scores and tag leads as MQL or SQL based on the agreed criteria. Manual classification is the #1 source of definition drift — teams override the criteria over time without anyone noticing.
Step 2: Required handover fields
When an MQL becomes SQL, the CRM should auto-populate a "handover packet" with:
- Fit details (company size, industry, ICP fit score)
- Engagement history (timeline of touchpoints)
- Intent signals (specific actions that triggered SQL status)
- Authority info (role, decision-maker confidence)
- Suggested talking points / pain hypotheses (from content engaged with)
Sales rep opens the lead and has full context immediately. No "what does this person actually need?" mystery.
Step 3: SLA for first contact
SQLs require fast response. The longer the delay, the lower the conversion rate. Industry data:
- SQL contacted within 5 minutes: 21% conversion to opportunity
- SQL contacted within 1 hour: 14% conversion
- SQL contacted within 4 hours: 9% conversion
- SQL contacted within 24 hours: 4% conversion
- SQL contacted after 24+ hours: 1.5% conversion
SLA target: contact within 4 business hours. Best-in-class: contact within 15 minutes for high-score SQLs.
Step 4: Sales acceptance or rejection
Sales reviews the SQL. Two outcomes:
- Accept: SQL becomes Sales Accepted Lead (SAL), discovery process begins
- Reject: SQL goes back to marketing with DOCUMENTED REASON
The documented rejection reason is essential. Without it, marketing has no signal about why their SQLs are failing sales acceptance. Common rejection reasons: wrong company size, wrong role/authority, no actual intent (just curious), competitor researcher, internal employee, ICP misfit.
Sales teams hate documenting why they rejected a lead. They want to move on to the next opportunity. But the rejection reason is the most valuable feedback marketing receives. Without it, marketing keeps generating the same flawed SQLs. Make rejection documentation MANDATORY in CRM workflow — lead cannot be returned to marketing without selecting a reason from a structured dropdown. Takes 5 seconds; saves months of misaligned effort.
The Weekly Feedback Loop
Definitions don’t stay aligned automatically. They need active maintenance through structured feedback:
Weekly 30-minute sync
Standing meeting with marketing manager + sales manager + revops. Agenda:
- This week’s SQL count vs target
- SQL acceptance rate (% sales accepted; should be 70%+)
- Top rejection reasons (rolled up from CRM data)
- Specific lead reviews — 2–3 representative SQLs discussed in detail
- Definition adjustment proposals if rejection patterns emerge
Quarterly definition review
Every 90 days, formal review of MQL and SQL definitions:
- Are the criteria still matching what closes deals?
- What patterns are showing up in won-deal analysis that aren’t in current SQL definition?
- Are any criteria producing high false-positive rates?
- Does ICP need adjustment?
Definition updates require both marketing and sales leadership sign-off. Document changes; communicate to all team members.
Real Case: Lewisville B2B Services Firm Lifts SQL-to-Deal 31%
In November 2025 we worked with a Lewisville-based B2B services firm (financial advisory services, ACV $35K–$200K, ~$8M annual revenue). Their MQL-to-SQL friction was severe:
- Marketing was generating ~180 MQLs/month
- ~75 became SQLs (42%)
- Sales accepted ~38 of those as SAL (51%)
- ~9 became opportunities (24%)
- ~3 closed (33%)
- SQL-to-deal conversion: 4%
- Sales-marketing relationship described as "tense, blame-heavy"
Implementation across 4 months:
- Month 1: 4-hour joint working session with marketing + sales + revops. Documented current ICP. Defined fit/engagement/intent/authority criteria. Built new MQL and SQL definitions both teams committed to.
- Month 2: CRM rebuild (HubSpot). Lead scoring automated based on criteria. Required handover packet built. Mandatory rejection reason dropdown added.
- Month 3: SLA enforcement — auto-alerts when SQL not contacted within 4 hours. Weekly 30-min sync established. First feedback iterations.
- Month 4: Definition adjustments based on first 8 weeks of data. Tightened SQL intent criteria (added "scheduled call OR demo request" as required signal). Loosened MQL engagement criteria slightly to capture more pre-SQL pipeline.
Implementation Checklist
- Joint working session — 4 hours, marketing + sales + revops co-create definitions.
- Document the 4 criteria with specific thresholds for MQL and SQL.
- CRM automation — lead scoring enforces definitions; no manual override.
- Required handover packet — fit, engagement, intent, authority data auto-populated.
- SLA enforcement — 4-business-hour first contact, auto-alerts when missed.
- Mandatory rejection reason dropdown when sales returns SQL to marketing.
- Weekly 30-min sync with marketing + sales + revops to review data.
- Quarterly definition review with formal sign-off process for updates.
5 Common MQL-to-SQL Mistakes
- 1. Marketing defines MQL unilaterally. Sales never agreed, so they won’t respect it. Co-creation required.
- 2. No rejection feedback loop. Marketing has no signal about which SQLs are failing. Definitions never improve.
- 3. SLA without consequences. "4-hour SLA" with no monitoring becomes 48-hour reality. Auto-alerts needed.
- 4. Definitions never updated. ICP shifts, market shifts, definitions stay static. Quarterly review essential.
- 5. Lead volume as success metric. Quantity over quality. Switch to SQL-to-deal conversion or revenue-per-MQL.
For Dallas B2B companies, rebuilding MQL/SQL alignment typically delivers 25–50% lift in SQL-to-deal conversion within 6 months without changing marketing spend. The investment is mostly time (4–6 weeks of process work, no significant tool cost beyond existing CRM). Pair with the interactive quiz framework in interactive quizzes and the lead scoring patterns in lead scoring CRM setup for complete lead qualification strategy.
Frequently Asked Questions
How is "Sales Accepted Lead" (SAL) different from SQL?
SQL is marketing’s determination that a lead meets qualifying criteria. SAL is sales’ ACTIVE acceptance after reviewing the SQL. The gap matters: a lead can be a valid SQL by criteria but unfit for current sales focus (e.g., wrong segment for current quarter’s priority). SAL forces explicit sales acceptance. Some orgs combine SQL/SAL into a single status; others keep them distinct. The distinction is most useful when sales has variable capacity or shifting priorities.
What about leads that come in already sales-ready (skip MQL)?
They exist. A senior buyer at a target account hits "Schedule a Demo" without any marketing touchpoints. They skip MQL entirely and become direct SQL. The framework should accommodate this — "direct SQL" path with same criteria thresholds but bypassing the engagement requirement. About 15–25% of B2B SQLs in our Dallas client data come through direct paths (referrals, demo requests from cold visitors, sales outbound prospects responding). Don’t force them through artificial MQL nurture.
How do MQL/SQL definitions work with account-based marketing (ABM)?
ABM operates differently. Target accounts are pre-qualified at the account level (not contact level). For ABM: any contact at a target account who engages becomes an MQL automatically (skipping individual fit check). SQL still requires authority + intent at the contact level. The fit dimension shifts from "is this person a fit" to "is anyone at this account a fit." Account-level scoring + contact-level qualification is the typical pattern for ABM-heavy orgs.
Should marketing have visibility into closed deals?
Yes, mandatory. The closed-loop reporting from "MQL source" through "closed deal" is essential for marketing optimization. Without it, marketing is optimizing leading indicators (MQLs) without knowing if they translate to revenue. Most CRMs (Salesforce, HubSpot, Pipedrive) support this natively. Marketing should see: deals closed by lead source, deals closed by content engagement pattern, deals closed by campaign. This is how marketing decides where to invest budget.
How does this interact with product-led growth (PLG) motions?
PLG complicates the MQL/SQL framework. Product usage signals (active users, feature adoption, expansion potential) become qualification criteria alongside traditional marketing engagement. Some PLG orgs use "Product Qualified Lead" (PQL) as additional stage between MQL and SQL. PQL = user actively using product who shows expansion or upgrade potential. Sales contacts PQLs differently than traditional SQLs (expansion conversation vs new-business conversation). For hybrid sales+PLG motions, document how PQL fits into the handover workflow explicitly.
Want us to align your MQL/SQL definitions?
We’ll facilitate the joint working session, design the criteria, configure your CRM scoring, build the handover workflow, and establish the feedback loop. Free for B2B companies with $50K+ ACV and 100+ monthly MQLs.
Get an MQL/SQL Alignment Audit Explore CRO Services