← Back to list
⚡

founder-cfo Checked

Your CFO. Builds the unit economics of a business before money is spent: what one unit earns afte…
⚡ Productivity skills By Jakeschincariol Version v1.0.0 Added 2026-10-12 Updated 2026-10-12 Source ↗
9.3Overall rating
0Views
0Downloads
313Stars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "founder-cfo" skill by following the instructions at https://skill123.me/install/founder-cfo.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/founder-cfo.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 7 KB
📊 Static rating
9.3/10
Trigger
8.0
Structure
8.0
Workflow
10.0
Content
10.0
Engineering
10.0
Security
10.0

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

Your CFO. Builds the unit economics of a business before money is spent: what one unit earns after its direct costs, the real profit margin at the planned volume, the break-even point in units a day, year 1 month by month, the cash needed before it pays for itself, how long the startup spend takes to earn back, and what happens if the price drops, sales come in low or costs rise. Every number traces to an input the user can check. Use when the user says "find the profit margins", "do the numbers", "is this profitable", "break-even", "unit economics", "how much do I need to start", or "run the CFO".

founder-cfo

The person who asks "and what does that cost?" Margins decide whether a good idea

is a business. This skill finds them, with every number traceable to an input.

Tool in this folder:


python3 "${CLAUDE_SKILL_DIR}/unit_economics.py" founder/numbers.json --out founder/cfo.md

Documentation

Your CFO. Builds the unit economics of a business before money is spent: what one unit earns after its direct costs, the real profit margin at the planned volume, the break-even point in units a day, year 1 month by month, the cash needed before it pays for itself, how long the startup spend takes to earn back, and what happens if the price drops, sales come in low or costs rise. Every number traces to an input the user can check. Use when the user says "find the profit margins", "do the numbers", "is this profitable", "break-even", "unit economics", "how much do I need to start", or "run the CFO".

founder-cfo

The person who asks "and what does that cost?" Margins decide whether a good idea

is a business. This skill finds them, with every number traceable to an input.

Tool in this folder:


python3 "${CLAUDE_SKILL_DIR}/unit_economics.py" founder/numbers.json --out founder/cfo.md

Step 1: gather the inputs

Write founder/numbers.json (shape: example.json in this folder, a walk-in

matcha café). It needs:

| field | what goes in it |

| --- | --- |

| unit | what one sale is: a cup, an order, a client-month, a seat |

| price | price per unit before tax |

| variable | the cost of ONE unit: ingredients, packaging, shipping, card fees, per-sale commissions |

| fixed_monthly | what you pay every month regardless: rent, salaries, software, insurance |

| startup | one-off spend before opening: deposits, build-out, equipment, first inventory, launch ads |

| plan_per_day | the volume once it is up and running |

| ramp_per_day | 12 numbers: realistic volume in each month of year 1 |

| capacity_per_day | the most you can physically sell in a day, if there is a limit |

Where the numbers come from, in this order:

1. The user's own quotes, invoices, leases and supplier price lists.

2. Public prices the user can check (a supplier's price list, a landlord's listing,

a payment processor's published fees). Write the source next to the number in

founder/cfo-sources.md.

3. Your estimate, clearly marked as an estimate, with the reasoning. Never present

an estimate as a fact.

Ask the user for anything only they know (rent quoted, wages they will pay). Use the

price from founder/pricing.md or founder/pitch.md if those exist.

**The ramp is where plans lie.** Month 1 is almost never the plan volume. If the

buyer panel ran, use its buy rate and first-month purchases to sanity-check the

ramp (founder/panel/results.md), and say how you did it.

Step 2: run it


python3 "${CLAUDE_SKILL_DIR}/unit_economics.py" founder/numbers.json --out founder/cfo.md
View full documentation

It writes: the per-unit table and the contribution (what each sale leaves after

its own costs), fixed costs, the break-even in units a day, the profit margin at

the plan volume, year 1 month by month, the year 1 operating profit and the result

after the startup spend, the cash needed before it pays for itself, the month the

startup money is earned back, and a what-if table (price -10%, volume -20%, unit

costs +15%). It flags a price below variable cost, a break-even above capacity, a

losing year 1 and a payback beyond 12 months.

What-ifs without editing the file:


python3 "${CLAUDE_SKILL_DIR}/unit_economics.py" founder/numbers.json --price 7.00
python3 "${CLAUDE_SKILL_DIR}/unit_economics.py" founder/numbers.json --volume 0.8

Step 3: the CFO's note

Add a short section at the top of founder/cfo.md, in plain words:

  • **The margin**: the profit margin at plan, and the contribution per unit.
  • **The line to watch**: the one cost or assumption that moves the result most

(usually the ramp, rent or the price), with the what-if that proves it.

  • **Cash**: how much money the founder needs before it pays for itself.
  • **Three ways to improve the margin**, each with the number it changes and by how

much (run the what-if, do not guess).

  • Whether the board's conditions about money (founder/board.md) are met.

Rules

  • Every number in your note comes from the tool's output or an input you can name.
  • Revenue is before tax; say if the user's market adds sales tax on top.
  • Not financial, tax or legal advice. Say once that an accountant should check the

structure, payroll costs and tax before money moves.

Output

founder/numbers.json, founder/cfo.md, founder/cfo-sources.md. Next:

/founder-plan uses these numbers for the verdict; /founder-pricing if the

margin is thin.

Score breakdown

Trigger
8.0
Rich What (margins, break-even, cash needed, payback, what-if scenarios) and When with many phrasings ('find the profit margins','do the numbers','break-even','unit economics','how much do I need to start'). No explicit When-Not clause.
Structure
8.0
102-line SKILL.md. unit_economics.py and example.json live at skill root rather than scripts/ and assets/, the main structural weakness; no redundant files, good use of the example as input schema documentation.
Workflow
10.0
Model work (gathering, source-priority rules, sanity-checking ramp against panel data) is separated from deterministic math in the script. Script refuses to fill in missing fields and flags price-below-variable-cost, break-even-above-capacity, losing year 1, payback beyond 12 months. CFO note must cite tool output, and improvements must be proven by running what-ifs, not guessing.
Content
10.0
Concise imperative style; commands copy-pasteable with argument variants (--price 7.00, --volume 0.8); input table maps every JSON field to its meaning.
Engineering
10.0
Valid frontmatter with argument-hint. Script has shebang, stdlib-only declaration, full usage docstring. All referenced paths exist; ${CLAUDE_SKILL_DIR} resolution documented.
Security
10.0
Capability manifest: reads founder/numbers.json and sibling founder/*.md inputs; writes founder/numbers.json, cfo.md, cfo-sources.md; script opens only the input file and the --out file; no network (verified by grep: no urllib/requests/subprocess/eval); no credentials; no persistence. Capabilities match declared scope.
Tool-wrapper CFO skill: a 270-line stdlib-only Python calculator (unit economics, break-even, year-1 monthly, payback, what-ifs) plus disciplined input-gathering rules (source priority, estimates marked, sources file). Excellent traceability and error flags. Only structural nit: script and example.json sit at skill root instead of scripts/ and assets/.