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.
git clone --depth 1 https://github.com/OneWave-AI/claude-skills /tmp/expansion-revenue-finder && cp -r /tmp/expansion-revenue-finder/expansion-revenue-finder ~/.claude/skills/expansion-revenue-finderSKILL.md
# 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`.
Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.
Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.
Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.
Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.
Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.