Software Growth

SQL (Sales qualified lead)

An SQL is a lead that sales has vetted and accepted as a real opportunity worth active selling time, based on need, budget and buying intent.

A sales qualified lead is a prospect that someone on the sales side has looked at and decided is worth a real conversation, a demo and a proposal. Where a marketing qualified lead is "interested and a good fit," an SQL is "likely to buy, and we are going to work on it." HubSpot describes the difference as sales readiness: an MQL is still exploring, an SQL has shown buying signals that justify active selling.

For a founder, the SQL is the first number you can reasonably tie to revenue. Everything before it is guessing about interest. Once a lead is an SQL, you can attach a close rate, a deal size and a sales cycle to it.

How leads become SQLs

The handoff usually happens when a lead does something that signals intent, such as requesting a demo, replying to outreach, or visiting the pricing page several times, and then passes a short qualification check. Many teams use some version of BANT (budget, authority, need, timing). Others ask simpler questions:

  • Do they have the problem you solve, and is it painful enough to act on this quarter?
  • Can the person you are talking to buy, or introduce you to someone who can?
  • Does the price fit their situation?
  • Is there a realistic timeline?

If the answer to most of these is yes, the lead becomes an SQL and gets a deal in your CRM. If not, it goes back to nurturing, with a note on why.

How to calculate the SQL conversion rate

Track two rates. The first is how many MQLs sales accepts. The second, which matters more, is how many SQLs become customers.

Suppose you create 50 SQLs in a quarter and close 10 of them. That is 10 / 50 = 20%. With an average first-year contract of $6,000, those SQLs produced $60,000 in new annual contract value, or $1,200 per SQL. If each SQL costs you 3 hours of selling time, you can see quickly whether a 20% rate pays for your time. This is the same number that feeds win rate and sales velocity.

HubSpot's guide says a healthy MQL-to-SQL rate generally sits between 10% and 20%, with B2B SaaS around 13%. Those are HubSpot's figures. Your SQL-to-customer rate depends heavily on price and market, so benchmark yourself against your last four quarters instead.

Common mistakes

  • Letting SQL mean "anyone who booked a call." A free demo with a student is not a qualified lead. Write the criteria down.
  • Disagreement between teams. If marketing sends 100 MQLs and sales accepts 3, the definition is broken, not the people. Review rejected leads together and reasons.
  • No timestamp. Record when each lead became an SQL, otherwise you cannot measure the sales cycle from that point.
  • Skipping the stage. In self-serve products, users pay without a sales conversation, so there are no SQLs for most revenue. That is fine.

For small teams

If you are the only person selling, you are marketing and sales. You do not need two stages, but you still benefit from one clear line: a lead is an SQL when you would spend an hour on a call with them. Count those, and track how many close. Once you have that number for a few months, you can forecast with it.

Sources

Back to the SaaS glossary