The boilr Agent is live Read now→

An SQL is ready for the real conversation.

Fit confirmed, signal live, worth a direct approach.

A Sales Qualified Lead has cleared ICP fit and shows a real reason to talk now, so the next move is outreach, not more research.

recruiter-lexikon / sales-qualified-lead
S
SQL
Sales Qualified Lead
Defined
Definition

A lead that has been reviewed against your ICP and buying signals and accepted as ready for active, direct pursuit, rather than further research or qualification.

At a glance
Term Sales Qualified Lead
Used for Deciding what gets worked, not just seen
In boilr What a verified task already is
b
boilr turns this term into a task
Defined here · operationalised by your AI employee

SQL, explained for the desk.

What it is, why it matters, and how your AI employee runs it.

What it is

A Sales Qualified Lead (SQL) is a lead that has been checked against your criteria, industry, size, role type, buying signal, and judged ready for direct, active pursuit rather than further vetting. The term comes from the wider B2B sales world, where it marks the handover point between marketing's "this looks promising" and sales' "I've checked, this is real." Recruitment agencies rarely run a separate marketing function, so on most desks the qualifying step collapses into one moment: a consultant, or the system working on their behalf, reviews an account and decides it is worth a message today.

An SQL is not the same as a raw name on a target list, and it is not the same as an ICP match on its own. A company can fit your ICP perfectly and still not be an SQL if nothing points to timing, no signal, no mandate, no reason to believe now is the moment. An SQL adds the second ingredient: the lead is not just a fit, it is a fit with a live reason to act.

An ICP match tells you the company fits. An SQL tells you now is the moment to say so.

Why it matters

Treating every ICP-matched account the same way wastes the one resource a desk cannot buy more of: consultant attention. A list of five hundred companies that merely fit the profile tells a consultant nothing about which twenty to call this week. Separating SQLs out gives the desk a working queue instead of a research project, and it protects the ICP-matched accounts that are not yet SQLs from being contacted too early, with no real hook.

It also changes how a desk measures itself. Counting ICP matches tells you how big your market is. Counting SQLs, and tracking how many become placements, tells you whether your targeting and timing actually work. A desk that only ever looks at the top of the funnel has no way to see where good leads are being lost.

How boilr handles it

In boilr, a lead only reaches your task inbox once it has effectively become an SQL: it matches your ICP, it carries a buying signal or a confirmed reason to approach, and the decision-maker is identified and enriched. Your AI sales employee does the qualifying work that a sales development rep would otherwise do by hand, continuously, across every company it watches, not just the ones a consultant happens to glance at.

You see the result as a ready-to-send task rather than a list to triage. You verify the account, the contact and the message, and you send it, in the Company Brain's language. That review step is what keeps the human judgement in the loop, while the volume of accounts actually assessed each day is far higher than any desk could manage checking leads one at a time by hand.

Questions, answered.

Everything a working consultant asks about sql, and how boilr puts it to work.

What is the difference between an SQL and an MQL?

An MQL (marketing qualified lead) is a lead that fits the target profile and shows some engagement, but has not yet been checked by anyone responsible for working it directly. An SQL has been reviewed and accepted for active pursuit, the flag that, yes, this is worth a real approach now. Most recruitment desks skip the MQL stage entirely, since there is rarely a separate marketing team doing the first pass.

Is every ICP match automatically an SQL?

No. ICP fit is necessary but not sufficient. A company can match your profile exactly and still sit as an unqualified lead if there is no signal, no mandate and no timing reason to approach it yet. An SQL needs both: the right kind of company, and a live reason this is the moment to talk to them.

Who decides whether a lead becomes an SQL?

Traditionally a sales development rep or the consultant themselves, after a quick review against agreed criteria: fit, authority, need, timing. The point of making the criteria explicit is that the decision does not have to live in one person's head, and it can be applied the same way whether a human or a system makes the first pass.

How do I know if my SQL-to-placement rate is healthy?

Track it over time against your own desk rather than an industry benchmark, since role mix and desk maturity change what "healthy" means. What matters more than the absolute number is the trend: if SQL volume rises but placements do not follow, the qualifying bar is too loose; if SQLs are rare but almost always convert, you can afford to widen it.

How does boilr use SQL in practice?

boilr qualifies leads to SQL standard before they ever reach your task inbox: ICP fit checked, a buying signal or clear reason to approach attached, and the right contact enriched. You are not deciding which leads deserve a look, you are reviewing and sending ones that already cleared that bar, which is what keeps a daily session down to a focused few minutes.

Helen Wright
Boilr gave us the BD structure and follow-up support to sign our first client and secure a job brief in under a month.
Helen Wright
Managing Director, 923 Jobs

Stop qualifying leads by hand. Review SQLs instead.

boilr qualifies every lead against your ICP and live buying signals before it reaches you, so your task inbox is already a queue of real, ready-to-send opportunities. One AI sales employee per consultant.