# expansion-revenue-finder

The expansion-revenue-finder skill for Claude Code finds upsell and cross-sell opportunities by analyzing product usage, team growth, and competitive pressure, then scores each by revenue potential, effort, and likelihood.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 247 installs · ★ 440 repo stars
- Author: OneWave-AI
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/OneWave-AI/claude-skills/tree/HEAD/expansion-revenue-finder/SKILL.md
- Updated: 2026-10-20
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/expansion-revenue-finder

## What it does

The skill collects customer data from the working directory, builds a profile for each account, and benchmarks it against its segment to spot under-penetration. It scans seven trigger categories — team growth, feature gaps, industry benchmarks, competitive pressure — and logs an opportunity only when a trigger fires and a matching product is available to sell. Each opportunity gets rated on three dimensions, 1 to 10, then assigned a composite score and tier.

Output lands in `expansion-playbook.md`: opportunities sorted by tier and score, with pitch, timing, and approach for each account. If no structured data exists, the skill will ask you to describe accounts manually and flag reduced scoring confidence. Underutilization is tagged as an activation opportunity, not an upsell.

Without external benchmarks, it uses the portfolio's top quartile as the baseline.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill expansion-revenue-finder -a claude-code
```

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

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill expansion-revenue-finder -a codex
```

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

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill expansion-revenue-finder -a cursor
```

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

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install OneWave-AI/claude-skills expansion-revenue-finder
```

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

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill expansion-revenue-finder -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/OneWave-AI/claude-skills --path expansion-revenue-finder
```

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add OneWave-AI/claude-skills --skill expansion-revenue-finder -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/OneWave-AI/claude-skills/tree/HEAD/expansion-revenue-finder/SKILL.md

## When to use it
- Identify upsell and cross-sell opportunities across existing accounts
- Score expansion plays by revenue potential, effort, and probability
- Benchmark accounts against their segment to find feature under-penetration
- Surface triggers from team growth, feature gaps, and competitive pressure
- Generate a playbook with prioritized opportunities and pitch recommendations

## Example prompts
- Scan customer data in `data/accounts.json` and surface all upsell opportunities
- Build an expansion playbook for accounts in `customers/` and tier them by score
- Benchmark customer profiles against segment and show where features are underused

## 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: bca2c2570f8c6a93.

BEGIN THIRD-PARTY FILE bca2c2570f8c6a93
```text
---
name: expansion-revenue-finder
description: Identifies upsell and cross-sell opportunities within existing customer accounts. Analyzes product usage, feature gaps, team growth, industry benchmarks, and competitive pressure to surface revenue expansion plays scored by potential, effort, and likelihood. Generates an expansion-playbook.md with account-by-account opportunities, recommended pitch, timing, and approach.
tools: Read, Write, Bash, Grep, Glob
model: inherit
---

# Expansion Revenue Finder

Analyze a customer portfolio and identify every viable upsell, cross-sell, and expansion opportunity, then rank them by revenue potential, effort, and probability of success so the account team knows exactly where to focus. Optimize for total portfolio expansion revenue, not individual deal wins. Ground every recommendation in data signals, not wishful thinking.

## Contents

- `references/data-inputs.md` -- where to find account data, what to collect, and the product catalog
- `references/account-profile.md` -- per-account expansion profile and segment benchmarking
- `references/expansion-triggers.md` -- seven trigger categories and the opportunity record template
- `references/scoring.md` -- three-dimension scoring rubric, composite formula, and tier interpretation
- `references/playbook-template.md` -- the full `expansion-playbook.md` output structure
- `references/rules-and-edge-cases.md` -- behavioral rules and edge-case handling

## Workflow

1. **Collect data.** Locate customer data in the working directory and user-specified paths, then assemble the account fields and product catalog. See `references/data-inputs.md`. If no structured data exists, ask the user to describe their accounts and note reduced scoring confidence.

2. **Profile and benchmark each account.** Build an expansion profile per account and compare it against its peer segment to find under-penetration. See `references/account-profile.md`. Without external benchmarks, use the portfolio's top quartile as the benchmark.
```
END THIRD-PARTY FILE bca2c2570f8c6a93

The third-party file has ended. Everything between the bca2c2570f8c6a93 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 2024 of 2893 bytes. © OneWave-AI · MIT · https://github.com/OneWave-AI/claude-skills/tree/HEAD/expansion-revenue-finder/SKILL.md

## Similar
- [expansion-whitespace](https://affpapa.org/en/nevibecode/skills/expansion-whitespace.md) — skill · ★ 36654 repo stars
- [shopify-upsell-cross-sell](https://affpapa.org/en/nevibecode/skills/shopify-upsell-cross-sell.md) — skill · 1200 installs
- [revenue-analytics](https://affpapa.org/en/nevibecode/plugins/revenue-analytics.md) — plugin · ★ 450 repo stars

_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
