Break-even point

What it means

Break-even is the level at which revenue equals total cost and the company is neither in profit nor in loss. It is calculated by splitting costs into fixed (rent, wages, accounting, software) and variable, which grow with every unit sold.

The formula is plain: fixed costs divided by the contribution per unit - price minus variable cost per unit. The answer is the number of units or the revenue needed to cover running the business.

The distance between planned revenue and break-even is called the margin of safety. It says how far revenue can fall before the company slips into loss. A firm with high fixed costs has a high break-even and a thin margin of safety, so a drop in orders hits it faster than a firm whose costs fall together with revenue.

How it works in practice

Break-even is the most practical figure in budgeting and in pricing: it shows whether a new hire, a lease or an ad budget can pay for itself at all, and at what volume. It pairs well with unit economics, which looks at a single unit rather than the whole firm.

In a service business the same logic is counted in hours: how many billable hours a month cover the fixed costs. That is usually a soberer view than a sales plan.

When a sole trader is thinking of moving to an s. r. o., we work out break-even again. Double-entry bookkeeping is added, along with the director’s pay and contributions or dividend payouts and other administrative costs the trade licence did not carry. Only with those in does it show at what turnover the change of form starts to pay.

What to watch out for

Reaching break-even does not put money in the account. Profit and cash drift apart through payment terms, stock and loan principal. A company can sit above break-even and still be short for payday.

The second mistake is splitting costs wrongly. Many that look like variable costs are fixed at least in the short run: production wages do not drop the moment orders fall, and the warehouse rent keeps running. A break-even worked out on the opposite assumption comes out lower than it really is.