Skip to main content

Coleda

Categories
SQL (Sales Qualified Leads)

MQL vs. SQL: Definitions, Handoff Rules, and Examples

MQL vs SQL comes down to who has checked the lead and what they checked. An MQL is a lead marketing has judged ready for sales, based on fit and engagement. An SQL is a lead sales has spoken to and confirmed has a real need, the authority to act, and a reason to buy soon.

Definition: An MQL (marketing qualified lead) has shown enough fit and interest for marketing to pass it on. An SQL (sales-qualified lead) has been confirmed by sales as a real buying opportunity worth working on.

The gap between those two sign-offs is where most of the pipeline goes missing. Below you will find a side-by-side comparison, the stages in between, two worked lead journeys, and a checklist to use before any lead moves from marketing to sales.

MQL vs SQL at a Glance

Most arguments about lead quality start because the two teams use different words for different checks. This table puts the marketing-qualified lead vs. sales-qualified lead difference in one place.

AreaMQL (Marketing Qualified Lead)SQL (Sales Qualified Lead)
Who qualifies it?Marketing, usually through lead scoring and data checksSales, usually an SDR or account executive, through a conversation
What it is judged onFit (industry, company size, job role, region) and engagement (downloads, visits, event attendance, email replies)Confirmed need, buying authority or access to it, budget available or being planned, and a timeline
EvidenceData and behaviorWhat the buyer said
Owner after qualificationSales development, for follow-upAccount executive, for an opportunity
Next stepFirst sales contact within the agreed timeDiscovery or demo meeting, then an opportunity in the CRM
If it failsGoes back to marketing nurtureGoes back to nurture or is closed with a reason
What it tells youThis person may be worth a sales conversation.This company may buy, and sales wants to pursue it.

The simplest way to remember MQL vs. SQL: an MQL is a prediction, and an SQL is a confirmation.

Where MQLs and SQLs Sit in the Funnel

Whether your team says MQL vs SQL or SQL vs MQL, the two are stops on a longer path. Many teams still use a version of the SiriusDecisions demand waterfall, which adds a stage between them that is often skipped in conversation:

  1. Inquiry or CQL: Someone responds: fills a form, downloads an asset, or registers for an event. A content-qualified lead (CQL) is an inquiry from content syndication that already matches agreed filters such as job title and company size.
  2. MQL. Marketing scores the lead on fit and engagement and decides it is worth a sales call.
  3. SAL (sales accepted lead). Sales agrees the MQL is worth contacting and commits to follow up. Nothing is confirmed yet. It is a promise to act.
  4. SQL: Sales has spoken to the buyer and confirmed the need, authority, budget, and timing well enough to pursue.
  5. Opportunity. The deal is open in the CRM with a value and a stage.

The SAL step matters more than it looks. It is the point where sales says, “Yes, we will work this lead,” which ends most arguments about whether leads were ever followed up.

Fit and Interest: The Two Tests Behind an MQL

Before any lead becomes an MQL, it has to pass two separate tests. Teams that blend them into one score end up passing the wrong people to sales.

Fit / EngagementLow engagementHigh engagement
High fitNurture: Right company and role, but not active yet. Keep them engaged.MQL: Right profile and showing interest. Pass to sales.
Low fitRemove or ignore: Wrong profile with no interest.Not a buyer: Students, job seekers, competitors, and vendors often land here. Do not pass to sales.

The bottom-right box is the one that hurts. These people download everything and attend every webinar, so a single combined score pushes them over the MQL line. Sales calls them, finds no buyer, and starts to distrust every MQL that follows. Keep fit and engagement as two scores, and require both.

For the full scoring criteria, see our guide on what makes a lead marketing qualified.

What Sales Checks to Turn an MQL Into an SQL

Marketing can only see behavior. Sales finds out the rest by asking. The SQL decision usually rests on four questions:

  • Need: Is there a problem we solve, and does the buyer agree it is a problem?
  • Authority: Is this person the decision-maker, or can they get us in front of one?
  • Budget: Is money set aside, or is there a clear plan to find it?
  • Timing: Is there a reason to act in a defined period, such as a contract renewal, a deadline, or a new project?

These are the BANT criteria. Most teams do not require all four on the first call. A common rule is a confirmed need plus at least two of the other three. Whatever rule you pick, write it down and get both teams to sign it. Our full SQL definition and qualification checklist covers the questions that confirm each one.

Two Lead Journeys, Start to Finish

Definitions are easier to apply with real shapes. Both journeys below are illustrative examples, not client results.

Journey 1: An MQL That Becomes an SQL

The buyer is an HR operations director at a 900-person logistics company. The seller offers workforce scheduling software.

StepWhat happened?Stage
1Downloads a guide on reducing overtime costs through a content syndication programInquiry (CQL)
2Opens two nurture emails and visits the pricing pageEngagement rises.
3Scores high on fit (right industry, company size, and role) and engagementMQL
4SDR accepts the lead and calls within the agreed time.SAL
5On the call, the director confirms that overtime costs are a board-level priority, owns the budget line, and says the current contract ends next quarter.SQL
6Demo booked with the director and finance leadOpportunity

What made it work: the fit was checked before the call, and the call confirmed need, authority, and timing in one conversation.

Journey 2: An MQL That Goes Back to Nurture

The buyer is an IT analyst at a 3,000-person retailer. The seller offers cloud cost management software.

StepWhat happened?Stage
1Attends a webinar on cloud cost controlInquiry
2Downloads two reports and clicks three emailsEngagement rises.
3The company fits well, the job role is a partial fit, and engagement is high.MQL
4SDR accepts the lead and callsSAL
5On the call, the analyst explains they are researching for an internal report. There is no project, budget, or owner yet.Not an SQL
6Lead returns to nurture with the note: “Researching. Check again when a project is approved.”Back to nurture

This is not a failure. The MQL was reasonable, the call was quick, and the note gives sales a reason to come back. The real failure would be leaving the lead in an “MQL” status for months with no outcome recorded.

The MQL to SQL Handoff Checklist

This is where the MQL vs SQL line gets crossed in practice. Run these checks before any lead moves from marketing to sales. If one fails, the lead is not ready.

  1. Fit score and engagement score both meet the agreed threshold.
  2. Contact data is checked: real person, current job title, and working email or phone.
  3. Consent or a lawful basis for contact is recorded.
  4. The lead record shows what the person engaged with and when.
  5. An owner in sales is assigned automatically, not by hand.
  6. The follow-up time limit is agreed and visible in the CRM.
  7. Every outcome has a set reason code: accepted, SQL, nurture, or disqualified, with a reason.

Our guide to the MQL to SQL handoff covers the service-level agreement behind points 5 to 7.

Should You Still Use MQLs at All?

Forrester has argued for years that B2B teams should move away from MQLs and toward buying groups and opportunities. The reasoning is sound: purchases are made by groups, and an MQL counts one person.

Our view is practical. Keep the MQL as a quality check inside marketing, because someone still has to decide which people are worth a sales call. But stop treating MQL volume as the goal. Report on SQLs, opportunities, and the pipeline, and look at how many people from the same account are engaging, not just the one who filled in a form. Used this way, the MQL vs SQL split stays useful without becoming the scoreboard.

How ColedaB2B Delivers Leads at Each Stage

As a partner, we deliver leads at the stage your team needs: content-qualified leads, MQLs, SQLs, BANT-qualified leads, and progressive leads that build profile data over several touches.

No lead is qualified without an opt-in. Every lead goes through automated checks and a human review before delivery, so your SDRs spend their time on conversations, not on fixing data. If you need leads that already carry confirmed BANT criteria, our sales qualified leads program covers that end of the funnel.

Want to see what a delivered lead looks like before you commit? We will share a sample lead file with the fields, qualification notes, and checks your team would receive.

Request a sample lead file

FAQs:

Who decides when an MQL becomes an SQL?

Sales does. Marketing decides when a lead becomes an MQL, but only a conversation with sales can confirm the need, authority, and timing that make it an SQL.

What is a sales-accepted lead?

A sales-accepted lead (SAL) is an MQL that sales has reviewed and agreed to follow up. It sits between MQL and SQL and records sales’ commitment to act on the lead.

Can a lead skip the MQL stage?

Yes. A demo request from a well-matched buyer, a referral, or a lead that sales finds directly can go straight to sales. Track these separately so they do not distort your MQL numbers.

How does BANT fit into SQL qualification?

BANT (budget, authority, need, timing) is the most common checklist sales use to confirm an SQL. Many teams require a confirmed need plus at least two of the other three.

Why do so many MQLs never become SQLs?

The usual causes are loose MQL criteria, slow follow-up, and fit and engagement blended into one score. A missing written SQL definition makes it worse, because nobody can agree why a lead was rejected.

Categories
Trends

Sales and Marketing Alignment: Shared Definitions, an SLA, and One Scorecard

Sales and marketing alignment means both teams work toward the same revenue goal, using the same definitions, rules, and measures. In practice, it rests on four things: shared lead stage definitions, a service level agreement (SLA) that both sides sign, one scorecard reviewed together, and a regular meeting rhythm. Without these, teams argue about lead quality instead of fixing it.

Definition: Sales and marketing alignment is the shared operating model in which sales and marketing agree on target accounts, lead definitions, response commitments, and success measures, and review them together on a fixed schedule.

Updated November 2026

Why Sales and Marketing Alignment Pays Off

In fact, alignment is not a soft goal. Forrester research published in 2023 found that companies with highly aligned customer-facing teams reported 2.4 times higher revenue growth and twice the profitability growth of companies without that alignment.

Moreover, the way companies buy makes alignment more important. Forrester’s State of Business Buying 2024 found that an average purchase involves 13 people, and 89% of purchases involve two or more departments. When a buying group is that large, marketing and sales both talk to it, often at the same time. So if they send mixed messages, buyers notice.

Speed also matters. Research published in Harvard Business Review found that firms contacting a lead within an hour were nearly seven times as likely to qualify it as those that waited longer. Therefore, fast follow-up depends on clear rules between the two teams.

Signs Your Teams Are Not Aligned

First, use this quick check. If three or more statements are true, alignment is costing you pipeline.

  • Sales says marketing leads are poor, and marketing says sales does not follow up.
  • The two teams use different numbers for the same month.
  • Nobody can say exactly what makes a lead an MQL or an SQL.
  • Leads wait days before anyone contacts them.
  • Rejected leads disappear, with no reason recorded.
  • Marketing reports clicks and form fills, while sales reports bookings.
  • Sales creates its own content because marketing content does not fit real conversations.

Step 1: Agree on Shared Lead Stage Definitions

In practice, alignment starts with words. If “qualified” means one thing to marketing and another to sales, every other agreement fails. So define each stage, who owns it, and what moves a lead into it.

StageDefinitionOwnerEntry rule
InquiryA person who has shown interest, such as a form fill or event registrationMarketingAny known contact action
Marketing qualified lead (MQL)A lead that fits the ICP and has shown enough interest for sales follow-upMarketingMeets fit and engagement scores agreed with sales.
Sales accepted lead (SAL)An MQL that sales has reviewed and agreed to work onSalesThe rep accepts within the agreed time.
Sales-qualified lead (SQL)A lead with a confirmed need, timing, and buying roleSalesDiscovery call confirms agreed criteria.
OpportunityA qualified deal with a value and expected close date in the CRMSalesMeets your opportunity creation rules

Then write these definitions into your CRM, not just a slide. For a clear comparison of the two most debated stages, see MQL vs SQL.

Step 2: Write a Sales and Marketing Alignment SLA

Next, a service level agreement turns good intentions into commitments both sides can track. Here is a template you can adapt.

AreaMarketing commits toSales commits to
VolumeDeliver an agreed number of MQLs per month, by segment.Work every MQL delivered
QualitySend only leads that meet the agreed MQL definition.Give a reason code for every rejected lead.
SpeedRoute MQLs to the right rep within minutes.Make first contact within the agreed time, such as one business hour for high-intent leads.
Follow-upProvide context with each lead: source, content used, scoreMake an agreed number of attempts across channels before recycling
FeedbackReview rejection reasons every month and adjust targeting.Share call insights and common objections.
ContentProduce assets for each stage and roleTell me marketing which assets help and which are missing.
ReportingReport MQL to SQL conversion by source each month.Keep lead and opportunity stages current in the CRM.

Finally, review the SLA every quarter. In particular, adjust volume and speed targets when your market, team size, or offer changes. For the details of moving leads between stages, read our guide to the MQL to SQL process.

Step 3: Build One Sales and Marketing Alignment Scorecard

However, separate reports create separate truths. Instead, give both teams one scorecard and review it together.

MeasureWhat it showsShared or owned
Target account coverageShare of target accounts engaged by marketing or salesShared
MQLs by segment and sourceWhere demand comes fromMarketing
MQL acceptance rateWhether marketing sends leads or sales agrees to workShared
Speed to first contactHow fast sales respondSales
MQL to SQL conversionWhether leads become real conversationsShared
Pipeline createdValue of new opportunitiesShared
Win rate and cycle lengthHow efficiently deals closeSales
Revenue against targetThe final result both teams serve.Shared

Above all, keep the scorecard short, so people read it. For a wider view of marketing results, learn how to measure marketing team performance beyond lead counts.

Step 4: Set a Meeting Rhythm

Even good agreements fade without regular review. A simple rhythm keeps them active:

  • Weekly (30 minutes): marketing and sales managers review new MQLs, speed to contact, and rejected leads.
  • Monthly (60 minutes): leaders review the scorecard, rejection reasons, content needs, and campaign plans.
  • Quarterly (half day): leadership reviews the SLA, target accounts, segments, and budget for the next quarter.

Also, use the same scorecard in every meeting. That way, discussions start from shared numbers, not opinions.

Step 5: Close the Feedback Loop on Rejected Leads

Rejected leads are useful data. However, they only help if you record why. So give sales a short list of reason codes and make one required when rejecting a lead.

For example, common reason codes include

  1. Not in target industry or size
  2. Wrong role or seniority
  3. Contact details incorrect
  4. No current need
  5. Existing customer or partner
  6. Duplicate of an open lead

Then, each month, review the codes by source. If one source produces many “wrong role” rejections, for example, change its targeting rather than arguing about it.

Align on Target Accounts and Messages

Sales and marketing alignment is not only about leads. Both teams should also agree on:

  • Which accounts matter most, using one shared target account list
  • The main problems each segment faces and how you solve them
  • Core messages and proof points, so ads, emails, and sales calls say the same thing
  • The buying group map for each segment, including who decides and who influences

As a result, when both teams use the same messages, buyers hear one story from first ad to final proposal. This matters even more when deals pass through several stages and owners. For how deals move after the first meeting, see our guide to pipeline stages and owners.

Give Sales Content It Will Actually Use

Content is one of the clearest tests of alignment. Often, marketing produces assets that sales never sends, while reps write their own emails and slides from scratch.

To fix this, build content from real conversations:

  1. Collect questions. Ask reps for the ten questions buyers ask most often, by stage.
  2. Map assets to stages and roles. For each question, decide which asset answers it, such as a case study, comparison guide, or cost model.
  3. Make assets easy to find. Keep one library, organized by stage and objection, not by campaign.
  4. Track use. Measure which assets reps send and which ones appear in won deals.
  5. Retire what nobody uses. Old assets clutter the library and confuse new reps.

As a result, marketing content starts to support live deals, and salespeople spend less time writing material that already exists.

Sales and Marketing Alignment With an Outside Lead Partner

Many B2B companies add an outside partner for lead generation or appointment setting. In that case, the partner becomes part of the same system, so the same rules should apply.

  • Share your lead definitions and the reason codes sales uses.
  • Include the partner’s leads in the SLA, with the same response times as internal leads.
  • Report partner leads on the same scorecard, by source, so quality is visible.
  • Hold a monthly review with the partner, using rejection data to adjust targeting.

Otherwise, teams often judge partner leads by different standards and quietly ignore them. With shared rules, however, they become a measurable source of pipeline and part of your sales and marketing alignment.

Tools and Data That Support Sales and Marketing Alignment

Tools do not create alignment. Still, poor data can break it. Focus on a few basics:

  • One CRM record per lead and account, shared by both teams
  • Required fields for lead stage, source, owner, and rejection reason
  • Automatic routing based on territory, segment, and account owner
  • Activity history visible to both teams, including content engagement and calls
  • Shared dashboards built from the scorecard

Generally, revenue operations teams own these systems. Otherwise, assign a named owner from either side.

A 90-Day Plan for Sales and Marketing Alignment

DaysActionOutput
1 to 15Run the diagnostic and pull current numbers for MQL acceptance, speed to contact, and MQL to SQL conversion.A baseline both teams accept
16 to 30Agree on lead stage definitions and update the CRM.One set of stages in one system
31 to 45Draft the SLA, review it with both teams, and get sign-off from both leaders.A signed SLA
46 to 60Launch the scorecard and the weekly and monthly meetingsA working review rhythm
61 to 90Add rejection reason codes, review the first results and adjust targetsThe first round of improvements

By day 90, good sales and marketing alignment should show up as faster contact times and fewer disputes about lead quality. More importantly, you will have shared numbers to improve from.

Align Targets and Incentives

People follow the goals they are paid and judged on. So if marketing earns credit for lead volume and sales only for closed deals, the two teams will pull in different directions.

A few changes help:

  • Share one revenue or pipeline target that both leaders report against.
  • Measure marketing on pipeline and accepted leads, not form fills alone.
  • Recognise sales follow-up, such as speed to contact and use of reason codes, in team reviews.
  • Review both teams’ targets together at the quarterly planning session.

These changes do not need a new pay plan. Even shared goals in team reviews make a visible difference, because each side can see how its work affects the other.

Common Alignment Mistakes

  • Writing an SLA that only marketing signs
  • Defining MQLs without sales input
  • Separate reports for the same funnel
  • Meetings without data, which turn into opinion contests
  • No reason codes, so rejected leads teach nothing
  • Treating alignment as a project rather than a permanent operating rhythm

How ColedaB2B Supports Aligned Revenue Teams

As a partner delivering sales qualified leads, we build our programs around the definitions your sales team already uses. Every lead goes through a three-step check of automated validation and human review before delivery, against criteria your team signs off. Each client works with a dedicated Center of Excellence, with 24/5 coverage, so lead delivery and feedback follow the same rhythm as your own meetings.

Want sales and marketing working from one set of rules? We will review your current lead definitions, SLA and reporting, and show where leads are getting lost between the teams.

Book an alignment workshop

FAQs:

What is sales and marketing alignment?

It is a shared operating model in which sales and marketing agree on target accounts, lead definitions, response commitments and success measures, and review them together on a fixed schedule.

What should a sales and marketing SLA include?

Include lead volume and quality commitments from marketing, response time and follow-up commitments from sales, feedback through rejection reason codes and shared reporting, with a quarterly review.

Who should own sales and marketing alignment?

Leaders of both teams own it jointly. Revenue operations often runs the systems, data and scorecard. Where there is no RevOps team, name one owner to keep definitions and reports current.

How do you measure alignment between sales and marketing?

Track MQL acceptance rate, speed to first contact, MQL to SQL conversion, pipeline created and revenue against target. Review them on one shared scorecard each month.

How often should sales and marketing meet?

A short weekly meeting for managers, a monthly scorecard review for leaders and a quarterly session to update the SLA, target accounts and budget work well for most B2B teams.

Categories
SQL (Sales Qualified Leads)

MQL to SQL Handoff: 7 Written Rules That Stop Good Leads Getting Lost

Why do good leads go cold between marketing and sales? Usually because nobody wrote down the rules. A working MQL to SQL handoff needs seven of them: one definition, required fields, routing, response times, an accept or reject window, reason codes, and a recycle path. This guide gives you each rule, ready to copy.

Definition: The MQL to SQL handoff is the point where marketing passes a qualified lead to sales, and sales either accepts it as a sales-qualified lead or sends it back with a reason.

Updated November 2026

Why Leads Get Lost Between Marketing and Sales

Most lost leads do not fail on quality. Instead, they fail in the gap between two teams. Here are the five most common breaks and what each one costs.

Where it breaksWhat happensWhat it costs
No shared definitionMarketing sends what it counts; sales wants something else.Reps stop trusting the queue.
Missing contextThe rep gets a name and a download, nothing more.A generic first call that goes nowhere
No ownerThe lead sits in a shared queue.Days pass before anyone calls.
No time limitSales follows up “when there is time.”Interest fades before contact
Silent rejectionsBad leads are ignored, not marked.Marketing keeps sending the same kind.

Each of these is a process problem, not a people problem. So the fix for a broken MQL to SQL handoff is a short written agreement that both teams sign.

Pass the Account, Not Just the Contact

Before the rules, one change in thinking. B2B purchases are group decisions. Forrester’s State of Business Buying 2024 found that 13 people take part in an average buying decision. In addition, 89% of purchases involve two or more departments.

That means one engaged contact rarely tells the full story. If a marketing manager and an IT lead from the same company both read your content this month, sales should see them together. As a result, the rep calls with a clear picture of who is involved and what they care about.

So match every lead to its company record before it reaches sales. Then show all engaged contacts from that account on the same record. To rank accounts by how many people are active, score engagement at the account level as well as per person.

The MQL to SQL Handoff Agreement: Seven Rules to Write Down

Put these seven rules in one shared document. Each rule has an owner and, where it matters, a time limit.

Rule 1: One Shared MQL Definition

First, write the MQL definition in one or two sentences that sales signs. Include fit (industry, company size, region, job level) and the activity that counts. For example: “A director or above at a software company with 200 to 5,000 staff in the US or UK who has requested a demo or read two buying-stage assets in 30 days. ” If your team needs a refresher, here is what counts as an MQL.

Rule 2: The Fields Every Lead Must Carry

No lead goes to sales without these fields filled in: name, job title, work email, phone number where consent was given, company, company size, country, the activity that qualified it, and the date of consent. If a field is empty, the lead stays with marketing until it is complete.

Rule 3: Route by Account Owner

Send each lead to the rep who owns that account. If no one owns it, use territory rules instead. Avoid shared queues, because a lead that belongs to everyone belongs to no one.

Rule 4: Response Times by Signal

Of course, not every lead needs the same speed. Match the response to the strength of the signal.

Lead signalFirst contact targetEscalate to the sales manager after
Demo or pricing requestWithin 1 business hour4 business hours
Three or more people active from one accountSame business day1 business day
Buying-stage content from a good-fit contactWithin 2 business days3 business days
Early-stage content download onlyStays in marketing nurtureNot sent to sales

Rule 5: Accept or Reject Within Two Business Days

After first contact, the rep has two business days to accept the lead or send it back. Accepting turns it into a sales-qualified lead. If your teams still disagree on where one stage ends, review MQL vs SQL together and agree on the line in writing.

Rule 6: Reject With a Reason Code

A rejection without a reason teaches nobody anything. Therefore, every rejection needs one code from a short, fixed list.

Reason codeWhat it meansWhat marketing changes
Wrong personRight company, wrong roleTighten job title rules; find the right role in the account.
No projectInterest, but no active needMove to nurture; review the qualifying activity.
Poor fitCompany outside the ideal customer profileFix targeting and form filters.
Already in a dealThe account is already in active sales talks.Check CRM matching before routing.
Bad dataWrong email, wrong phone, or unreachableReview data checks and the source.
No responseFive contact attempts with no replyRecycle with a date to try again.

Rule 7: Recycle, Do Not Delete

Rejected leads go back to marketing with their reason code and a date. Then, after 90 days, re-score them. Many “not now” leads become ready later, so deleting them throws away the pipeline you have already paid for.

What Sales Should Receive: A Lead Record Template

In practice, a name and a download are not enough for a useful first call. Instead, every lead should arrive with this record. The example below is for illustration only.

FieldExample
ContactHead of IT Operations
CompanyLogistics company, 900 staff, United States
Other people active from this accountFinance Director, Operations Manager
What they engaged withA guide on warehouse system costs; a comparison page
Signal that qualified itThree people active within 14 days
Likely buying stageComparing options
GapsNo contact yet from procurement
ConsentOpt-in recorded, with date and source
Suggested first stepOffer a cost comparison call with the IT and finance leads together.

With this record, the rep can open the call with the problem the account is researching. That is what turns a lead into a conversation. For the full checklist sales uses next, see what makes a lead sales-qualified.

How Fast Should Sales Respond After the MQL to SQL Handoff?

Speed still matters. For example, a well-known Harvard Business Review study found that companies contacting online leads within an hour were nearly seven times as likely to qualify them as companies that waited longer. The study is from 2011 and covered online leads, so treat it as a direction rather than a rule.

Buyer behavior also points the same way. Today, buyers usually make the first contact themselves, after most of their research is done. They expect a fast and informed reply. That is why Rule 4 sets the tightest target for demo and pricing requests, where the buyer has asked to talk.

What to Measure in the MQL to SQL Handoff

Track five numbers every month. Taken together, they show whether the rules work.

MetricHow to calculate itWhat a healthy trend looks like.
Acceptance rateLeads accepted by sales ÷ leads sentRising, or steady at a level both teams agree
Time to first contact.Average hours from routing to first call or email, by signalWithin the Rule 4 targets
Rejection rate by reasonRejections per reason code ÷ all rejectionsNo single code grows month after month
SQL to opportunity rateOpportunities created ÷ accepted leadsRising as definitions tighten
Recycled leads that returnRecycled leads that later become SQLsSteady flow back into the pipeline

The 30-Minute Monthly Review

Finally, hold one short meeting each month with a marketing lead, a sales manager, and someone from marketing ops. Keep the same agenda:

  1. Review the five metrics against last month.
  2. Look at the top two rejection reasons and agree on one fix for each.
  3. Read three accepted leads that became opportunities and three that did not.
  4. Update the MQL definition or the fields if the evidence calls for it.
  5. Write down what changed, with an owner and a date.

Over a few months, this meeting does more for your MQL to SQL handoff than any new scoring tool.

How ColedaB2B Delivers Leads Sales Can Act On

As a partner, we deliver sales-qualified leads built on the criteria your sales team signs off on. Every lead goes through a three-step check that combines automated validation with human review. Each client has a dedicated Center of Excellence, and our team works in shifts for 24/5 coverage. Our 98.3% rate of acceptance reflects this process. We also never qualify a lead without an opt-in.

Want to see what sales we receive? We will share a sample lead record built on your target profile, with the fields and context described in this guide.

Request a sample lead record

FAQs:

What is the MQL to SQL handoff?

It is the point where marketing passes a qualified lead to sales. Sales then accepts it as a sales-qualified lead or returns it with a reason, based on rules both teams agreed in advance to.

Why do leads get lost between marketing and sales?

Usually because the rules are unclear. Common causes are no shared definition, missing context, no named owner, no response time, and rejections without a reason.

How fast should sales follow up on a marketing qualified lead?

Match the speed to the signal. Demo and pricing requests deserve contact within one business hour. Strong account-level activity deserves contact the same day, and content-only leads can wait up to two business days.

What should a lead record include before it goes to sales?

Contact and company details, other people active from the account, what they engaged with, the signal that qualified it, any gaps, the consent record, and a suggested first step.

Who owns the MQL to SQL handoff?

Both teams share it. Marketing owns the definition, the data, and the fixes, while sales owns the response time and the accept or reject decision. Marketing ops usually owns the routing and the reports.

Categories
SQL (Sales Qualified Leads)

What Is a Sales-Qualified Lead? Definition, Criteria, and Examples

A sales-qualified lead (SQL) is a prospect that sales has spoken to and confirmed is worth pursuing. The company fits your customer profile, the buyer has a real need, there is a reason to act soon, and the person can make or influence the decision. In short, it is a likely opportunity that sales has checked directly.

Sales-qualified lead definition: An SQL is a lead that sales has confirmed, through a direct conversation, meets the agreed criteria for fit, need, timing, and authority.

What Is an SQL in Practice?

The key word is confirmed. A good sales-qualified lead definition is about evidence from the buyer, not a score in your marketing system.

That rules out three things teams often count as SQLs by mistake:

  • A high lead score. Scores predict interest. They cannot confirm a project.
  • A demo request on its own. Many are from students, competitors, or people comparing prices for later.
  • A filled-in BANT form. A buyer ticking “budget approved” on a form is not the same as saying it on a call.

Getting this wrong has a cost beyond wasted sales time. A 2025 Gartner survey of 632 B2B buyers found that 73% actively avoid suppliers who send irrelevant outreach. Calling people who are not ready, in the wrong role, or at the wrong company makes it harder to reach them later.

The SQL sits after the MQL in the SiriusDecisions demand waterfall that many teams still use. If you need the side-by-side view, our guide on how MQLs and SQLs differ covers it.

The SQL Qualification Checklist

This checklist turns the sales-qualified lead definition into four checks. Each one comes with the question that confirms it on a call.

CheckWhat it meansQuestion that confirms itConfirmed whenRed flag
FitThe company matches your ideal customer profile.“Can you tell me about your team and the systems you use today?”Industry, company size, region, and current setup match the profile.Far outside your usual deal size or segment
NeedThere is a problem you solve, and the buyer agrees it is a problem.“What happens if this stays as it is for another year?”The buyer describes a cost or risk in their own words.“We’re just looking at what’s out there.”
TimingSomething gives the buyer a reason to act within a defined period.“Is there a date or event driving this?”A renewal, deadline, project start, or budget cycle is identified.No date, no event, or “sometime”
AuthorityThe person makes the decision or can involve the decision-maker.“Who else will be involved in choosing a solution?”The decision-maker joins the call or agrees to attend the next one.Cannot identify who makes the decision

Fit is a gate, not a score. If the company is wrong, the other three do not matter.

Why a budget is not a separate check: few buyers will confirm a budget on a first call, and asking too early can end the conversation. Budget is better confirmed through authority: if the decision-maker is involved and the need is real, budget becomes a planning question, not a qualification question. Our guide to BANT lead qualification covers when to ask about budget directly.

Three Calls, Three Verdicts

Here is the checklist applied to three discovery calls. All three are illustrative examples, not client results.

CheckCall A.Call B.Call C.
BuyerVP Finance, 1,500-person manufacturerIT Manager, 400-person healthcare groupHead of Operations, 25-person agency
The seller offersAccounts payable automationEndpoint securityEnterprise data platform
FitYes.Yes.No: below minimum company size
NeedYes: invoice backlog delays the month-end close.Yes: a recent audit flagged unmanaged devicesYes: reporting takes too long.
TimingYes: a new ERP system goes live next quarter.Partly: “this year,” with no specific dateYes, he wants a fix this month.
AuthorityYes: owns the budget; CFO signsNo: the CIO decides.Yes, the owner is on the call.
VerdictSQLNot yetDisqualified
Next stepDemo with finance and ITSecond call with the CIO to confirm timingRecommend a lighter, self-serve option.

Call A passes all four checks. The ERP go-live gives a real deadline, and the buyer holds the budget line.

Call B is the most common case, and the one team that handles it worst. The need is real, but timing is loose, and the decision-maker is missing. It is not an SQL yet, and it should not be dropped either. The right move is a second call with the CIO. If the CIO confirms a date, it becomes an SQL.

Call C shows why fit comes first. Three out of four checks pass, and the buyer is keen, but the company is far too small for the product. Passing it to an account executive wastes their time and leads to a deal that will not close or a customer who will not stay.

What Should an SQL Record Contain?

A sales-qualified lead definition is only as useful as the record behind it. When an SDR marks a lead as an SQL, the account executive should be able to pick it up without calling the buyer to ask the same questions again. Every SQL record should hold:

  • Company name, size, and industry
  • Contact name, job title, and how they fit in the decision
  • Other people in the buying group, by name or role
  • The need, written in the buyer’s own words
  • The timing event and its date
  • The decision process and who signs
  • The agreed next step and its date
  • The lead source and the first touch
  • Who qualified the lead, and when

If a field is empty, the SQL is not finished.

Writing Your Own Sales Qualified Lead Definition

A checklist from a blog post is a starting point. Your own sales-qualified lead definition needs to reflect how your customers actually buy. Four steps get you there:

  1. Start from closed-won deals. Look at your last 20 to 30 wins. Note the company profile, the trigger that started the project, and who signed. That is your real pattern.
  2. Set the minimum for each check. Decide what counts as confirmed for fit, need, timing, and authority; in plain words, both teams understand.
  3. List the disqualification reasons. Wrong size, no need, no timing, no access to the decision-maker, already under contract. A fixed list makes reporting possible.
  4. Review it every quarter. Compare SQLs that became opportunities with those that did not, and tighten the definition where it lets weak leads through.

Get sales leadership and marketing leadership to sign the final version. A definition only one team agrees with will not hold.

How Do You Know Your SQLs Are Good?

Track these four numbers every month:

  • SQL-to-opportunity rate: the share of SQLs that become real opportunities.
  • Account executive acceptance: how often the AE agrees with the SDR’s SQL call after the first meeting.
  • Win rate on SQL-sourced deals: whether qualified deals actually close.
  • Top disqualification reasons: if one reason keeps coming up, fix it earlier in the funnel.

A falling SQL-to-opportunity rate is the earliest warning. It usually means the definition has loosened, or SDRs are under pressure to hit an SQL number.

How ColedaB2B Qualifies Leads Before Delivery

As a partner, we qualify leads against the criteria your team sets, including BANT where you need it. No lead is qualified without an opt-in, and every lead is checked by a person before delivery, alongside automated data checks. Your team receives leads with the qualification notes already attached, so the first sales call starts where ours ended.

Want to see how qualified leads arrive? We will share a sample lead file with the fields, qualification notes, and checks your team would receive.

Request a sample lead file

FAQs:

What makes a lead sales qualified?

A lead is sales qualified when sales confirms, in conversation, that the company fits your profile and the buyer has a real need, a reason to act soon, and access to the decision.

Is an SQL the same as a BANT lead?

Not always. A BANT lead meets budget, authority, need, and timing criteria, often confirmed by a qualification call. An SQL is whatever your own definition says, which may use BANT or a different checklist.

Who should qualify for SQLs, marketing, or sales?

Sales, or a sales development team working for sales. Marketing qualifies MQLs from data and behavior, but only a conversation can confirm an SQL.

How do you track SQL quality over time?

Watch the SQL-to-opportunity rate, how often account executives accept SQLs, and the win rate on SQL-sourced deals. Review the top disqualification reasons each month.

Can you buy sales-qualified leads?

Yes. Some partners, including our sales-qualified leads program, deliver leads already qualified against your criteria. Ask to see a sample file and the qualification notes before you sign.