Financial modeling

Skill mfwarren/entrepreneur-claude-skills/skills/finance/financial-modeling

Production-ready entrepreneurship skills for Claude Code — marketing, sales, operations, finance, and leadership. 24 skills built by a founder, for founders.From the repository description

Install

npx -y skills add mfwarren/entrepreneur-claude-skills --skill financial-modeling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, 520 tokens by cl100k_base, as published. Nobody here has run it

Financial Modeling

Revenue forecasts, expense modeling, cash flow projections, and scenario analysis.

Purpose

Build financial models that help founders make decisions — not impress investors with hockey sticks. Focus on the assumptions that matter and the scenarios that could kill the business.

Workflow

Step 1: Gather Context

Business model and revenue streams
Current monthly revenue and expenses (or estimates)
Growth assumptions and drivers
Planned hires or major expenses
Funding status and runway needs

Step 2: Revenue Model

Build bottom-up from drivers:

Customers x ARPU = Revenue (SaaS)
Traffic x Conversion Rate x AOV = Revenue (e-commerce)
Clients x Project Value x Utilization = Revenue (services)
Units x Price = Revenue (CPG/product)

Monthly projections for 12-24 months.

Step 3: Expense Model

Categorize:

Fixed costs (rent, salaries, SaaS tools)
Variable costs (COGS, commissions, shipping)
Growth investments (marketing spend, new hires)

Step 4: Cash Flow

Revenue - Expenses = Net burn/profit
Cash balance projection
Runway calculation: Cash / Monthly Burn = Months of runway

Step 5: Scenario Analysis

Three scenarios:

Base case: Realistic assumptions
Upside case: Things go well (what changes)
Downside case: Things go badly (what breaks)

For each: when do you run out of cash? When do you break even?

Step 6: Key Metrics Dashboard

Monthly Recurring Revenue (MRR)
Burn rate
Runway
Gross margin
Growth rate (MoM)

Output Format

## Financial Model: [Business Name]

### Revenue Projections (12 months)
| Month | Revenue | Expenses | Net | Cash Balance |
|-------|---------|----------|-----|-------------|

### Key Assumptions
[Listed and explained]

### Scenario Analysis
| Scenario | Break-even | Runway | Key Risk |
|----------|-----------|--------|----------|

### Dashboard Metrics
[Current key metrics]

Constraints

Always label assumptions explicitly — the model is only as good as its inputs
Don't project beyond what's reasonable for the business stage
Flag when the user's growth assumptions are unrealistic
Note that this is a planning tool, not a guarantee
Cash flow matters more than P&L for startups — always include it

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most finance skills give in 520 tokens

Counted across 469 of the 469 authors here whose files we hold, read 2026-08-07

Extract date vendor amount and descriptionin 15 of 469, across 3 files
Scan folder for invoice filesin 14 of 469, across 2 files
Rename files to standard formatin 14 of 469, across 2 files
Show organization plan before movingin 14 of 469, across 2 files
Generate summary CSVin 14 of 469, across 2 files
Organize files by categoryin 13 of 469, across 1 file
Preserve original filesin 13 of 469, across 1 file
Flag files missing critical infoin 13 of 469, across 1 file
Produce the requested output filein 9 of 469, across 4 files
Build best, base, and worst case scenariosin 9 of 469, across 5 files
Implement backoff if rate limit errors occurin 8 of 469, across 3 files
Determine the weighted average cost of capitalin 8 of 469, across 4 files

Said here and by no other author read

gather business model and revenue stream context
project monthly revenue and expenses for twelve to twenty-four months
include a key metrics dashboard
always label assumptions explicitly
flag unrealistic growth assumptions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.