How do you audit marketing-sourced pipeline quality and spot rotten SQL sources?
To audit marketing-sourced pipeline quality, segment SQLs by source and compare close rates, average deal size, and time-to-close against your baseline over a rolling 6–12 month period. Rotten sources typically show close rates 30–50% below your average, high early-stage churn, or deals that stall past your median sales cycle. Flag any source where more than 60% of SQLs never advance past the first sales meeting or where the cost per closed-won deal exceeds 3x your target CAC.
Brief
Track SQL→Opportunity close rate by source. Below 20% kills your deal math; above 50% questions your SQL gate.
Detail
Marketing sourced 100 SQLs last month. Sales closed 12 of them. That's 12% close rate. Is that good or terrible? Depends on the source:
- High-intent webinar (gated, vertical-focused): 35–45% SQL→Opp
- Organic content (blog, SEO): 22–28% SQL→Opp
- Paid ads (brand keyword): 18–25% SQL→Opp
- List/outbound nurture: 8–15% SQL→Opp
If your paid ads are only hitting 12%, that's below the band. Your MQL gate is too loose.

Quality Audit Framework
For each source, calculate over 90 days:
| Source | SQLs | Opportunities | Opp Rate | Avg Deal Size | Qual? |
|---|---|---|---|---|---|
| Webinar (Jan 22) | 47 | 22 | 47% | $62K | YES |
| Organic Content | 183 | 34 | 19% | $38K | AUDIT |
| Paid Search (Brand) | 91 | 15 | 16% | $31K | NO |
| ABM Account (Cold) | 24 | 8 | 33% | $145K | YES |
| Event Booth | 18 | 2 | 11% | $21K | KILL |
The *Paid Search (Brand)* source is bleeding money. Why? Three tests:
- Is the form too loose? (Landing page accepts anyone)
- Is the audience wrong? (Targeting SMB instead of Enterprise)
- Is the message misaligned? (Ad promises X, product is Y)
Root Cause by Data Pattern
Run this audit monthly. Kill sources dropping below 18% SQL→Opp unless they're volume plays (high MQL count, lower quality acceptable).
TAGS: pipeline-quality,SQL-sources,source-audit,marketing-sourced,conversion-by-channel
---
Source Stack
- Andreessen Horowitz "16 Startup Metrics": https://a16z.com/16-startup-metrics/
- OpenView Expansion SaaS Benchmarks: https://openviewpartners.com/expansion-saas-benchmarks/
- Bessemer "10 Laws of Cloud": https://www.bvp.com/atlas/10-laws-of-cloud
- First Round Review: https://review.firstround.com/
- Lenny\'s Newsletter benchmark archive: https://www.lennysnewsletter.com/
- HubSpot State of Sales Report: https://www.hubspot.com/state-of-marketing

---
Verified Financial Benchmarks (2024-2025)
| Metric | Verified figure | Source |
|---|---|---|
| Rule of 40 median (Series B+) | 34-42 | Bessemer |
| ARR per employee (Series B) | $130K-$190K | OpenView |
| ARR per employee (Series D+) | $230K-$320K | Bessemer |
| Top-quartile mid-market ARR growth | 45-65% YoY | Bessemer |
| Median runway at Series A | 22-28 months | Carta |
| Median founder dilution Series A | 18-22% | Carta |
| Median founder dilution through C | 52-62% total | Carta |
| PE-backed SaaS multiple at exit | 8-14x ARR | PitchBook |
| Median strategic acquisition (2024) | 6-9x ARR | 451 Research |
---
Verified Financial Benchmarks (2024-2025)
| Metric | Verified figure | Source |
|---|---|---|
| Rule of 40 median (Series B+) | 34-42 | Bessemer |
| ARR per employee (Series B) | $130K-$190K | OpenView |
| ARR per employee (Series D+) | $230K-$320K | Bessemer |
| Top-quartile mid-market ARR growth | 45-65% YoY | Bessemer |
| Median runway at Series A | 22-28 months | Carta |
| Median founder dilution Series A | 18-22% | Carta |
| Median founder dilution through C | 52-62% total | Carta |
| PE-backed SaaS multiple at exit | 8-14x ARR | PitchBook |
| Median strategic acquisition (2024) | 6-9x ARR | 451 Research |

---
The Bear Case (Customer-Side Adoption Friction)
Three friction vectors:
- Budget reallocation in downturn — services/SaaS get aggressive cuts. 20-30% pipeline compression, 90-day cash buffer.
- Buying-committee expansion — Gartner: 6 → 11 stakeholders/decade. Each adds 30-45 days.
- Procurement-driven price compression — 20-40% discounts are closing condition, not opener.
Mitigation: ACV-expansion tiers, exec-sponsor motions, renewal escalators 5-7% annual.
---

See Also (related library entries)
Cross-references for adjacent operator topics drawn from the current 10/10 library set, ranked by tag overlap with this entry:
- q251 — How do you design a sales contest that doesn't tank pipeline quality after it ends?
- q9502 — How do you scale a workshop-led senior tech-training business in 2027 — what's the proven path past the single-operator ceiling?
- q9559 — How should a CRO calibrate qualification rigor when cash position and runway are forcing a choice between conservative organic growth and ag
- q9558 — What's the framework for a CRO to decide whether to build two separate sales motions (organic vs M&A/upmarket) with distinct qualification r
Follow the q-ID links to read each in full.
Related on PULSE
- [How Do I Measure Marketing-Sourced vs Sales-Sourced Pipeline Fairly in 2027?](/knowledge/q16219)
- [How do you measure marketing-sourced vs sales-sourced pipeline in 2027?](/knowledge/q12872)
- [How do you measure marketing-sourced pipeline contribution in 2027?](/knowledge/q12262)
- [Should I open or buy a White Spot franchise in 2027?](/knowledge/q14985)
- [How do you coach a CSM to spot expansion opportunities?](/knowledge/q14045)
- [How do you spot a struggling remote rep before it's too late?](/knowledge/q14030)
SQL Source Waterfall Analysis: Diagnosing Where Pipeline Leaks Occur
A single close-rate metric hides where the real rot lives. Build a source-level waterfall that tracks every stage from MQL → SQL → Accepted Opportunity → Closed Won, segmented by channel (e.g., LinkedIn Ads, Content Downloads, Webinar Registrations, Partner Referrals). Calculate stage-to-stage conversion rates for each source, not just the final close rate.
For example, a source with a 40% SQL-to-Opportunity conversion but a 10% Opportunity-to-Close rate reveals a different problem than one with 20% SQL conversion and 60% Opportunity-to-Close. The first suggests poor qualification criteria at the SQL stage (sales is accepting leads that don't fit), while the second indicates weak lead quality that fails to progress at all. Map these waterfalls monthly and flag any source where the Opportunity-to-Close rate drops below 20% or where SQL-to-Opportunity exceeds 50% (likely a sign the SQL gate is too loose).
Add a time-to-close dimension: sources that take 90+ days to close with low win rates often indicate misaligned buyer intent or product-market fit issues. Compare against your overall average sales cycle (typically 30-90 days for B2B SaaS). A source that closes faster than average but at lower rates may be attracting tire-kickers, while one that closes slower with similar rates might still be valuable if deal sizes are larger.
SQL Source Degradation Score: Tracking Quality Over Time
Rotten sources don't always start rotten—they degrade. Create a SQL Source Degradation Score that tracks the rolling 3-month trend for each source across three metrics: SQL-to-Opportunity rate, average deal size, and days-to-close. A source earns a "degradation alert" when any metric drops by more than 15% compared to its own trailing 6-month baseline.
For instance, if LinkedIn Ads historically converted 35% of SQLs to opportunities with a $50K average deal size, but now shows 25% conversion with $40K deals over two consecutive months, that's a clear signal. The source isn't dead yet, but the audience or messaging is shifting. Investigate whether ad creative, targeting, or landing page copy changed, or if market conditions altered buyer behavior.
Combine this with pipeline velocity—the rate at which SQLs move through stages. A source with declining velocity (e.g., 60 days from SQL to close vs. a baseline of 45) may be accumulating stale leads that sales reps deprioritize. Flag any source where velocity drops below 80% of its baseline for two months running. This early warning lets you pause spend or adjust targeting before the source becomes a full "rotten" drain on the pipeline.
SQL Source Audit Checklist: 5 Questions to Ask Weekly
Build a repeatable audit routine with these five questions, answered weekly for your top 5 SQL sources:
- Are SQLs from this source actually being worked by sales within 24 hours? Check CRM timestamps. If >20% of SQLs sit untouched for 48+ hours, the source is likely producing low-priority leads that reps ignore. Fix by tightening SQL criteria or adding a lead-scoring overlay.
- What's the SQL-to-meeting-booked rate for this source? A source with high SQL volume but low meeting conversion (below 30%) suggests the SQL definition is too broad. Compare against your best source (often inbound demo requests at 50-70% meeting rate). If a paid source falls below 20%, pause it and re-evaluate the offer or targeting.
- How many SQLs from this source become disqualified within the first 30 days? Track "disqualified" reasons (budget, authority, need, timing). If >25% of SQLs from a source are disqualified for budget or authority, the source is attracting the wrong buyer persona. Adjust targeting or content to filter earlier.
- What's the average deal size for closed-won SQLs from this source vs. the source's average SQL? A wide gap (e.g., $30K SQL average but only $15K closed-won average) indicates that the source generates many small, low-quality leads that never convert into meaningful revenue. Compare against your target deal size; if the gap exceeds 40%, the source is diluting pipeline value.
- Is the source's cost-per-SQL increasing while quality decreases? Track cost-per-SQL alongside degradation score. A source where cost-per-SQL rises by >20% quarter-over-quarter while close rate drops by >10% is a clear candidate for reallocation. Set a threshold: if cost-per-SQL exceeds 3x the average cost-per-SQL of your top 3 sources, pause and re-optimize before scaling further.
Run this audit every Monday morning using a shared dashboard (e.g., in your CRM or BI tool). Flag any source that fails two or more questions for three consecutive weeks—that's the definition of a rotten source needing immediate action.
Lead Velocity & Stalling Patterns
Track the time-to-first-meeting and time-to-close per source over a rolling 90-day window. Rotten sources often show a telltale pattern: SQLs accept meetings quickly but then stall hard. A healthy source should see 70%+ of SQLs book a meeting within 5 business days, with at least 40% advancing to a second meeting within 14 days. If a source shows a 50%+ drop-off between first and second meetings, or if the average time from SQL to closed-won exceeds 120 days (when your baseline is 60–90), you're looking at pipeline rot — leads that look interested but never commit.
Sales Feedback Correlation Loops
Build a monthly sales feedback score (1–5) per source, collected from reps within 48 hours of initial contact. Cross-reference these scores against actual close rates. A source averaging 2.5 or lower on feedback but still generating high SQL volume is a red flag — reps are telling you these leads don't fit, but marketing keeps feeding them. Conversely, a source with 4+ feedback scores but low close rates may indicate a qualification issue (too strict or too loose) rather than a rotten source. Track the delta: if feedback scores drop by 1+ point over 3 months while SQL volume stays flat, that source is actively degrading.
Cost-to-Close & Pipeline Velocity Impact
Calculate cost per SQL and cost per closed-won by source, then normalize against your target CAC. A rotten source often hides behind low cost-per-SQL ($50–$100) but reveals itself through a cost-per-closed-won that's 2–3x higher than your target ($5,000–$15,000 vs. a $2,000–$5,000 target). Also measure pipeline velocity impact: how many days does this source add to your overall weighted pipeline age? If removing a source would reduce your average pipeline age by 15+ days while only dropping total pipeline value by 5–10%, that source is dragging down your entire forecast accuracy.
Sources
- Marketing Attribution & Analytics Platforms (e.g., HubSpot, Marketo, Salesforce) — documentation on pipeline attribution models and source tracking.
- Forrester Research — reports on B2B marketing measurement and pipeline quality benchmarks.
- Gartner — research on marketing ROI, lead scoring, and sales-marketing alignment.
- American Marketing Association (AMA) — resources on marketing metrics and data quality best practices.
- Demand Gen Report — articles and case studies on pipeline auditing and source analysis.
- LinkedIn Marketing Solutions Blog — insights on B2B lead source evaluation and conversion data hygiene.
FAQ
What’s the first step to audit marketing-sourced pipeline quality? Start by mapping every lead source to its corresponding SQL and closed-won stages in your CRM. This lets you see which channels actually produce revenue, not just volume. A simple source-to-revenue report often reveals that a high-SQL source may have terrible close rates.
How do you identify a “rotten” SQL source? Look for a source that generates many SQLs but has a conversion-to-close rate significantly below your average—typically 20-40% lower. Also check if those SQLs have unusually short sales cycles or high early-stage churn, which suggests they were never truly qualified.
Should I rely on first-touch or last-touch attribution for this audit? Use both, but start with first-touch to see which sources initiate pipeline, then overlay last-touch to understand which channels close deals. A source that dominates first-touch but rarely appears in last-touch is often a top-of-funnel waste.
What metrics matter most beyond SQL count? Focus on SQL-to-opportunity conversion rate, opportunity-to-close rate, and average deal size by source. A source with high SQL volume but low conversion (under 10-15%) or tiny deal sizes is a clear red flag.
How often should I run this audit? Quarterly is a good cadence for most B2B teams, but if you’re scaling spend fast, do it monthly. The key is to catch trends before they become budget drains—waiting a year can waste 20-30% of your marketing budget.
Can I automate this audit? Yes, many CRM and BI tools can automate source-to-revenue reports, but the interpretation still needs human judgment. Automate the data pull, then manually review outliers—like a source that suddenly spikes in SQLs but drops in close rate.










