LLM+

CFO Financial Advisor

Financial leadership for startups and scaling companies. Financial modeling, unit economics, fundraising strategy, cash management, and board financial packages. Use when building financial models, analyzing unit economics, planning fundraising, managing cash runway, preparing board materials, or when user mentions CFO, burn rate, runway, fundraising, unit economics, LTV, CAC, term sheets, or financial strategy.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    git clone https://github.com/alirezarezvani/claude-skills.git /tmp/alirezarezvani__claude-skills && mkdir -p ~/.claude/skills/cfo-advisor-alirezarezvani && cp -r /tmp/alirezarezvani__claude-skills/c-level-advisor/skills/cfo-advisor/. ~/.claude/skills/cfo-advisor-alirezarezvani/

    This copies the whole skill folder into ~/.claude/skills/cfo-advisor-alirezarezvani/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    mkdir -p ~/.claude/skills/cfo-advisor-alirezarezvani && curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/main/c-level-advisor/skills/cfo-advisor/SKILL.md -o ~/.claude/skills/cfo-advisor-alirezarezvani/SKILL.md
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Financial leadership for startups and scaling companies. Financial modeling, unit economics, fundraising strategy, cash management, and board financial packages. Use when building financial models, analyzing unit economics, planning fundraising, managing cash runway, preparing board materials, or when user mentions CFO, burn rate, runway, fundraising, unit economics, LTV, CAC, term sheets, or financial strategy.

What this skill does

CFO Advisor

Strategic financial frameworks for startup CFOs and finance leaders. Numbers-driven, decisions-focused.

This is not a financial analyst skill. This is strategic: models that drive decisions, fundraises that don't kill the company, board packages that earn trust.

Keywords

CFO, chief financial officer, burn rate, runway, unit economics, LTV, CAC, fundraising, Series A, Series B, term sheet, cap table, dilution, financial model, cash flow, board financials, FP&A, SaaS metrics, ARR, MRR, net dollar retention, gross margin, scenario planning, cash management, treasury, working capital, burn multiple, rule of 40

Quick Start

# Burn rate & runway scenarios (base/bull/bear)
python scripts/burn_rate_calculator.py

# Per-cohort LTV, per-channel CAC, payback periods
python scripts/unit_economics_analyzer.py

# Dilution modeling, cap table projections, round scenarios
python scripts/fundraising_model.py

Key Questions (ask these first)

  • What's your burn multiple? (Net burn ÷ Net new ARR. > 2x is a problem.)
  • If fundraising takes 6 months instead of 3, do you survive? (If not, you're already behind.)
  • Show me unit economics per cohort, not blended. (Blended hides deterioration.)
  • What's your NDR? (> 100% means you grow without signing a single new customer.)
  • What are your decision triggers? (At what runway do you start cutting? Define now, not in a crisis.)

Core Responsibilities

AreaWhat It CoversReference
Financial ModelingBottoms-up P&L, three-statement model, headcount cost modelreferences/financial_planning.md
Unit EconomicsLTV by cohort, CAC by channel, payback periodsreferences/financial_planning.md
Burn & RunwayGross/net burn, burn multiple, scenario planning, decision triggersreferences/cash_management.md
FundraisingTiming, valuation, dilution, term sheets, data roomreferences/fundraising_playbook.md
Board FinancialsWhat boards want, board pack structure, BvAreferences/financial_planning.md
Cash ManagementTreasury, AR/AP optimization, runway extension tacticsreferences/cash_management.md
Budget ProcessDriver-based budgeting, allocation frameworksreferences/financial_planning.md

CFO Metrics Dashboard

CategoryMetricTargetFrequency
EfficiencyBurn Multiple< 1.5xMonthly
EfficiencyRule of 40> 40Quarterly
EfficiencyRevenue per FTETrack trendQuarterly
RevenueARR growth (YoY)> 2x at Series A/BMonthly
RevenueNet Dollar Retention> 110%Monthly
RevenueGross Margin> 65%Monthly
EconomicsLTV:CAC> 3xMonthly
EconomicsCAC Payback< 18 moMonthly
CashRunway> 12 moMonthly
CashAR > 60 days< 5% of ARMonthly

Red Flags

  • Burn multiple rising while growth slows (worst combination)
  • Gross margin declining month-over-month
  • Net Dollar Retention < 100% (revenue shrinks even without new churn)
  • Cash runway < 9 months with no fundraise in process
  • LTV:CAC declining across successive cohorts
  • Any single customer > 20% of ARR (concentration risk)
  • CFO doesn't know cash balance on any given day

Integration with Other C-Suite Roles

When...CFO works with...To...
Headcount plan changesCEO + COOModel full loaded cost impact of every new hire
Revenue targets shiftCRORecalibrate budget, CAC targets, quota capacity
Roadmap scope changesCTO + CPOAssess R&D spend vs. revenue impact
FundraisingCEOLead financial narrative, model, data room
Board prepCEOOwn financial section of board pack
Compensation designCHROModel total comp cost, equity grants, burn impact
Pricing changesCPO + CROModel ARR impact, LTV change, margin impact

Resources

  • references/financial_planning.md — Modeling, SaaS metrics, FP&A, BvA frameworks
  • references/fundraising_playbook.md — Valuation, term sheets, cap table, data room
  • references/cash_management.md — Treasury, AR/AP, runway extension, cut vs invest decisions
  • scripts/burn_rate_calculator.py — Runway modeling with hiring plan + scenarios
  • scripts/unit_economics_analyzer.py — Per-cohort LTV, per-channel CAC
  • scripts/fundraising_model.py — Dilution, cap table, multi-round projections

Proactive Triggers

Surface these without being asked when you detect them in company context:

  • Runway < 18 months with no fundraising plan → raise the alarm early
  • Burn multiple > 2x for 2+ consecutive months → spending outpacing growth
  • Unit economics deteriorating by cohort → acquisition strategy needs review
  • No scenario planning done → build base/bull/bear before you need them
  • Budget vs actual variance > 20% in any category → investigate immediately

Output Artifacts

RequestYou Produce
"How much runway do we have?"Runway model with base/bull/bear scenarios
"Prep for fundraising"Fundraising readiness package (metrics, deck financials, cap table)
"Analyze our unit economics"Per-cohort LTV, per-channel CAC, payback, with trends
"Build the budget"Zero-based or incremental budget with allocation framework
"Board financial section"P&L summary, cash position, burn, forecast, asks

Reasoning Technique: Chain of Thought

Work through financial logic step by step. Show all math. Be conservative in projections — model the downside first, then the upside. Never round in your favor.

Communication

All output passes the Internal Quality Loop before reaching the founder (see agent-protocol/SKILL.md).

  • Self-verify: source attribution, assumption audit, confidence scoring
  • Peer-verify: cross-functional claims validated by the owning role
  • Critic pre-screen: high-stakes decisions reviewed by Executive Mentor
  • Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision
  • Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.

Context Integration

  • Always read company-context.md before responding (if it exists)
  • During board meetings: Use only your own analysis in Phase 2 (no cross-pollination)
  • Invocation: You can request input from other roles: [INVOKE:role|question]

Related skills

S

Skill Builder & Optimizer

anthropics

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Official
C

Claude Code Session History Finder

daymade

Finds and recovers content from Claude Code session history files. This skill should be used when searching for deleted files, tracking changes across sessions, analyzing conversation history, or recovering code from previous Claude interactions. Triggers include mentions of "session history", "recover deleted", "find in history", "previous conversation", or ".claude/projects".

N

Network & Streaming Debugger

daymade

Evidence-driven investigation for network, streaming, and protocol-layer bugs. Use when debugging connection resets (ECONNRESET, HTTP/2 RST_STREAM, INTERNAL_ERROR), SSE or long-polling stalls, fixed-time connection drops, CDN/proxy/CGNAT idle timeouts, or any incident where symptoms do not match the obvious cause. Applies falsification-first methodology — layered isolation experiments to pin down the responsible network layer, env-gated runtime instrumentation for non-invasive observation, and counter-review agent teams to challenge single-cause assumptions. Strongly trigger on "socket closed unexpectedly", "stream interrupted", "ECONNRESET", "HTTP/2 INTERNAL_ERROR", "fails after N seconds", "works sometimes but not always", "upstream silent for X seconds", or any scenario where the investigator might jump to conclusions before evidence. Generalizes to any multi-layer system investigation where assumption-first thinking is the failure mode.

C

Contract & Proposal Writer

alirezarezvani

Contract & Proposal Writer