Diagnose pipeline stalls and fix conversion blocks
pipeline-reviewerskillsetup L1★6
gvkhosla/founder-skills ↗What it does
Diagnose why deals stall and fix immediate conversion bottlenecks
Best for
Founders and sales leaders who want to stop guessing why deals die and need a crisp diagnosis of the one thing to fix first to unblock pipeline conversion.
Inputs
- · Current pipeline (stage, deal size, days in stage)
- · Lost deal patterns from past 3 months (reasons, objections, who said no)
- · Sales call notes or transcripts (if available, for objection language)
- · positioning.md (ICP alignment check)
Outputs
- · Pipeline diagnosis (conversion rate by stage, comparison to benchmark)
- · Most likely bottleneck (e.g., discovery too short, no budget conversation, wrong buyer, messaging miss)
- · Objection patterns (grouped by type and stage)
- · Deal-stage weakness (e.g., 50% of deals stall at proposal)
- · Immediate fixes for this week (not 30-day plan)
- · Next sales skill to run
Preconditions
- · Pipeline data exists (even rough — deal size, stage, days in stage)
- · At least 5 lost deals documented (or current deals are too new to diagnose patterns)
Failure modes
- · Diagnosis treats symptom (low close rate) instead of root cause (wrong buyer, weak messaging, broken demo)
- · Recommends hiring sales when problem is product-market fit or messaging
- · Ignores that early-stage pipelines are too small for statistical confidence (n < 10 deals)
Trust signals
- · Calls out most likely bottleneck explicitly (not soft 'maybe it's messaging')
- · Recommends immediate fixes for this week (not 30-day initiative when deals are dying now)
- · Acknowledges when pipeline is too small for pattern confidence (early stage caveat)
- · Objection patterns grouped by type (budget, technical, competitive, organizational)