mcpbeat

Expansion Revenue Finder

onewave-ai/expansion-revenue-finder

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.

6k tokens
context cost
the whole folder, loaded on every use
7
files
instructions only
0
copies elsewhere
how many repositories repackaged it
235
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/OneWave-AI/claude-skills --skill expansion-revenue-finder

The instruction itself

3 sections, as written by the author

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

  • 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.
  • 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.
  • 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.
  • 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.
  • 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.

How to use it

Copy the folder

Take onewave-ai/expansion-revenue-finder from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.