Skip to content
Back to skills

Fin Sales Pipeline

ASecurity

Manages the sales pipeline — buyer-evidence stage criteria, pipeline coverage ratio (3x), sales velocity formula, win rate consistency, and stalled deal cleanup. Use when user says "sales pipeline", "pipeline coverage", "deal stages", "sales velocity", or "stalled deals".

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 9, 2026
ai-agentsgo

Security analysis

A100/100

Scanned October 9, 2026

npx -y skills add meshcode-ai/skills --skill fin-sales-pipeline --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fin Sales Pipeline?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Fin Sales Pipeline
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/meshcode-ai-fin-sales-pipeline/badge)](https://www.skillsdirectory.com/skills/meshcode-ai-fin-sales-pipeline)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: fin-sales-pipeline
description: Manages the sales pipeline — buyer-evidence stage criteria, pipeline coverage ratio (3x), sales velocity formula, win rate consistency, and stalled deal cleanup. Use when user says "sales pipeline", "pipeline coverage", "deal stages", "sales velocity", or "stalled deals".
license: MIT
metadata:
  source: "alirezarezvani/claude-skills (MIT) · commercial"
  category: exec
---

# Sales Pipeline

## Stage definitions — buyer-evidence based
Move stages from sales activities to **actions the buyer took**: discovery → meeting held → needs agreed (documented) → pricing presentation agreed → contract review. Activity-based stages are usually front-loaded, inflating the pipeline.

## Coverage ratio
Target ÷ average deal size = required number of opportunities. On new pipeline, **3x coverage** is the baseline — the longer the cycle and the lower the win rate, the more you need 4x+. Multiplying by stage conversion rates yields the required opportunities per stage. Coverage is built linearly every week, not in the final week.

## Velocity · win rate
**Pipeline velocity = #opportunities × average deal size × win rate ÷ average cycle length (days)**. Use sensitivity to pick which of the 4 levers to move. Win rate requires definition consistency — removing cancelled opportunities from the denominator inflates it (keep the as-of-opportunity-creation basis).

## Sludge removal
Deals with 2 consecutive non-responses, or that sit in one stage beyond 2 cycles, are auto-flagged → keep or kill decisions with rationale. A low performer's tell is not opportunity count but stage-move speed.

## Output
Opportunities and conversion rate per stage table, coverage diagnosis (× vs. target), sensitivity across the 4 velocity elements, disposition of 3 sludge deals.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…