Unit Economics for Cloud: How to Measure Cost Per Customer

Raw cloud spend is a vanity metric. A company spending $500K/month on cloud and growing 200% YoY is doing better than one spending $100K/month with flat revenue. Unit economics — cost per customer, per transaction, per active user — connect cloud spend to business outcomes.

Why Unit Economics Change Everything

When engineering teams own a "cost per active user" KPI, optimization decisions become obvious. Caching a database query isn't just good engineering — it's measurably reducing cost per user by $0.003. That's motivating in a way that "reduce cloud spend" isn't.

Unit economics also enable better growth decisions. If acquiring a new customer costs $120 in CAC and your cloud cost per customer is $8/month, scaling 10x costs are predictable. Without unit economics, every growth decision is a financial unknown.

Key Cloud Unit Economic Metrics

Cost Per Active User (CPAU)	Cloud spend / Monthly Active Users
Cost Per Transaction	Cloud spend / Transactions processed
Infrastructure Cost Ratio (ICR)	Cloud spend / Revenue (%)
Cost Per GB Stored	Storage cost / GB of customer data
Cost Per API Call	Cloud spend / API requests handled
Compute Cost Per Order	EC2/container cost / Orders fulfilled

Calculating Cost Per Customer

Formula: Total cloud spend / Monthly Active Customers

The challenge: allocating shared costs. Start with direct costs (services that serve customers directly: web servers, databases, CDN). Allocate shared infrastructure proportionally. Exclude internal tooling and dev/test environments from customer-serving cost.

# Simple cost-per-customer calculation
total_cloud_spend         = 180000  # $180K/month
internal_tooling          = 22000   # dev, CI/CD, monitoring
customer_serving_spend    = 158000
monthly_active_customers  = 45000

cost_per_customer = 158000 / 45000  # = $3.51/customer/month

Infrastructure Cost Ratio (ICR)

ICR = Cloud Spend / Revenue. Industry benchmarks vary widely:

SaaS companies (mature): 5–15% ICR
SaaS companies (high-growth): 15–30% ICR (efficiency traded for scale)
Marketplaces: 1–5% ICR (GMV is large vs. cloud costs)
ML/AI-heavy products: 20–40% ICR (GPU inference costs are high)

A rising ICR as you scale is a warning sign — it means your cloud costs are growing faster than revenue. A falling ICR is the goal: each additional dollar of revenue requires less marginal cloud spend.

// FAQ

How often should we calculate cloud unit economics?

Monthly, minimum. Weekly for high-growth companies or during major product launches. The goal is to catch cost-per-unit regressions before they compound — a new feature that doubles cost per transaction needs to be identified in days, not quarters.