Build ROI analyses, TCO comparisons, and value calculators for prospects. Use this skill when a rep needs to justify the investment to a prospect, build a business case with numbers, create an ROI model, compare total cost of ownership, says "build me an ROI calculator", "what's the payback period", "help me show the value", "TCO comparison", or when a prospect asks "what's the return on this?". Also trigger when building value engineering tools, cost-benefit analyses, or investment justification documents.
Builds custom ROI analyses and TCO comparisons using prospect data to quantify investment value and payback periods.
/plugin marketplace add https://www.claudepluginhub.com/api/plugins/jbalbu01-sales-enablement-2/marketplace.json/plugin install jbalbu01-sales-enablement-2@cpd-jbalbu01-sales-enablement-2This skill inherits all available tools. When active, it can use any tool Claude has access to.
Help reps quantify the value of their solution in the prospect's specific context. An ROI analysis turns "our product is great" into "here's exactly how much money this saves you and how fast you'll see the return." It's the single most powerful tool for getting budget approved.
┌─────────────────────────────────────────────────────────────────┐
│ ROI CALCULATOR │
├─────────────────────────────────────────────────────────────────┤
│ MODELS │
│ 1. ROI Analysis — Return on investment with payback period │
│ 2. TCO Comparison — Total cost of ownership vs alternatives │
│ 3. Cost of Inaction — What it costs to NOT buy your solution │
│ 4. Value Calculator — Interactive model prospects can customize │
├─────────────────────────────────────────────────────────────────┤
│ OUTPUT │
│ • Financial model with assumptions clearly stated │
│ • Executive-ready summary │
│ • Sensitivity analysis (best/likely/worst case) │
│ • Interactive HTML calculator (if requested) │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Deal size, company revenue, and team context │
│ + ~~CRM: Current solution and contract details │
│ + ~~conversation intelligence (Gong): Discovery call metrics │
│ + ~~conversation intelligence (Gong): Prospect-stated costs │
│ + ~~data enrichment (ZoomInfo): Company financials & headcount │
│ + ~~data enrichment (ZoomInfo): Industry and tech stack context │
│ + ~~data enrichment (Clay): Company enrichment and signals │
│ + ~~data enrichment (LinkedIn): Company growth and hiring data │
└─────────────────────────────────────────────────────────────────┘
CRITICAL: Before asking for pricing and cost data, pull everything from connected tools. Real company data makes the ROI model dramatically more credible than industry averages.
Check if you have access to CRM tools (look for tools containing search_crm_objects, get_crm_objects, or similar).
If CRM tools ARE available:
deals for the company/deal name the user mentioned.
dealname, amount, dealstage, closedate, pipeline, hubspot_owner_id, dealtype, descriptionamount field gives you the investment number for the ROI modelname, domain, industry, numberofemployees, annualrevenue, description, founded_yearfirstname, lastname, jobtitle, emailZoomInfo (if available):
zoominfo_search_company with the prospect company name/domain.
zoominfo_get_tech_stack for the prospect company.
Clay (if available):
clay_enrich_company with the prospect company domain.
LinkedIn (if available):
linkedin_search_companies for hiring trends and growth indicators.
Check if you have access to Gong tools (look for tools prefixed with gong_).
If Gong tools ARE available:
gong_search_calls with the company name.gong_get_transcript on discovery calls.
"I pulled context for the [Company] ROI model: $[X] deal size per CRM. Per ZoomInfo, they're a $[X]M revenue company with [N] employees in [industry]. [If Gong:] On the discovery call, they mentioned spending $[X] per month on [current solution] and losing [N] hours per week to [problem]. Building the ROI model with their actual numbers now..."
After the auto-pull, ask ONLY for what the tools couldn't provide:
Build using ALL evidence. Use prospect-stated numbers (from Gong) as primary inputs. Use ZoomInfo/CRM data as secondary inputs. Use industry benchmarks only as fallback. Cite sources: "Per prospect (Gong discovery call):", "Per CRM:", "Per ZoomInfo:", "Industry benchmark:"
memory/deal-patterns.md with ROI drivers that resonate by industry/personamemory/product.md with new cost/value data points discoveredmemory/changelog.mdAbout your solution:
About the prospect:
Don't worry if you don't have everything — I'll use reasonable industry assumptions and clearly label them. The prospect can adjust.
# ROI Analysis: [Your Solution] for [Company]
**Prepared:** [Date]
**Annual Investment:** $[amount]
**Projected Annual Return:** $[amount]
**ROI:** [X]%
**Payback Period:** [X months]
---
## Executive Summary
[2-3 sentences: "Based on [Company]'s specific situation, we project a [X]% ROI with a [X]-month payback period. The primary value drivers are [top 2-3]. Conservative estimates suggest $[X] in annual savings/revenue impact."]
---
## Investment
| Component | Annual Cost |
|-----------|-----------|
| [Product/license] | $[amount] |
| [Implementation] | $[amount] (one-time) |
| [Training] | $[amount] (one-time) |
| **Total Year 1** | **$[amount]** |
| **Annual Recurring** | **$[amount]** |
---
## Value Drivers
### 1. [Value Driver Name] — $[amount]/year
**Current State:** [What they do today and what it costs]
**Future State:** [What changes with your solution]
**Calculation:**
- [Input] × [Rate] × [Factor] = $[amount]
**Assumption:** [Clearly state the assumption and how to verify]
### 2. [Value Driver Name] — $[amount]/year
[Same structure]
### 3. [Value Driver Name] — $[amount]/year
[Same structure]
---
## Three-Year Projection
| | Year 1 | Year 2 | Year 3 | Total |
|---|--------|--------|--------|-------|
| **Investment** | $[X] | $[X] | $[X] | $[X] |
| **Returns** | $[X] | $[X] | $[X] | $[X] |
| **Net Value** | $[X] | $[X] | $[X] | $[X] |
| **Cumulative ROI** | [X]% | [X]% | [X]% | [X]% |
---
## Sensitivity Analysis
| Scenario | Annual Return | ROI | Payback |
|----------|-------------|-----|---------|
| **Conservative** (50% of projected) | $[X] | [X]% | [X] months |
| **Expected** | $[X] | [X]% | [X] months |
| **Optimistic** (150% of projected) | $[X] | [X]% | [X] months |
Even in the conservative scenario, the investment pays for itself in [X] months.
---
## Cost of Delay
Every month you wait costs approximately $[monthly impact]:
- [Cost element 1]: $[X]/month
- [Cost element 2]: $[X]/month
Over a typical [X]-month evaluation cycle, the cost of delay is $[total].
---
## Assumptions and Methodology
| Assumption | Value | Source |
|-----------|-------|--------|
| [Assumption 1] | [Value] | [Prospect-provided / Industry benchmark / Estimate] |
| [Assumption 2] | [Value] | [Source] |
All assumptions are adjustable. We recommend validating these numbers with your finance team.
---
## Sources
- [Industry benchmarks used]
- [Research cited]
When requested, I can build an HTML calculator the rep can share with the prospect. It includes:
This is powerful because it puts the prospect in control — they trust their own numbers more than yours.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.