DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to calculate real margins, break-even and payback with Founder Skill

Run unit economics on your numbers to see profit per sale, break-even and cash needed.

Who it is forA founder with planned prices and costs who needs to know whether each sale makes money and how long the startup spend takes to earn back.

The problemRevenue projections hide per-sale costs, and it is unclear how many units are needed to cover fixed costs.

The outcomeA CFO report with contribution per sale, profit margin at plan, break-even per day, year 1 by month, cash needed, payback and what-ifs.

What you need first

  • A Claude account, or Claude Code for plugin install and sub-agents
  • Python 3.8 or newer for the tools (no pip install needed)
  • A project folder where the founder/ files will be written

Steps

  1. Install the skills with cp -r founder-skill/skills/founder-* ~/.claude/skills/ or by pasting the repo link into Claude.
  2. Run /founder-cfo or fill in founder/numbers.json using skills/founder-cfo/example.json as the template.
  3. Run python3 skills/founder-cfo/unit_economics.py founder/numbers.json --out founder/cfo.md to produce the report.
  4. Replace the estimates with real supplier quotes and rerun the command.

Prompt for your agent

Using the Jakeschincariol/founder-skill repo, build founder/numbers.json for <business name> from the prices and costs I give you, then run `python3 skills/founder-cfo/unit_economics.py founder/numbers.json --out founder/cfo.md`. Output the contribution per sale, break-even per day and year 1 totals from cfo.md. Verify that every number traces to an input and that missing fields produce an error rather than a guessed value.

Caveat. The CFO marks every estimate as an estimate, so check costs with suppliers and payroll and tax with an accountant.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page