Marketing qualified lead

A 300-person fintech downloads your integration guide, visits pricing twice, and signs up for a webinar. That sounds like a marketing qualified lead. Then an SDR checks the record and finds a junior researcher at a company that doesn't use your supported payment processor.

A marketing qualified lead, or MQL, is a contact whose company and role fit your target market and whose recent behavior suggests a business problem worth investigating. It isn't a guarantee of buying intent. It’s a reason to look closer.

That distinction matters because a form fill is easy to count. A useful sales conversation is harder.

What is a marketing qualified lead?

An MQL has cleared a threshold agreed by marketing and sales. The threshold normally combines two things:

• Fit: company size, industry, geography, role, revenue, or technology environment. These should come from your ideal customer profile, not from whatever fields happen to be available in the CRM.
• Relevant behavior: a pricing visit, demo request, integration question, repeat visits from several people at one account, or another action tied to an active problem.

A person with a perfect job title who only reads a general blog post may be a good target, but not an MQL yet. Someone who requests a security review but works for a three-person agency may have strong interest and no commercial fit.

Both parts matter. An MQL is not just “someone who engaged with marketing.”

What should MQL criteria include?

The right threshold depends on your sales motion. A low-cost product with a short buying cycle can accept more uncertainty. A compliance platform sold to banks for six-figure contracts cannot.

Start with the account. Does the company fall inside the segment you can serve profitably? Then look at the person. Are they close to the problem, part of the buying group, or likely to know who owns it?

After that, look for a trigger. A trigger gives the activity context. It might be:

• a new VP of Operations
• a funding round followed by a hiring push
• an enterprise customer asking for SOC 2 evidence
• a processor change that creates integration work
• an audit finding or reporting deadline

A score can turn these rules into routing logic, but the score isn't the definition. Ten points for an ebook and twenty for a webinar won't tell you much if neither action has any connection to pipeline.

My view: teams get MQLs backwards when they start with the scoring tool. They ask what the platform can count, then call the result qualification. Start with the sales problem instead. What evidence would make an SDR spend ten minutes researching this account?

MQL criteria example

Take a company with 50 to 500 employees that sells reconciliation software to finance teams at payments businesses.

A sensible MQL might be a finance, operations, or payments leader at a company above the required transaction volume, using a supported processor or considering a processor change, who requests an integration checklist or asks how migration works.

A newsletter subscription wouldn't qualify. Neither would one generic ebook download from an otherwise suitable account.

Now take a cybersecurity vendor selling SOC 2 readiness software to venture-backed SaaS companies. A controller or security leader who attends a session on audit evidence collection is more interesting if the company recently raised a Series B, hired a security executive, or signed an enterprise customer with compliance requirements.

The same webinar attendance means less without that context. The person might be researching an active audit. Or they might be collecting material for a university assignment. The activity is identical. The commercial meaning isn't.

MQL vs. SQL

An MQL has met marketing's threshold. A sales qualified lead, or SQL, has passed a second test with sales.

A lead enters the database through a form, event, referral, ad, or outbound campaign. Marketing then decides whether the contact has enough fit and relevant activity to route for review. Some companies call the next stage a sales accepted lead, or SAL. That stage simply records whether sales accepted responsibility for follow-up.

The SQL stage should mean that an SDR or salesperson found a credible business problem, relevant stakeholders, a buying process, or a next step. The exact requirements vary, but “they downloaded something” isn't enough.

This is where reporting often gets silly. Marketing reports 2,000 MQLs. Sales says only 140 were worth contacting. Both numbers may be accurate. They’re just measuring different things.

The handoff should include a reason, not a task with no context. For example:

300-person fintech, changed processors last month, requested the migration checklist, likely reconciliation issue. Ask how the processor change affects close and reporting.

That gives an SDR somewhere to start. “Follow up on content engagement” doesn't.

Why MQL scoring often breaks

Most scoring systems reward what is easy to measure:

• page views
• email clicks
• form fills
• event registrations
• content downloads

Those actions can matter. But they are weak evidence on their own. Someone may open six emails because the subject lines are good. That doesn't tell you whether they have budget, authority, or a deadline.

Separate fit scores from behavior scores. Fit could include employee count, industry, role, revenue band, and installed technology. Behavior could include a pricing visit, a demo request, repeat activity from multiple contacts at the same account, or a direct question about deployment.

Add negative signals too. A student title, personal email address, unsupported country, competitor domain, or company below your minimum size should lower the priority. If every interaction adds points, the model eventually treats irrelevant activity as buying intent.

Review the model against accepted leads and pipeline. Suppose a content syndication vendor produces a 40% form-fill rate but almost no accepted leads. That source isn't performing just because the contact count looks good. A smaller webinar series that produces fewer MQLs but more opportunities may deserve more budget.

Don't compare MQL conversion with a universal benchmark. A six-month enterprise sales cycle and a 14-day SaaS motion shouldn't use the same reporting window. Group MQLs into cohorts and follow them through accepted lead, SQL, opportunity, and closed-won revenue.

How marketing and sales should manage MQLs

Write the agreement before building another dashboard.

Marketing should document the required company and contact attributes, qualifying actions, disqualifiers, routing rules, and follow-up window. Sales should confirm that these are contacts its team can actually work.

The return path matters just as much. When an SDR rejects an MQL, “bad lead” isn't useful. Use a reason such as “below minimum company size,” “wrong geography,” “no active project,” “student,” or “unsupported technology.” Review those reasons every month. They show where the definition is wrong.

If sales accepts a lead but it never progresses, record that too. Maybe finance titles convert and generic operations titles don't. Maybe webinar attendees are only useful when the topic covers a live compliance deadline. Maybe a new executive hire is a stronger trigger than a funding announcement in your market.

Change the rules when the evidence changes. Otherwise the MQL definition becomes a document everyone cites and nobody trusts.

Teams running cold outreach should keep outbound prospects separate from inbound MQLs. An outbound prospect can be an excellent fit without taking a marketing action. Calling that person an MQL muddies source reporting and hides which motion created the opportunity.

The useful question isn't how many MQLs marketing produced. It's whether the label helps the next person make a better decision.