Put the historical account in its period
In a September 2024 personal article, Levels discussed Photo AI, Interior AI, compute spending and short-term revenue changes after podcast exposure. This is a dated personal operating account, not our independent audit of current finances.
Editorial analysis: products share more than code
Shared founders, infrastructure and channels mean isolated product revenue can hide common upkeep. Sudden traffic can add queues, retries and refund questions. New-user counts alone do not establish growth quality; sustained delivery after exposure is the continuing-business question.
Record completed useful tasks, inference resources, support time and recovery costs by product, with shared expenses separately. Mark short events as separate periods instead of mechanically extending a day's results into stable months or years. This is our proposed method, not Levels' disclosed accounting system.
A single case is not an income projection
We do not use his historical figures to estimate others' earnings or infer no external suppliers from a solo narrative. Further reading: compute resources and actual net costs.