Skip to main content
skill CX Codex

business-case — Claude Code skill: ROI, NPV, IRR and TCO

business-case is a Claude Code skill that calculates ROI, NPV, IRR, payback period and TCO. It runs when an agent builds a financial case or compares build vs buy.

MIT 162 installs ★ 305 updated 2026-11-07

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add yonatangross/orchestkit --skill business-case -a claude-code
Open on GitHub

What business-case does

Skill builds business cases across five financial frameworks: ROI for quick checks, NPV for multi-year investments, IRR to compare competing projects, payback period for break-even timing, TCO for total cost of ownership. Inside — decision tables, a business case template with sections for costs, benefits and sensitivity analysis, formulas with discount rates (10% enterprise, 15–20% growth, 25–40% startup), and a hidden cost checklist for build/buy/partner comparisons.

Skill uses Read, Glob, Grep, WebFetch and WebSearch commands. For NPV you need a discount rate and cash flow projections by year; for TCO you need CAPEX, OPEX, opportunity costs and hidden costs (training, migration, downtime risk).

What it helps with

  • calculate NPV and IRR for a three-year investment
  • compare TCO for build, buy and partner
  • build a business case with sensitivity analysis
  • estimate payback period for a SaaS platform
  • pick the right framework for a GO/NO-GO decision

Example prompts for the agent

  • Calculate NPV for a project: $50k upfront, $30k annual benefits for three years, 10% discount rate
  • Compare TCO for build vs buy: $100k development cost vs $20k/year SaaS
  • Build a business case with ROI, NPV and sensitivity analysis

How to install business-case

1Skills CLI (Vercel)

npx skills add yonatangross/orchestkit --skill business-case -a claude-code

2Manually: put the files in place

~/.claude/skills/business-case/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/business-case/

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

Questions about business-case

How to install business-case in Claude Code?

Run npx skills add yonatangross/orchestkit --skill business-case -a claude-code, skill installs to ~/.claude/skills/business-case/SKILL.md.

What does the business-case skill do?

Skill calculates ROI, NPV, IRR, payback period and TCO using built-in formulas and templates. Helps build financial cases for investment decisions and build vs buy comparisons.

Which discount rates does business-case use?

Skill provides three ranges: 10% for enterprise, 15–20% for growth companies, 25–40% for startups. You pick the rate based on business type.

Source text

SKILL.md · MIT
---
name: business-case
compatibility: "Claude Code 2.1.277+"
description: "ROI, NPV, IRR, payback and TCO for investment decisions. Use when building a financial justification, cost-benefit or build-vs-buy analysis."
user-invocable: false
disable-model-invocation: false
metadata:
  owner-agent: "product-strategist"
  category: document-asset-creation
  version: "1.0.0"
  author: "OrchestKit"
  complexity: "medium"
  tags: "roi, npv, irr, tco, build-vs-buy, financial-analysis, cost-benefit"
allowed-tools: "Read Glob Grep WebFetch WebSearch"
---

# Business Case

Financial frameworks for investment justification and decision support.

## When to Use Each Framework

| Framework | Use When |
|-----------|----------|
| **ROI** | Quick sanity check; time value of money doesn't matter much |
| **NPV** | Multi-year investments; gold standard for GO/NO-GO |
| **IRR** | Comparing projects competing for the same budget |
| **Payback Period** | Leadership asks "how fast do we break even?" |
| **TCO** | Build vs. buy; total cost including hidden/ongoing costs |
| **Sensitivity Analysis** | High uncertainty; need to stress-test assumptions |

## Decision Tree

```
Is the investment multi-year?
  YES → Use NPV (+ IRR to compare alternatives)
  NO  → ROI is sufficient

Is this a build vs. buy decision?
  YES → TCO comparison across all three options
  NO  → Skip TCO, use NPV/ROI

Are assumptions uncertain?
  YES → Add sensitivity analysis (3 scenarios)
  NO  → Base case only
```

## Quick Reference Formulas

```
ROI = (Net Benefits - Total Costs) / Total Costs × 100%

NPV = Sum(Cash Flow_t / (1 + r)^t) - Initial Investment
  r = discount rate (10% enterprise, 15-20% growth, 25-40% startup)
  Decision: Accept if NPV > 0

IRR = discount rate where NPV = 0
  Decision: Accept if IRR > hurdle rate

Payback Period = Initial Investment / Annual Cash Flow
  Benchmarks: SaaS 6-12 mo, Enterprise platform 12-24 mo, Infra 24-36 mo

TCO = CAPEX + (OPEX × years) + Opportunity Cost + Hidden Costs
```

## Business Case Template

```markdown
# Business Case: [Project Name]

## Executive Summary
[2-3 sentences: what we're investing in and expected return]

## Financial Analysis

### Investment Required
| Item | One-Time | Annual |
|------|----------|--------|
| Development | $X | |
| License / SaaS | | $X |
| Implementation | $X | |
| Training | $X | |
| Maintenance | | $X |
| **Total** | **$X** | **$X** |

### Expected Benefits
| Benefit | Annual Value | Confidence |
|---------|--------------|------------|
| Time savings (X hrs × $Y/hr) | $X | High |
| Error reduction | $X | Medium |
| Revenue uplift | $X | Low |
| **Total** | **$X** | |

### Key Metrics
| Metric | Value |
|--------|-------|
| 3-Year TCO | $X |
| NPV (10% discount) | $X |
| IRR | X% |
| Payback Period | X months |
| ROI | X% |

## Sensitivity Analysis
| Scenario | Discount Rate | Year 1 Benefits | NPV |
|----------|---------------|-----------------|-----|
| Base case | 10% | $X | $X |
| Conservative | 15% | $X × 0.75 | $X |
| Optimistic | 8% | $X × 1.25 | $X |

## Risk Analysis
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| | | | |

## Recommendation
[GO / NO-GO] — [one-sentence rationale]
```

## TCO: Build vs. Buy vs. Partner

See [rules/business-cost-benefit.md](rules/business-cost-benefit.md) for the full 3-year TCO template and hidden cost checklist.

Key hidden costs to never omit:

| Category | Build | Buy |
|----------|-------|-----|
| Opportunity cost | Yes — team blocked from other work | No |
| Switching costs | N/A | Yes — vendor lock-in |
| Downtime risk | You own uptime | Partial SLA coverage |
| Security/compliance | Your responsibility | Shared |

## Common Pitfalls

| Pitfall | Mitigation |
|---------|------------|
| Simple ROI without time value | Always use NPV for multi-year decisions |
| Ignoring soft costs (training, change mgmt) | Add 30% buffer to implementation estimates |
| Optimistic benefit estimates | Use conservative estimates, document assumptions |
| Sunk cost included in forward analysis | Evaluate future costs/benefits only |
| No sensitivity analysis | Always test conservative + optimistic scenarios |

## References

- [ROI & Financial Metrics](rules/business-roi.md) — NPV, IRR, payback period formulas with code examples
- [Cost-Benefit & TCO](rules/business-cost-benefit.md) — Build vs. buy TCO template, hidden costs, sensitivity analysis
- [ROI Calculation Guide](references/roi-calculation-guide.md) — Detailed cost breakdown (CAPEX/OPEX/opportunity cost)
- [Build-Buy-Partner Decision](references/build-buy-partner-decision.md) — Scoring matrix across 5 dimensions

## Related Skills

- `ork:market-sizing` — Size the opportunity before building the business case
- `ork:competitive-analysis` — Assess competitive context and moat for the investment
- `ork:product-frameworks` — Full product strategy toolkit (prioritization, OKRs, personas)

---

Version: 1.0.0

© OrchestKit · MIT · yonatangross/orchestkit

Similar skills

All skills for Finance and business →

From the same set86

The whole set →
browser-tools browser-tools is a Claude Code skill that adds safety rules for browser automation with agent-browser, including scraping ethics, request pacing, local URLs, and authentication. It runs automatically during browser automation. CX Codex +1 191installs scope-appropriate-architecture scope-appropriate-architecture classifies projects into six tiers and picks patterns that fit their scope, preventing microservices for MVPs. Activates during design and complexity checks. CX Codex +1 179installs storybook-mcp-integration The storybook-mcp-integration Claude Code skill connects Storybook MCP tools to work with existing components. The agent can find component docs, open story previews, and run story tests. CX Codex +1 166installs help This skill scans the installed OrchestKit skills and sorts them into categories. It helps you find the workflow or skill that matches a task. CX Codex +1 166installs testing-e2e testing-e2e provides Playwright E2E standards, page object patterns, and axe-core accessibility checks. Activates when editing tests or playwright.config.*. CX Codex +1 160installs interaction-patterns interaction-patterns — a skill for Claude Code supplies UI interaction rules for loading, pagination, overlays and notifications. It comes into play while building these interface behaviors. CX Codex +1 160installs documentation-patterns The documentation-patterns skill provides patterns for READMEs, ADRs, OpenAPI docs, changelogs, and technical writing. Use it when drafting project docs or recording an architecture choice. CX Codex +1 150installs okr-design okr-design is a Claude Code skill for setting goals and defining success metrics. It helps structure OKRs, KPI trees, and experiment measures. CX Codex +1 140installs

Project sponsors

Companies that keep this analytics open