SQL (sales qualified lead)

How a sales qualified lead works

A sales qualified lead marks the point where a lead becomes a real sales conversation. Salesforce defines it as a lead flagged by a sales team member as likely to convert and ready to progress in the sales process 1. HubSpot's lifecycle model places it right after the marketing qualified lead and defines it as a contact or company that sales has qualified as a potential customer 2.

What changes is who owns the call. A marketing qualified lead is marketing's judgment, based on fit and engagement. An SQL is sales' judgment, usually made after a call or a reply. Salesforce lists qualification through personal contact, usually a call or video meeting, as a common trait of an SQL 1.

Salesforce describes three checks that most sales teams apply 1.

• Fit. The lead looks like customers who have already bought, which is the buyer persona and the ideal customer profile in practice.
• Pain. The lead has a problem the product can solve.
• No blocking gaps. Budget, authority, need and timing are present or credibly on the way.

HubSpot also keeps a separate Lead Status property for the SQL stage, so a team can track whether the lead is new, in progress or connected without changing the lifecycle stage itself 2.

Once a lead is an SQL, the next step is concrete. A rep books a demo, sends a proposal or opens an opportunity. If none of that happens within an agreed window, the lead should go back to nurture with a reason rather than sit in the stage forever.

The SQL count is also the bridge between marketing and sales reporting. Marketing tracks how many of its leads sales accepted, and sales tracks how many accepted leads turned into opportunities and closed deals. When both teams read the same stage, arguments about lead quality turn into a question with an answer, namely which criteria predicted a closed deal and which did not.

What makes the SQL call reliable

The SQL decision is only as good as the evidence behind it. Three practices make it repeatable.

Score readiness to buy above interest. Salesforce suggests assigning points to traits linked to readiness to buy, covering behavior plus geography, role, company size and industry, and including negative scores for leads without adequate budget 1. Its point is that an SQL score should reflect a prospect ready to buy now rather than one still shopping 1. A lead score that mostly counts email clicks will promote curious readers ahead of buyers.

Watch the content a lead consumes. HubSpot notes that leads closer to buying engage with bottom of the funnel content such as pricing pages, case studies, product demos and ROI calculators, while earlier leads read blog posts, guides and webinars 3. HubSpot's shorthand is that an MQL is window shopping while an SQL is asking for the price 3.

Confirm it with a person. Salesforce recommends human contact in the process even when AI tools help with scoring, because a call reveals details about pain points that a score cannot 1.

Write the criteria into required CRM fields. If a rep cannot move a lead to SQL without recording the budget owner and the timeline, the label means the same thing across the team.

Example of a sales qualified lead

Salesforce gives a simple example of the jump from interest to SQL 1. A consulting firm sells to healthcare organizations. Staff from a midsize hospital system attended a webinar and downloaded several white papers, which made them a marketing qualified lead.

After a short call, the rep learns that the hospital has allocated budget for consultants and wants to start preparing for a year-end audit in Q2 1. They are comparing several providers. The fit is right, the need is specific and the budget exists, so the lead becomes an SQL.

A second contact, the CFO of a small community hospital, also downloaded an audit guide. On an email exchange, the CFO says they are still working out whether they can afford a consultant 1. That lead stays a marketing qualified lead and goes back to nurture.

Before the first SQL reaches the CRM, the operations team makes sure the record is usable. An n8n workflow calls the RichAPI email_finder and email_verifier endpoints over HTTP and then writes the contact with n8n's own HubSpot node, because RichAPI has no HubSpot app 4. An IF node on the success field keeps a miss, which returns HTTP 200 with success false, from overwriting a good address with a blank one 4.

On 500 rows at a 60% hit rate, the finder bills 300 found addresses at 5 credits, and the 200 misses cost nothing 4. Verifying the 300 at 2 credits brings the run to 2,100 credits 4.

SQL vs PQL

A product qualified lead is judged by what a person does inside a free trial or free plan. A sales qualified lead is judged by sales after a conversation. Product-led companies often use both, with product usage feeding the sales review.