expansion-revenue-finder
About expansion-revenue-finder
A sales-planning skill that analyzes customer portfolios to find and prioritize expansion opportunities. It grounds recommendations in account data and produces a ranked playbook for account teams.
Key features
- 01Account profiling and segment benchmarks
- 02Seven-category trigger scan
- 03Revenue, effort, and likelihood scoring
- 04Prioritized expansion playbook
- 05Portfolio-wide opportunity insights
Use cases
- 01Prioritize accounts for upsell and cross-sell
- 02Compare account penetration within segments
- 03Separate product activation from upsell
- 04Plan outreach using ranked opportunities
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ onewave-ai/ claude-skills --skill expansion-revenue-finderAfter installing, type/expansion-revenue-finderin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/account-profile.mddata-inputs.mdexpansion-triggers.mdplaybook-template.mdrules-and-edge-cases.mdscoring.mdDetails
From the project READMEExpansion 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 catalogreferences/account-profile.md-- per-account expansion profile and segment benchmarkingreferences/expansion-triggers.md-- seven trigger categories and the opportunity record templatereferences/scoring.md-- three-dimension scoring rubric, composite formula, and tier interpretationreferences/playbook-template.md-- the fullexpansion-playbook.mdoutput structurereferences/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.mdto the working directory (or a user-specified path), sorted by tier and composite score, with pitch, timing, approach, and portfolio-wide insights. Seereferences/playbook-template.md.
Apply the behavioral rules and edge-case handling throughout. See references/rules-and-edge-cases.md.