A marketing qualified lead (MQL) is a prospect who has shown enough buying intent — through behavior, fit, or both — to justify sales follow-up, but not enough to be a confirmed opportunity. The practical takeaway: most MQL definitions fail because they are written once, never tested against revenue data, and never signed off by sales. The companies that fix this see 40–60% higher lead-to-close rates within two quarters.

Most MQL Definitions Are Marketing’s Opinion, Not a Sales Agreement

Marketing writes the definition. Sales ignores it. Leads pile up, conversion rates crater, and both teams blame each other. This is the default state at roughly 70% of B2B companies with fewer than 200 employees. The root cause is not bad data or bad tools. It is the absence of a signed, numeric agreement between marketing and sales on what “qualified” actually means. Without that agreement, every MQL is a guess.

A definition that survives is one sales helped write, one that is tied to a specific lead-to-opportunity conversion rate target, and one that has a review date on the calendar. Everything else is a placeholder.

The MQL Definition Has Two Components: Fit and Intent

Fit answers: is this person in a company that could actually buy from us? Intent answers: has this person done something that signals they want to? You need both. Either alone produces garbage leads.

Fit signals (firmographic and demographic):

• Company size (revenue band or headcount range your ICP maps to)
• Industry vertical
• Job title or seniority level of the contact
• Geography, if your coverage model requires it
• Technology stack, if your product has integration dependencies

Intent signals (behavioral):

• Pricing page visit (high weight — assign 25–30 points)
• Demo or trial request (often auto-converts to SQL, skip MQL entirely)
• Repeated content downloads (3+ assets in 14 days)
• Webinar attendance, not just registration
• Email click-through on a bottom-of-funnel sequence
• Third-party intent data showing category research

A contact who hits both thresholds — fit score above 40, behavioral score above 30, for example — becomes an MQL. A contact who scores high on fit but has zero behavior is a cold name. A contact who downloads everything but works at a company with 8 employees and no budget is a content consumer, not a buyer. Neither gets passed to sales.

MQL vs SQL: The Line Is a Handoff Protocol, Not a Fuzzy Feeling

The MQL vs SQL distinction breaks down when it lives only in a slide deck. Make it operational.

An MQL is marketing’s output: the lead meets threshold criteria and is ready for sales review. A sales qualified lead (SQL) is sales’ acceptance: a rep has touched the lead, confirmed fit and intent in a real conversation, and agreed to work it as an active opportunity. The moment between MQL and SQL is the handoff. That handoff needs a defined SLA: how fast does sales respond, what counts as a valid “worked” attempt, and what happens if they reject the lead.

A clean MQL-to-SQL SLA covers four things:

1. Response time. Sales contacts every MQL within a defined window. Research consistently shows leads contacted within 5 minutes convert at 6× the rate of leads contacted after 30 minutes. Pick a number. Write it down. Measure it weekly.
2. Attempt definition. What counts as a “worked” lead? One email does not count. Three touches across two channels in five business days is a reasonable minimum.
3. Rejection criteria. Sales can reject an MQL, but only for documented reasons: wrong title, company already in a deal, out of territory, confirmed non-buyer. Vague rejections (“not a fit”) do not count and should trigger a joint review.
4. Feedback loop cadence. Marketing and sales review MQL-to-SQL conversion rate monthly. If it drops below the agreed floor (example: 25%), both teams investigate together before the next campaign ships.

The MQL definition is not a marketing document. It is a contract between two revenue teams. If sales did not sign it, it does not exist.

A Lead Scoring Framework That Does Not Require a Data Science Team

Most lead scoring frameworks overcomplicate the model and under-invest in the data hygiene that makes the model work. Start simple. Run it for 90 days. Then add complexity based on what the data actually shows.

Step 1: Set your MQL threshold. Pick a total score number (100 is common) that a contact must reach before getting flagged. Split it: 50 points maximum from fit, 50 points maximum from behavior.

Step 2: Weight fit attributes. Assign points to each firmographic and demographic attribute. Example: target industry = 20 points, right title level = 15 points, target company size = 15 points. Cap at 50. Contacts outside your ICP cannot score past 25 regardless of behavior.

Step 3: Weight behavioral attributes. Assign points to actions. Example: pricing page view = 25 points, attended a live demo webinar = 20 points, downloaded a bottom-funnel asset = 15 points, opened 3+ emails in 7 days = 10 points. Apply time decay: behavioral scores drop 20% every 30 days of inactivity.

Step 4: Apply negative scoring. Student email domain = minus 30 points. Competitor domain = minus 50 points (or route to a separate track). Job title indicates no budget authority = minus 20 points.

Step 5: Test and calibrate. After 90 days, pull every MQL from the cohort. What percentage became SQLs? What percentage closed? Work backward. If a specific behavior (say, pricing page visit) appeared in 80% of closed deals but only 30% of MQLs, weight it higher. This is not a one-time build. It is a quarterly calibration.

Our MQL-to-revenue AI demand engine runs this calibration continuously, using closed-won data to auto-adjust weights without a manual audit every quarter.

Five Mistakes That Kill MQL Definitions Within 60 Days

1. Volume optimization instead of quality optimization. If your MQL goal is a raw number (“500 MQLs per month”), you will hit it by lowering the threshold. You will also flood sales with junk leads and destroy trust in the entire system. Set a quality floor first — minimum MQL-to-SQL conversion rate — then let volume be the output, not the input.
2. No time decay on behavioral signals. A contact who visited your pricing page 11 months ago and has done nothing since is not a warm lead. Behavioral scores must decay. If your CRM or MAP does not support time decay natively, build a workaround. No decay = stale leads treated as hot ones.
3. Treating all content equally. A top-of-funnel blog visit and a bottom-of-funnel ROI calculator completion are not the same signal. Scoring them the same inflates scores for tire-kickers and understates urgency for real buyers.
4. Skipping the sales SLA conversation. Marketing publishes the definition, assumes sales is aligned, and discovers six months later that reps have been ignoring MQL alerts entirely. Get the SLA on paper before you launch the model, not after.
5. No audit trail on rejected leads. If sales can reject without documentation, you lose the data you need to improve the model. Every rejection must carry a reason code. Aggregate those codes monthly. They will tell you exactly what to fix.

The Marketing/Sales SLA Template: What to Include

A one-page SLA is enough. Here is the structure:

• MQL definition: Exact scoring criteria (fit attributes and weights, behavioral attributes and weights, MQL threshold score). Signed by marketing lead and sales lead.
• MQL-to-SQL SLA: Response time commitment, attempt definition, rejection reason codes, and escalation path for aged MQLs.
• Shared KPIs: MQL volume, MQL-to-SQL conversion rate, SQL-to-opportunity rate, average deal size by MQL source, marketing-influenced revenue. Both teams own these numbers.
• Review cadence: Monthly check on conversion rates, quarterly full model review, annual ICP and threshold reset.
• Arbitration process: When marketing and sales disagree on a lead’s status, who has final say and how fast must they decide?

This document does not need legal review. It needs two signatures and a shared dashboard. The marketing strategy work we do at HiddenPeak almost always starts here because everything downstream — campaigns, content, demand gen spend — is unreliable until this agreement exists.

When to Rebuild Your MQL Definition From Scratch

Iterate on the model if conversion rates drop 10–15% quarter over quarter. Rebuild from scratch if:

• Your ICP has changed materially (new segment, new product line, new price point)
• MQL-to-SQL conversion has been below 15% for two consecutive quarters
• Sales has stopped working MQL alerts altogether
• You have merged with or acquired another company and the definitions conflict
• Your go-to-market motion has shifted (product-led to sales-led, or the reverse)

A rebuild takes 4–6 weeks done properly: ICP validation, closed-won analysis, sales interviews, scoring model draft, SLA negotiation, and MAP/CRM configuration. Cutting corners here costs 6–12 months of pipeline quality problems on the back end.

The AI demand engine framework we use compresses that timeline significantly by pulling closed-won signal patterns automatically rather than relying on manual deal reviews.

What Good Looks Like: Benchmarks Worth Targeting

These are not industry averages pulled from a vendor whitepaper. These are the thresholds we use to evaluate whether a program is working:

• MQL-to-SQL conversion rate: 25–40% is healthy. Below 20% means the definition is too loose or sales is not working leads. Above 50% may mean the threshold is too high and you are leaving pipeline on the table.
• SQL-to-opportunity rate: 60–75%. If it is lower, the SQL definition needs tightening.
• MQL response time: under 8 business hours. Every hour over that costs conversion rate measurably.
• Rejected MQL rate: under 20%. Above that, the model is broken or sales is gaming the system.
• Marketing-influenced pipeline: 40–60% of total pipeline in a balanced GTM motion. Higher is not always better — it depends on your sales-led vs. marketing-led ratio.

Start the Audit Before You Rebuild the Model

If your MQL definition is not producing predictable pipeline, the fix starts with a 30-minute conversation — not a six-month analytics project. At HiddenPeak AI, we run a free audit of your current lead scoring framework, MQL-to-SQL conversion data, and sales SLA gaps. We will tell you exactly what is broken and what to fix first. No deck, no sales pitch. Book the audit at /contact/ and walk away with a prioritized action list you can implement the same week.