Cost per SQL: calculation, method and quality management

The cost per SQL measures the marketing budget spent to generate a Sales Qualified Lead, that is to say a lead considered sufficiently relevant to be worked on by the sales team.

The formula is simple:

```text
Coût par SQL = budget dépensé / nombre de SQL générés
```

Example: if a campaign spends €4,000 and produces 40 SQLs, the cost per SQL is €100.

But the really important part isn't the division. This is the definition of SQL. If no one agrees on what an SQL is, your cost per SQL becomes a number in a suit: it looks serious, but it may be fuzzy.

Before calculating, you need to clarify the steps.

A SQL is not just a lead that clicked on the right campaign. It must correspond to sales criteria: need, fit, timing, decision-making capacity or credible next action.

This is why the cost per SQL is more demanding than the CPL. It prevents you from celebrating a volume that tires the dirty ones.

Cost per SQL forces channels to be compared on their ability to produce useful business work.

Let's take two campaigns:

If you are flying CPL, Campaign A looks better. If you pilot with SQL, campaign B becomes more interesting.

This is the kind of table that avoids bad discussions. The CPL is not false, it is incomplete. It measures the price of the contact, not the value of the conversation signal.

The first mistake is qualifying too early. If your SQL definition is too lightweight, the KPI looks like a renamed CPL.

The second mistake is qualifying too late. If you wait for a very advanced opportunity to count an SQL, you are mixing sales qualification and pipeline.

The third mistake is forgetting the processing time. A lead can be good at the start and deteriorate if support comes too late. The cost per SQL must therefore be read with the contact rate and the speed-to-lead.

The fourth mistake is comparing channels without looking at intent. A channel can produce less SQL but better value, or more SQL but less closing. The KPI guides the discussion, it does not replace judgment.

For an ad agency, the cost per SQL is particularly interesting. It allows you to move away from platform reporting and talk business with the client.

Instead of only showing impressions, clicks, CPLs and conversions, the agency can show:

• how many leads were deemed exploitable;
• which channels produce the best SQL;
• which campaigns generate volume but little quality;
• where the funnel loses the most value;
• what actions can improve the pipeline without increasing the budget.

It's also a good bridge to Qualification KPIs. An agency that knows how to speak SQL, qualified appointments and cost per opportunity becomes more difficult to compare to an agency that “runs campaigns”.

Formlyy helps create the signal that makes cost per SQL measurable: conversational qualification, CRM context, lead prioritisation, appointment progress and status tracking. For agencies, the Formlyy agency offer places this KPI inside a multi-client model measured beyond CPL.

This logic naturally connects to cost per qualified lead and cost per qualified appointment. SQL is not a very serious island in the middle of CRM. It is a step in the chain that transforms acquisition, qualification and appointments into measurable revenue.

Without this layer, many teams get stuck between two numbers: CPL on the acquisition side and revenue on the business side. Cost per SQL serves as a bridge between the two.

The question is not: “Which is the cheapest lead?”

The question becomes: which source produces the most truly workable leads at an acceptable cost?