Usage-based SaaS revenue rises or falls with customer consumption, while infrastructure and support costs can move with that usage too. Evaluating unit economics therefore requires looking at both the revenue curve and the cost to serve each cohort.
Choose the unit of analysis
Possible units include customer, account, usage tier, transaction, or workload. Select the unit that links billing to delivery costs and is useful for the pricing or acquisition decision.
Define the period and normalize for contract terms, credits, minimum commitments, and overages. A billed amount may not equal recognized revenue or collected cash.
Map variable and fixed costs
Identify infrastructure, third-party fees, support, implementation, and other costs that change with usage. Separate variable cost from fixed platform and staffing costs.
Measure costs at the same grain as revenue where possible. If shared cloud or service costs must be allocated, document the rule and examine sensitivity.
Analyze cohorts and usage patterns
Compare customer cohorts by acquisition source, product configuration, and time since activation. Examine both average usage and the distribution; a small group of heavy users can dominate totals.
Track whether usage growth reflects customer value, a one-time workload, or a costly pattern that needs product or pricing attention.
Use the model to inform pricing and growth
Review contribution margin, retention, expansion, support burden, and customer outcomes together. A high-consumption account can be valuable or unprofitable depending on its price and service cost.
Our guide to contribution margin modeling covers how variable costs affect an offer’s economics.
Related reading: contribution margin.
Practical checklist
- State the economic question and cost or revenue basis.
- Keep assumptions and allocation rules visible and testable.
- Review the decision when customer mix, capacity, or timing changes.
How did this article land?
Choose one reaction. You can change it anytime.