What the stack actually costs to run, for any date range — AI usage, subscriptions, telephony and infrastructure, vendor by vendor. Costs that arrive in different places and on different days are gathered into one figure.
A flat subscription and a per-token API bill behave nothing alike, and are usually tracked in different places or not at all. Both land in the same total here.
Where an API exposes spend or balance, the number is pulled rather than typed in from an invoice that arrives three weeks later.
A vendor with no amount set is called out as unknown instead of silently counting as nothing — which is how stack costs get understated for months.
Each row carries its reasoning: the monthly rate, the days in range, whether billing export is on, whether a key is missing. A surprising figure comes with the reason attached.
AI, infrastructure and telephony total separately, so a rising bill is traced to the kind of spend that caused it rather than investigated from scratch.
Costs are pro-rated across the window being asked about, so a week can be costed as honestly as a month.
Revenue minus media spend is not profit. The operating cost of the tooling is the missing term, and it is rarely written down anywhere.