Skip to main content

Monetization and Unit Economics

Unit economics connect a business quantity to a declared unit. They become misleading when revenue recognition, refunds, shared-cost allocation, currency, or time horizon is implicit. A positive contribution estimate is not profit, customer lifetime value, cash flow, or permission to ignore non-financial harm.

Prerequisites​

Complete feature adoption over the product lifecycle. Retain the eligible population and maturity limits before attaching money.

Learning goals​

  • State currency, nominal/real basis, horizon, and recognized quantities.
  • Separate an accounting identity from assumptions and forecasts.
  • Show allocated, excluded, and missing costs.
  • Keep service, privacy, accessibility, and distributional guardrails beside financial metrics.

Decision contract​

The fixture asks whether the current day's report-export population warrants further evaluation. It declares EUR, one UTC calendar day, EUR 30 recognized revenue, EUR 4 refunds, and EUR 9 of allocated payment, support, and platform costs. The resulting EUR 17 contribution is an arithmetic identity under those assumptions. It is not a causal estimate of the feature's incremental value.

The allocation basis is equal daily allocation to the review population. Customer acquisition, general labor, and capital/tax effects are missing. Those omissions make the number incomplete even though the subtraction is reproducible. A scenario table should vary allocations and missing costs before a material decision.

Worked example​

import json
from pathlib import Path

contract = json.loads(Path("tests/fixtures/product-analytics/product-review-contract-v1.json").read_text())
economics = contract["unit_economics"]
allocated = sum(economics["allocated_costs_eur"].values())
contribution = economics["recognized_revenue_eur"] - economics["refunds_eur"] - allocated
per_payer = contribution / economics["paying_accounts"]
print(f"currency={economics['currency']} horizon=2026-10-02 revenue={economics['recognized_revenue_eur']:.2f} refunds={economics['refunds_eur']:.2f}")
print(f"allocated_cost={allocated:.2f} contribution={contribution:.2f} per_payer={per_payer:.2f} missing_costs={len(economics['missing_costs'])}")

Expected output:

currency=EUR horizon=2026-10-02 revenue=30.00 refunds=4.00
allocated_cost=9.00 contribution=17.00 per_payer=5.67 missing_costs=3

Limitations and common mistakes​

  • Mixing daily revenue with monthly cost, currencies, or tax bases invalidates the identity.
  • Average contribution hides distribution and marginal cost.
  • Allocated shared cost depends on a policy; a different defensible basis can change the unit result.
  • Customer lifetime value requires retention and future-value assumptions that this fixture does not supply.
  • Monetizable value does not replace unmonetizable benefits, harms, risk, or distributional analysis.

Practice​

Recalculate contribution under two platform-cost allocations and a plausible missing-labor range. State which conclusions survive. Add a non-financial guardrail that could veto expansion even when contribution stays positive.

Next steps​

Decomposing metric movements separates arithmetic contributors to change from explanations of why they changed.

Primary sources​

Checked 2026-10-19: FinOps Foundation, Introduction to Cloud Unit Economics; HM Treasury, The Green Book 2026; IFRS Foundation, IFRS 15 revenue recognition.