How to read a revenue projection without fooling yourself

A scenario is not a prediction

A projection describes what would happen if assumptions hold. It does not claim they will. Multiple scenarios should therefore keep their assumptions visible.

Production capacity is physical and depends on time, budget and format. A scenario can change modeled audience or conversion, but should not magically multiply feasible output.

Separate monthly and accumulated figures

Revenue in a month belongs to one row. Accumulated revenue adds all previous rows. Poor labels can make users confuse month-twelve performance with the annual total.

Accumulated result is accumulated revenue minus accumulated cost. A negative figure indicates an investment phase inside the model, not automatic debt or a realized loss.

Gates prevent phantom revenue

Every stream needs a condition. Platform ads depend on official requirements. Affiliate links can begin earlier when relevant and disclosed. Sponsorship needs sufficient audience or manual approval. An own product needs recurring demand.

A gate decides when a stream enters the calculation. It does not replace platform, brand or network review.

Break-even belongs to the full catalog

Published pieces can keep contributing after their first month. Break-even should therefore not be expressed as isolated views required per video. The correct comparison adds revenue and cost across the entire catalog.

Break-even is highly sensitive to long-tail behavior, cadence and monthly cost. An honest projection shows when it does not appear in the modeled period.

Read the crossing point as a planning signal, not a guarantee. If real costs, cadence or audience behavior differ from the assumptions, update the model before making a spending decision.

Recommended next step