What Is a Qualified Lead? MQL, SQL, and When Sales Should Engage

The qualified lead definition most B2B revenue teams use has two parts: fit (could this company and contact buy from us?) and intent (are they showing signs they want to evaluate or buy now?). A contact with perfect firmographics but zero commercial behavior is a prospect—not a qualified lead. A contact who downloads one blog post from a personal Gmail with no company match is a name in the database—not a qualified lead.

For service businesses, a qualified lead typically means:

• ICP match — industry, company size, geography, and role align with who you serve profitably.
• Reachable decision-maker or influencer — the contact can start or advance a buying conversation.
• Defined intent threshold — actions that signal evaluation or purchase readiness, not passive content consumption alone.
• Exclusions cleared — not a competitor, student, job seeker, existing customer, or out-of-territory record.

Qualification is stage-dependent. Early in the funnel, "qualified" may mean ready for structured nurture. Later, it means ready for a sales conversation. The mistake is using one definition for every channel and every lifecycle status.

Lead generation captures demand—forms, ads, SEO, events. Demand generation builds awareness and category interest over time. Both feed the same pipeline, but they produce contacts at different readiness levels. A demand gen program may deliver engaged audiences long before anyone hits a pricing page; a lead gen program should deliver contacts closer to commercial intent. Qualification rules must reflect that mix, or marketing will over-score awareness traffic and sales will stop trusting the queue.

FunnelWon helps B2B teams build lead generation systems where capture, scoring, and handoffs align—so "qualified" means the same thing in HubSpot, Salesforce, and the Monday pipeline meeting.

Search for qualified lead definition and you will see acronyms used interchangeably. In practice, three labels matter for handoffs: MQL, SQL, and sometimes SAL (sales accepted lead).

Marketing qualified lead (MQL)

An MQL is a contact marketing identifies as meeting agreed fit and intent criteria—ready for sales review, not necessarily ready to close. Marketing owns the criteria and the volume at creation. Document MQL rules in four areas:

1. Firmographic fit — company size, industry, geography, tech stack, or other ICP filters enforced at capture or enrichment.
2. Behavioral threshold — demo request, pricing page visit, multiple high-intent pages, webinar attendance with duration minimum, or score crossing a defined bar.
3. Hard rules vs scoring — some actions auto-MQL ("Book a call" on a service page); others accumulate points over time.
4. Exclusions — competitors, bad data, personal emails without business context, territories you do not serve.

Sales qualified lead (SQL)

An SQL is a lead sales accepted after confirming pursuit is warranted—need, fit, authority, and timing validated through review or discovery. SQL means sales agrees the conversation is worth active effort. SQL is not "we emailed them once." It is "we accept ownership of this opportunity path."

Sales accepted lead (SAL)

Some orgs use SAL as the bridge: marketing passes an MQL, sales accepts or rejects within SLA, and SAL becomes the accepted subset. Whether you call it SQL or SAL, the operational point is the same—marketing's promise meets sales' confirmation.

How the stages connect

Map these labels to your lead generation funnel stages: capture produces contacts, nurture builds intent, qualification produces MQLs, and sales acceptance produces SQLs or opportunities. When definitions live only in marketing automation defaults, MQL volume rises and SQL conversion collapses. Co-author definitions with sales, publish them in one lifecycle map, and review monthly against win/loss feedback.

For SLA-backed handoffs—speed-to-lead, rejection reasons, shared scorecards—see sales and marketing SLAs. Qualification without enforcement is a vocabulary exercise.

Lead scoring turns qualification from opinion into rules—when the model is simple enough for sales to trust and updated often enough to stay accurate.

Fit scoring (demographic / firmographic)

Fit points answer "should we sell to this account?" Common inputs:

• Company size and revenue band — match to your ICP sweet spot; penalize too small or too large when economics break.
• Industry and sub-vertical — weight industries where you win at higher rates.
• Geography and territory — zero or negative score outside coverage.
• Role and seniority — economic buyer and champion roles score higher than generic inboxes.
• Tech stack or trigger events — when relevant to your offer (new funding, hiring spree, platform migration).

Build fit criteria from buyer personas and closed-won analysis—not from who marketing wishes would buy.

Intent scoring (behavioral)

Intent points answer "are they evaluating now?" Weight actions by commercial proximity:

• High intent — demo request, contact sales, pricing page, proposal download, repeat visits to service pages.
• Mid intent — case study deep dives, comparison content, webinar live attendance, email replies.
• Low intent — single blog view, social click, newsletter subscribe—valuable for nurture, insufficient alone for MQL.

Apply recency decay. A pricing page visit six months ago should not carry the same weight as one this week unless other signals confirm sustained evaluation.

Negative scoring and hygiene

Subtract points or hard-disqualify for:

• Competitor domains and known bad-fit segments
• Personal email with no enrichable company
• Job-seeker content paths (careers, "how to become a…")
• Unengaged records after defined nurture exhaustion

Operational rules that keep scoring honest

1. Cap total score from any single action — prevents one viral blog visit from auto-MQLing junk fit.
2. Require fit floor for MQL — e.g., behavioral score only promotes to MQL if firmographic fit exceeds minimum.
3. Review score-to-win correlation quarterly — if high scorers lose and low scorers win, adjust weights.
4. Sync scoring with CRM stages — when sales disqualifies, feed reason codes back into model and capture rules.

Scoring supports qualification; it does not replace discovery. The goal is fewer, better handoffs—not maximum MQL badges.

The qualified lead definition fails in handoff, not in theory. Sales should engage when delay costs conversion and the contact meets agreed criteria—not when every captured name enters a rep queue.

Route to sales immediately

Engage sales without nurture delay when:

• Explicit commercial request — demo, quote, pricing, "talk to sales," or calendar booking on a service page.
• High-intent behavior plus ICP fit — pricing or comparison pages after proof engagement, or lead score crossing MQL threshold with firmographic fit confirmed.
• Inbound reply with buying context — direct response to nurture or outbound showing timeline, budget band, or project scope.
• Event or webinar high engagement — attended live, asked product-fit questions, requested follow-up—especially within 24 hours while context is fresh.
• Named account ABM signals — target account showing multiple stakeholder visits or intent spike per your ABM rules.

For inbound demo and pricing requests, speed-to-lead targets of minutes—not days—are standard. Delay here erodes conversion regardless of nurture quality.

Keep in marketing nurture

Do not route to sales when:

• Fit is unclear or below ICP floor — enrich first or disqualify; do not waste SDR cycles.
• Single low-intent action — one blog download, one social ad click, generic newsletter signup.
• Timing signals "not now" — form responses indicating next fiscal year or research phase; enroll in dated nurture instead.
• Missing critical fields — no company, no role, unreachable phone/email; fix capture before handoff.
• Existing pipeline or customer — route to account owner or customer success, not new-business queue.

Nurture paths should escalate with behavior—see email nurture sequences for welcome-education-proof-offer structure and triggers that promote contacts when intent rises.

The gray zone: SDR qualification calls

Many B2B teams use SDRs between marketing and AE for contacts that show promise but lack full SQL certainty. Use a defined sales development qualified lead (SDQL) or equivalent stage: marketing MQL → SDR conversation → SQL or recycle. Document attempt cadence, disqualification reasons, and recycle rules so gray-zone leads do not rot in limbo.

Decision matrix (quick reference)

When engagement rules are documented and tied to CRM automation, marketing stops guessing whether sales will call—and sales stops rejecting leads marketing thought were obvious.

Definitions and scoring only work when handoffs, metrics, and feedback loops are operational—not slide-deck theory.

Document the one-page qualification standard

Publish a single reference both teams sign: ICP summary, MQL criteria with CRM field names, SQL acceptance rules, exclusion list, scoring model overview, and engagement triggers. Link it from your CRM dashboard header. If reps cannot find it in ten seconds, it does not exist.

Every handoff carries context

Sales should not hunt for why a lead qualified. Pass:

• Source and campaign (preserved first-touch)
• Form responses or chat summary
• Pages viewed and assets downloaded
• Lead score breakdown (fit vs intent)
• Assigned owner and SLA deadline

Automation via email marketing automation and CRM workflows reduces manual gaps—especially sales alerts on pricing visits or score threshold crosses.

Metrics that prove qualification works

Track qualification health, not just volume:

• MQL-to-SQL (or SAL) conversion rate — persistently below target means criteria or nurture mismatch.
• SQL-to-opportunity rate — discovery quality after acceptance.
• Win rate by source and MQL cohort — validates scoring weights against revenue.
• Cost per SQL and cost per opportunity — full-funnel efficiency beyond CPL; compare to B2B CPL benchmarks with quality context.
• Rejection reason mix — structured picklists, reviewed weekly with marketing.
• Time from capture to sales engagement — median and SLA breach rate by lead type.

Close the feedback loop

Monthly, review ten won and ten lost deals from marketing-sourced SQLs: did scoring predict outcome? Quarterly, adjust MQL thresholds when product, ICP, or motion changes. When sales marks "bad fit" repeatedly on a campaign, pause spend and fix targeting before scaling nurture.

Qualification is how lead generation connects to revenue. Teams that treat every capture as equal optimize for vanity metrics. Teams that define fit, intent, and engagement timing optimize for pipeline—and give sales a queue they will actually work.

FunnelWon designs lead generation programs with qualification built in: ICP-aligned capture, scoring models sales trusts, nurture that escalates intent, and handoffs backed by SLAs—so qualified means revenue-ready, not just marketing-ready.