What Is an MQL? MQL vs. SQL in B2B SaaS

In B2B SaaS companies, the oldest argument between marketing and sales always starts with the same sentence: "The leads marketing sends us are low quality." Marketing fires back: "Sales doesn't follow up on the leads." More often than not, the root of this argument is a definition gap. The concept of a "qualified lead" means something different to everyone. To the marketing team, anyone who downloads an e-book might be valuable. The sales team, on the other hand, only sees a company with a clear budget and need as a real opportunity. This is exactly where the concepts of MQL (Marketing Qualified Lead) and SQL (Sales Qualified Lead) come in.

In this article, we'll cover what an MQL is, how it differs from an SQL, and how to design the handoff between the two stages. From scoring models to CRM setup, and from the service level agreement between marketing and sales to the metrics you should track, we'll walk through every topic with concrete examples. Our goal is to help you build a system where everyone on your team means the same thing when they say "qualified lead."

What Is an MQL?

An MQL, or Marketing Qualified Lead, is a prospect who has shown interest as a result of marketing activities and, based on predefined criteria, has the potential to become a sales candidate. In short, it's the stage where the marketing team says, "This person fits our target audience and has shown clear interest in us."

There are two core dimensions to the MQL definition:

• Fit: How closely do the person and the company match your ideal customer profile (ICP)? Industry, company size, employee count, geography, tech stack and the person's job title are all part of this dimension.
• Intent/Engagement: How much, and in what ways, has the person interacted with your brand? Visiting your pricing page, attending a webinar, downloading a case study or clicking on your emails are signals in this dimension.

Here's an important distinction: an MQL is not yet someone who is ready to buy. An MQL is a prospect who has become "warm" enough that they may be worth the sales team's time. For example, if you sell HR software, an HR manager at a 200-employee logistics company who reads three posts on your blog and downloads your "Payroll processes checklist" e-book might qualify as an MQL. But that person may not be ready to request a demo today.

What Is an SQL?

An SQL, or Sales Qualified Lead, is a prospect that the sales team has evaluated and judged highly likely to turn into a real sales opportunity. At the SQL stage, there's more than just interest. There's a validated need, a reasonable timeline and concrete information about the decision-making process.

For a lead to count as an SQL, you generally need positive answers to the following questions:

• Does the company have a concrete problem it wants to solve?
• Is there a budget allocated, or one that could be allocated, for this problem?
• Have you gained access to the decision-maker or the decision-making process?
• Is a specific timeframe for the purchase being discussed?

Let's go back to the HR software example above. The same HR manager requests a demo and, during the discovery call, mentions that the contract for their current payroll software ends in four months. They add that they're looking for alternatives and will make the decision together with the CFO. At this point, the lead is now an SQL.

Key Differences Between MQLs and SQLs

We can summarize what separates the two concepts as follows:

• Ownership: MQLs are owned by the marketing team. SQLs are owned by the sales team (SDR, BDR or Account Executive).
• Evaluation method: MQLs are mostly identified through automated scoring and behavioral data. SQLs are validated by a person, usually through a discovery call.
• Purchase intent: An MQL means "interested." An SQL means "has a need and a process."
• Funnel position: MQLs sit in the middle of the funnel. SQLs are at the bottom of the funnel, closest to the opportunity stage.
• Communication tone: Educational content and nurturing flows suit MQLs. With SQLs, you move straight into sales conversations, demos and proposals.
• Success metric: For MQLs, you track volume and the MQL-to-SQL conversion rate. For SQLs, you track conversion to opportunity, win rate and pipeline value.

Why is it so important to clarify these differences? Because if you treat an MQL like an SQL, your sales team ends up calling people who aren't ready yet. They waste their time and scare off potential customers with premature pressure. If you treat an SQL like an MQL, you leave a company that's ready to buy waiting in an automated email flow and lose it to a competitor.

The Journey Through the Funnel: From Lead to Opportunity

MQLs and SQLs don't mean much on their own. They're part of a broader lead lifecycle. A typical B2B SaaS funnel consists of the following stages:

1. Visitor / Anonymous user: Someone who comes to your website but whose identity you don't know.
2. Lead: Someone who becomes identifiable by filling out a form or sharing their contact information.
3. MQL: A lead who meets the fit and engagement criteria and passes a set score threshold.
4. SAL (Sales Accepted Lead): A lead the sales team has reviewed and accepted, saying "I'll follow up on this one." This intermediate stage is a critical checkpoint for marketing-sales alignment.
5. SQL: A lead whose need, budget and timing have been validated through a discovery call.
6. Opportunity: A sales process in the CRM with a deal amount and an expected close date.
7. Customer: A company that has signed the contract.

Many companies skip the SAL stage. However, SAL is the best way to see whether the sales team is actually evaluating the leads coming from marketing. If you track what percentage of MQLs convert to SALs, you'll quickly see whether your scoring model matches the sales team's expectations.

How to Define Your MQL Criteria

An MQL definition is entirely company-specific. Rather than copying another company's model, you need to start from your own data. Here's a step-by-step approach:

1. Analyze your won customers

Pull a list of the customers you've won over the last 12-18 months. Look at what they have in common:

• Which industries do most of them come from?
• What employee count range do they cluster in?
• What was the job title of the first person you were in contact with?
• What content did they engage with before buying?
• Which channel did they come from?

This analysis forms the foundation of your ideal customer profile and your "pre-purchase behavior" patterns.

2. Also examine lost leads and leads that never converted

Looking only at successes is misleading. Also identify the segments that fill out lots of forms but never become customers. For example, students, employees of competitors, very small businesses or geographies you don't serve may fall into this group. These are the criteria that should receive negative points.

3. Build a lead scoring model

A simple but effective scoring model has two columns: a fit score and an engagement score. The example below is a hypothetical model designed for a B2B SaaS company selling to mid-sized businesses:

Fit scores:

• Being in a target industry: +15
• Employee count between 50 and 500: +15
• Director-level title or above: +20
• Manager-level title: +10
• Being located in a served country: +10
• Personal email address (gmail, hotmail, etc.): -15
• Student or competitor: -50

Engagement scores:

• Visiting the pricing page: +20
• Downloading a case study: +10
• Attending a webinar: +15
• Reading a blog post (each): +2 (up to +10)
• Clicking on a marketing email: +3
• No engagement for 30 days: -10

In this model, you could set the MQL threshold at, say, 60 points. But there's an important nuance here. Rather than looking only at the total score, it's healthier to set a minimum threshold for each dimension. For example, you could require at least 30 points for fit and at least 20 for engagement. Otherwise, a highly active student outside your target audience could become an MQL, and so could a CEO who fits your ideal profile but has never engaged at all. Neither is worth the sales team's time.

4. Keep direct hand-raising signals separate

Demo requests, "I'd like to talk to sales" forms or pricing quote requests shouldn't be subject to scoring. These signals should route leads that meet basic fit criteria directly to the sales team. Leaving someone who requested a demo waiting in a nurturing flow is one of the most common, and most costly, mistakes in B2B SaaS.

The MQL-to-SQL Handoff: The Role of the Sales Team

Once an MQL reaches the sales team, the process becomes people-driven. The SDR or BDR evaluates the lead through a short initial call. The most commonly used frameworks for this evaluation are:

• BANT: Budget, Authority, Need, Timeline. Simple and fast. Works well for shorter sales cycles and the SMB segment.
• MEDDIC / MEDDPICC: Includes components such as Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain and Champion. Better suited to enterprise sales and decision processes with multiple stakeholders.
• CHAMP: Challenges, Authority, Money, Prioritization. It starts by discussing the problem first, so it offers a more customer-centric approach.

Whichever framework you choose, what matters is writing down your SQL criteria and turning them into required fields in your CRM. For example, you can enforce at the system level that the "Main problem identified," "Decision-maker," "Estimated budget range" and "Target start date" fields must be filled in before a lead can move to the SQL stage.

Some example questions you can ask during a discovery call:

• "What put this topic on your agenda right now?"
• "Which step in your current process wastes the most time?"
• "What happens over the next six months if you don't solve this problem?"
• "Who else besides you is involved in an investment decision like this?"
• "Have you tried a solution before? Why didn't you continue with it?"

These questions both qualify the lead and leave the customer feeling advised rather than pressured into a sale.

Setting Up an SLA Between Marketing and Sales

For an MQL-SQL system to work, a written service level agreement (SLA) between the two teams is essential. The SLA clarifies each side's commitments to the other.

Marketing's commitments could include, for example:

• Generating a set number of MQLs each month (for example, 120 MQLs)
• Ensuring a certain percentage of MQLs come from the target segment
• Providing complete source, engagement history and score details for each MQL in the CRM

Sales' commitments could include, for example:

• Making first contact with each MQL within a set time (for example, within 4 business hours)
• Making at least 5-6 contact attempts for each MQL (phone, email, LinkedIn)
• Marking the rejection reason in the CRM using a standard option if they don't accept the MQL

This last item is especially important. Standard rejection reasons such as "No budget," "Wrong person," "Bad timing," "Outside target segment" and "Unreachable" are the most valuable feedback marketing can get for improving its scoring model. An organization that regularly analyzes rejection reasons makes its MQL definition more accurate every quarter. To make this loop systematic, check out our article on strategies for building a continuously learning B2B SaaS organization with CRM.

Setting Up the MQL and SQL Process in Your CRM

No matter how good your definitions are, they stay on paper unless they're properly reflected in your CRM. Whether you use HubSpot, Salesforce, Pipedrive or another CRM, the basic setup steps are similar:

1. Define lifecycle stages: Create stages such as Lead, MQL, SAL, SQL, Opportunity and Customer as a standard field on contact and company records.
2. Set up scoring fields: Create separate fields for the fit score and the engagement score. Have the total score calculated automatically.
3. Create automatic transition rules: When the score threshold is crossed, make sure the lead automatically moves to the MQL stage and is assigned to the relevant sales rep.
4. Define assignment logic: Use territory, segment or round-robin logic to make sure MQLs go to the right person.
5. Add notification and task automation: When an MQL is assigned, send the rep an instant notification and create a "First contact" task. Send an alert to the manager when the SLA window is exceeded.
6. Add required fields: Make the necessary fields mandatory for moving to SQL and for rejections.
7. Build a reporting dashboard: See stage-to-stage conversion rates, average transition times and source-based performance on a single screen.

Data quality is the foundation of this system. Missing information from forms (company size, industry, job title) skews scoring. That's why it pays to integrate data enrichment tools with your CRM. For example, B2B data platforms like Apollo.io can help calculate the fit score correctly by filling in company and title information for a lead that came in with only an email address.

How Does the MQL Concept Change in Outbound Sales?

The MQL concept was born in the world of inbound marketing. So where does the MQL fit in a team that actively does outbound prospecting?

In outbound, the process works in reverse. The lead is chosen by the SDR, not by marketing content. In this case, the first stage is usually a fit-based target list. Since the companies on this list already match the ICP, the "fit" dimension is satisfied from the start. The engagement signal shows up as an email reply, a response to a LinkedIn message or a yes to a meeting.

Many teams track outbound prospects who respond positively in a separate category. These are sometimes called "outbound MQLs" or "engaged prospects." What's critical here is keeping inbound- and outbound-sourced leads separate in reporting. That's because conversion rates, sales cycle lengths and cost structures differ significantly between the two. Merging both sources into a single MQL pool prevents you from seeing which channel actually works.

If you want to build a data-driven lead generation infrastructure on the outbound side, Sales Corner, which specializes in data-driven B2B sales and lead generation, can support this process end to end.

MQL, SQL and PQL: A New Balance in Product-Led Growth

In SaaS companies that operate on a freemium or free trial model, a third concept comes to the fore: PQL (Product Qualified Lead). A PQL is a user who has actually used the product and has shown through their usage behavior that they see value in it. For example, in a project management tool, a user who invites three teammates and creates more than 20 tasks within the first week is a strong PQL candidate.

A PQL is usually a much stronger purchase signal than an MQL. That's because there's a big difference between consuming content and using a product to get value from it. In a product-led growth model, the MQL doesn't disappear entirely. But its role changes. The MQL remains important at the stage of driving trial sign-ups. On the sales team's priority list, however, PQLs move to the top. We covered how to strike this balance in detail in our article on the PQL-driven sales approach that turns product usage into revenue.

Key Metrics to Track

Once you've set up your MQL-SQL system, you should regularly monitor the following metrics:

• MQL volume: The number of MQLs generated per month, broken down by source.
• MQL → SAL rate: The percentage of MQLs accepted by the sales team. If it's low, your scoring model doesn't match sales' expectations.
• MQL → SQL conversion rate: The clearest indicator of marketing quality.
• SQL → Opportunity and Opportunity → Win rates: Show the efficiency of the sales process.
• Velocity: The average number of days it takes a lead to move from MQL to SQL and from SQL to close.
• First response time: The time between an MQL being assigned and first contact being made.
• Cost per MQL and cost per SQL: Measure the efficiency of channel budgets.

Let's see how these metrics work together with a simple example calculation. Say you generated 300 MQLs in a quarter, and 240 of them were accepted by sales (an 80 percent SAL rate). Of those accepted, 72 became SQLs after a discovery call (30 percent). 36 of the SQLs turned into opportunities, and 9 of those were won. In this case, your MQL-to-customer conversion rate is 3 percent. If your average annual contract value is 120,000 TL, the expected value of each MQL to you is roughly 3,600 TL. This figure is very useful for setting the upper limit on how much marketing spend you can afford per MQL.

When comparing channel-based costs, pay special attention to paid channels. You can explore how paid search campaigns affect MQL quality in our Google Ads guide for B2B SaaS. Similarly, our article on whether LinkedIn ads really deliver value in B2B SaaS will help you assess which channel brings in more qualified MQLs. If you'd like to strengthen your organic presence on LinkedIn, you might also consider working with Social Media Corner, which handles B2B LinkedIn and Instagram management.

Common Mistakes

Here are the traps companies setting up an MQL-SQL system often fall into:

• Making MQL volume the only measure of success: If the marketing team is measured solely on MQL count, there's a temptation to lower the threshold. Always add SQL and pipeline contribution to their targets.
• Setting up the scoring model once and forgetting about it: As the market, product and target audience change, the model becomes outdated. Review it at least quarterly.
• Looking only at behavior: Highly active but off-target users keep the sales team busy. Always include the fit dimension.
• Neglecting score decay: If someone who attended a webinar six months ago still has a high score today, the model is misleading. Add logic for scores that decrease over time.
• Losing rejected MQLs: Instead of deleting a lead that said "Bad timing," put them back into a nurturing flow. They could become an SQL six months later.
• Ignoring the account-level view: In B2B, purchase decisions are organizational, not individual. Three different people from the same company engaging in the same week is a much stronger signal than one person's high score. Consider account-level scoring as well.
• Being slow to make first contact: A warm MQL's interest cools quickly. Put first response time at the center of your SLA.

Conclusion

MQL and SQL are not just acronyms. They are agreements that allow marketing and sales to speak a common language. An MQL is the point where marketing says, "This person has the right profile and is showing interest." An SQL is the stage where sales confirms, "This company has a real need and a buying process." When the handoff between the two stages is designed well, the sales team's time is used efficiently, the marketing budget flows to the right channels and the pipeline becomes predictable.

For a successful system, build a scoring model based on your won customers. Create a written SLA between your teams. Support this structure in your CRM with required fields and automations. Recalibrate your definitions every quarter by regularly analyzing rejection reasons. If you're growing product-led, integrate PQLs into this structure; if you work outbound, integrate engagement signals.

If you want to create your own MQL and SQL definitions, configure your CRM around this process or strengthen the alignment between your marketing and sales teams, we at SAAS Corner are here to help. Reach out to us through our contact page, and let's map out a roadmap that fits your growth goals together.

Related Posts

• A Guide to Generating Qualified Leads with B2B Webinars
• Google Ads for B2B SaaS: Costs and Setup Guide
• Keep Outbound Emails Out of Spam: SPF, DKIM, DMARC
• Is Cold Email Dead? No, It Just Changed