agentleFS
fzfcleefzfclee/consulting-skills/skills/break-even-analysis/SKILL.md

break-even-analysis

Skill6 starsChanged 4 months agoApache-2.0View on GitHub

Use when a commercial, operational, or investment decision needs a threshold for viability. Use when applying the Break Even Analysis consulting method and when a user asks for Break Even Analysis, method execution, structured diagnosis, or action planning.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to run Break Even Analysis as a practical consulting method, not as a generic framework explanation.

    line 9
  2. Very specific:

    If an input is missing, do not block automatically.

    line 28
  3. Distinctive:

    Do not use when fixed costs, variable costs, unit revenue, and the relevant time horizon cannot be estimated.

    line 32
  4. Distinctive:

    Keep wording professional and plain enough that a smart non-specialist can use the output directly.

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Break Even Analysis

Use this skill to run Break Even Analysis as a practical consulting method, not as a generic framework explanation.

Method Notes

  • Separate fixed cost, variable cost, unit economics, and time horizon.
  • State the exact threshold that makes the option viable.
  • For a single-product constant unit-price/unit-cost model in one period, q >= 0, fixed cost F >= 0, price p and variable cost v give profit(q) = (p - v)q - F. Use consistent units, currency and period. If F > 0 and p - v > 0, break-even q = F / (p - v); for indivisible units, round up for a non-loss volume. If F > 0 and p - v <= 0, no feasible nonnegative quantity breaks even; a negative quantity is not a target.
  • If F = 0, q = 0 breaks even in this model; positive quantities break even only when p = v, gain when p > v, and lose when p < v. Revenue, time-to-payback, savings or nonconstant/multi-product models need their own stated formula, assumptions and domain; do not mechanically reuse the unit-volume formula.

Required Inputs

Collect or infer these inputs before execution:

  • fixed costs
  • variable costs
  • price or benefit per unit
  • time horizon
  • constraints

If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use when fixed costs, variable costs, unit revenue, and the relevant time horizon cannot be estimated. Break-even analysis tests an economic threshold; it does not establish overall strategic fit.

Adjacent Methods

  • cost-benefit-analysis: compare broader benefits, costs, timing, and risk.
  • pricing-strategy-check: test price metric, willingness to pay, margin, and discount risk.

Step-by-Step Execution

StepRequired inputHow to executeOutput
Define break-even unitDecision, economics, unit of value.Choose unit, revenue, margin, savings, or time as the threshold.Break-even definition.
Separate cost typesFixed cost, variable cost, recurring cost, one-off cost.Classify costs so the formula is clear.Cost structure.
Estimate unit economicsPrice, margin, savings, utilization, adoption.Calculate contribution or benefit per unit.Unit economics.
Calculate thresholdCost structure and unit economics.Compute break-even quantity, revenue, savings, or months.Break-even threshold.
Test realismMarket size, capacity, adoption, timeline.Assess whether reaching the threshold is plausible.Viability interpretation.

Output Template

### 1. Decision And Unit
Decision:
Unit of analysis:
Time horizon:
Currency / tax treatment:

### 2. Economics
| Input | Value | Source | Confidence |
|---|---|---|---|
|  |  |  |  |

### 3. Break-Even Result
Contribution margin per unit:
Break-even volume / time:
Formula:
Capacity check:

### 4. Sensitivity And Decision
| Variable change | New threshold | Decision implication | Validation action |
|---|---|---|---|
|  |  |  |  |

### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:

Quality Gate

  • Produce the method-specific outputs for Decision And Unit, Economics, Break-Even Result; do not substitute a generic framework summary.
  • Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
  • Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
  • Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
  • State missing inputs and the smallest validation action instead of inventing precision.
  • State the model domain and denominator condition beside the formula/result; report no feasible break-even when appropriate rather than an invalid negative-volume target.
  • Keep wording professional and plain enough that a smart non-specialist can use the output directly.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.