compute-break-even-units
Use when asked how many units or how much sales cover the cost base. Computes break-even from fixed cost and contribution margin, adds a target profit, and reports the margin of safety.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- compute-break-even-units
- description
- Use when asked how many units or how much sales cover the cost base. Computes break-even from fixed cost and contribution margin, adds a target profit, and reports the margin of safety.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档SOURCE.md350 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Compute break-even units
Break-even is the volume where contribution exactly pays the fixed base. It converts a cost structure into a sales target and exposes how much cushion the plan actually has.
Procedure
-
Total the fixed cost for the period: rent, salaried payroll, software, the fixed platform fee. Say $84,000 a month.
-
Get contribution margin per unit: price minus variable cost. $20.00 - $12.00 = $8.00.
-
Break-even units = fixed cost / contribution per unit.
``` python3 -c "from decimal import Decimal as D; print(D('84000')/D('8'))" # 10500.0 units ``` -
Break-even revenue = break-even units * price = 10,500 * 20 = $210,000, or equivalently fixed / contribution ratio = 84,000/0.40.
-
Add a target profit: units = (fixed + target) / contribution. For $30,000 of profit: (84,000+30,000)/8 = 14,250 units.
-
Compute the margin of safety = (expected units - break-even units) / expected units. At 14,000 expected against 10,500 break-even, safety is 25%.
-
Stress the two inputs together. A 10% price cut raises break-even by the same share as the margin lost and is the most common way a plan misses.
-
Round up, never down, when a plan needs a whole number of units to cover cost: 10,500 covers, 10,499 does not.
-
Keep variable cost per unit in integer minor units so the division has a stated rounding rule; a float contribution reassigns the rounding to the wrong side.
-
Re-state break-even whenever price or fixed cost changes. It is a living target, not an annual figure.
Pitfalls
- Dividing by gross margin instead of contribution margin.
- Forgetting that a price cut lowers the contribution the fixed base is divided by.
- Rounding break-even units down and leaving the plan a unit short of covering cost.
- Treating a step cost as fixed past the volume where it steps up.
- Using last period's variable cost after an input change.
- Float contribution that reassigns the rounding of the break-even unit.
Verification
```
python3 -c "from decimal import Decimal as D; print(D('84000')/D('8'))"
# 10500.0 -> 10,500 units cover $84,000 fixed at $8.00 contribution
```
Pass when fixed cost, contribution per unit and both break-even figures are shown. Report break-even units, break-even revenue, and the margin of safety at the planned volume.
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.