Sales qualified lead (SQL) is an organisation’s label for a potential customer accepted for sales follow-up. Define what your team needs to confirm before assigning it, and keep the supporting information with the decision.
Explain what the label means
In HubSpot’s documentation, MQL is marketing-qualified for sales, SQL is a sales-qualified potential customer, and Opportunity means association with a deal.
HubSpot also permits customised lifecycle stages. When using these terms, record your team’s definitions rather than assuming another organisation uses the same boundary. Keep the qualification decision separate from a purchase commitment.
State the acceptance criterion
Write the condition your team needs to confirm before assigning SQL status. Identify the information that would support that decision and who will review it. A criterion such as “interested” needs more explanation: what did the person say or request that makes this a suitable sales follow-up?
Choose criteria for the actual service and sales process. A requested conversation can provide a reason to ask a clarifying question while the buyer’s budget or purchasing commitment remains unknown. Avoid filling those gaps from a job title or a page visit.
A fictional acceptance review
Imagine an unnamed label-printing team receiving this invented enquiry: “Can we discuss printing labels for our products?” For this illustration, the team has chosen the following local rule.
Sales accepts a lead when the intended use is clear and the requester wants a discussion.
| Criterion or decision | Fictional record | Review finding |
|---|---|---|
| Requested discussion | Requested. | Supported by the enquiry. |
| Intended use | Not described. | Still needed. |
| Acceptance decision | Pending. | Reviewer asks about intended use. |
Under this fictional rule, the enquiry supports the discussion element but leaves the use requirement unresolved. The reviewer would ask what the labels are for before deciding whether the criterion is met. No qualification or sale is completed in this illustration.
Keep the evidence with the decision
Save the relevant enquiry or conversation note with the qualification record. Distinguish the person’s statement from your interpretation. If someone describes a need, note that description; if you believe the service fits, explain the basis and identify any detail that still needs checking.
When a required fact is missing, record the gap and the next question. In the example, a note saying “intended use not confirmed” explains the pending decision more clearly than a status field alone. Choose a follow-up that addresses the enquiry rather than adding unrelated sales messages.
Review the decision when information changes
A status change should be explainable from the information behind it. If the team changes its criterion, record which version governed an earlier decision before comparing the records. A different count of SQLs could reflect a different definition; investigate that change before calling it a change in buyer readiness.
Use the right related view
Buyer Journey helps investigate purchase questions. Conversion Funnel covers ordered counts and rates with declared denominators. Here, the task is to explain why a particular lead was accepted for sales follow-up or why that decision remains pending.
Sources
HubSpot documents these lifecycle labels. The chosen rule, enquiry and acceptance worksheet are editorial illustrations, not a validated qualification model or an account test.