ericrisco/rsc-harness / skills/sales-pipeline
sales-pipeline
VerifiedUse when an operator runs deals out of a spreadsheet or Notion and wants real stages, win probabilities, deal hygiene, a weekly follow-up sweep, and a defensible roll-up forecast — including the case where the pipeline looks full but nothing closes. NOT statistical or scenario forecast modelling (that is `forecasting`), NOT sourcing prospects (that is `lead-gen`), NOT writing the outbound emails (that is `cold-outreach`), NOT the proposal or quote (that is `proposals`), NOT the post-close kickoff (that is `client-onboarding`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.8 KB |
| evals/README.md | markdown | 814 B |
| evals/cases.yaml | config | 4.5 KB |
| references/forecasting-math.md | markdown | 3.7 KB |
| references/stage-playbook.md | markdown | 4.0 KB |
| scripts/verify.shexecutable | script | 7.5 KB |
references/forecasting-math.md
View on GitHub# Forecasting math — worked examples and the column contract
This is the simple stage-weighted roll-up that falls out of a clean pipeline.
It is **not** statistical forecasting — no scenarios, no time-series, no cohort
projection. If the ask needs those, route to `forecasting`.
All figures use the load-bearing benchmarks: stage probabilities from the stage
model, the current **~18% B2B win rate** (down from ~21%, with cycles ~12%
longer YoY — *Ebsta/Pavilion 2025 B2B Sales Benchmark*), and the segment
coverage benchmarks below. *(Drivetrain / Coefficient / forecastio.ai; ORM Tech;
First Page Sage — all accessed 2026-06-02.)*
## 1 — Weighted forecast on a 5-deal list
`weighted_value = value × stage win_prob`, then apply stale decay (no touch
14+ days → halve; 30+ days → drop from the roll-up).
| id | value | stage | win_prob | last_touch age | adjustment | weighted |
|---|---|---|---|---|---|---|
| D-1 | 40,000 | Discovery | 0.30 | 3 d | none | 12,000 |
| D-2 | 25,000 | Negotiation | 0.65 | 6 d | none | 16,250 |
| D-3 | 60,000 | Proposal | 0.40 | 18 d | halve (14d+) | 12,000 |
| D-4 | 30,000 | Qualification | 0.10 | 40 d | **drop** (30d+) | 0 |
| D-5 | 50,000 | Negotiation | 0.65 | 2 d | none | 32,500 |
- Raw weighted (no decay): 12,000 + 16,250 + 24,000 + 3,000 + 32,500 = **87,750**.
- Decayed weighted forecast: 12,000 + 16,250 + 12,000 + 0 + 32,500 = **72,750**.
The 15,000 gap is exactly the cost of stale deals — which is why you decay
before you report, never after.
## 2 — Pipeline coverage by segment
`coverage = Total Qualified Pipeline Value ÷ Revenue Target`. "Qualified"
excludes stale (30d+) deals.
| segment | win rate | min | target |
|---|---|---|---|
| Enterprise ($100K+ ACV) | 15–20% | 5× | 6–7× |
| Commercial ($25–100K) | 20–30% | 3.5× | 4–5× |
| SMB (<$25K) | 30–40% | 2.5× | 3–4× |
*(ORM Tech, accessed 2026-06-02.)*
**Worked:** a Commercial team with a $250K quarterly target and $900K of
qualified (non-stale) pipeline has coverage = 900 / 250 = **3.6×**. That clears
the 3.5× minimum but sits below the 4–5× target — adequate, not comfortable.
If coverage drops two weeks running with no closes, escalate; that is the red
flag, not a single low snapshot.
## 3 — Pipeline velocity
`velocity = (Open opps × Avg deal size × Win rate) ÷ Sales-cycle length (days)`
→ dollars/day. *(Salesmotion / ORM Tech.)*
**Worked:** 40 open opps × $30,000 avg × 0.18 win ÷ 90-day cycle =
216,000 / 90 = **$2,400/day**.
Cycle length is the highest-leverage term: cut the 90-day cycle ~20% to 72 days
and velocity rises to 216,000 / 72 = **$3,000/day** — a ~25% lift from one
lever. Use your **real, current** cycle length; a shorter historical cycle
flatters the number the same way an old win rate does.
## 4 — The column contract `verify.sh` enforces
The pipeline artifact (CSV or markdown table) must have a header containing at
least these columns; `verify.sh` is a structural + arithmetic lint over them,
not a judgement of deal quality.
| column | check |
|---|---|
| `stage` | present in header; each value in the allowed set: Prospecting, Qualification, Discovery, Proposal/Demo (or Proposal / Demo), Negotiation, Closed (Won/Lost) |
| `value` | present; numeric |
| `win_prob` | present; `0 ≤ win_prob ≤ 1` |
| `weighted_value` | present; equals `round(value × win_prob)` within tolerance |
| `close_date` | present and non-empty on every **open** deal |
| `next_step` | present and non-empty on every **open** deal |
| `last_touch` | present and non-empty on every **open** deal |
Plus: at least one **coverage** summary line/row must be present somewhere in
the file (a line matching `coverage`). An empty or missing-content file is a
clean pass — the lint never false-fails on nothing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |