What are cost per SQL and pipeline-to-spend, and how do you calculate them?
Cost per SQL is total program spend divided by the number of sales-qualified leads created in the period. Pipeline-to-spend is the pipeline value created in the period divided by the same spend, shown as a ratio. Use both with the same definition of spend and the same stage definitions, read them by account tier and channel, and treat them as lagging measures that need a sales-cycle-aware window.
Key takeaways
The formulas
| Metric | Formula | Question it answers |
|---|---|---|
| Cost per SQL | Program spend / SQLs created in the period | What does a sales-qualified lead cost us? |
| Cost per opportunity | Program spend / opportunities created | What does a real sales opportunity cost us? |
| Pipeline-to-spend | Pipeline value created / program spend | How much pipeline did each dollar create? |
| Closed-won to spend | Closed-won revenue / program spend | How much revenue did each dollar return, after the cycle completes? |
Worked example, hypothetical numbers only: $60,000 of spend that produced 20 SQLs and $450,000 of pipeline gives a cost per SQL of $3,000 and a pipeline-to-spend ratio of 7.5.
What to include in spend
Leaving fees and tools out makes the ratio look better and loses the trust of finance. Pick one definition and keep it for every report.
- Media across LinkedIn, Google, Microsoft and ABM platforms
- Agency or management fees
- Tools and platform licences used by the program
- Creative and content production attributed to the program
We fix source data, routing and attribution so sales and finance trust the numbers.
Define the stages first
An SQL is only comparable across months if marketing and sales agree what qualifies it. The same applies to an opportunity and to pipeline value, such as whether it is the deal amount at creation or at a later stage.
Write the definitions into your CRM fields and keep them stable. Our guide to MQL, SAL, SQL and SQO definitions covers how to set them.
Read them by account tier and channel
A blended number hides the story. Tier 1 accounts usually cost more per SQL because the audience is narrow and the offer is more tailored, yet they can produce the largest deals. Report each tier and each channel separately and decide budget on pipeline-to-spend within the tier.
Common mistakes
- Using a window shorter than the sales cycle, so pipeline appears to lag spend
- Counting influenced pipeline as created pipeline
- Changing stage definitions mid-year
- Comparing channels with different attribution rules
We report cost per SQL and pipeline-to-spend from the CRM for every revenue program. If you want to see how that would look on your data, book a free pipeline plan.
Frequently asked questions
How do you calculate cost per SQL?
Divide total program spend by the number of sales-qualified leads created in the same period, using one agreed definition of SQL.
What is pipeline-to-spend?
The pipeline value created in a period divided by the spend in that period, expressed as a ratio such as 7.5 to 1.
Is cost per SQL better than cost per lead?
For enterprise B2B, yes, because it reflects sales qualification rather than form fills. Cost per opportunity and pipeline-to-spend go a step further.
Related service: RevOps and marketing operations. See also pricing and client results.
We run enterprise B2B demand generation for teams in Montreal, Toronto, Ottawa and the United States.