Need help with B2B Marketing?
Let the smarketers’ team drive your pipeline with data-led campaigns and AI-powered growth strategies.
Cost per SQL is your marketing spend divided by the sales-qualified leads it produces in the same period, and the figure means nothing until you attach it to an average contract value and a sales cycle. A $2,000 cost per sales qualified lead is efficient at $500,000 ACV and ruinous at $20,000 ACV. That relationship explains why cross-industry lead cost benchmarks mislead so consistently, and why the only number worth managing to is the one your own margin structure allows.
What follows builds that number from inputs you already have.
How do you calculate cost per SQL?
Cost per SQL equals total marketing spend for a period divided by the SQLs created in that period. It also equals cost per MQL divided by your MQL to SQL conversion rate, so a $300 MQL converting at 20% costs $1,500 per SQL. The harder question is what ceiling your margins allow, which the model below answers.
Why do published cost per SQL benchmarks mislead?
Most published figures average across companies whose economics have nothing in common. A benchmark mixing a $12,000 ACV product with a $1.2M enterprise platform produces a mean that describes neither.
Underneath that sits definition drift. One company counts an SQL when a rep accepts a lead, another when a discovery call is booked, a third when that call is completed and qualified against a framework. Those definitions differ in volume by a factor of two to three, which moves cost per SQL by the same factor without anything real changing.
STAT
The average B2B buying decision now involves 13 internal stakeholders and 9 external influencers, and buyers use an average of seven information sources. Sources: Forrester, State of Business Buying, January 2026; Gartner, May 2026.
More stakeholders and more sources means more touches per qualified opportunity, which pushes cost per SQL up in a way older benchmarks do not reflect.
Published medians for the same year show how far apart these figures sit:
| Source and date | Reported median cost per SQL | Scope |
|---|---|---|
| Demand Gen Report Benchmark Survey, 2024 | $612 | B2B programs across ACV bands |
| Directive Consulting B2B SaaS Benchmark Report, 2024 | $762 | B2B SaaS, 312 accounts |
| First Page Sage B2B Lead Generation Benchmarks Report, 2024 | $1,357 | Surveyed North American B2B companies |
Same year, same metric, a spread of more than 2x. The gap comes from sample mix and definitions, not from performance.
How do you calculate a good cost per SQL for your business?
Derive the ceiling from your own margin instead of hunting for a benchmark. Four steps, ten minutes.
- First-year gross profit per customer equals ACV multiplied by gross margin.
- Allowable customer acquisition cost equals that gross profit divided by your target CAC payback period, expressed in years (12 months = 1).
- Marketing’s allowable share equals allowable CAC multiplied by marketing’s share of total acquisition cost.
- Allowable cost per SQL equals marketing’s allowable share multiplied by your SQL to closed-won rate.
In one line: allowable cost per SQL = (ACV × gross margin ÷ payback period in years) × marketing share of CAC × SQL to closed-won rate.
Across four ACV bands at a twelve-month payback target, the model gives this:
| Input | Under $25K | $25K to $100K | $100K to $500K | $500K plus |
|---|---|---|---|---|
| Example ACV | $15,000 | $60,000 | $250,000 | $900,000 |
| Gross margin | 80% | 75% | 70% | 65% |
| First-year gross profit | $12,000 | $45,000 | $175,000 | $585,000 |
| Allowable CAC (12-month payback) | $12,000 | $45,000 | $175,000 | $585,000 |
| Marketing share of CAC | 50% | 45% | 40% | 35% |
| Marketing allowable CAC | $6,000 | $20,250 | $70,000 | $204,750 |
| SQL to closed-won rate | 25% | 22% | 20% | 15% |
| Allowable cost per SQL | $1,500 | $4,455 | $14,000 | $30,713 |
Those are not survey results. They are outputs of the four steps using illustrative inputs, and the point is that you replace every row with your own. Our customer acquisition cost calculator runs the same arithmetic.
Note the direction of travel: allowable cost per SQL rises roughly twentyfold across the bands while gross margin falls. That is why a programme that looks wasteful in one band is underfunded in another.
Why does cost per SQL vary by B2B vertical?
Vertical variation is real, but it comes from four mechanics rather than from anything inherent to the industry label.
| Mechanic | Effect on cost per SQL | Verticals where it bites hardest |
|---|---|---|
| Regulatory content burden | Raises cost of every asset and adds review cycles | Life sciences, financial services, healthcare technology |
| Committee size | More roles to reach before qualification | Enterprise software, industrial capital equipment |
| Auction density | Paid media unit costs rise with competitor count | Cybersecurity, HR technology, martech |
| Sales-assist requirement | Qualification needs a technical resource, not a form | Systems integration, manufacturing services |
Before using any published cost per SQL benchmark, ask what SQL definition it uses and what ACV range the sample covers. Without both it is not usable. In our own B2B SaaS demand generation engagements across 2024 and 2025, cost per SQL ran between $420 and $1,860, lower for product-led motions and higher for enterprise sales-led ones. Those are actuals. The model above gives a ceiling, and the gap between the two is your headroom.
How does channel mix affect cost per SQL?
Channel mix explains more variance between two similar companies than vertical does. Each channel in your B2B lead generation mix has its own cost shape and qualification rate.
| Channel | Cost behaviour | Effect on cost per SQL | Hidden cost |
|---|---|---|---|
| Paid search | Rises with competitor bids | Low at high intent, steep at scale | Brand term defence |
| Paid social | Falls with creative quality | Mid, lower qualification | Creative refresh |
| Content and organic | Fixed build, near zero marginal | Lowest after 9 to 12 months | Slow first result |
| Events and field | Fixed per event | Highest, best downstream conversion | Uncounted staff time |
| Outbound and ABM | Scales with headcount | High, aimed at named accounts | Data and enrichment |
The common mistake is comparing paid search cost per SQL to organic and concluding organic is cheaper. Organic looks cheaper because its build cost was expensed in an earlier quarter. Amortise the content investment across twelve months of SQLs before comparing.
How does sales cycle length raise cost per SQL?
A longer cycle means more touches and more months of media before the same SQL converts. Model it as a carry cost.
| Input | Short cycle | Long cycle |
|---|---|---|
| Months from first touch to SQL | 2 | 9 |
| Nurture touches required | 6 | 22 |
| Cost per touch across content and media | $40 | $40 |
| Nurture cost carried per SQL | $240 | $880 |
| Re-engagement of stalled records | Minimal | Adds roughly 20% |
Carry cost is why cutting a programme mid-cycle looks like a saving and is not. You keep the spend already sunk into month five contacts and lose the conversion due in month nine.
PROOF POINT
Eclat Health cut cost per lead from $5 to $1.82, a 63.6% reduction, alongside a 200% traffic increase. In a higher-ACV motion, KeyReply moved cost per lead from $75 to $51.86 and lifted click-through from 2% to 4.43%. These are cost per lead results, not cost per SQL, but the mechanism carries through: better qualification upstream, not cheaper clicks.
What can cost per SQL benchmarks tell you, and what can't they?
Cost per SQL benchmarks are useful for direction and useless as targets. A benchmark can tell you that paid social generally qualifies at a lower rate than paid search, which is worth knowing. It cannot tell you what your cost per SQL should be, because it does not know your margin, your definitions or your cycle.
Three questions expose whether a published figure is worth reading. How large is the sample and how is it distributed across ACV? What definition of qualified applies? Is it a mean or a median, and if a mean, what happened to the outliers?
How do you set a cost per SQL baseline in 30 days?
We did this for a manufacturing services client whose reported cost per lead had swung between $90 and $400 across four quarters. The swing was definitional: two teams were marking lifecycle stages differently in the same portal. Once we fixed the stage definitions and rebuilt the RevOps reporting, roughly a third of the variance disappeared without any change to spend.
- Write one shared SQL definition and get sales to sign it. One sentence, one owner, one system of record.
- Timestamp lifecycle stage transitions so you can measure cycle length, not just volume.
- Attribute cost by channel including internal time, at a stated hourly rate.
- Pull 90 days of history and calculate cost per SQL weekly, so variance is visible.
- Compare the actual against your allowable figure. That gap is the number to manage.
Before you trust the cost figure, check your qualification rate with our MQL to SQL conversion rate calculator.
How do you lower cost per SQL without gaming it?
It falls honestly in three ways: raise the qualification rate, shorten the path to qualification, or raise ACV. It falls dishonestly in one: loosen the SQL definition. The dishonest route is faster and shows in the dashboard immediately, which is why it happens.
Guard against it by always reporting cost per SQL and SQL to closed-won rate on the same chart in your revenue attribution dashboard. A falling cost per SQL beside a falling close rate is a definition change, not efficiency.
When does the allowable cost per SQL model not apply?
The model assumes a twelve-month CAC payback period. Growth-funded businesses often accept eighteen or twenty-four months, which raises the allowable figure sharply, and businesses under cash pressure need less than twelve. Set that input with your CFO rather than accepting the default.
It also assumes a stable gross margin. In services businesses where delivery margin varies by client, the average understates the cost of winning low-margin work, so run the model per service line.
Finally, it says nothing about volume. An allowable $30,713 per SQL does not help if your market contains 200 accounts and you can work 40 a year. In small markets coverage is the constraint, not efficiency.
Frequently Asked Questions
What is a good cost per SQL?
There is no universal figure. Derive your ceiling from margin: first-year gross profit divided by your CAC payback target gives allowable CAC, multiplied by marketing’s share and then by your SQL to closed-won rate gives allowable cost per SQL. Anything below that ceiling is good for your business.
Why do B2B cost per lead and cost per SQL benchmarks vary so widely?
Three reasons. Samples mix wildly different contract values, definitions of qualified differ by a factor of two to three between companies, and most published figures are distorted by outliers. Two companies reporting the same cost per SQL may be measuring different events entirely.
Does cost per SQL rise with contract value?
Yes, and it should. Higher contract values carry more gross profit per customer, which raises the allowable acquisition cost, while longer cycles and larger buying committees raise the real cost of qualification. A high cost per SQL in a high-ACV motion is a sign of correct investment, not waste.
How is cost per SQL different from CAC?
Cost per SQL measures spend divided by qualified leads at one funnel stage. CAC measures total sales and marketing cost divided by new customers won. Cost per SQL is a marketing efficiency metric; CAC is a business metric, and the two connect through your SQL to closed-won rate.
Should internal salaries count in cost per SQL?
Include them whenever you compare in-house against agency, or one channel against another, otherwise the comparison flatters whichever option uses more internal time. Apply a stated loaded hourly rate consistently and report both the media-only and fully loaded figures.
How long does it take to establish a reliable baseline?
About 30 days for instrumentation, then 90 days of history to read it against. The prerequisite is one agreed SQL definition. Without it you are measuring reporting behaviour rather than demand performance, however long you collect data.
How do you calculate cost per SQL from cost per MQL?
Divide cost per MQL by your MQL to SQL conversion rate. A $300 MQL at a 20% conversion rate produces a $1,500 cost per SQL, so a falling conversion rate raises cost per SQL even when media costs hold steady.
Swati Bansal
Sr. Content Strategist
