A lead vetted by sales as ready for direct deal conversation because they meet ICP criteria and have shown buying urgency or intent.
A Sales Qualified Lead (SQL) is a prospect who has passed through marketing vetting and sales qualification — they fit your Ideal Customer Profile (ICP), have been verified as a real contact, and show credible signals of buying intent or timeline.
The SQL is where accountability transfers from marketing to sales. Marketing hands off an MQL (Marketing Qualified Lead) — someone who met engagement thresholds. Sales then makes the phone call, runs a qualification conversation, and either upgrades them to SQL status or disqualifies them. That SQL gets routed to an AE or working account.
An AE handling an inbound SQLs has already won the opening. The prospect knocked on the door, marketing confirmed they fit the company's standard, and they're in the call because sales confirmed they have a problem worth solving right now.
Your job in that call: confirm the buying timeline is real, not just "interesting in theory." Ask when they'd expect implementation or when budget gets approved. If they say "someday" or "next fiscal year," they may be MQL-level interest re-labeled as SQL. Downgrade and move on. Real SQLs have a calendar reason for talking to you in the next 60 days.
Contrast this with a cold outbound prospect you found yourself. That person hasn't self-identified as ready yet. Your discovery call earns them SQL status after you prove they have a budget, a timeline, and a business reason to act. The label flips during the call, not before it.
| Term | Who decides | When it happens | Your move |
|---|---|---|---|
| Lead | Database or list | Name enters your system | Verify it's real; check domain and title |
| MQL | Marketing, based on engagement | Prospect hits a threshold (form fill, email opens, demo request) | Hand to sales; sales decides if worth calling |
| SQL | Sales, after a conversation | Rep confirms ICP fit + buying intent + real timeline | Route to AE; build the deal |
An MQL might be a CFO at a 100-person tech company who downloaded a whitepaper. But they downloaded it at 11 p.m. on a Friday, they're not the buyer for your product, and they've never replied to outreach. Marketing's threshold was met; sales' reality check is not.
An SQL is that same CFO after you called her, asked why she downloaded it, and she said her CEO is frustrated with current vendor and wants to talk in Q2 when the renewal cycle starts. Now it's real.
Sales and marketing disagree on what makes someone SQL-ready because they never defined it together. Marketing thinks engagement is enough. Sales thinks only a confirmed budget counts. Meanwhile, a prospect sits in limbo or gets called too early by an AE who isn't ready yet.
Fix this with a simple monthly 30-minute sync: review the last batch of SQLs together. Marketing explains why they marked each one as MQL. Sales explains which ones were actually ready and which ones were false positives. Adjust the MQL-to-SQL criteria based on what actually converted.
The most common definition drift: Marketing classifies a demo request as SQL. Sales spends two hours prepping, gets on the call, and discovers the prospect was just kicking tires. SQL threshold should require either a business problem statement from the prospect or confirmation they control budget. Demo request alone isn't enough.
An MQL is a prospect marketing has deemed engaged enough to pass to sales based on behavioural signals like form fills or email clicks. An SQL is that same prospect after a sales rep has confirmed they fit your ideal profile, have budget, and have a real timeline to buy.
The sales rep who qualifies it does. Marketing creates the MQL tag; sales makes the SQL decision after a conversation confirms buying intent and ICP fit. Without that conversation, there's no SQL.
Yes. If a prospect inbounds directly with a specific problem and buying signal—like requesting a demo with budget details—sales can classify them as SQL without a prior marketing touch.
It controls resource allocation. An AE on a true SQL has much higher close odds than on a lead that was marked SQL in error. Accurate classification makes pipeline forecasts predictable and prevents reps from chasing false positives.
Part of our guide to Discovery calls.
Repwing listens to your discovery calls and puts the next question on your phone while you are still in the conversation. Fourteen days free, no card.
Start free trial