Unit economics
Unit economics is measuring cloud cost per unit of business value, such as cost per order, per customer or per API call, by dividing what a product costs by how much it delivered. It shows whether spend is growing because the business is growing or because the product is becoming less efficient.
In plain English
Think of a car's fuel economy. Knowing you spent more on fuel this month says little; miles per gallon tells you whether you drove further or drove worse.
Formula and worked example
Unit cost = cost ÷ units delivered
- Cost
- = the cloud cost allocated to the product or team in the period
- Units delivered
- = how many of the chosen business unit it served in the period, such as orders, customers or API calls
| Checkout's allocated cost in March | $22,000 |
|---|---|
| Orders processed in March | 440,000 |
| Cost per order in March | $0.050 |
| Cost per order in February: $19,500 ÷ 350,000 orders | $0.056 |
| Change in cost per order | −10% |
Cost went up 13%, but orders went up 26%, so each order cost 10% less. The showback report raised a flag; unit economics shows the team grew efficiently. A rising cost per order would have been the real warning.
Why unit economics matters
A growing cloud bill is good news if the business is growing faster. Total cost can't tell you which it is; cost per unit can. That makes unit economics the bridge between engineering and the business: engineers can move it, and leadership understands it.
The FinOps Foundation separates two kinds of unit metric. Resource efficiency metrics, such as cost per GB stored or cost per token, are signals engineers control directly. Business metrics, such as cost per transaction or per customer, tell leadership what each unit of value costs.
Common mistakes
- Picking a unit nobody uses. Choose a unit the business already tracks, such as orders, active customers or API calls, so the number means something outside engineering.
- Leaving out shared costs. A cost per order that ignores the shared platform looks better than it is. Use allocated cost, including each team's share of shared costs.
- Changing the basis. If allocation rules or the cost basis change, unit cost changes with them. Keep the basis fixed, or restate the history when it changes.
- Reacting to a single month. Unit costs swing with seasonality and one-off projects. Watch the trend over several months before acting.
How CloudYali helps
CloudYali's Unit Economics cost views track ratios over time, such as Cursor cost per accepted line of AI-written code or per agent request, and its allocation and Showback views give each team's cost, the cost side of your own unit metrics.
Related terms
Allocation & accountability
Cost allocation
Cost allocation is assigning every part of the cloud bill to the team, product or customer responsible for it, using accounts, tags and agreed rules for shared costs. It turns one invoice into numbers each owner can act on, and it is the basis for showback, chargeback and unit economics.
Allocation & accountability
Showback
Showback is reporting each team's allocated cloud cost back to that team, for visibility and accountability, without moving money between budgets. It shows owners what their choices cost so they can act on it, and unlike chargeback it is not entered into the company's accounts.
FinOps foundations
FinOps
FinOps is an operational framework and cultural practice that maximizes the business value of technology, enables timely data-driven decisions, and creates financial accountability through collaboration between engineering, finance and business teams. In practice, the people who spend on the cloud see what it costs, own it, and decide with that cost in mind.
AI, data & SaaS costs
Cost per token
Cost per token is what a language model charges for each token it reads or writes, usually quoted per million tokens, with input, cached input and output tokens priced separately. Output tokens typically cost several times more than input, so the mix of token types, not just the volume, decides the bill.
Optimization
Cloud waste
Cloud waste is cloud spend that buys nothing the business needs: idle resources, over-provisioned resources and commitments paid for but not used. It's measured in money rather than resources, and removing it lowers the bill without changing what users get, which is why cost optimization usually starts there.
Governance & planning
Budget
A budget is a planned spending limit for a period, such as a team's monthly cloud cost, with alerts when actual or forecasted spend crosses thresholds you set, such as 80% and 100%. On AWS, Azure and Google Cloud a budget warns rather than stops spending, unless you attach actions or automation to it.
Frequently asked questions
What is a good unit metric?
One the business already counts and that moves with cloud use: orders for a shop, active customers for SaaS, API calls for a platform. Start with one, and add more as teams ask for them.
Should unit cost always go down?
Usually, but not always. A new feature can rightly raise cost per order if it raises revenue per order more. Compare unit cost with unit revenue where you can.
How is unit cost different from cost per token?
Cost per token is a resource efficiency metric: what a model charges for its work. Business unit metrics, such as cost per customer conversation, also depend on how many tokens each piece of work uses.
