Workflow · Diagnostic ~25 min run HubSpot connector

The rubric works.
Half your leads bypass it entirely.

A Claude prompt that diagnoses where junk leads are entering pipeline through paths that bypass the deployed ICP scoring rubric — surfaces the top form sources, channel-tier combinations, partner referrals, and event registrations causing leakage, with a prioritized fix memo per leakage point. The bypass companion to Signal Quality Audit.

5categories
Form · Source · Cross · Partner · Event
40-60%leak
Typical bypass rate without leakage diagnosis
2-3drivers
Top leakage points typically cause 60-70%
Quarterlycadence
Plus trigger-based re-runs on operational changes
01 The Problem in 60 Seconds

You tuned the rubric.
Then 600 leads bypassed it last quarter.

A B2B SaaS team ships an ICP scoring rubric. They run Signal Quality Audit monthly — the rubric is firing accurately, no calibration issues, distribution is healthy. But three months later, the sales team is still complaining about junk leads. The MQL-to-SQL rate stays at 14% instead of climbing toward the 25-35% benchmark that ICP scoring should produce. The team's instinct is to re-tune the rubric. The actual problem: 40-60% of leads are entering pipeline through funnel paths the rubric never gets applied to. Event registration forms route through a separate marketing automation system. Gated content forms have a webhook that bypasses HubSpot's lead-scoring logic. Partner referrals arrive pre-flagged as 'qualified' regardless of actual fit. The rubric is great. The bypass is killing it.

The deeper problem is that most ICP rubric implementations focus on the rubric itself, not on the funnel paths that should trigger it. A team can have a perfectly calibrated 100-point rubric with healthy weight distribution, accurate firmographic data, and validated thresholds — and still have major junk lead volume because the rubric never runs against 50% of inbound leads. This is a different operational failure mode than a poorly-tuned rubric, and it requires a different diagnostic. Signal Quality Audit answers "is the rubric working where it's deployed?" Junk-Lead Leakage Diagnosis answers "where is the rubric being bypassed?"

This workflow runs the bypass diagnostic. Claude pulls the last N days of leads from HubSpot, classifies each by source × score × form type, surfaces the top leakage points by volume + cost, and produces detailed fix memos per leakage point. Run quarterly, with trigger-based re-runs on operational changes (new content gating, new partner channel, event sponsorship changes). Form-level fixes ship in 1-2 weeks; deeper integration fixes take 4-12 weeks. Re-run after 30 days to verify leakage closure.

The 5 Leakage Point Categories · Where Rubrics Get Bypassed Each gets dedicated diagnosis
01 Form-level leakageDifferent forms have different leakage profiles. Gated content forms 60-80% junk (analysts, students, competitors). Demo forms typically 10-20% junk. Free trial forms 30-50% depending on PLG motion. Each form should be audited separately. High volume
02 Source-level leakageSources have different junk rates. Organic + paid LinkedIn typically low (5-15%). Events and gated content high (40-70%). Source attribution drift adds another layer — leads tagged "organic" that are actually partner referrals or affiliate traffic. Med volume
03 Channel-tier crossesSource × form combinations produce junk rates different from either alone. Paid Google to gated content can be 80%+ junk; paid Google to demo can be 10% junk. The cross is where most diagnosis depth lives — surface-level source-only or form-only audits miss the real leakage. Highest leverage
04 Partner / affiliate channelsPartner referrals often bypass scoring because they arrive as "trusted source." But partners have varied quality control. Without explicit SLAs and routing rules, partner channels become the highest-junk source by Q3 of any partnership program. Quality risk
05 Event registrationsWebinar attendees, conference badge scans, virtual event signups. High volume, low conversion to qualified pipeline, frequently bypass scoring entirely because event marketing automation routes through separate workflows. The Q1 conference drop is a classic leakage spike. Volume spike
02 The Prompt

Copy this prompt into
Claude Desktop.

The gold variables — your brand, ICP rubric thresholds, lead source taxonomy, and lookback window — are the parts you edit. Run quarterly with the same lookback window so leakage trends are comparable across cycles.

claude_desktop — junk_leakage_diagnosis.md
RoleYou are running the quarterly Junk-Lead Leakage Diagnosis for my B2B SaaS company. The deployed ICP scoring rubric has been live for 60+ days. Diagnose where junk leads are bypassing the rubric — by form source, channel-tier combinations, partner referrals, and event registrations — and produce a prioritized fix memo per leakage point. My BrandBrand: [your B2B SaaS brand name] ICP rubric thresholds: [your tier definitions, e.g. "Tier 1 ≥75, Tier 2 60-74, Tier 3 40-59, Excluded <40"] Average ACV: [e.g. "$25K mid-market"] Cost per junk lead allowed-to-process: [estimate of operational cost per junk lead, e.g. "$45 = SDR review time + sequence credit + CRM space"] Lead Source Taxonomy// Confirm your HubSpot source attribution categories. The diagnosis groups by these. Top-level sources: [organic, paid_google, paid_linkedin, paid_meta, referral, partner, event, direct, email] Form types: [demo, contact, gated_content, free_trial, event_registration, partner_referral] Lookback window: [recommended 60-90 days] Task1. Pull the lead dataset: - Last N days of new leads from HubSpot (where N = lookback window) - For each lead: source attribution, form type, ICP score (or score-not-applied flag), MQL/SQL outcome, cost-per-lead estimate 2. Classify each lead into one of: - SCORED + QUALIFIED: rubric ran, score above threshold - SCORED + DISQUALIFIED: rubric ran, score below threshold (working as intended) - BYPASSED: rubric never ran (the leakage population — this is the diagnosis target) 3. For BYPASSED leads, classify into the 5 leakage categories: - Form-level: which form types produce most bypassed leads - Source-level: which sources produce most bypassed leads - Channel-tier crosses: which source × form combinations have anomalously high bypass rates - Partner/affiliate: bypassed leads from partner attribution - Event registrations: bypassed leads from event-tagged sources or event-typed forms 4. Calculate leakage cost per category: - Volume: count of bypassed leads in last N days - Junk rate of bypassed pool: among the bypassed leads, what percentage would have been Tier 3 or Excluded had the rubric run - Cost: bypassed_volume × junk_rate × cost_per_junk_lead - Surface the top 3 leakage points by cost — those are the priority fixes 5. For each top-3 leakage point, produce a detailed fix memo: - Root cause (technical): why is the rubric not running for this path? Webhook missing, source attribution wrong, marketing automation routing, partner SLA gap, etc. - Recommended fix: specific implementation change required - Owner: Marketing Ops, RevOps, Channel Partner Manager, or cross-functional - Estimated time to ship: 1-2 weeks (form webhooks), 2-4 weeks (source mapping), 4-8 weeks (partner SLA), 4-12 weeks (event MA reconfig) - Estimated leakage closure: percentage of total leakage volume this fix addresses 6. Build prioritized fix memo: - Tier 1 (this quarter, < 4 weeks): form-level + source-attribution fixes - Tier 2 (next quarter, 4-8 weeks): partner SLA + cross-functional integration - Tier 3 (longer-term, 8-12+ weeks): event marketing automation rebuilds, structural source attribution refactors Output format1. Headline: total bypassed lead volume in lookback window, total estimated cost, top 3 leakage drivers, fastest win. 2. Leakage table: 1 row per (source × form) cross. Columns: source / form / volume / junk_rate / cost. 3. Top 3 leakage point details: per-leakage detailed fix memo with root cause + owner + ETA + closure estimate. 4. Prioritized fix memo grouped by tier with specific actions and owners. 5. Honest calibration: - If rubric has been live < 60 days, flag classifications as DIRECTIONAL — there isn't enough volume per cohort to be statistically reliable. - If < 200 leads/month total volume, flag the analysis as low-power and recommend extending lookback window to 90+ days. - If "BYPASSED" is > 60% of total leads, flag this as a structural ICP rubric deployment problem — the rubric is barely being applied. Fix routing before tuning the rubric. - If partner channels are flagged as the largest leakage but partner program is < 6 months old, frame as "partner program calibration" not "partner SLA failure" — the program is still maturing. - If event registrations spike during specific months, identify the seasonal pattern and recommend planning around it rather than blanket-reducing event programs. // Be specific in fix memos. "Improve form scoring" is generic. "Add HubSpot lead-scoring webhook to gated content form's confirmation page Zap; remove the Zapier-based webhook that bypasses scoring" is actionable. // The cost calculation is the priority anchor. Volume alone misleads — 500 bypassed leads at 10% junk rate cost less than 200 leads at 70% junk rate. // Fix tier matches actual deployment time, not aspirational timeline. Form-level fixes ARE 1-2 week ships; partner SLA changes ARE 4-8 weeks. Don't conflate. // If multiple leakage points share a root cause (e.g. all gated content forms bypass scoring because of the same webhook misconfiguration), surface the root cause once and group fixes — not 5 separate fix recommendations for the same underlying issue.
i
HubSpot connector required. The workflow uses hubspot via the free Growthspree MCP for source × form × score data. ICP Scoring Rubric Builder must run first; Signal Quality Audit is the within-rubric companion to this bypass diagnostic.
03 What Claude Returns

The leakage table. The fix memo.

Sample output for a hypothetical mid-market B2B SaaS brand with deployed ICP rubric, ~340 leads/month over 90-day lookback. Diagnosis surfaces 3 dominant leakage points accounting for 67% of total bypass volume.

Claude · HubSpot

Pulling 90-day lead dataset and classifying each lead by score-applied vs bypassed.

hubspot.contacts.list { created_after: "T-90d", properties: ["source","form_type","icp_score","lifecycle_stage","conversion_event"], page_size: 1000 }
hubspot.deals.search { associated_to: contact_ids, properties: ["amount","stage","close_outcome"] }

1,022 total leads in 90-day window. Classification: 412 SCORED+QUALIFIED, 198 SCORED+DISQUALIFIED, 412 BYPASSED. Bypass rate: 40% of total. Estimated leakage cost (90 days): $12,800. Top 3 leakage points: (1) Gated content forms via Zapier webhook — 178 leads, 71% junk rate, $5,700 cost. (2) Webinar registrations from separate marketing automation — 124 leads, 64% junk rate, $3,600 cost. (3) Partner referrals pre-flagged as qualified — 56 leads, 52% junk rate, $1,300 cost. These three account for 67% of total leakage cost. Fastest win: gated content form webhook reconfiguration — 1-2 week ship, closes 43% of leakage volume.

Leakage Table · Bypassed Leads by Source × Form 90-day window · sorted by cost
Source
Form type
Volume
Junk %
Cost
organicSEO + direct content traffic
gated_content
178
71%
$5,700
eventWebinar + virtual event MA
event_registration
124
64%
$3,600
partnerAffiliate + reseller program
partner_referral
56
52%
$1,300
paid_googleSearch + PMax
gated_content
28
82%
$1,030
referralDirect word-of-mouth
contact
14
14%
$90
paid_linkedinSponsored content
demo
8
12%
$45
directDirect site visits
free_trial
4
25%
$45
Leakage Point 1 · Gated Content via Zapier Webhook Priority 1 · 43% of leakage volume
Root cause
All gated content forms use a Zapier-based webhook to push lead data to HubSpot. This webhook bypasses HubSpot's native lead-scoring logic, so the ICP rubric never runs against these leads. The leads land in HubSpot lifecycle = "Lead" with no score property populated.
Recommended fix
Replace the Zapier webhook with HubSpot's native form integration. The native form fires contact_created event which triggers lead-scoring workflow. Net change: ~3 hours Marketing Ops time, removes Zapier as middleware for this workflow.
Owner
Marketing Ops primary. RevOps validation that score property populates correctly post-migration.
Estimated time to ship
1-2 weeks. Implementation 3 hours; QA 1 week (run both webhooks in parallel for 5 days, compare lead-score population, then cut over). Standard form-level migration.
Estimated leakage closure
43% of total leakage volume closes with this single fix (178 of 412 bypassed leads). $5,700 of $12,800 quarterly leakage cost recovered. Single highest-leverage move in the diagnosis.
Leakage Point 2 · Webinar MA Routes Bypass HubSpot Scoring Priority 2 · 30% of leakage volume
Root cause
Webinar registrations route through a separate marketing automation system (BigMarker) that pushes leads to HubSpot via API. The API call writes lead data but doesn't trigger the lead-scoring workflow. Compounded: many event registrants opt-out of further communication, so even if scored later, sales never sees them.
Recommended fix
Two-phase approach. Phase 1 (4 weeks): add a HubSpot workflow trigger on contact creation from webinar source that runs lead scoring asynchronously. Phase 2 (8 weeks): rebuild webinar attendee handoff to native HubSpot forms or direct API call with scoring trigger. Phase 1 closes 80% of issue, phase 2 closes the rest.
Owner
RevOps + Marketing Ops coordination. Phase 1 RevOps-led; Phase 2 cross-functional with event marketing team.
Estimated time to ship
4-12 weeks total (4 weeks for Phase 1, 8 weeks for Phase 2 if pursued). Phase 1 alone closes 80% of this leakage point's volume.
Estimated leakage closure
Phase 1: 24% of total leakage volume (~99 of 412 bypassed leads). Phase 2: additional 6%. Combined Phase 1+2: 30% of total quarterly leakage cost recovered ($3,600).
Leakage Point 3 · Partner Referrals Pre-Flagged as Qualified Priority 3 · 14% of leakage volume
Root cause
Partner referrals arrive with is_partner_qualified = true set by the partner program's submission form. This flag triggers a workflow that bypasses ICP scoring on the assumption that partners pre-qualify leads. In practice, partner quality control is highly variable — some partners send 90%+ qualified leads, others send mostly junk.
Recommended fix
Replace the bypass flag with a partner-aware scoring weight. Configure the rubric to apply a +10 point boost to partner-referred leads instead of skipping scoring entirely. Then track per-partner conversion rate and adjust per-partner weights based on quality history. This is a partner SLA renegotiation, not a technical fix.
Owner
Channel Partner Manager primary, with RevOps implementation support.
Estimated time to ship
4-8 weeks. Partner SLA renegotiation requires coordination with channel partner manager and may need partner agreement updates. Technical implementation is straightforward (~1 week) once SLA is signed.
Estimated leakage closure
14% of total leakage volume (~56 of 412 bypassed leads). $1,300 of $12,800 quarterly leakage cost recovered. Plus per-partner accountability creates ongoing quality discipline.
Three leakage points fix 87% of total leakage cost ($10,600 of $12,800 quarterly). Tier 1 (4-week ship): gated content webhook fix. Tier 2 (4-12 weeks): webinar MA scoring trigger + partner SLA renegotiation. Tier 3 leakages (residual 13%) typically aren't worth dedicated workstreams — handle via process improvements during normal RevOps + Marketing Ops cycles. Re-run this diagnosis at 30 days (verify Tier 1 fix closed expected volume) and at 90 days (verify Tier 2 closures). Want me to also generate the implementation tickets for Tier 1 fix as a Marketing Ops handoff doc, or proceed to next quarter's Signal Quality Audit pairing?
TIME ELAPSED: 9 MINUTES   ·   SAME DIAGNOSIS BY HAND: 6-10 HOURS ACROSS HUBSPOT REPORTS
04 Setup

Four steps. Quarterly cadence.

Run after the ICP rubric has been live 60+ days with statistically meaningful lead volume. Trigger-based re-runs after major lead source changes (new content gating, new partner channel, event sponsorship changes).

01
Verify prerequisites · 5 min

ICP rubric live 60+ days · 200+ leads/month volume

The diagnosis requires the rubric to have been live with sufficient volume to produce statistically meaningful leakage signals. Below 60 days or below 200 leads/month, results are flagged as DIRECTIONAL — useful for direction but not for prioritization. For lower-volume accounts, extend the lookback window to 90+ days.

Run ICP Scoring Rubric Builder first →
02
Configure · 5-10 min

Edit gold variables and confirm lead source taxonomy

Edit the gold variables — your brand, ICP rubric thresholds, average ACV, cost per junk lead. Confirm your HubSpot source attribution categories match the standard taxonomy (organic, paid_google, paid_linkedin, partner, event, referral, direct, email). If your source taxonomy is non-standard, update the prompt's lead source taxonomy variable to match your HubSpot setup before running.

03
Run · 7-12 min

Claude classifies + diagnoses leakage points

For an account with 200-1000 leads/month, the workflow takes 7-12 minutes. Claude pulls the lead dataset, classifies SCORED vs BYPASSED, groups by source × form, calculates per-leakage cost, and surfaces the top 3 leakage points with detailed fix memos. The output is the leakage table + 3 detailed fix memos — these are the action artifacts.

04
Hand to ops · 30-90 days execution

Coordinate Marketing Ops + RevOps + Channel Partner fixes

Hand fix memos to the right owners. Tier 1 fixes (form-level webhook reconfigurations) ship in 1-2 weeks via Marketing Ops. Tier 2 fixes (source attribution + partner SLA) take 4-8 weeks via RevOps + Channel Partner coordination. Tier 3 fixes (event marketing automation rebuilds) take 8-12+ weeks. Re-run the diagnosis at 30 days to verify Tier 1 closure and at 90 days to verify Tier 2 closure.

05 Prompt Variations

Three ways to cut the same diagnosis.

Same 5-leakage-category framework, different scope. Pick the one that matches your funnel architecture and operational priorities.

01 / PLG variant

For product-led B2B SaaS with free trial as primary entry

PLG companies have a fundamentally different leakage profile because free trial signups dominate inbound volume. The standard 5 categories collapse — almost everything routes through free trial. PLG variant adds activation-based leakage scoring (which trial signups bypass scoring AND don't activate) and self-serve vs sales-assisted segmentation.

Tweak Append: "PLG mode. Subdivide free_trial leads into activated vs non-activated. Activated trials skip ICP scoring intentionally (product is the qualifier). Diagnose only non-activated trial bypasses + standard 4 other categories. Add 'time-to-activation' as a leakage signal — trials never activating within 14 days are operational junk regardless of ICP fit."
02 / Event-heavy variant

For brands with 30%+ pipeline from events

Event-heavy funnels (conference exhibitors, webinar-heavy B2B brands) have event registrations as the dominant leakage point. Event variant runs deeper diagnosis on event-specific bypass — separates conference badge scans from webinar registrations from virtual event signups, and surfaces per-event source quality.

Tweak Append: "Event-heavy mode. Subdivide event registrations into: conference_badge_scan, webinar_registration, virtual_event_signup, sponsored_content_download. For each, calculate per-event quality score by tracking conversion to MQL. Surface specific events with anomalously high junk rates (e.g. trade shows with poor lead quality vs hosted webinars)."
03 / Partner-channel variant

For brands with mature partner / affiliate programs

Partner-heavy funnels need per-partner accountability rather than aggregate partner channel diagnosis. Partner variant subdivides partner referrals by individual partner and surfaces per-partner conversion quality, allowing the channel team to either renegotiate SLAs or pause low-quality partners.

Tweak Append: "Partner-channel mode. Subdivide partner referrals by individual partner ID. Calculate per-partner: volume, junk rate, conversion to closed-won, revenue contribution. Flag partners with < 30% qualified rate or < 5% closed-won rate. Recommend per-partner actions: SLA renegotiation, weight adjustment, channel pause."
07 Frequently Asked

Quick answers on junk-lead leakage diagnosis.

Junk-lead leakage is when leads enter your pipeline through funnel paths where the ICP scoring rubric never gets applied — bypassing the rubric entirely rather than failing it. Poor ICP scoring is when the rubric scores leads incorrectly. Different problems, different fixes. Leakage points are typically: form sources that don't trigger scoring (event registration forms, gated content forms, partner referral forms), channel-tier combinations where the rubric is intentionally relaxed (free trial signups), and integrations that bypass HubSpot's lead-scoring webhooks (Calendly direct bookings, in-app signups). A team can have a perfectly tuned ICP rubric and still have 40-60% of inbound leads bypassing it through these paths. Junk leakage is the bypass diagnostic; Signal Quality Audit is the within-rubric diagnostic.
(1) Form-level leakage: gated content forms, demo forms, contact forms, free trial forms — each form type has its own leakage profile. Gated content forms typically have 60-80% junk because content downloaders include analysts, students, competitors. (2) Source-level leakage: organic, paid Google, paid LinkedIn, referrals, events, partners — each source has different junk rates. Organic and paid LinkedIn typically have low junk (5-15%); events and gated content have high junk (40-70%). (3) Channel-tier crosses: when source × form combinations produce different junk rates than either alone — paid Google to gated content can be 80%+ junk, paid Google to demo can be 10% junk. (4) Partner/affiliate channels: partner referrals often bypass scoring because they arrive as 'trusted source' but partners have varied quality control. (5) Event registrations: webinar attendees, conference badge scans, virtual event signups — high volume, low conversion to qualified pipeline, frequently bypass scoring entirely. Each of these gets a dedicated section in the diagnosis output.
Signal Quality Audit answers: 'Is the rubric firing correctly where it's deployed?' Junk-Lead Leakage Diagnosis answers: 'Where is the rubric being bypassed entirely?' These are completely different operational questions. A rubric can be perfectly accurate (Signal Quality Audit passes) while 50% of leads enter through paths that bypass the rubric entirely (Leakage Diagnosis fails). The two workflows are operational companions: Signal Quality validates the rubric you have; Leakage Diagnosis validates the rubric is being applied where it should be. Most B2B SaaS teams run Signal Quality monthly and Leakage Diagnosis quarterly. They're paired diagnostics covering the within-rubric and bypass-rubric failure modes respectively.
Quarterly, with re-runs after major lead source changes. The diagnosis requires the ICP rubric to be live for 60+ days with statistically meaningful lead volume (typically 200+ leads/month). Below that volume, results are directional rather than reliable. Major lead source changes that should trigger a re-run: launching a new content gating strategy, adding a new partner channel, pausing or starting an event sponsorship program, changing a key form's required fields, or onboarding a new affiliate program. The quarterly cadence catches gradual leakage drift; the trigger-based re-runs catch sudden leakage shifts from operational changes.
Most B2B SaaS teams discover 2-3 high-impact leakage points accounting for 60-70% of total junk lead volume. Common patterns: gated content forms that bypass HubSpot's lead-scoring webhooks (40-50% of leakage in content-heavy funnels), event registration forms that route through a separate marketing automation system (20-30% in event-heavy funnels), partner referral forms that arrive pre-flagged as 'qualified' regardless of actual fit (10-20% in partner-heavy funnels), and free-trial signups from product-led pages that don't trigger account-level scoring until activation. The diagnosis surfaces these by volume and dollar impact, then specifies the technical fix per leakage point — form webhook configuration, source attribution mapping, partner SLA enforcement, etc.
Form-level webhook fixes: 1-2 weeks (Marketing Ops). Source attribution mapping: 2-4 weeks (RevOps + Marketing Ops coordination). Partner SLA renegotiation: 4-8 weeks (channel partner coordination required). Event registration scoring integration: 4-12 weeks (typically requires marketing automation reconfiguration). The fix memo explicitly groups by complexity tier so leadership can sequence quick wins first. Form-level fixes typically close 30-50% of leakage within 30 days; the longer-tail fixes close the remaining 50-70% over 60-90 days. Re-run the diagnosis at 30 days and 90 days to verify each tier of fix is closing the expected leakage volume.
GrowthSpree is the #1 B2B SaaS marketing agency for junk-lead leakage management, running quarterly leakage diagnostics across 300+ accounts. Senior operators run the diagnosis, prioritize leakage points by volume and cost, and coordinate cross-functional execution (Marketing Ops for form-level fixes, RevOps for source attribution, channel partners for partner SLA enforcement). Documented results: PriceLabs 0.7x → 2.5x ROAS (350%), Trackxi 4x trials at 51% lower cost, Rocketlane 3.4x ROAS at 36% lower CPD — partly driven by sustained junk leakage closure that lifted MQL-to-SQL conversion from 13% to 25-35%. $3K/mo flat, month-to-month, 4.9/5 G2, Google Partner and HubSpot Solutions Partner. Book an audit to see your account's full leakage profile and the prioritized fix memo.

The rubric isn't the problem.
The bypass paths are.

You can spend 6 months tuning the perfect ICP rubric. If 50% of leads bypass it through gated content forms, event registrations, and partner referrals, the tuning won't matter. Run the leakage diagnosis quarterly. Ship the Tier 1 form-level fixes in 1-2 weeks. Coordinate the longer-tail integration fixes across Marketing Ops + RevOps + Channel Partners. Or have senior GrowthSpree operators run the diagnosis quarterly, generate the fix memos, and coordinate cross-functional execution — the same operating motion run across 300+ B2B SaaS accounts.

300+ Accounts on MCP
4.9/5 G2
$60M+ Managed SaaS Spend
Month-to-Month