Cost per SQL in Outbound: DACH Benchmark and Formula

The one outbound number that actually steers decisions

Many outbound discussions revolve around reply rates and meeting counts. But the metric that actually matters for the business case is a different one: cost per SQL — what it costs to produce a sales qualified lead, meaning a qualified prospect ready to buy who fits the ICP. This number connects effort and outcome, and it’s what makes different models — in-house SDR, agency, GTM system — comparable in the first place.

This article delivers the honest calculation: which costs really belong in it, what the formula looks like, what orders of magnitude are realistic in the DACH region, and why cost per SQL beats cost per lead. Upfront, the most important warning: there’s no universally valid euro figure. Adopting someone else’s number as a target means measuring yourself against someone else’s reality. Only your own calculation is reliable.

Why cost per SQL, not cost per lead

A lead is just a contact — an email address, a data record. An SQL is a prospect that sales has assessed as worth pursuing. The difference matters because cost per lead can be artificially pushed down through sheer volume: more cheap addresses, more reach, lower cost per lead — at falling quality. In that case, cost per SQL quietly rises, because few of the many cheap leads ever become qualified.

Cost per SQL measures what counts: the fully loaded cost of producing a prospect ready to buy. That’s exactly why it’s harder to game and the better steering metric. And it forces you to take qualification seriously — the step where most outbound programs lose money without noticing. Where that step breaks down is covered in the article on the reply-to-meeting gap in B2B outbound.

The full cost breakdown

The most common mistake is only counting the visible costs — the tool license, the agency retainer. The real cost per SQL contains four blocks:

Cost block	What belongs in it	Often forgotten
Data	enrichment, lists, verification, signals	data quality drives the rate
Tools	sending infrastructure, sequencing, CRM, warmup	multiple tools add up
Personnel / agency	SDR salary + overhead, or retainer + margin	overhead, management, downtime
Time / build	ramp-up, setup, playbook development	biggest hidden item

The fourth block especially — build and ramp-up time — is almost always underestimated. A new SDR isn’t productive from day one; the first months carry a high cost per SQL that only falls with the learning curve. A detailed breakdown of these items for SaaS is provided in the article on outbound costs for SaaS.

The formula

The calculation itself is simple — the art lies in honestly capturing all the costs:

Cost per SQL  =  fully loaded costs of a period
                 ─────────────────────────────
                 number of SQLs in that period

An illustrative example calculation (freely chosen numbers, not a benchmark):

• Full monthly costs: data €800 + tools €600 + SDR (fully loaded) €7,500 + prorated build time €1,100 = €10,000
• SQLs per month: 20
• Cost per SQL: €10,000 / 20 = €500

Whether €500 is good or bad is decided entirely by the deal value: at €2,000 ACV that’s ruinous, at €30,000 ACV it’s excellent. That’s why cost per SQL should never be assessed in isolation, but always relative to the contribution margin of a closed deal.

The four models compared on cost

Cost structure differs fundamentally by model:

Model	Cost profile	Learning curve	What remains at the end
In-house SDR	high fixed cost, slow start	rises, but tied to the person	team knowledge (fragile on turnover)
Outbound agency	retainer + margin, fast start	stays with the provider	list of results
Pure tools (DIY)	low license cost, high time investment	stays with your own team	setup, if staff stays
GTM system + operator	medium fixed cost, fast start	stays in your own workspace	learning system

The often-overlooked point is the learning curve: with an SDR it’s tied to a person and lost on resignation; with an agency it stays with the provider; with a GTM system it stays in your own workspace and lowers cost per SQL over time. The fundamental trade-off between building yourself, buying, and outsourcing is covered in the article Build vs. buy in AI outbound, and the concrete comparison of tool versus service in the article Outbound tools vs. service.

What actually lowers cost per SQL

Cost per SQL doesn’t fall through more volume, but through better rates along the chain. The most effective levers:

• A sharper ICP. Fewer but better-fitting contacts raise the share that turn into SQLs — the strongest single lever.
• Better qualification. Don’t invest time in contacts that will never become an SQL. That directly lowers cost per qualified lead.
• More relevant outreach. A hook that hits the real pain point lifts reply and positive-reply rates — same cost, more SQLs.
• A preserved learning curve. A system that learns from every outcome gets more accurate over months, instead of starting from zero with every staff change.

For how many contacts realistically sit behind a meeting and thus behind an SQL, see the benchmark cold emails per B2B meeting — a useful input for sanity-checking your own cost per SQL.

Where CegTec fits in

CegTec runs GTM Goat, a context-aware GTM system optimized for qualified outcomes rather than volume. The effect on cost per SQL comes from three directions: sharper targeting against the ICP, qualification built in before the meeting, and a learning loop that stays in your own workspace and increases accuracy over time. Every external action runs through a human approval point, GDPR-compliant. Outbound and meeting generation are our most deeply proven capability — the economic advantage isn’t lower list prices, but a falling cost per SQL, because the learned knowledge belongs to you.

Conclusion

Cost per SQL is the most honest outbound metric, because it connects effort and qualified outcome and can’t be dressed up through volume. Calculate it cleanly — with all four cost blocks, including the hidden build time — and you get a steerable number instead of a gut feeling. It’s lowered not by more reach, but by a sharper ICP, better qualification, more relevant outreach, and a learning curve that stays in-house. And it’s always assessed relative to deal value. For how a GTM system lowers cost per SQL over time, see the overview of GTM Goat.

---

Start your free trial · 4 weeks free, no credit card. Prefer to see it running first? Book a demo.