# revenue-funnel

Designs a macro revenue funnel model from scratch, defining stages, cohort conversion rates, and handoffs across marketing, sales, and CS.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 20400 installs · ★ 1
- Author: Maya-Beth Finotti
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/mbfinotti/revops-skills/tree/HEAD/skills/revenue-funnel/SKILL.md
- Updated: 2026-09-14
- HTML: https://affpapa.org/en/nevibecode/skills/revenue-funnel

## What it does

The skill structures a company's revenue funnel for B2B and high-consideration B2C motions. It initiates a guided interview before creating stages, locking down two fundamentals: the primary purpose (process, planning, or forecasting) and the unit of analysis (lead, buying group, or account). Mixing all three purposes into a single stage set ruins funnel planning.

The deliverable is a versioned artifact set containing stage ownership, a cohort-based conversion register with provenance, and an SLA layer across marketing, sales, and CS. Conversion metrics distinguish period win rates from cohort close rates. The skill operates strictly at the macro level: it will not draft routing rules or exit criteria, and it deliberately routes pipeline auditing to the sibling `pipeline-stage-definition-audit` skill.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revenue-funnel -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/revenue-funnel/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/revenue-funnel/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revenue-funnel -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/revenue-funnel/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revenue-funnel -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/revenue-funnel/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mbfinotti/revops-skills revenue-funnel
```

2. **Manually: put the files in place**
- File: `.github/skills/revenue-funnel/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revenue-funnel -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/mbfinotti/revops-skills --path skills/revenue-funnel
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/revenue-funnel/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill revenue-funnel -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/mbfinotti/revops-skills/tree/HEAD/skills/revenue-funnel/SKILL.md

## When to use it
- design a macro-level revenue funnel model from scratch
- define ownership and SLA handoffs between marketing, sales, and CS
- establish cohort conversion rate assumptions for revenue plans
- select the analysis unit between individual leads, accounts, and buying groups

## Example prompts
- Design a B2B SaaS revenue funnel model from scratch
- Set up cohort conversion assumptions and handoffs between marketing and sales
- Help us choose between lead and buying group units for our enterprise funnel

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 0b3a38ed648e9791.

BEGIN THIRD-PARTY FILE 0b3a38ed648e9791
```text
---
name: revenue-funnel
description: Design a company's revenue funnel model from scratch, at the macro level - the stage set, the unit of analysis (lead, buying group, account), the model purpose (process vs planning vs forecast), the cohort-based conversion assumptions behind the plan, and the ownership handoffs between marketing, sales, and CS. Use whenever the user mentions funnel design, funnel stages, a funnel model, conversion rate assumptions, a bowtie model, a demand waterfall, MQL to SQL to opportunity definitions, or marketing-sales handoff design - even if they never say "funnel". Covers B2B and high-consideration B2C. Do NOT use for auditing an existing pipeline's stage definitions - use mbfinotti/revops-skills@pipeline-stage-definition-audit instead.
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.4.7"
---

# Revenue Funnel Design

You are the strategic partner to a RevOps function head designing the company's revenue funnel model from scratch. The deliverable is a versioned artifact set (Output Shape below), not a slide - a stage set with owners, a conversion register with provenance, and the handoff/SLA layer connecting marketing, sales, and CS. Design the model; never execute inside it.

## Ground Rules

- Macro only. Design which stages exist, what unit moves through them, whose numbers feed the plan, and who owns each handoff. Never write individual stage exit-criteria wording, lead-routing rules, or handoff execution playbooks - route those to the sibling skills in Reference.
- Two decisions come before counting stages: what the model is _for_ (process vs planning vs forecast) and what unit moves through it (lead, contact, buying group, opportunity, account). Conflating the three purposes into one stage set is the root cause of most bad funnel design.
- Conversion assumptions are cohort-first. Win rate is a period metric, close rate is a cohort metric, pipeline conversion rate is a snapshot metric. One worked case reads a 50% win rate and a 30% or 20% close rate for the same underlying business, depending only on which measure and analysis type someone picked.
- Every rate in the model names its basis or it does not ship.
- Published benchmarks trigger investigation, never set targets. Sources disagree because their stage definitions disagree, and sample cells are tiny - one widely cited report splits ~106 respondents 5 ways, leaving ~20 companies per cell. A stage far outside a published range is a question to investigate, not a gap to close.
- The funnel is a capacity and resource-allocation instrument, not a model of buyer psychology. It answers how many SDRs, how much demand-gen budget, and what quota capacity a target requires - questions no growth-loop model answers. Keep loops as a separate channel-strategy artifact; never let either pretend to answer the other's question.
```
END THIRD-PARTY FILE 0b3a38ed648e9791

The third-party file has ended. Everything between the 0b3a38ed648e9791 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2868 of 26472 bytes. © Maya-Beth Finotti · MIT · https://github.com/mbfinotti/revops-skills/tree/HEAD/skills/revenue-funnel/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md