founder-cfo
Skill1 starsChanged 13 days agoMITView on GitHub
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".
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- Mrz1nn/founder-skillsedited, first seen Nov 15, 2026
- Jakeschincariol/founder-skilledited, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- Jakeschincariol/founder-skill★ 13185% same
- Mrz1nn/founder-skills★ 085% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- founder-boardSkill
- founder-brandSkill
- founder-competitorsSkill
- founder-consumerSkill
- founder-launchSkill
- founder-marketingSkill
- founder-offerSkill
- founder-opsSkill
- founder-planSkill
- founder-pricingSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Write founder/numbers.json (shape: example.json in this folder, a walk-in matcha café in Berlin).
- Very specific: line 52
Every cost section must be present.
- Very specific: line 73
Staff: Put wages in payroll as gross.
- Very specific: line 91
Ask the user for anything only they know (rent quoted, wages they will pay).
- Very specific: line 123
Add a short section at the top of founder/cfo.md, in plain words:
- Distinctive: line 135
Every number in your note comes from the tool's output or an input you can name.
- Distinctive: line 144
Not financial, tax or legal advice.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
EU edition: prices are in euros (or the local currency) and include VAT the way European customers see them, staff are entered by gross wage with employer social contributions added on top, and German Kleinunternehmer status is checked.
Tool in this folder:
python3 "${CLAUDE_SKILL_DIR}/unit_economics.py" founder/numbers.json --out founder/cfo.mdStep 1: gather the inputs
Write founder/numbers.json (shape: example.json in this folder, a walk-in
matcha café in Berlin). It needs:
| field | what goes in it |
unit | what one sale is: a cup, an order, a client-month, a seat |
currency, number_format | "EUR" and "de" (1.234,56 €) by default; "en" for €1,234.56 |
price | the price per unit as the customer sees it |
price_includes_vat | true for consumer prices (in the EU they must be shown with VAT), false for B2B net prices |
vat_rate | the rate for THIS product, e.g. Germany 0.19 standard or 0.07 reduced; ask if unsure (see below) |
kleinunternehmer | true only if the user will use the German small-business VAT exemption (section 19 UStG) |
variable | the cost of ONE unit, net of VAT you can reclaim: ingredients, packaging, shipping, card fees, commissions |
payroll | staff: {label, gross_monthly, kind} with kind regular or minijob; the tool adds employer costs |
fixed_monthly | everything else you pay monthly: rent and Nebenkosten, Steuerberater, insurance, Berufsgenossenschaft, software |
startup | one-off spend before opening: deposit (Kaution, often 3 months' cold rent), fit-out, equipment, first inventory, launch ads |
days_per_month | 30 if you open every day, about 26 if you close on Sundays (most shops in Germany must) |
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 |
Every cost section must be present; write [] if there really is none. A missing
section makes the plan Incomplete, never "Profitable". Numbers can be JSON
numbers or strings like "5,90"; never write an ambiguous "1.234" (the tool
refuses it).
VAT is where EU plans go wrong. The tool splits the shelf price into net price
and VAT, because VAT is the tax office's money, not revenue. Rates differ by
country and by product (in Germany, for example, food and drinks are treated
differently, and takeaway and eat-in rules have changed over the years). Check
the rate for the exact product on the national tax authority's site or with a
Steuerberater, and write the source in founder/cfo-sources.md. Selling online
to consumers in other EU countries above 10.000 € a year means their VAT rates
and the OSS scheme: flag it.
Kleinunternehmer (Germany). Since 2025 a business can skip charging VAT if last year's turnover was at most 25.000 € and this year's stays at most 100.000 €; in the founding year the 25.000 € line applies. The tool flags the month the plan crosses it. It is a trade-off (simpler, cheaper for consumers, but no input VAT back on the fit-out and equipment), so present it as a question for the Steuerberater, not a recommendation.
Staff. Put wages in payroll as gross. Employer social contributions are
added (defaults: about 21% for regular staff, about 31% for a Minijob in
Germany; override with payroll_oncost). Check every wage is at or above the
statutory minimum wage of the country (Germany: Mindestlohn, 13,90 € an hour in
2026, 14,60 € from 2027) for the hours in the rota, and that a Minijob stays under
its monthly limit (603 € in 2026). For other countries, ask for the local rate
and say it is an estimate.
Where the numbers come from, in this order:
- The user's own quotes, invoices, leases and supplier price lists.
- Public prices the user can check (a supplier's price list, a listing on
ImmoScout24 or a commercial property site, SumUp's or the bank's published
card fees, the Minijob-Zentrale's rates). Write the source next to the number in
founder/cfo-sources.md. - 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.mdIt writes: the per-unit table (shelf price, VAT, net price, unit costs) 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, a payback beyond 12 months, missing cost sections and a Kleinunternehmer plan that outgrows the limit. It also shows the VAT collected in year 1, money to set aside for the Umsatzsteuer-Voranmeldung.
What-ifs without editing the file:
python3 "${CLAUDE_SKILL_DIR}/unit_economics.py" founder/numbers.json --price 6,50
python3 "${CLAUDE_SKILL_DIR}/unit_economics.py" founder/numbers.json --volume 0.8Step 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 in the report is net of VAT. Profit is before income tax and trade tax (Gewerbesteuer in Germany, with a 24.500 € allowance for sole traders and partnerships; corporations such as a UG or GmbH pay corporate tax instead).
- The legal form changes the numbers: a sole trader's own pay is not a cost (it
comes out of profit, and they pay their own health insurance, often 400 to
1.000 € a month in Germany); a GmbH or UG managing director's salary is. Ask
which form, and put the founder's own health insurance in
fixed_monthlyif the business has to cover it. - Not financial, tax or legal advice. Say once that a Steuerberater 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.
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
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.

