Skip to main content
skill CX Codex

expansion-revenue-finder — Claude Code skill: what it does

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.

MIT 247 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill expansion-revenue-finder -a claude-code
Open on GitHub

What expansion-revenue-finder 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.

What it helps with

  • 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 for the agent

  • 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

How to install expansion-revenue-finder

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill expansion-revenue-finder -a claude-code

2Manually: put the files in place

~/.claude/skills/expansion-revenue-finder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/expansion-revenue-finder/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about expansion-revenue-finder

How to install expansion-revenue-finder in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill expansion-revenue-finder -a claude-code, the skill will land in ~/.claude/skills/expansion-revenue-finder/SKILL.md.

What does expansion-revenue-finder do?

The skill analyzes customer accounts, surfaces upsell and cross-sell triggers (team growth, feature gaps, competitive pressure), scores each opportunity by revenue, effort, and likelihood, and generates a playbook with priorities and pitch recommendations.

What if I don't have structured customer data?

The skill will prompt you to describe accounts manually and flag reduced scoring confidence in the playbook, using the portfolio's top quartile as the benchmark instead of external data.

Source text

SKILL.md · MIT
---
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.

3. **Scan for triggers.** Check every trigger category for each account. Record an opportunity only when a trigger fires AND a matching product/feature is available to sell. Capture each as a structured opportunity record. See `references/expansion-triggers.md`. Flag underutilization as a separate "activation opportunity," not an upsell.

4. **Score and tier.** Rate each opportunity on revenue potential, effort, and likelihood (1-10 each), compute the composite, and assign a tier. See `references/scoring.md`.

5. **Generate the playbook.** Write `expansion-playbook.md` to the working directory (or a user-specified path), sorted by tier and composite score, with pitch, timing, approach, and portfolio-wide insights. See `references/playbook-template.md`.

Apply the behavioral rules and edge-case handling throughout. See `references/rules-and-edge-cases.md`.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Marketing and content →

From the same set185

The whole set →
okr-generator okr-generator builds a structured okr-plan.md file using the Google and Intel framework from your company targets and team baselines. CX Codex +1 250installs renewal-predictor The renewal-predictor skill analyzes seven account health dimensions—engagement, support, adoption, satisfaction, billing, stakeholder continuity. CX Codex +1 249installs utm-link-generator utm-link-generator builds UTM-tagged links under unified naming rules, tracks duplicates, and outputs variants for LinkedIn, email, social, and ads. CX Codex +1 249installs saas-replacement-planner saas-replacement-planner analyzes your SaaS stack and produces a replacement plan with ROI calculations, implementation timeline, and risk assessment for switching to AI agents. CX Codex +1 247installs agent-swarm-deployer agent-swarm-deployer deploys parallel sub-agent swarms for heavy data jobs like bulk document summarization, dataset processing, and multi-record content generation. CX Codex +1 247installs churn-autopsy churn-autopsy — a skill for post-mortem analysis of client churn. Collects interaction history, support tickets, usage logs and exit feedback, then builds a timeline of decline and identifies root causes. CX Codex +1 244installs scout-pro scout-pro scans conversation history, verifies installed tools, and builds multi-skill chains tailored to your current development task. CX Codex +1 244installs hyperframes-ad-director hyperframes-ad-director turns a marketing brief into a finished short-form video ad built in HyperFrames: hook, script, storyboard, HTML composition, captions, and voiceover. CX Codex +1 185installs

Project sponsors

Companies that keep this analytics open