CommunityCoding & Developmentgithub.com

burn-test

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".

What is burn-test?

burn-test is a Claude Code agent skill that 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".

Works with✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/peaknr35/shark-Tank-proof/tree/main/skills/burn-test

Installed? Explore more Coding & Development skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

What does burn-test do?

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, and says plainly how many of those inputs are real.

Read ${CLAUDE_SKILL_DIR}/../receipts/rules.md first.

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:

fieldwhat goes in it
unitwhat one sale is: a cup, an order, a client-month, a seat
priceprice per unit before tax
variablethe cost of ONE unit: ingredients, packaging, shipping, card fees, per-sale commissions
fixed_monthlywhat you pay every month regardless: rent, salaries, software, insurance
startupone-off spend before opening: deposits, build-out, equipment, first inventory, launch ads
plan_per_daythe volume once it is up and running
ramp_per_day12 numbers: realistic volume in each month of year 1
capacity_per_daythe 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.

Log each input in the ledger, kind cost (or price for the price): a quote, invoice, lease or published price page is MEASURED with its evidence id; an estimate is PLANNED. The plan reports how many costs are backed.

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. The panel's numbers are an upper bound; if no real buyer has committed yet, the honest ramp is lower than the panel suggests, never higher.

Step 2: run it

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

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 hard truth: the number most likely to sink it, and how many of the inputs are quotes versus estimates ("4 of 11 costs are quoted; the ramp is a guess").
  • The bad case: run --volume 0.5 and report it in one line. If there is no real demand evidence yet, this is as likely as the plan.
  • 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.
  • Every output of the model (margin, break-even, year 1, payback) is PLANNED. Never call a projected margin "the real margin" or a result.
  • 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: /kill-or-build uses these numbers for the verdict; /litmus if the margin is thin.

Individual skills in this repo

This repo contains 5 individual skills — each has its own dedicated page.

dealbreaker

Builds an offer too good to refuse. Lists every problem the buyer hits on the way to the result they want, turns each into a solution, trims to what is cheap to deliver and valuable to the buyer, and stacks it with honest bonuses, a guarantee the CFO can afford, real urgency and a clear name. Scores it on the value equation (outcome, likelihood, time, effort) and re-tests it on a quick buyer panel. Use when the user says "make my offer better", "why won't people buy", "what should I include", "guarantee", "bonuses", "grand slam offer", or after the panel shows people passing.

handshake

Turns the founder folder into the thing that gets one real person to say yes to the next step: a one-page pilot offer for a customer, an NSF Project Pitch or grant answer for a funder, an investor or lender one-pager, a business case for a boss, or an invite for the people who will use it. Always writes the one-sentence, three-sentence and three-minute versions first. Builds only from claims in the evidence ledger that the audience may see, never from simulated buyers, and checks the finished pitch with the ledger before it goes out. Use when the user says "pitch this", "write a pilot offer", "one-pager", "grant pitch", "NSF pitch", "deck for", "email this customer", "business case", or "what do I send them".

kill-or-build

Your business planner. Compiles everything the other Shark Tank Proof skills wrote (the board's verdict, the competitors, the buyer panel, pricing, the offer, the CFO's numbers, marketing, brand, operations, the launch plan and the evidence ledger) into one business plan with a verdict at the top that is computed, never written by hand: Profitable (the numbers pass and a real buyer has paid, signed or booked), Unproven (works on paper, no real buyer yet), Not yet (with the failing numbers) or Incomplete. A simulated panel can fail a plan but never pass one. Adds an executive summary and a one-page version. Use when the user says "write my business plan", "put it all together", "is it profitable", "give me the plan", or at the end of the Shark Tank Proof pack.

shark-board

Your board of directors, built to disagree with you. Puts a business idea in front of a four-member board, each a sub-agent reading the idea through one published framework: the Offers lens (from Alex Hormozi's $100M Offers), the Monopoly lens (from Peter Thiel's Zero to One), the Product lens (from Walter Isaacson's biography of Steve Jobs) and the Evidence lens (from Rob Fitzpatrick's The Mom Test), which scores only what real people have done. Each member scores the idea, names what would kill it and the cheapest test that would prove it, and votes fund, fund with conditions, or pass. Use when the user says "test my business idea", "would this work", "pressure-test this", "what would a board say", "is this a good business", or starts the Shark Tank Proof pack on a new idea.

truth-serum

The consumer panel. Spins up a swarm of buyer sub-agents (default 100, --quick for 20) trained on the user's target customer, each with a different income, age, buying behaviour and objection, shows every one the same pitch, and runs the business through 100 buyer scenarios to see who buys, who doesn't, and why. Tallies the answers into buy rates by segment, the reasons people pass in their own words, what would flip a no, and price answers for litmus. Every result is labelled SIMULATED: it finds objections and the questions to ask real buyers, and never counts as demand. Use when the user says "would people buy this", "test it on customers", "run the consumer panel", "simulate buyers", "who is my customer", or "validate demand".

Related Skills