business-finance-fundamentals

Understand essential business finance — profit margins, unit economics, cash flow, LTV/CAC, and the 4 methods to increase revenue. Use when: analyzing business profitability, making pricing decisions, evaluating SaaS unit economics, financial planning.

26 stars

Best use case

business-finance-fundamentals is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Understand essential business finance — profit margins, unit economics, cash flow, LTV/CAC, and the 4 methods to increase revenue. Use when: analyzing business profitability, making pricing decisions, evaluating SaaS unit economics, financial planning.

Teams using business-finance-fundamentals should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/business-finance-fundamentals/SKILL.md --create-dirs "https://raw.githubusercontent.com/TerminalSkills/skills/main/skills/business-finance-fundamentals/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/business-finance-fundamentals/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How business-finance-fundamentals Compares

Feature / Agentbusiness-finance-fundamentalsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Understand essential business finance — profit margins, unit economics, cash flow, LTV/CAC, and the 4 methods to increase revenue. Use when: analyzing business profitability, making pricing decisions, evaluating SaaS unit economics, financial planning.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Business Finance Fundamentals

## Overview

You don't need an MBA to understand business finance. You need to understand five things: how money comes in (revenue), how money goes out (costs), what's left (profit), how long customers stay and pay (LTV), and how much it costs to get them (CAC). Everything else is a variation of these five.

This skill covers the essential financial frameworks from the Personal MBA — the 4 methods to increase revenue, unit economics, LTV/CAC analysis, and the critical distinction between profit and cash flow.

## Instructions

When a user asks about business profitability, unit economics, pricing impact, or financial health, apply these frameworks.

### The 4 Methods to Increase Revenue

Every business in the world can only increase revenue in exactly four ways. There are no exceptions:

1. **Increase the number of customers** — More marketing, better conversion, new channels. Linear impact: 2x customers = 2x revenue (usually hardest and most expensive).

2. **Increase the average transaction size** — Upsells, bundles, premium tiers, add-ons. Example: "Would you like fries with that?" generates billions for McDonald's.

3. **Increase the frequency of transactions** — Subscriptions, consumables, habit-building. Example: Moving from one-time purchase to subscription model = recurring revenue.

4. **Increase prices** — Value-based pricing, premium positioning. Highest leverage: a 10% price increase with no cost change goes straight to profit. Often causes < 5% customer loss.

**The Revenue Impact Formula:**
```
Revenue = Customers × Average Transaction × Frequency × Price
```

A 10% improvement in ALL four factors:
```
1.1 × 1.1 × 1.1 × 1.1 = 1.46 → 46% revenue increase from four 10% improvements
```

### Profit Margin Analysis

**Gross Margin** = (Revenue - Cost of Goods Sold) / Revenue
- SaaS benchmark: 70-85%
- Services benchmark: 40-60%
- Physical products: 30-50%

**Net Margin** = (Revenue - ALL Costs) / Revenue
- Healthy SaaS: 15-25% net margin at scale
- Healthy services: 10-20% net margin

**Why margins matter more than revenue:**
- $1M revenue at 10% margin = $100k profit
- $500k revenue at 40% margin = $200k profit
- The smaller business is more profitable. Revenue is vanity, profit is sanity.

### Unit Economics: LTV and CAC

**Customer Lifetime Value (LTV):**
```
LTV = ARPU / Monthly Churn Rate

Example:
  ARPU = $90/month
  Monthly churn = 5%
  LTV = $90 / 0.05 = $1,800
```

More precise with gross margin:
```
LTV = (ARPU × Gross Margin) / Monthly Churn Rate

Example:
  ARPU = $90, Gross Margin = 80%, Churn = 5%
  LTV = ($90 × 0.80) / 0.05 = $1,440
```

**Customer Acquisition Cost (CAC):**
```
CAC = Total Sales & Marketing Spend / New Customers Acquired

Example:
  Spent $17,000 on marketing last month
  Acquired 50 new customers
  CAC = $17,000 / 50 = $340
```

**The LTV/CAC Ratio — The Single Most Important SaaS Metric:**

| LTV/CAC | Verdict | Action |
|---------|---------|--------|
| < 1:1 | Losing money on every customer | Stop acquiring. Fix product or pricing immediately. |
| 1-2:1 | Barely surviving | Reduce CAC or increase LTV urgently. |
| 2-3:1 | Borderline healthy | Optimize — you have a business but it's fragile. |
| 3-5:1 | Healthy | Good unit economics. Scale carefully. |
| > 5:1 | Excellent or under-investing | Either very efficient or not spending enough on growth. |

**CAC Payback Period:**
```
Payback = CAC / (ARPU × Gross Margin)

Example:
  CAC = $340, ARPU = $90, Gross Margin = 80%
  Payback = $340 / ($90 × 0.80) = 4.7 months
```

Benchmark: Payback should be < 12 months. Under 6 months is excellent.

### Breakeven Analysis

```
Breakeven Point = Fixed Costs / (Price per Unit - Variable Cost per Unit)

Example:
  Fixed costs: $8,000/month (salaries, hosting, tools)
  Price per customer: $90/month
  Variable cost per customer: $12/month (API calls, support)
  Breakeven = $8,000 / ($90 - $12) = 103 customers
```

Below 103 customers: losing money. Above 103: every new customer adds $78/month profit.

### Cash Flow vs Profit

**Profit** is an accounting concept. **Cash flow** is reality. You can be profitable on paper and still go bankrupt (customer pays Net 60, you pay salaries now — profit positive, cash negative, business dead).

**Cash flow rules:**
1. Collect money as fast as possible (annual plans > monthly, prepayment > Net 30)
2. Pay expenses as late as reasonably possible (negotiate terms)
3. Always have 3-6 months of operating expenses in reserve
4. Annual plan with discount is almost always worth it: offer $890/year vs $90/month ($1,080). You get $890 cash NOW.

### Allowable Acquisition Cost

How much CAN you spend to acquire a customer? Max Allowable CAC = LTV x Target Margin. Example: LTV = $1,800, target margin 60%, Max CAC = $1,800 x 0.40 = $720. If actual CAC is $340, you have $380 of headroom to invest more in growth.

## Key Formulas

```
ARPU = MRR / Customer Count
LTV = (ARPU × Gross Margin) / Monthly Churn Rate
CAC = Total Sales & Marketing Spend / New Customers Acquired
LTV/CAC Ratio = LTV / CAC
CAC Payback = CAC / (ARPU × Gross Margin)
Breakeven Customers = (Fixed Costs + Marketing Spend) / (ARPU × Gross Margin)
Max Allowable CAC = LTV × 0.40 (keep 60%, spend up to 40% on acquisition)
```

## Examples

### Example 1: SaaS health check

**User request:** "My SaaS has $45k MRR, 500 customers, 8% monthly churn, $17k/month marketing spend, 50 new customers/month, 75% gross margin, $22k fixed costs. Am I healthy?"

**Output:**
```
SaaS Unit Economics Report:

  ARPU:               $90/month
  LTV:                $844 (low — churn is killing you)
  CAC:                $340
  LTV/CAC:            2.5x — WARNING: Borderline healthy
  CAC Payback:        5.0 months (acceptable)
  Median Customer Life: 12.5 months

  Monthly P&L:
    Revenue:          $45,000
    Gross Profit:     $33,750 (75%)
    - Fixed Costs:    -$22,000
    - Marketing:      -$17,000
    Net Margin:       -$5,250 (-11.7%) ← LOSING MONEY

  Breakeven:          578 customers (you have 500 — 78 short)

  Revenue Lever Impact (10% improvement each):
    #1 Reduce churn 8%→7.2%:     +$5,625/month (HIGHEST IMPACT)
    #2 Increase ARPU $90→$99:    +$4,500/month
    #3 Increase prices 10%:       +$4,500/month
    #4 More customers 50→55/mo:  +$450/month

  Diagnosis: Your #1 problem is churn. At 8%/month, customers live only
  12.5 months on average. Fix churn first — it has the highest ROI.
  If you halve churn to 4%, LTV doubles to $1,688 and you become profitable.
```

### Example 2: Price increase impact modeling

**User request:** "What happens if I raise prices 20% from $49 to $59/month? I have 300 customers."

**Output:**
```
Price Increase Impact Model: $49 → $59/month (+20%)

  Scenario A: No customer loss (best case)
    Revenue: $14,700 → $17,700 (+$3,000/month, +$36k/year)
    If costs unchanged: $3,000/month goes straight to profit

  Scenario B: 5% customer loss (typical)
    Customers: 300 → 285
    Revenue: $14,700 → $16,815 (+$2,115/month, +$25k/year)
    Still a clear win.

  Scenario C: 15% customer loss (aggressive)
    Customers: 300 → 255
    Revenue: $14,700 → $15,045 (+$345/month)
    Marginal win, but fewer customers = lower support cost.

  Break-even churn from price increase:
    You'd need to lose 51+ customers (17%) for this to be net negative.
    Research shows < 5% typically leave after a 20% price increase
    when communicated well with adequate notice.

  Recommendation: DO IT. Grandfather existing customers for 3 months,
  apply new price to all new signups immediately.
```

## Guidelines

- Always calculate LTV with gross margin, not raw ARPU. LTV = (ARPU × Gross Margin) / Churn.
- When churn is above 5% monthly, flag it as the #1 priority. Nothing else matters until churn is fixed.
- Present the 4 revenue levers ranked by impact for the specific business, not in generic order.
- Cash flow warnings should be prominent when a business is profitable on paper but cash-negative.
- Price increase modeling should always include 3 scenarios: no loss, typical loss (5%), and aggressive loss (15%).
- Remind users: "Revenue is vanity, profit is sanity, cash is king."

Related Skills

dexter-finance

26
from TerminalSkills/skills

Build autonomous financial research agents that analyze stocks, SEC filings, earnings calls, and market data to produce investment reports. Use when: automating investment research, building AI-powered stock analysis, creating financial due diligence agents.

zustand

26
from TerminalSkills/skills

You are an expert in Zustand, the small, fast, and scalable state management library for React. You help developers manage global state without boilerplate using Zustand's hook-based stores, selectors for performance, middleware (persist, devtools, immer), computed values, and async actions — replacing Redux complexity with a simple, un-opinionated API in under 1KB.

zoho

26
from TerminalSkills/skills

Integrate and automate Zoho products. Use when a user asks to work with Zoho CRM, Zoho Books, Zoho Desk, Zoho Projects, Zoho Mail, or Zoho Creator, build custom integrations via Zoho APIs, automate workflows with Deluge scripting, sync data between Zoho apps and external systems, manage leads and deals, automate invoicing, build custom Zoho Creator apps, set up webhooks, or manage Zoho organization settings. Covers Zoho CRM, Books, Desk, Projects, Creator, and cross-product integrations.

zod

26
from TerminalSkills/skills

You are an expert in Zod, the TypeScript-first schema declaration and validation library. You help developers define schemas that validate data at runtime AND infer TypeScript types at compile time — eliminating the need to write types and validators separately. Used for API input validation, form validation, environment variables, config files, and any data boundary.

zipkin

26
from TerminalSkills/skills

Deploy and configure Zipkin for distributed tracing and request flow visualization. Use when a user needs to set up trace collection, instrument Java/Spring or other services with Zipkin, analyze service dependencies, or configure storage backends for trace data.

zig

26
from TerminalSkills/skills

Expert guidance for Zig, the systems programming language focused on performance, safety, and readability. Helps developers write high-performance code with compile-time evaluation, seamless C interop, no hidden control flow, and no garbage collector. Zig is used for game engines, operating systems, networking, and as a C/C++ replacement.

zed

26
from TerminalSkills/skills

Expert guidance for Zed, the high-performance code editor built in Rust with native collaboration, AI integration, and GPU-accelerated rendering. Helps developers configure Zed, create custom extensions, set up collaborative editing sessions, and integrate AI assistants for productive coding.

zeabur

26
from TerminalSkills/skills

Expert guidance for Zeabur, the cloud deployment platform that auto-detects frameworks, builds and deploys applications with zero configuration, and provides managed services like databases and message queues. Helps developers deploy full-stack applications with automatic scaling and one-click marketplace services.

zapier

26
from TerminalSkills/skills

Automate workflows between apps with Zapier. Use when a user asks to connect apps without code, automate repetitive tasks, sync data between services, or build no-code integrations between SaaS tools.

zabbix

26
from TerminalSkills/skills

Configure Zabbix for enterprise infrastructure monitoring with templates, triggers, discovery rules, and dashboards. Use when a user needs to set up Zabbix server, configure host monitoring, create custom templates, define trigger expressions, or automate host discovery and registration.

yup

26
from TerminalSkills/skills

Validate data with Yup schemas. Use when adding form validation, defining API request schemas, validating configuration, or building type-safe validation pipelines in JavaScript/TypeScript.

yt-dlp

26
from TerminalSkills/skills

Download video and audio from YouTube and other platforms with yt-dlp. Use when a user asks to download YouTube videos, extract audio from videos, download playlists, get subtitles, download specific formats or qualities, batch download, archive channels, extract metadata, embed thumbnails, download from social media platforms (Twitter, Instagram, TikTok), or build media ingestion pipelines. Covers format selection, audio extraction, playlists, subtitles, metadata, and automation.