How to calculate cost per SQL
Cost per SQL moves the efficiency question past raw leads to sales-qualified ones, which are far more predictive of revenue. It filters out the cheap-but-worthless leads that make cost per lead misleading.
It sits between cost per lead and cost per opportunity in the funnel and, like them, is most useful broken out by channel so you can compare where qualified demand comes from most efficiently.
- Spend / SQLs The formula
- Qualified leads Closer to revenue than CPL
- By channel Where to compare
Short answer
Cost per SQL is the average spend to generate one sales-qualified lead. Divide the relevant sales and marketing spend in a period by the number of SQLs generated. If you spent 80,000 dollars and produced 100 SQLs, cost per SQL is 800 dollars. It is sharper than cost per lead because SQLs are qualified and closer to revenue.
Step by step
Total the relevant spend
Sum the sales and marketing spend attributable to demand generation in the period. Be explicit about whether team costs are included.
Count SQLs generated
Count sales-qualified leads produced in the period, using a consistent SQL definition agreed with sales.
Divide spend by SQLs
Cost per SQL equals spend divided by SQLs generated. Break it out by channel to compare efficiency.
Connect to CAC
Combine cost per SQL with SQL-to-customer conversion to estimate demand-gen cost per customer, a major component of fully loaded CAC.
Worked example
Channel A produces leads at 30 dollars each but converts only 5 percent to SQLs, so cost per SQL is 600 dollars. Channel B produces leads at 60 dollars but converts 20 percent to SQLs, so cost per SQL is 300 dollars.
Despite double the cost per lead, Channel B's cost per SQL is half of Channel A's. Optimizing on cost per lead would have sent budget to the worse channel; cost per SQL reveals the truth.
How Ardovo handles it
Ardovo computes cost per SQL by channel and links it to downstream conversion and CAC, so you never optimize for cheap leads that never qualify. Rook flags channels with low cost per lead but high cost per SQL, the classic lead-quality trap.
Frequently asked questions
What is the cost per SQL formula?
Sales and marketing spend in a period divided by the number of sales-qualified leads generated. It is sharper than cost per lead because SQLs are qualified and closer to revenue, filtering out worthless cheap leads.
How is cost per SQL better than cost per lead?
SQLs are qualified and predict revenue far better than raw leads. A channel with cheap leads but few SQLs has a high cost per SQL, exposing a lead-quality problem that cost per lead alone would hide.
How does cost per SQL relate to CAC?
Multiply cost per SQL by the number of SQLs needed to win a customer (1 divided by SQL-to-customer conversion) to estimate demand-gen cost per customer, a major input to fully loaded CAC.