Defining a Marketing Qualified Lead for SaaS

A marketing qualified lead, or MQL, is a lead that marketing considers ready for sales attention. A clear marketing qualified lead definition is one of the most useful agreements a SaaS company can make, because it tells marketing what to optimize for and tells sales which leads deserve their time first. When the definition is good, the handoff between the two teams becomes routine. When it is poor, the handoff becomes a running argument.

The argument usually sounds the same everywhere. Marketing celebrates hitting its MQL target. Sales complains that the leads are not real buyers, ignores many of them and focuses on its own prospecting. Leadership sees a funnel where MQL numbers rise while pipeline stays flat and cannot tell which team is right. Almost always, the root cause is a definition that rewards activity rather than buying likelihood.

This guide covers what should go into an MQL definition, how to score leads, how to work with sales on the details and how to check that the definition actually predicts revenue.

What makes a lead qualified

Most useful MQL definitions combine two kinds of signal: fit and engagement. Each tells you something different, and neither is enough on its own.

Fit

Fit describes how closely a lead matches your ideal customer profile. The usual fit attributes for a B2B SaaS company are company size, industry, the lead's role and the region they operate in. A director of marketing at a software company inside your target size range is a strong fit. A student researching a class project or a freelancer at a one-person consultancy is a weak fit, no matter how interested they seem.

Fit matters because it determines whether a lead could become a good customer at all. A lead with no fit can download every guide you publish and still never buy, or buy and churn because the product was not built for them. The fit data you need often comes from the form a lead fills out, from enrichment based on their work email domain, or from both. Keep the fit criteria specific enough to be useful. "B2B companies" is too broad to filter anything; "B2B SaaS companies with a dedicated marketing function" is something you can actually apply.

Engagement

Engagement describes how interested the lead appears right now. Some engagement signals are strong: a demo request is an explicit statement that someone wants to talk to sales. Visits to your pricing page usually indicate someone is evaluating cost, which tends to come late in a buying process. Other signals are weaker but still meaningful in combination, such as downloading several pieces of content on related topics, attending a webinar, or, for products with a free plan or trial, using the product in ways that resemble how paying customers use it.

The key is to treat engagement signals differently based on what they reveal about buying intent. Reading a top-of-funnel blog post tells you someone is curious about a topic. Comparing plans on your pricing page tells you someone is considering paying. A definition that weights those equally will flood sales with curious readers.

An example MQL definition

Combining fit and engagement produces a definition like this one:

A lead from a B2B SaaS company with 20 to 500 employees, in a marketing or revenue role, who has visited the pricing page and downloaded a buying guide, or requested a demo.

This definition is specific enough that anyone on either team can apply it and reach the same answer. It requires fit, so leads outside the target market do not qualify. It requires meaningful engagement, so a single newsletter signup does not qualify. And it treats a demo request as sufficient engagement on its own, because someone asking to talk to sales is exactly what sales wants to know about.

Lead scoring

A written definition works well for small volumes. As volume grows, many teams turn the definition into a lead score, assigning points to fit and engagement attributes and setting a threshold above which a lead becomes an MQL.

A simple illustrative model might give a significant number of points for a company size inside your ideal range and for a target role. It might give a meaningful amount for a pricing page visit, a large amount for a demo request, a small amount for webinar attendance and subtract points for a personal email domain, since that often signals a student or a job seeker rather than a buyer. The threshold is then set so that a lead needs both reasonable fit and some real engagement to cross it, while a demo request from a good-fit lead crosses it immediately.

The exact numbers matter less than the logic behind them. Weight each signal according to how strongly it predicts buying, and make sure fit and engagement both contribute. Resist the temptation to add dozens of scoring rules. A model with a handful of well-chosen signals is easier to understand, easier to explain to sales and easier to fix when it is wrong. Complex models with many small point values tend to produce scores nobody trusts.

Negative scoring is just as important as positive scoring. Competitors, existing customers, job seekers and very small companies can all be excluded or penalized so they do not inflate your MQL count.

Align with sales

An MQL definition that marketing writes alone rarely works. Sales has direct knowledge of which leads turn into real conversations, and they are the ones who have to act on every MQL. Build the definition together.

Agree on four things. First, the MQL criteria themselves, written down so nobody has to guess. Second, response time expectations: how quickly sales will follow up on a new MQL, since a demo request that waits several days for a reply often goes cold. Third, the sales acceptance criteria, meaning what makes sales accept or reject an MQL after a first look, so rejections are consistent and explainable. Fourth, a feedback loop, where sales records why they rejected a lead and marketing reviews those reasons regularly.

Many teams formalize this with a sales accepted lead stage, sometimes called an SAL, between MQL and opportunity. That stage makes the handoff measurable. If sales accepts a high share of MQLs, the definition is working. If acceptance is low, the reasons sales gives will usually point to exactly what needs to change.

Review lead quality together on a regular schedule, ideally monthly at first. Look at a sample of recent MQLs, discuss which ones turned into conversations and which did not, and adjust.

Validate against outcomes

The ultimate test of an MQL definition is whether MQLs turn into revenue. Track the MQL-to-opportunity rate, the MQL-to-customer rate and the revenue that comes from deals that started as MQLs. Compare those numbers across lead sources and over time.

If MQLs rarely become opportunities, the definition is letting in too many leads that are not ready or not a fit. If MQLs convert well but there are very few of them, the definition may be too strict, and good leads may be sitting unqualified in your database. Either way, the data tells you which direction to adjust.

Be patient with this analysis. B2B sales cycles take time, so the effect of a definition change on revenue may not show up for a quarter or more. In the meantime, sales acceptance and opportunity creation are useful leading indicators.

MQL vs PQL

For product-led companies with a free plan or trial, product usage is often a stronger buying signal than marketing engagement. A product-qualified lead, or PQL, is a user or account whose behavior inside the product suggests they are likely to buy, such as completing setup, inviting teammates or reaching a usage limit.

PQLs can outperform MQLs because they reflect what people do with the product rather than what content they read. Many companies use both. MQLs capture interest from people who have not tried the product yet, while PQLs identify active users who are ready for a sales conversation or an upgrade prompt. If you run both, define how they interact, so the same account is not routed to sales twice through different paths.

Avoid vanity MQLs

The fastest way to make an MQL definition useless is to count low-intent activity as qualification. If every content download becomes an MQL, the number will grow nicely and say almost nothing about pipeline. Sales will learn to ignore MQLs, and marketing will lose the ability to prove its contribution.

The pressure to inflate MQLs usually comes from targets. If marketing is measured primarily on MQL volume, there is a constant temptation to loosen the definition. Measuring marketing on opportunities or pipeline created, alongside MQLs, reduces that pressure and keeps both teams focused on the outcome that matters.

Review regularly

Your ideal customer profile, your product and your marketing channels all change over time, and your MQL definition should change with them. Revisit it quarterly, and whenever strategy shifts, such as when you move upmarket, launch a new product line or add a self-serve plan. A definition that was right a year ago may now be letting in the wrong leads or filtering out the right ones.

Common mistakes

The most common mistake is an engagement-only definition that ignores fit, which produces many active leads who will never buy. The second is writing the definition without sales input, which guarantees it will be ignored. The third is never validating the definition against revenue, so nobody knows whether it works. The fourth is static scoring that never changes even as the market and product evolve.

A worked example (illustrative)

Consider a B2B SaaS company that defined an MQL as anyone who downloaded two pieces of content. Marketing hit its MQL target every month, but sales accepted few of those leads, and fewer still turned into opportunities. Both teams were frustrated, and neither had evidence to settle the disagreement.

They decided to start from the outcome. They looked at the previous six months of closed-won deals and asked what those customers had in common before their first sales conversation. A pattern emerged. Most customers worked at companies within a specific size range. Most held marketing, revenue or operations roles. And most had visited the pricing page or requested a demo before talking to sales. Content downloads, on the other hand, showed little relationship to buying. Plenty of customers had never downloaded anything, and plenty of heavy downloaders never bought.

The new MQL definition required three things together: a company size within the target range, a target role, and either a demo request or a pricing page visit combined with one other engagement signal.

MQL volume dropped noticeably, which required a frank conversation with leadership about targets. But sales acceptance rose, and the number of opportunities created from MQLs increased, because the leads reaching sales now resembled past buyers. Sales started following up on MQLs quickly again, because they trusted them.

Questions for your next MQL review

When you sit down with sales to review your definition, a few questions keep the discussion grounded. Ask what your last twenty or so closed-won customers had in common before their first sales conversation. Ask which engagement signals appear often in won deals and rarely in lost ones. Ask what share of MQLs sales accepts and why the rest are rejected. And ask whether you are counting anything as an MQL that never turns into pipeline.

Use won and lost deals as your evidence rather than opinions, and repeat the review every quarter.

The takeaway

A useful marketing qualified lead definition combines fit and meaningful engagement, is built and agreed with sales, and is validated against pipeline and revenue. Keep it simple enough that both teams can apply it, review it as your business changes, and add PQLs if your product lets people try before they buy.