Sales qualified leads are buyers ready to talk now

Salesforce, citing Studio Science, defines sales qualified leads as leads that have expressed interest in your offerings and are ready to talk with your team. On paper that's a low bar. In practice it's a high one. Interest is easy to collect. Readiness to talk takes judgement.

The marketing qualified lead (MQL) sits one step earlier. Marketing has qualified it, and sales then decides which MQLs become SQLs and get a follow-up. Salesforce's March 2024 guide describes that handoff: a list of leads arrives, many names are already marked by marketing, and the rep sorts the MQLs into SQLs. The split of work is the whole point. Marketing narrows the field. Sales spends its calls.

HubSpot's 2025 Sales Trends Report describes qualification as an evaluation of a prospect's fit, buying readiness and likelihood to become a customer. Those are separate tests. A lead can pass one and fail another. A company can match your profile exactly and have no plan to buy this year. Another can be eager and still be the wrong size or in the wrong market to ever become a customer.

So here's where the simple definition does not hold. Fit alone does not make an SQL. If a company matches your profile but has shown no sign it wants to talk, it's an MQL at best. Calling it early spends a rep's time on a conversation the buyer hasn't asked for.

That gives you a decision to make before anything else. Write down, in one sentence, what makes a lead ready to talk in your business. It might be a reply to an email, a form fill, or a return to your pricing page. Pick the signals first, then argue about scores. Without that sentence, sales and marketing will each use their own meaning of SQL, and the handoff Salesforce describes turns into an argument.

Salesforce's State of Sales Report finds that reps spend only 28% of their week actually selling. The rest goes on everything else. Every call a rep makes to a weak lead comes out of that 28%.

The same research finds that 69% of sales professionals agree their jobs are harder now. They're under enormous pressure to hit targets. Salesforce's lead qualification guide, from March 2024, draws the obvious conclusion: sales teams need to focus on the highest quality leads to make their numbers. That's the case for a strict SQL test. A loose one fills the calendar with calls that go nowhere.

There's also a split in how good the leads feel. HubSpot's 2025 Sales Trends Report found that 73% of salespeople rate their marketing leads as high or very high quality. Another 27% say they need better-quality leads from marketing. So most reps aren't unhappy with what marketing sends. Still, more than a quarter want better.

Handle that split with care. It's opinion from a survey. It does not measure how many of those leads closed, and it can't tell you which group is right. A rep can rate a lead as high quality and still lose the deal. Quoting 73% to defend your current process is as weak as quoting 27% to attack it.

There's a trade-off too, and it's an uncomfortable one. A strict filter means fewer leads reach sales, and some real buyers will be left out. If your team has little pipeline to begin with, a tight rule can starve the reps instead of protecting them. In that case loosen the test a little and watch what happens on calls.

What you can do this week: ask your reps which leads they dropped last quarter and why. Their answers are a better rule-book than any survey average. Put the top reasons next to your SQL sentence and see whether the two agree.

The ranking guides on SQLs all start from the lead: a form fill, an answered question, a score. Your own site holds an earlier signal that they leave out. It shows which companies came to you, which pages they read, and when they came back. Read it by company, never by person. The useful question is which accounts returned across separate visits.

Start with the order of pages. Here's an illustration, not a result. Company A reads one blog post and leaves. Company B reads your docs, returns on another day to read pricing, then later opens a comparison page. Company B is doing what a buyer does when the question changes from "what is this" to "is this the right one". Company A is doing research. An account that moves from docs to pricing or to a comparison page may be closer to a decision than one that only read a blog post. None of the sources in hand measured that, so treat it as a hypothesis and test it against your own sales outcomes.

Repeat returns are the second thing to read. One long visit can be a single sitting of curiosity, or a tab left open. Coming back on a different day takes a second decision to spend time on you. A return on separate days is a stronger pattern than one long visit. This is a hypothesis too, and the check is simple: do the companies that returned reach a conversation more often than the ones that didn't?

The signal names the account, so it can be routed. A company that's already a customer, or already in an open deal, goes to the account owner. A new company goes to whoever works new accounts. Then sales does the part no page view can do: it asks. That's what turns a company visit into an SQL under the Salesforce definition. The visit gets a rep to the door. The conversation decides.

Now the cases where this misleads you. A company visit can come from a competitor, a partner, a researcher or a job candidate. A visit is not intent until sales confirms it on a call. And the reading works the same way for a US team and an Indian team. What differs is how much traffic each site has and which privacy rules apply, which the next section covers.

Decide which pages mean "evaluating" on your own site. Pricing, a comparison page and docs are the obvious candidates. Write the list down before you look at any data, so you don't fit the list to the answer.

The strongest case against scoring is a plain one. A prospect can answer every qualifying question well and still not be a fit. They say the right things on the call, they have a budget line, and they still never become a customer. That's HubSpot's point about fit, readiness and likelihood being separate tests. A good answer to one of them is not a pass on all three.

Visit data has its own failure, and you should say so plainly before you start. A site with little traffic rarely shows the same company twice. The method then finds nothing. If your pages get a trickle of visits, "came back on separate days" will describe almost no one, and the list will be empty or made of noise. In that case, stay with the questions and the form fills. Don't invent a pattern from three or four rows.

Country is the next gap. The sources in hand do not split qualification data by country, so there's no stat here on how a US team differs from an Indian one. What you can say is that both should check which privacy rules apply to visitor data in their own market before acting on a list. These sources are not a source for law, so that check belongs with your own legal review. Do it before the list reaches a rep, not after.

There's an exception to all this, and it's about humility. When a company list keeps proving wrong on calls, drop the rule and go back to the questions. A method that sends reps to the wrong account is worse than no method. It costs a slice of the 28% of the week that reps actually spend selling.

So hold both tools at once. Questions tell you what a prospect says. Visits tell you what an account did on its own, without being asked. Each can be wrong. When they agree, you have your strongest lead. When they disagree, call anyway, but let the call settle it.

You don't need a new tool or a big project to test this. You need a list of companies that visited, a note of the pages they read, and the next round of calls. Here's the method.

1. Export a list of companies that visited your site over a window long enough to show repeat returns.
2. Keep only companies that came back on separate days. Drop single visits.
3. For each one left, note the pages it read and in what order: docs, pricing, a comparison page.
4. Remove competitors, partners, researchers, job candidates and existing customers you already know.
5. Mark the rest as priority or not, and route each priority company to its account owner.
6. After the calls, compare. Did the marked companies reach a conversation more often than the rest?

The last step is the one that matters. Keep the rule only if the marked companies did better. If they didn't, you've lost a week and learned something real, which is cheaper than building outbound on a guess.

This does not work when your traffic is too low. If step 2 leaves you with a handful of companies, you can't tell a pattern from luck. Wait, widen the window, or put the effort into the questions your reps ask. And if the check works in the US market but your Indian traffic is thin, or the other way round, run it for each market separately. Don't blend them into one list and call it proof.

PageFox is the wrong choice for a site with little traffic: it tells you which companies are already visiting, it does not bring new visitors.

Decide what makes a lead ready to talk in your business, and write it down as one rule that sales and marketing both sign. Then pull the companies that visited your site, keep the ones that came back on separate days, and check them against your next round of sales calls.