Find where the funnel leaks and what to fix.

“Our funnel converts worse every quarter. Where does it leak, and which accounts deserve the next sprint?”

Finds the leak, the accounts to work next, and where the scoring model is quietly letting you down.

FIND MORE PIPELINEADVANCEDENRICHMENT TOOLSSEQUENCERCRM✓ APPROVED 4/4
EXAMPLE PROMPTS
>Diagnose where we leak by channel using this funnel export and closed won data
>Score these accounts and tell me which ones to work next
>Audit our scoring model. Which good accounts is it quietly ranking too low?
ABOUT THIS SKILL

What this skill does

This is your diagnostic partner for understanding a sales funnel: why it is converting or not, which accounts to work next, and where the scoring model is letting you down. A scoring dashboard tells you what is happening. This skill helps you understand why, what to do about it, and which accounts deserve the next sprint. It works across three modes that share one six-gate funnel framework, one multi-source signal stack, and the same cohort-anchored math.

Inputs

  • Works today with: your funnel counts by stage and channel, with a cohort entry date per channel, plus your fit scores if you have them. Paste or upload.
  • More powerful connected to a CRM: cohort dates, stages, scores, contacts, and owners, live.
  • More powerful connected to a product-analytics tool: real product engagement for the Product channel.
  • Sharper with ICP-qualification, community or intent, enrichment, and meeting tools.

How it works

  1. 1
    The six funnel gates

    Strike zone is the sequence of conversion gates from a new lead to closed revenue. For each cohort and channel, six gates matter:

    1. Cohort created (a qualified-account date fires) to Meeting booked.
    2. Meeting booked to Meeting completed (show rate).
    3. Meeting completed to SQL (your Qualification stage).
    4. SQL to SQO (your Discovery stage).
    5. SQO to Closed Won.
    6. Closed Won to average deal size and cycle time.

    Each gate has a different failure mode and a different intervention. Misdiagnosing the gate wastes weeks fixing the wrong thing.

  2. 2
    Mode 1: Funnel Diagnosis

    Default mode is conversational. Work interactively. Do not dump a full report unprompted.

    1. Anchor on a channel and a cohort window. Ask what they want to diagnose.
    2. Pull live data from the CRM. Always run queries. Do not analyze from memory.
    3. Find the leaky gate. Compare each gate to the channel's trailing baseline and to the other channels. The leaky gate has the largest negative gap.
    4. Diagnose with the pattern framework. Each leaky gate has two to four known failure modes. Identify which fits.
    5. Recommend a specific action. Named: a person, a list of accounts, a process change, a target.
    6. Offer the written write-up only if asked.
  3. 3
    Mode 2: Sprint Planning

    Converts the funnel from a diagnostic into an execution backlog.

    1. Define the cohort. Default: all accounts whose qualified-account date falls in the target window.
    2. Multi-source enrich every account in parallel: CRM firmographics and stage, ICP-tool fit, product-analytics engagement, community signals, and enrichment contacts on the top tier only (the paid step, check credits first).
    3. Compute composite scores. Tier into Hot, Warm, Watch, Disqualify.
    4. Build the spreadsheet: Sprint Ranking, Top Buying Committee, Scoring Rubric, Cohort Summary, Scoring Gaps.
    5. Hand off. Reps work the buying-committee tab top-down.

    Cost guardrails. The enrichment tool is the only paid source. Cap spend per run unless approved.

  4. 4
    Mode 3: Scoring Audit

    When the independent qualifier, product analytics, community signals, and CRM disagree with your scoring model, the disagreement is the finding.

    • Model False-Negatives: the engagement score sits at its floor value, but product analytics show real sustained team adoption.
    • Model-Missed ICPs: an independent qualifier scores a strong fit, but the model's account-fit score is low or null. A firmographic miss, not an engagement miss.

    Common scoring failure modes: score-floor collapse, "no score" read as low fit, no buying-title weighting, no trend velocity, no ICP penetration ratio.

  5. 5
    Action format (all modes)

    Every recommendation needs three parts: Who (named person or role), What (a specific change), By when (a date or sprint). If you cannot fill all three, diagnose deeper.

Output format

STRIKE-ZONE FUNNEL DIAGNOSIS  ·  Trailing 90 days

OUTBOUND COHORT
  Meeting Set:  47
  to SQL:       16  (34%, BELOW 55% target)
  to SQO:        9  (56%, strong)
  to Closed Won: 4  (44%, strong)
  Velocity: avg 82 days meeting to close
  Diagnosis: Leakage at MEETING to SQL. Getting meetings, not qualifying them in.

LEVERAGE POINT (dollarized):
  Outbound meeting-to-SQL +10% = 5 more SQLs per quarter
  At ASP $22K that is +$110K pipeline + 2 more Closed Won
  = +$44K ARR per quarter at current win rate

WHAT MOVES THE NUMBER:
  1. Listen to 5 outbound meeting recordings, find the qualification gap
  2. Test a qualification-first meeting structure on the next 10 outbound meetings
  3. Compare Inbound vs Outbound conversion at the SQL stage to find the delta

Use generic placeholder names (Acme, Vertex, Northwind) and "Rep" in your own outputs. Never carry real account or person names into a shared artifact.

Tips

  • Use your own selling methodology consistently. Do not introduce a framework the team does not run.
  • Lead with conversion, not volume.
  • Cohort math, not snapshot math. Anchor the cohort by entry date and trace it forward.
  • Honest caveats. If a cohort is too young or a field is not groupable, say so.
  • Use the audience's own taxonomy. Keep expansion as its own motion, not a funnel channel.
  • If a channel-source field is a formula field, filter on it but do not group by it.
  • Filter renewals out of new-business math.
  • If a query needs a field you cannot confirm exists, fail loud and ask. Never invent field names.
RELATED SKILLS
ALL FIND MORE PIPELINE SKILLS →