If you projected a business growing 12% per year, does it make sense for the break-even analysis to show a single fixed number, calculated with year-1 data? That methodological contradiction is exactly what we fixed. From today, the break-even point is calculated and plotted year by year across the entire project horizon, against the actual projected volume of each period.
The change in one line
The Break-Even block in the dashboard adds a second visualization: the Break-Even Evolution chart, which compares your projected volume year by year against that year's BE. The classic chart (revenue vs. total costs) is still there because it teaches the logic; the new one answers a different question: when am I going to be comfortably above break-even?
If you want to try it on your own project, you can load the data into the dashboard and open the break-even section: the new visualization appears below the traditional chart.
How it was calculated before
Until yesterday, the dashboard showed a single Break-Even card with three figures: how many units you needed to sell per year to avoid losses, what that meant in dollars, and a margin of safety calculated solely against year-1 volume. The classic break-even chart (revenue vs. total costs) used those same parameters.
The formula is properly applied. The problem wasn't the math, it was the time slice: if your project grew 10% per year over five years, that growth fed NPV, IRR, and Payback, but didn't show up anywhere in the break-even analysis. The result: two views of the same project that told incompatible stories.
The implicit assumption that broke the logic
Showing a static BE for a 5-year horizon assumes, without saying so, that year-1 volume is representative of every year. That's false by the model's own construction: the analysis projects year-t volume as Q × (1 + g)t−1, where g is the growth rate the user entered.
Why we decided to change it
Three concrete reasons, in order of importance:
- The real margin of safety changes over time. A project can start with an MS of 10% (tight zone) and end at 50% (robust zone) in year 5. Summarizing that trajectory in a single year-1 number hides exactly what's most useful for deciding: how much financial cushion you need in the early years, until growth lifts you off BE.
- The entrepreneur going to the bank doesn't ask "how much do I need to sell to avoid losing". They ask "when am I going to be comfortably above". The previous chart didn't answer that question — the new one does, showing two lines (projected volume vs. BE) year by year.
- Internal consistency of the analysis. If NPV, IRR, and Payback use growing flows, the break-even analysis can't freeze time. Technical users (accountants, project evaluators) catch that inconsistency fast and lose trust in the rest of the analysis.
The conclusion that changed: a project where year-1 volume is just above BE can be perfectly solid if it grows 15% annually, or very fragile if it depends on staying flat. Before, that nuance wasn't visible. Try the new visualization on your own project — the numbers change meaning when seen this way.
How it works now
The break-even block in the dashboard keeps the traditional chart (because it's still educational: it shows how revenue and cost curves form) and adds a new visualization: Break-Even Evolution, with two time series:
- Green line: projected volume year by year (Q × (1 + g)t−1).
- Dashed red line: the break-even point in each year.
While the green line stays above the red one, that year the project covers all its costs. The faster they separate, the more cushion. Hovering over each year shows the annual margin of safety and an "above / below" BE indicator for instant reading.
The formal formula
MS(t) = (Q(t) − BE(t)) / Q(t), where Q(t) = Q₀ · (1 + g)ᵗ⁻¹
Donde
- MS(t)
- Margin of safety in year t[%]
- Q(t)
- Projected volume in year t[units]
- BE(t)
- Break-even point in year t[units]
- Q₀
- Year-1 volume entered by the user
- g
- Annual sales growth rate[%]
Desarrollo
- 1.BE(t) = FC(t) / (P(t) − UVC(t))
- 2.Q(t) = Q₀ × (1 + g)^(t−1)
- 3.MS(t) = max(0, (Q(t) − BE(t)) / Q(t))
Criterio de decisión
- MS(t) ≥ 40%
- Robust year: the project absorbs large drops in demand.
- 20% ≤ MS(t) < 40%
- Acceptable year: the cushion is reasonable for most sectors.
- MS(t) < 20%
- Tight year: small price or cost shifts push you into losses.
In this first iteration, price, unit variable cost, and fixed costs are constant in nominal terms. The important change is that volume is no longer assumed static. Cost escalation by inflation is on the immediate roadmap.
A concrete example: a neighborhood bakery
To keep the difference between the old and new readings out of the abstract, let's model a bakery with realistic numbers:
- Price per unit (average ticket): $15
- Variable cost per unit: $6 (ingredients + delivery)
- Monthly fixed costs: $4,500 (rent, salaries, utilities)
- Year-1 volume: 7,200 annual units (≈ 600/month)
- Expected growth: 12% per year
- Horizon: 5 years
The classic formula gives a constant BE of $54,000 annual / ($15 − $6) = 6,000 units per year.
Old reading (static)
"Your BE is 6,000 units, you sell 7,200, margin of safety ≈ 16.7%". Apparent conclusion: tight zone, fragile project. Many entrepreneurs with good projects discard numbers like these thinking they're on the verge of losses.
New reading (dynamic)
| Year | Projected volume | BE | Margin of safety | Reading |
|---|---|---|---|---|
| 1 | 7,200 | 6,000 | 16.7% | Tight |
| 2 | 8,064 | 6,000 | 25.6% | Acceptable |
| 3 | 9,032 | 6,000 | 33.6% | Comfortable |
| 4 | 10,115 | 6,000 | 40.7% | Solid |
| 5 | 11,329 | 6,000 | 47.0% | Robust |
The conclusion flips: the project starts fragile but gains solidity quickly. The decision isn't "discard it" but "secure extra working capital to cover the first 18–24 months, where MS is tight". Operational, actionable information — different from a flat verdict.
Another example where the reading gets worse
To avoid making it seem the change always flatters projects: now imagine a corner store with flat volume (no growth) and the same costs. MS stays fixed at 16.7% for all five years — no favorable trajectory, no cushion gain. That visualization clearly shows the model depends on holding sales perfectly, with no margin for error. The new chart makes that fragility impossible to ignore.
What's next
This change sets the stage for two improvements already queued: cost escalation by inflation (so BE moves year by year as nominal fixed costs rise, distinct from when price and variable cost grow at the same time) and break-even by scenario, where the MS trajectory is compared under pessimistic, base, and optimistic scenarios in the same chart. When they're ready, you'll see them here on the changelog with the same format: what we did before, why it changed, and a numerical example showing the difference.
Did you find a case where this new analysis led you to a different decision? Write to psservices.client@gmail.com and, if it makes sense, we'll add it as an example in this same article. In the meantime, apply what you read now → and watch how your project's margin of safety evolves year by year.
¿Te fue útil? Compartilo