Which Channel Is Actually Funding Your Sales Org? Inbound SQL Cost by Channel

Why CAC-by-Cohort Lies to You

Blended CAC is the marketing equivalent of averaging your reps' quota attainment and reporting the mean. It produces a single reassuring number that tells you almost nothing about what's actually happening.

Say you're spending $15,000 a month on marketing. You closed 12 SQLs last month. Blended cost-per-SQL: $1,250. Fine, maybe.

Except three of those SQLs came from organic search posts you wrote eight months ago. Six came from Google Ads. Two came from a newsletter mention. One came from a Reddit thread where a user cited your pricing page.

The Google Ads SQLs cost you $2,200 each. The SEO SQLs cost you effectively $180 each (amortized content spend). The newsletter mention cost you zero. The Reddit SQL cost you zero.

Your "$1,250 blended cost" is a fiction propped up by two free leads and three cheap ones. The moment your SEO dips, your blended CAC explodes, and you won't know why until you're three months deep into a cash problem.

This is why CAC payback period calculations need to be segmented by how leads actually enter the funnel. Cohort-level math hides channel-level decisions.

The fix isn't complex. It's a spreadsheet plus CRM hygiene. But most founders never build it because nobody told them what they'd find.

---

The Five Inbound Channels Worth Measuring Separately

Not all channels pool together cleanly. These five produce meaningfully different SQL costs, close rates, and ACV distributions. Treat them as separate cost centers.

Organic search. Blog posts, programmatic landing pages, comparison pages, anything that ranks. The spend is content production time plus distribution. The SQL shows up weeks or months after the dollar leaves.

Paid search. Google Ads and Bing targeting bottom-of-funnel intent keywords. The spend is immediate, the lead is immediate, the SQL cost is high. The moment you pause the budget, it stops completely.

LinkedIn content and ads. Organic LinkedIn posts plus sponsored content. Organic LinkedIn has near-zero variable cost; ads on LinkedIn run $8-$15 per click in most B2B SaaS verticals, which compounds aggressively into high cost-per-SQL.

Partner and affiliate referral. Customer referrals, integration partners, agency referrals. Low variable cost per lead, hard to scale predictably, but close rates are typically the highest of any channel.

Community. Hacker News, Reddit, Slack communities, newsletters, Twitter/X threads. Entirely nonlinear. One HN front-page post can drive 200 signups. Week-to-week it produces zero. Hard to attribute, easy to undervalue.

Segment these five before you add any more complexity. Sub-segmenting LinkedIn organic vs. LinkedIn ads, or Google branded search vs. non-branded, comes later.

---

Realistic SQL Cost Benchmarks for Each Channel

These aren't survey averages. They reflect what founders in the $1M-$10M ARR band consistently see when they actually run the calculation.

Organic search (SEO): $150-$600 per SQL, depending on how much content you're producing and how well it's targeted. The cost is almost entirely production: writing time, editing time, publishing. At scale, it compresses. Well-targeted SEO posts hitting striking-distance keywords can produce SQLs at the lower end of this range with no per-lead variable cost.

Paid search: $800-$3,500 per SQL is the realistic range for B2B SaaS under $10M ARR. Competitive keywords in categories like project management, CRM, or HR tech push toward the ceiling. Niche verticals with lower search volume sit closer to $800. HubSpot's State of Marketing Report consistently shows paid search as the highest per-lead cost channel for B2B companies.

LinkedIn: $900-$2,500 per SQL for paid. Organic LinkedIn, if your founder is posting consistently and has an audience, can produce SQLs for near zero variable cost, but the founder's time has to be counted somewhere. LinkedIn SQLs tend to close at higher ACVs, which is the only reason the math often still works.

Referral/partner: $50-$400 per SQL. The cheapest channel by far, once the program is running. The cost is the referral fee or rev-share (if any), plus the operational overhead of managing the relationships. The challenge: you can't turn it on by writing a check.

Community: Effectively $0-$200 per SQL when the channel is working. The cost is time invested in the communities. The output is erratic, a well-placed thread can produce a burst, then nothing for six weeks. Don't depend on it as a primary channel. Do track it separately so you don't accidentally undercount it.

---

How to Actually Run the Calculation

Four steps. None of them require a BI tool or a data analyst.

Step 1: Define SQL consistently. An SQL sourced from SEO has to meet the same criteria as one from paid search. Same ICP, same intent signals, same handoff stage. If your sales team treats a paid search lead differently from a referral lead at the qualification stage, your numbers are measuring two different things.

Step 2: Attribute spend accurately. This is where most teams fail. Paid search is easy, pull it from Google Ads. SEO spend is content production hours multiplied by fully-loaded writer cost, plus any tooling. If you're publishing four posts a month and each takes six hours to write, that's 24 hours at your content contractor rate, plus your Search Console tool, plus any editing time. Count it. LinkedIn ads pull from the campaign manager. Organic LinkedIn is founder time. Referral is partner fees. Track these in a single sheet, by month.

Step 3: Count SQLs per channel in the same window. Pull CRM data for the same month. Add a lead source field if you don't have one already. The field should capture: organic search, paid search, LinkedIn organic, LinkedIn ads, referral, community, direct (unknown). Don't let "direct" swallow 40% of your leads, that's attribution failure, not a channel.

Step 4: Divide and segment by ACV. Cost-per-SQL is spend divided by SQLs. Then add one column: average ACV of the deals that originated from each channel. A $2,000-per-SQL LinkedIn lead that closes at $24,000 ACV has a fundamentally different profile than a $400-per-SQL paid search lead closing at $7,000. You need both numbers to make a reallocation decision.

If your CRM is HubSpot or Salesforce, this requires at minimum a custom lead source property and a report filtered by that property. It's a one-afternoon build. If you're on something lightweight like Pipedrive, a Google Sheet with manual source tagging covers 90% of what you need at $3M ARR.

---

What the Numbers Usually Reveal

Three patterns show up almost every time founders run this exercise for the first time.

Paid search costs 3-6x more per SQL than organic search targeting the same intent keywords. This doesn't mean paid search is wrong. It means you're paying for speed and volume while SEO is still building. The question is whether the speed premium is worth it at your current stage.

LinkedIn SQLs are expensive per-lead but close faster and at higher ACV in most B2B verticals. The ICP quality skews better when someone finds you through a professional network context. Before you cut LinkedIn spend based on per-SQL cost alone, look at the downstream close rate and average deal size.

Referral and community SQLs close 20-40% faster than paid search SQLs, in most cases. The trust transfer is already done. The sales cycle compression alone can make a $300-per-SQL community lead worth more than a $900-per-SQL paid search lead, even at the same ACV. Understanding what a healthy sales cycle looks like for your deal size puts this math into sharper relief.

The single most common finding: one channel is producing 60-70% of SQLs at 3-4x the cost of another, and no one had noticed because the numbers were blended.

---

Fixing the Channel Mix Without Blowing Up Revenue

The wrong move is to immediately kill the expensive channel. You'll close the revenue tap before the cheaper channel can fill the gap.

The right sequence: compress the expensive channel to its minimum viable spend (keep it alive, reduce the budget), and invest the freed capital into compounding channels. SEO is the canonical example. Every post you publish continues producing SQLs for 12-36 months. A Google Ads campaign resets to zero the day you pause it.

The compounding math is real and it's not close: if you're spending $6,000/month on paid search producing 4 SQLs, and you redirect $3,000 of that into content production at $500/post (6 posts), and those posts each produce 0.5 SQLs/month after three months of indexing, you've added 3 SQLs/month by month four, at a marginal cost that compounds downward as the posts age.

The practical problem: most founders can't produce 6 posts a month. Writing one takes four to six hours, and the topic-to-keyword connection between a Notion idea and an actual Search Console opportunity rarely gets made. The posts that rank are the ones targeting keywords you're already close to ranking for, and most founders never look at that data.

This is the exact gap MorBizAI closes. The engine pulls your Search Console striking-distance keywords weekly, drafts a 1,400-1,800 word SEO post in 60-90 seconds in your brand voice, and publishes directly to WordPress via the REST API. No copy-paste, no formatting step, no context-switching into a CMS. The keyword intelligence and the content production are the same workflow.

The waitlist is live at morbiz.ai/marketing-engine.

When is it worth keeping an expensive channel anyway? Two conditions: the channel produces SQLs with meaningfully higher ACV than your cheaper channels, and your close rate from that channel is competitive. A LinkedIn SQL at $1,800 cost closing at 28% to a $30,000 ACV deal has a better payback than a paid search SQL at $600 closing at 12% to an $8,000 ACV deal. Run the numbers per channel before you reallocate.

One important caveat: knowing when to scale sales spend at all matters as much as knowing which channel to fund. If your cohort retention isn't solid, cheaper SQLs don't help. You're just filling a leaky bucket faster.

---

What to Do With This Analysis Once You Have It

Channel SQL cost analysis isn't a one-time project. Run it quarterly.

Channels drift. Paid search CPCs increase as competitors enter. A LinkedIn post from your founder builds an audience over 12 months and then starts producing organic SQLs at near-zero cost. SEO posts that ranked well in January can slide by Q3 if competitors publish competing content.

The goal isn't to optimize to a single channel. It's to know, at any given moment, which channel is overperforming, which is subsidized by the others, and where the next dollar of marketing spend actually goes to work.

Most B2B founders at $3M-$8M ARR have never asked which channel funds their sales org. They track CAC by quarter. They review campaign performance by click-through rate. They look at pipeline by rep. But nobody opens a spreadsheet with five rows, one per channel, and asks: what did each of these actually cost me per SQL, and what ACV did it close at?

Run that spreadsheet once. The decision it forces is almost always obvious. The hard part was never the math.