CostMonStart free

Cloud cost

Unit economics

Infrastructure cost expressed per customer, per request, or per transaction, not as one company-wide total.

Cloud cost

Last updated

Definition

A total monthly cloud bill tells you almost nothing about whether the business is getting more efficient. It only grows with usage. Divide the same spend by an active-customer count, a request count, or a completed-transaction count. You get a number you can compare over time. Does it cost more or less to serve the same unit of value as the product and its usage change?

This is where cloud and AI cost measurement meet. Per-request cost, the AI and LLM equivalent, applies the same idea to a metered API call instead of an infrastructure footprint.

You can also export a per-unit cost view as a report. Save it once, and it can produce a CSV or PDF export on demand. It can also go to a channel on a recurring schedule for whoever owns the metric.

Where it shows up

Unit economics is a computed metric, not a native billing field. Take a total spend figure from the billing export. Divide it by an active-customer count, a request count, or a completed-transaction count. You pull that count separately from the product's own usage data, over the same period.

What makes it expensive

Watching a total monthly bill alone, you may mistake growth in spend for a problem. It may only track growth in usage. A total cannot tell you whether serving one customer costs more this quarter than last quarter. Divide the bill before you worry.

A total nobody owns, nobody fixes.

An unattributed cost stays unowned. CostMon assigns spend to an owner, so someone can act on it.

Esc