Unit Economics
Develop and track metrics that provide an understanding of how an organization’s technology use and technology management practices impact the value of the organization’s products, services, or activities.
Define Unit Metrics which support Organizational Goals
- Define and document goals the organization is trying to achieve through the investment in technology and its application
- Define and document metrics which will drive the decisions, behaviors or outcomes needed
- Define and document measurements that are appropriate to evaluate technology use and cost
- Define unit metrics and KPIs which satisfy the needs of those organizational goals
- Distinguish resource efficiency unit metrics from business unit metrics, and clarify how they relate
Ensure Unit Economic data is available
- Provide feedback to Data Ingestion to gather appropriate information to calculate unit metrics and KPIs
- Assess business data quality and validate terminology alignment early, leveraging FOCUS
- Define a strategy for providing KPI data to all appropriate stakeholders in the channels they use for decision making
- Document data sources, correlations, and unit metric calculations for all personas
Validate Impact of Unit Metrics
- Review impact of unit metrics on actual performance and other goals
- Establish a cadence for metric review, adoption, modification, and refresh
Definition
Unit Economics brings together what an organization spends on technology and the value that technology spending creates. Without a way to relate costs to benefits received, it is difficult to understand whether spending is appropriate.
Unit economics provide cues to meet organizational goals through technology usage. They help communication between personas by tying technology costs more directly to business outcomes.
Unit economic metrics can be defined for many aspects of technology usage. They may track technology cost by revenue, per million authorized users, per transaction, per customer, or per case resolved, depending on the goals of the organization or the product. They can also be defined for technical aspects such as cost per service request, cost per workload, cost per seat used, cost per VM, cost per GB stored, or cost per token.
These unit economics can help engineering teams identify design and operational improvements, and help product owners understand direct and indirect costs driven by customer or employee usage, enabling workload placement, packaging, pricing, and roadmap tradeoffs. They can also reinforce progress toward margin or financial goals, including industry specific unit views such as cost of service delivery as a percent of revenue, or IT spend framed against the business units that generate premium or margin outcomes.
By pairing technology spend with value measurements, changes in spending can be interpreted as economies of scale, productivity gains, or runaway cost drivers within a unit metric. In practice, many organizations find the most actionable view is a trend over time within a defined FinOps Scope, rather than forcing broad comparability across unrelated business objectives, products or services.
Unit economics is often discussed in terms of marginal cost (unit cost metrics) and, where feasible, marginal revenue (unit revenue metrics). Comparing marginal cost and marginal revenue can help highlight break-even points and profitability dynamics. Where revenue attribution is difficult, outcome value proxies are often used, for example demand, throughput, customer experience, risk reduction, or service levels. When compared with the revenue or value generated by each unit, these metrics can support broader economic discussions such as contribution margin, product sustainability, or pricing tradeoffs.
When FinOps practitioners first address measuring unit costs, it is often in the context of Cloud Unit Economics. The unit economics of public cloud and other consumption-based IT services can be more useful for decision making because the variable use and cost model of public cloud allows for rapid increases or decreases in usage, and multiple rate optimization options. So understanding the impact of these near-real-time changes can be more impactful to business value. For further details on defining, implementing, and building upon unit economics with FinOps teams, the unit economics working group has published a paper on Introduction to Cloud Unit Economics.
Unit costs can guide strategic decisions and generate benefits beyond efficiency by exposing underutilized services, prompting consolidation or architecture changes, and highlighting cases where costs are outpacing delivered value. Unit costs can also show why rising costs are not always negative if proportionally more business value is being delivered.
Unit metrics can generally be sorted into two broad categories:
- Resource Efficiency Unit Metrics (for example cost per GB stored, cost per GB transferred, cost per virtual CPU, cost per seat used, cost per token)
- Business Unit Metrics (for example cost per tenant, cost per transaction, cost to serve, cost per case resolved)
Engineers can more easily implement resource efficiency unit metrics as controllable signals within their domain and a way to demonstrate value and best practices. Implementing business unit metrics provides broader organizational context, enabling Leadership and Product owners to make explicit tradeoffs across cost, speed, quality, and risk, and is often an indicator of higher maturity.
For organizations adopting Generative AI, early unit economics often starts with cost per token and expands toward outcome oriented measures, for example cost per assist, cost per agent action, or cost per case deflected, so decision makers understand what the token was used for and what value it generated. Baselines can help demonstrate efficiency gains as adoption grows, and point of consumption awareness can reduce surprise spend by making unit costs visible where usage happens.
Ultimately, unit costs are more than KPIs, as they can guide a cultural shift. They foster shared responsibility for technology spending and consumption by aligning technology costs with business value. Engineers become cost conscious architects, product teams build value driven features, and leadership steers technology investments toward outcomes aligned to business strategy and objectives.
Shifting Left in Unit Economics means getting per-unit cost thinking in front of people early enough to shape a decision (rather than reporting it after the bill lands). At Crawl, you shift left the resource-efficiency metrics you already control, and you incorporate the business-value metrics later, as trust and data catch up. Mature, shift-left FinOps is a Run-level behavior for this capability.
In other words, “shift-left at Crawl” is the data seed planted, not the finished practice. At Crawl, Unit Economics are modest by design: they’re mostly technical, resource-efficiency metrics (cost per GB, per vCPU, per token), centered on direct variable cost in (usually) one technology category (e.g. public cloud), with low organizational adoption and business-outcome data not yet correlated at any granular level. Run Maturity is where unit economics get considered early enough to shape build-vs-buy decision, architecture, workload placement, migration, sourcing, and pricing. Everything in-between helps mature the practice as shift-left activities build trust within organizational constraints.
Maturity Assessment
Crawl
Given low adoption, most of the Crawl value is cultural: getting engineers to treat design choices as per-unit cost choices before the tooling or business data exists to measure them precisely.
- Unit economics at the total cost / organizational results level in basic ways
- Primarily working on technical unit cost metrics which are more concrete and centered on variable cost and use technology categories like public cloud
- Business outcome data, which may be harder to gather or correlate is not used at a granular level of detail
- Low organizational adoption or understanding of unit economics to drive decision making
- Unit economics focus on direct variable costs rather than TCO, ROI or shared costs more broadly
- Resource-efficiency metrics showing up in design reviews, not only in reporting. A rough “what does this cost per GB, per 1,000 requests, per token” question during an architecture discussion.
- Order-of-magnitude estimation during planning. Not a forecast, just a back-of-envelope unit cost for a proposed design, kept in the variable-cost, single-category lane.
- Instrumentation planted while teams build. Tag resources and emit a usage counter (the denominator) during development so the data exists later, even though you are not calculating sophisticated metrics yet. This tends to be the cheapest, highest-leverage move at Crawl.
- Point-of-consumption visibility. Surface a rough unit cost where the usage decision happens, for example cost per token in the dev environment or a cost-per-request note in the design doc.
Walk
- Leadership, Product or Engineering teams develop unit economics with support of FinOps Practitioners, specific to their scope of work
- Unit economics used in other important technology categories to create visibility of cost across public cloud, SaaS use, data centers, etc. for important Scopes of spend
- Value and outcome data is used more often, leaders start referencing stable business unit metrics in decision making routines
- Moderate trust and decision use, typically in priority areas rather than across the technology investment and operational landscape
- Unit economics begin to account for fully loaded costs, or costs outside of direct technology use
- Business unit metrics (like cost per customer, cost to serve, or contribution margin) become more trustworthy
- Fully-loaded and TCO views (whereas Crawl stays with direct variable cost); and formal governance or ownership of definitions
Run
- All operational FinOps Scopes include defined unit metrics for related segments of technology spending and usage, aligned to business context for visibility and decision making at multiple levels of the organization
- Unit economics applied equally across all managed technology categories, consistently across different FinOps Scopes
- Unit metrics incorporate fully loaded costs across all applicable technology categories
- Unit metrics available at multiple levels of organizational and technical granularity
- High trust and consistent use in investment and optimization decisions, with clear ownership and governance of definitions
- Unit economics are defined and considered early, shaping build vs buy, architecture, workload placement, migration, sourcing, and pricing decisions
Functional Activities
FinOps Practitioner
As someone in the FinOps team role, I will…
- Connect technology-related spend, usage and adoption to the organization’s business strategy and priorities through Executive Strategy Alignment
- Communicate the importance of using Unit Economics to tie technology cost to organizational value consistently
- Build collaboration between other personas to understand the key metrics involved in the organization, for applicable FinOps Scopes
- Define and document meaningful metrics in partnership with Leadership, Engineering and Product Personas that relate technology cost and usage to business value
- Document metric definitions, assumptions, and cost inclusions for consistent interpretation
- Provide visibility to unit metrics and KPIs in appropriate channels for each FinOps Persona, including point of consumption visibility where usage decisions occur
- Align FinOps Personas on outcomes, demand drivers, and relevant unit metrics
- Support governance cadence for metric review, changes, and retirement
- Separate avoidance, savings, and cost reduction measurements
Product
As someone in a Product role, I will…
- Define outcome goals, demand assumptions, and sustainable cost to serve targets
- Provide input to FinOps Practitioners regarding key organizational metrics and goals related to my area of responsibility
- Co-define meaningful metrics that demonstrate business value from my products
- Clarify business data sources, data points and unit definitions to reduce debate
- Track defined metrics to demonstrate the value the products are bringing to the business
- Work with FinOps teams to expand AI metrics beyond tokens toward outcome related measures
- Capture baseline, intervention, and outcome evidence
- Estimate lifecycle cost and expected business value
- Prioritize demand within affordability and value constraints
Finance
As someone in a Finance role, I will…
- Provide input to FinOps Practitioners regarding key organizational metrics and goals related to my area of responsibility
- Align unit metrics with organization wide budgeting, forecasting, reporting, and financial guardrails
- Define allocation rules and cost structures supporting fully loaded business unit metrics
- Incorporate unit metrics into variance narratives, explaining drivers, not just spend
- Validate metric assumptions, reconciliation, and consistency across sources
- Track and embed these into financial reporting to demonstrate our improved/worsened financial position in terms of technology investment/efficiency
- Feed lessons into standards and future estimates
- Compare pricing, commitment, marketplace, and BYOL options
- Validate demand, entitlements, and contract flexibility
- Define renewal, exit and consumption accountability
Procurement
As someone in a Procurement role, I will…
- Provide input to FinOps Practitioners regarding key organizational metrics and goals related to my area of responsibility
- Incorporate the use of unit metrics into procurement planning and decision making
- Use unit metrics to inform vendor selection, renewals, and commercial model choices
- Consider terms affecting unit economics, including commitments, entitlements, and consumption exposure
Engineering
As someone in an Engineering role, I will…
- Provide input to FinOps Practitioners regarding key organizational metrics and goals related to my area of responsibility
- Support the ideation of unit economic metrics that support engineering making meaningful contributions to the organization.
- Use Unit Economics metrics to drive better organizational efficiencies through architectural, performance, reliability and workload placement decisions
- Define controllable drivers behind resource efficiency metrics, explain impacts on business metrics
- Partner on data instrumentation to improve unit definitions and outcome correlation
- Estimate cost impacts from code and configuration changes
- Retire resources when value or ownership ends
- Select approved services, patterns and placement options
Leadership
As someone in a Leadership role, I will…
- Make clear to all Personas what unit economic metrics are meaningful to the organization’s success, aligned to strategic outcomes
- Sponsor ownership, governance, and change control for metric definitions and cost inclusions
- Provide specific guidance on timing, format, and scope of required unit economic metrics, including distinguishing between leadership business unit metrics from engineering control metrics
- Use these delivered metrics to make better informed, data driven decisions aligning technology spend to business value
Measures of Success & KPIs
Measuring success in this capability often focuses on whether unit economics is improving decisions and outcomes, not only whether dashboards exist.
Organizational success can be measured in terms of the percentage of teams, personas, or stakeholders that are using unit economics metrics in decision making to communicate about technology use, and the percentage of priority areas where business unit metrics are stable enough to reduce repeated debate over definitions.
The use of both resource efficiency unit metrics and business unit metrics can be in place for FinOps Scopes which materially impact business results or drive large amounts of value. In some organizations, continuous improvement is reflected in unit cost trends over time within a product, cohort, or defined scope, and may be reviewed in a consistent cadence, for example as part of operating reviews or annual efficiency routines.
Automation, or the ability to automatically calculate unit economics metrics using repositories which are well documented, accessible, and correlated, tends to be most apparent in metrics critical to broader business decision making. Where unit economics expands across vendors and technology categories, normalization of cost and usage datasets can improve consistency and trust.
Regular review and periodic analysis of impacts can allow adjustment of metrics where needed, addition of new metrics to drive additional good behavior, or retirement of metrics which no longer serve the needs of the organization, including situations where comparisons across dissimilar products are creating more confusion than insight.
KPIs
Cost per API Call
Measures the average cost for each API call made to AI services. This KPI helps track the efficiency of managed AI services like AWS SageMaker or Google Vertex AI.
Cost per API Call
Measures the average cost for each API call made to AI services. This KPI helps track the efficiency of managed AI services like AWS SageMaker or Google Vertex AI.
Formula
Cost Per API Call = Total API Costs / Number of API Calls
Candidate Data Sources:
- API usage reports
- Dashboards from AI platforms
- Logs from AI platforms
- Cloud billing data
Example:
- If the total API costs are $1,200 and the number of API calls made is 240,000, the cost per API call is: $1,200/240,000 = $0.005 per API call
Related Capabilities
Reporting & Analytics
Data Value Density
Measures the strategic ROI of data cloud platform assets by comparing the business value generated to the total cost of ownership (TCO) of the data product. This KPI shifts the focus from cost-cutting to value-maximization. A higher ratio indicates a high-margin data product that generates significant business utility, while a ratio approaching or falling below
Data Value Density
Measures the strategic ROI of data cloud platform assets by comparing the business value generated to the total cost of ownership (TCO) of the data product. This KPI shifts the focus from cost-cutting to value-maximization. A higher ratio indicates a high-margin data product that generates significant business utility, while a ratio approaching or falling below 1.0 signals a "value leak" where the cost of maintaining the data exceeds its benefit.
Formula
Data Value Density = Total Business Revenue or Value Index / Total Data Platform TCO
Candidate Data Source(s):
- End-to-end Data Cloud Platform cost reports
- Product analytics or user engagement telemetry
- Finance or capital allocation systems
Rate Optimization
Usage Optimization
Licensing & SaaSValue for AI Initiatives
Measures the financial or value return generated by AI initiatives relative to their cost. This KPI helps to justify the investment in AI services and aligns them with business outcomes.
Value for AI Initiatives
Measures the financial or value return generated by AI initiatives relative to their cost. This KPI helps to justify the investment in AI services and aligns them with business outcomes.
Formula
Return On Investment = (Financial Benefits – Costs) / Costs * 100
Candidate Data Sources:
- API usage reports
- Dashboards from AI platforms
- Logs from AI platforms
- Cloud billing data
Example:
- If the financial benefits from an AI project are $50,000 and the total costs incurred are $20,000, the ROI is: (50,000−20,000)/20,000 * 100 = 150%
KPIs & BenchmarkingCost per Gigabytes Stored
Measures average cost per GB stored, impacted through storage tiers and by maximizing data life-cycle management.
Cost per Gigabytes Stored
Measures the average cost per GB stored, impacted through storage tiers and by maximizing data life-cycle management. This average cost can be categorized by specific or combination of the following FOCUS fields to gain more insights and map them to business units : Region ID, Account ID, Service Category ID, SKU ID.
Formula
Cloud Storage Costs / Number of GB stored
Data Sources:
- CSP Billing Data and Cloud Console
Related Capabilities
Time to Achieve Business Value
Measures the time it takes to achieve measurable business value from AI initiatives. This KPI uses a “breakeven point” of doing a function with AI versus the cost of performing it some other way (like with labor). It provides the awareness around the forecasted days to achieve the full business benefit vs the actual business
Time to Achieve Business Value
Measures the time it takes to achieve measurable business value from AI initiatives. This KPI uses a “breakeven point” of doing a function with AI versus the cost of performing it some other way (like with labor). It provides the awareness around the forecasted days to achieve the full business benefit vs the actual business results achieved and understanding the opportunity costs and value per month.
Formula
Time to Value (days) = Total Value associated with AI Service / daily Cost of Alternative solution
Candidate Data Sources:
- API usage reports
- Dashboards from AI platforms
- Logs from AI platforms
- Cloud billing data
Example:
- If an AI initiative starts on January 1, 2024, and the model is successfully deployed on April 1, 2024, the Time to Value is: April 1, 2024−January 1, 2024=3 months.
- Forecast to get $100k/mo of business within 1 month, but it actually took 5 months and only achieved $50k/mo business benefit, 5 months was the time to business value metric to track and seek to improve.
Forecasting
Planning & EstimatingCPI - Cost Performance Indicator
CPI, or Cost Performance Indicator, is a valuable KPI for all the FinOps Capabilities within the ‘Quantify Business Value’ domain.
CPI - Cost Performance Indicator
CPI, or Cost Performance Indicator, is a valuable KPI for all the FinOps Capabilities within the ‘Quantify Business Value’ domain. Unlike an ‘actual vs budget’ comparison, CPI focuses on tracking the value delivered compared to the cost spent on cloud. This metric is derived from Earned Value Management (EVM), a project management technique that integrates cost, schedule, and performance data. It provides insights into how efficiently a project or initiative is utilizing its budget. CPI on FinOps Business Value context should be interpreted as follows:
- If CPI > 1: Business Value is higher, compared to budgeted cloud cost.
- If CPI = 1: Business Value is expected compared to budgeted cloud cost.
- If CPI < 1: Business Value is lower, compared to budgeted cloud cost.
- Budgeted Cost per selected time period*
- Expected Unit Economic per selected time period*
- Actual Unit Economic per selected time period*
- Effective Cost per selected time period*
Formula
CPI = Earned Value / Effective Cost at time period
Where,
Earned Value = Budgeted Cost per selected time period * % Complete
And where,
% Complete = Expected Unit Economic per selected time period / Actual Unit Economic per selected time period * 100
Data sources:
- CSP Billing Data
- Internal Finance Metrics
Related Capabilities
Anomaly-Detected Cost Avoidance
Measures amount of cost avoidance as a result of identifying and correcting an anomaly.
Anomaly-Detected Cost Avoidance
Measures amount of cost avoidance as a result of identifying and correcting an anomaly. See Playbook for more details.
Formula
Total cost of the unpredicted & correctable amount of spend * Projected Amount of Days the anomaly could have occurred if the underlying issue was not addressed
Data Sources:
- Monitoring Tools
Related Capabilities
Anomaly ManagementForecast Accuracy Rate (Spend)
This metric compares forecasted vs. actual cloud spend over a specific period (e.g., day, month, quarter).
Forecast Accuracy Rate (Spend)
This metric compares forecasted vs. actual cloud spend over a specific period (e.g., day, month, quarter). While percentage variance is the primary metric, dollar differences can also be informative. Each organization defines its acceptable variance.
Formula
((Forecasted Public Cloud Spend – Actual Public Cloud Spend) / Forecasted Public Cloud Spend)
Data Sources:
- CSP Billing Data
- Organizational forecast documents
Related Capabilities
Forecast Accuracy Rate (Usage)
Compares forecasted vs. actual cloud usage (vCPUs, Memory, etc) over a specific period (e.g., day, month, quarter).
Forecast Accuracy Rate (Usage)
Compare forecast vs. actual cloud usage (serviceName, serviceCategory, serviceSubCategory, etc) over a specific period (e.g., day, month, quarter). This should be specific to service types (ex, measure by a specific serviceName, SKU, serviceCategory, serviceSubCategory etc). Percent variance is recommended, although the scale of usage should also be considered. Each organization defines its acceptable variance
Formula
Formula : For specific ServiceName or ServiceCategory or SKU
((Forecasted Resource Utilization – Actual Resource Utilization) / Forecasted Resource Utilization)
Data Sources:
- CSP Billing Data
- Organizational forecast documents
Related Capabilities
SustainabilityCount of FinOps Learning Opportunities Offered
Measure of the number of FinOps courses developed and offered to primary and supporting personas.
Count of FinOps Learning Opportunities Offered
Measure of the number of FinOps courses developed and offered to primary and supporting personas (e.g. monthly, quarterly, annually).
Formula
Target number of courses grouped by time period
Data Sources:
- Self Reporting
- Internal Training
- Learning Management Systems
Related Capabilities
FinOps Education & EnablementInputs & Outputs
Inputs
- Data Ingestion technology cost and usage data, business relevant value and demand data, and requirements for a common repository of usage and billing data that can span technology categories such as public cloud, data center, SaaS, AI etc.
- Use of FOCUS (FinOps Open Cost and Usage Specification) as a standardized billing and usage schema that can simplify normalization of cost datasets as well as terminology used in unit economics reporting
- Business Performance data from operational areas or FinOps Scopes being measured with Unit Economics
Outputs
- Unit Economic targets (ranges and thresholds) for each Scope of the FinOps practice
- Unit metrics used to measure business outcomes may be consistent, but the target values expected for each Scope may differ
Related Assets
Introduction to Cloud Unit Economics
FinOps for Streaming and Real-Time Data Platforms to Optimize Value
Cloud Unit Economics Story Collection
Unit Economics in the Public Sector
Unit Economics: A Government Organizational Perspective
The Benefits of Cloud Unit Economics for Your Organization
Driving Intelligent FinOps Investment Decisions with Unit Economics