agentleFS
elvismuslielvismusli/business-validator/skills/financial-modeling/SKILL.md

financial-modeling

Skill1 starsChanged 9 months agoMITView on GitHub

Use after market-research to build a financial model with unit economics, revenue forecasts, and break-even analysis — requires run_id from idea-intake

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read all three input files using the exact run_id.

    line 53
  2. Very specific:

    If the brief lacks detail, ask the user via AskUserQuestion:

    line 60
  3. Distinctive:

    LTV/CAC ratio: Must be greater than 3 for viability

    line 72
  4. Very specific:

    Ensure the output directory exists: mkdir -p docs/reports/<run_id>

    line 90
  5. Distinctive:

    All numbers must show their assumptions

    line 150
  6. Distinctive:

    Use industry benchmarks where available, cite sources

    line 151

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Financial Modeling

Overview

Build a basic financial model for a business idea based on the business brief and market research data. Includes unit economics, 3-scenario revenue forecast, cost structure, and break-even analysis.

<HARD-GATE> You MUST have the run_id and read both the business brief AND the market research section before building the model. Financial projections without market data are guesswork. Required files: - `docs/business-briefs/<run_id>.md` - `docs/reports/<run_id>/01-market-research.md` - `docs/reports/<run_id>/02-competitor-analysis.md` (for pricing benchmarks) </HARD-GATE>

Inputs

  • run_id: From idea-intake (format: YYYY-MM-DD-<slug>-<hhmm>)
  • Business brief: docs/business-briefs/<run_id>.md
  • Market research: docs/reports/<run_id>/01-market-research.md
  • Competitor analysis: docs/reports/<run_id>/02-competitor-analysis.md

Output

  • File: docs/reports/<run_id>/03-financial-model.md

Process

digraph financial_modeling {
    "Verify run_id and read inputs" [shape=box];
    "Ask clarifying questions if needed" [shape=box];
    "Calculate unit economics" [shape=box];
    "Build cost structure" [shape=box];
    "Create 3-scenario forecast" [shape=box];
    "Calculate break-even" [shape=box];
    "Write 03-financial-model.md" [shape=box, style=filled, fillcolor="#e8f5e9"];

    "Verify run_id and read inputs" -> "Ask clarifying questions if needed";
    "Ask clarifying questions if needed" -> "Calculate unit economics";
    "Calculate unit economics" -> "Build cost structure";
    "Build cost structure" -> "Create 3-scenario forecast";
    "Create 3-scenario forecast" -> "Calculate break-even";
    "Calculate break-even" -> "Write 03-financial-model.md";
}

Step 1: Read Inputs

Read all three input files using the exact run_id. Extract:

  • Target audience and willingness to pay (from brief)
  • Market size and growth (from market research)
  • Competitor pricing (from competitor analysis)

Step 2: Ask Clarifying Questions (if needed)

If the brief lacks detail, ask the user via AskUserQuestion:

  • Expected average price point
  • Main cost categories
  • Team size at launch
  • Customer acquisition channels

Step 3: Build the Model

Unit Economics

  • CAC (Customer Acquisition Cost): Based on industry benchmarks + stated channels
  • ARPU (Average Revenue Per User): Based on pricing model
  • LTV (Lifetime Value): ARPU multiplied by average customer lifespan
  • LTV/CAC ratio: Must be greater than 3 for viability

Cost Structure

  • Fixed costs (team, infrastructure, tools)
  • Variable costs (per-customer costs)
  • One-time costs (development, legal, launch)

Revenue Forecast (3 scenarios, months 1-36)

  • Pessimistic: Low acquisition, high churn
  • Base: Industry-average metrics
  • Optimistic: Strong product-market fit

Break-even Analysis

  • Monthly fixed costs divided by (ARPU minus variable cost per customer)
  • Months to break-even in each scenario

Step 4: Write Output

Ensure the output directory exists: mkdir -p docs/reports/<run_id>

Save to docs/reports/<run_id>/03-financial-model.md:

## Financial Model

**Run ID:** <run_id>

### Unit Economics

| Metric | Value | Assumption |
|--------|-------|------------|
| ARPU (Monthly) | $X | [basis] |
| CAC | $X | [basis] |
| LTV | $X | [calculation] |
| LTV/CAC | X.X | [interpretation] |
| Gross Margin | X% | [basis] |

### Cost Structure

| Category | Monthly Cost | Type |
|----------|-------------|------|
| Team | $X | Fixed |
| Infrastructure | $X | Fixed |
| Marketing | $X | Variable |
| [Other] | $X | [type] |
| **Total Fixed** | **$X** | |
| **Variable per Customer** | **$X** | |

### Revenue Forecast (36 months)

| Month | Pessimistic | Base | Optimistic |
|-------|-------------|------|------------|
| 3 | $X | $X | $X |
| 6 | $X | $X | $X |
| 12 | $X | $X | $X |
| 24 | $X | $X | $X |
| 36 | $X | $X | $X |

### Break-Even Analysis

| Scenario | Customers Needed | Months to Break-Even |
|----------|-----------------|---------------------|
| Pessimistic | X | X |
| Base | X | X |
| Optimistic | X | X |

### Key Assumptions
- [Assumption 1]
- [Assumption 2]

### Financial Health Indicators
- Burn rate: $X/month
- Runway (with stated budget): X months
- Funding gap (if any): $X

Quality Standards

  • All numbers must show their assumptions
  • Use industry benchmarks where available, cite sources
  • State uncertainty ranges for key assumptions
  • Flag any metrics below healthy thresholds (e.g. LTV/CAC less than 3)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.