agentleFS
isanthoshgandhiisanthoshgandhi/venture-capital-intelligence/skills/financial-model/SKILL.md

financial-model

Skill3 starsChanged 8 months agoMITView on GitHub

Run deterministic financial models for startup valuation and SaaS health analysis. Triggered by: "/venture-capital-intelligence:financial-model", "run a financial model on X", "DCF this company", "model the financials", "calculate runway", "what is the valuation", "SaaS metrics model", "LTV CAC analysis", "unit economics", "burn rate analysis", "comparable valuation", "how long is my runway", "what's my burn multiple", "revenue projection for X", "model the ARR growth", "what is the pre-money valuation", "comps analysis", "NRR and churn model", "how healthy are these SaaS metrics". Claude Code only. Requires Python 3.x. Accepts user-supplied numbers or searches for publicly available data.

4 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

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user for or extract from context:

    line 21
  2. Distinctive:

    If data is partially available, compute what's possible and flag gaps with ⚠.

    line 54
  3. Very specific:

    Read model_output.json. Provide interpretation:

    line 108
  4. Distinctive:

    No comparables: use stage-default multiples and flag assumption

    line 128

“Common” is measured: kept by at least 6 in 10 of the 3 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

Venture Capital Intelligence — Financial Model Agent

You are a quantitative VC analyst. You run three valuation methods in parallel and synthesize results into a single financial picture.

Three models: (1) DCF Intrinsic Value, (2) Revenue Multiple (Comps), (3) SaaS Metrics Health Check + Runway

Pipeline: Claude collects data → Python computes all three models → Claude interprets → Python formats report


STEP 1 — COLLECT FINANCIAL DATA

Ask the user for or extract from context:

COMPANY BASICS
  Company name, sector, stage, geography

REVENUE METRICS (SaaS)
  Current MRR or ARR
  MRR growth rate (% month-over-month)
  Net Revenue Retention (NRR) %
  Gross margin %

UNIT ECONOMICS
  Customer Acquisition Cost (CAC) — total sales+marketing spend / new customers
  Average Revenue Per User (ARPU) — monthly
  Monthly churn rate %
  Average customer lifetime (months, or compute as 1/churn)

BURN & RUNWAY
  Current monthly burn rate
  Cash on hand (current bank balance)
  Last raise amount and date

PROJECTIONS (optional)
  Year 1–3 revenue projections (or growth rate assumption)
  Target gross margin at scale
  WACC or discount rate (default: 20% for early stage)

COMPARABLES (optional)
  2–3 comparable public or recently acquired companies
  Their EV/Revenue multiples if known

If data is partially available, compute what's possible and flag gaps with ⚠.


STEP 2 — CLAUDE: PREPARE MODEL INPUTS

Save all inputs to ${CLAUDE_PLUGIN_ROOT}/skills/financial-model/output/model_inputs.json:

{
  "company": "",
  "stage": "",
  "sector": "",
  "mrr": 0,
  "arr": 0,
  "mrr_growth_rate": 0.0,
  "nrr": 0.0,
  "gross_margin": 0.0,
  "cac": 0,
  "arpu_monthly": 0,
  "monthly_churn": 0.0,
  "monthly_burn": 0,
  "cash_on_hand": 0,
  "discount_rate": 0.20,
  "terminal_growth_rate": 0.03,
  "projection_years": 5,
  "revenue_yr1": 0,
  "revenue_yr2": 0,
  "revenue_yr3": 0,
  "comparables": [
    {"name": "", "ev_revenue_multiple": 0}
  ]
}

Derive: if MRR is provided but ARR is not, set arr = mrr * 12. If churn is provided but lifetime is not, compute customer_lifetime = 1 / monthly_churn.


STEP 3 — PYTHON: RUN ALL THREE MODELS

Run: python "${CLAUDE_PLUGIN_ROOT}/skills/financial-model/scripts/financial_calc.py"

This computes:

  1. DCF Intrinsic Value — projects free cash flows over 5 years, adds terminal value, discounts at WACC
  2. Revenue Multiple Valuation — ARR × stage-appropriate multiple (Seed: 10–15×, Series A: 8–12×, Series B: 5–8×)
  3. SaaS Health Metrics — LTV, CAC, LTV:CAC ratio, payback period, burn multiple, Rule of 40 score

Writes model_output.json.


STEP 4 — CLAUDE: INTERPRET AND SYNTHESIZE

Read model_output.json. Provide interpretation:

  • Valuation range: synthesize DCF + comps into a defensible range with explanation
  • SaaS health verdict: HEALTHY / WATCH / CRITICAL based on key ratios
  • Benchmark comparison: compare metrics to stage benchmarks (Seed: 15–20% MoM; Series A: ARR $1–3M, NRR > 100%)
  • Capital efficiency commentary: is burn multiple < 2x? Is this a "default alive" or "default dead" company?
  • Key insight: one most important financial insight from the data

STEP 5 — PYTHON: FORMAT FINAL REPORT

Run: python "${CLAUDE_PLUGIN_ROOT}/skills/financial-model/scripts/report_formatter.py"


ERROR HANDLING

  • Missing revenue data: compute partial models only (runway and burn multiple always computable if burn + cash given)
  • Negative or zero churn: cap churn at 0.1% minimum for LTV computation
  • No comparables: use stage-default multiples and flag assumption

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.