A publication can keep receiving views, searches, listens or clicks long after release. Ignoring that tail forces every piece to recover its full cost immediately.
This guide explains the decision rule before tools or figures. Examples describe methodology, not guaranteed results.
A piece does not end with its launch month
A publication can keep receiving views, searches, listens or clicks long after release. Ignoring that tail forces every piece to recover its full cost immediately.
An accumulated catalog treats each publishing month as a cohort. In later months, that cohort contributes a declining share of lifetime performance while new cohorts are added.
The curve must depend on platform
Platforms do not share the same lifespan. Search-led content often remains useful while feed posts can concentrate performance early. The curve should not be copied unchanged across formats.
Monthly shares should add up to the expected lifetime result of a piece. If they do not, the projection silently creates or destroys performance.
Separate learning from long tail
A new project can improve through practice. Learning affects future cohorts, while the long-tail curve describes how each cohort is distributed over time. Applying a scenario multiplier twice distorts both effects.
Each scenario should have an explicit performance assumption while keeping capacity and cost logic stable.
Calculate accumulated break-even
Every month adds revenue and cost. Break-even occurs when accumulated revenue reaches or exceeds accumulated cost. If this does not happen inside twelve months, the tool should say so rather than inventing a later month.
The useful question becomes not “how many views does each video need?” but “when does the full catalog begin to cover the system that produces it?”
Recommended next step
The planner turns this decision rule into capacity, cost, scenarios and an operating week using your constraints.
Build my plan