Unit economics

Define unit metrics to support organizational cloud goals

• Define and document the goals your organization wants to achieve with the cloud.

• Define and document the metrics that drive desired behaviors or outcomes.

• Define and document objective standards to evaluate your organization's cloud usage and costs.

• Define unit metrics and Key Performance Indicators (KPIs) that align with your organization's cloud goals.

Ensure unit economics data is available

• Establish a feedback process for data ingestion to ensure the necessary data for calculating KPIs is collected.

• Develop a strategy to make KPI data accessible to all stakeholders.

• Document the data sources, data correlations, and unit metric calculation methods required for all roles.

Validate the effectiveness of unit metrics

• Evaluate the impact of unit metrics on achieving goals by measuring actual performance.

• Establish a process for periodically reviewing, modifying, and retiring metrics.

Definition

Unit economics connects an organization's cloud spending with the fundamental value it creates. Without understanding how to track and compare benefits and costs, you cannot accurately determine whether your spending is effective.

Unit economics provides valuable insights to help an organization achieve its goals using the cloud. It facilitates effective communication between different roles and is a key method for linking cloud costs to business outcomes.

Unit economics metrics can measure many different aspects of cloud usage. For example, based on the goals of your organization or the application you are tracking, you can track business metrics such as cost per unit of revenue, cost per million authorized users, cost per transaction, or cost per customer. You can also track technical metrics such as cost per microservice load for a website, cost per click for customer interaction, or cost per GB of customer data storage.

Unit economics metrics should show engineering teams which elements cause unnecessary costs or deliver high value. This guides them to prioritize incremental improvements. The metrics should also show product owners the direct and indirect costs that result from customer product usage. This helps product teams create better pricing models. Additionally, the metrics can keep all organization members aware of the progress toward financial goals.

When you combine cloud costs with value measurement, changes in cloud costs can correspond to overall changes in value. Unit economics helps you understand the real impact on your business. If cloud costs rise, a unit economics view can help you determine if your organization is achieving economies of scale or if your metrics indicate runaway costs. FinOps practitioners often use the concept of cloud unit economics when they measure unit costs. They view cloud unit economics as a profit-maximization system that uses objective standards to reflect an organization's true performance in FinOps and in the business as a whole. Cloud unit economics achieves these organizational goals by measuring the marginal costs (also known as unit cost metrics) and marginal benefits (also known as unit revenue metrics) related to cloud software development and delivery.

By calculating the difference between marginal costs and marginal benefits, FinOps practitioners can determine where cloud operations break even and start to generate profit. This is an important concept in economics. It is also one of the most effective ways to support data-driven business decisions for cloud investments. For more information about how to develop, implement, and refine cloud unit economics metrics, see the capability implementation paper published by the Unit Economics Working Group.

The benefits of unit economics go beyond improving efficiency. Unit costs can act as a compass to guide management in making strategic decisions. Unit costs can reveal hidden inefficiencies in underutilized services, which promotes strategic service consolidation or architectural changes. Unit costs can identify when costs exceed business value, which prompts stakeholders to re-evaluate resource allocation and product decisions. Unit cost analysis can demonstrate that an increase in cloud costs can be positive, as long as the growth in business value is proportional to the growth in cloud costs.

Unit metrics can generally be divided into two main categories:

• Resource efficiency unit metrics, such as cost per GB of storage, cost per GB of transfer, and cost per virtual CPU (vCPU).

• Business unit metrics, such as cost per available seat mile for flights, cost per tenant, and cost per transaction.

Resource efficiency unit metrics help engineers demonstrate their team's value and share best practices within the team. Business unit metrics provide broader context for the entire business and indicate a higher level of maturity.

Ultimately, unit costs are not just KPIs—they guide a shift in organizational culture. By aligning technical costs with business value, they foster a sense of responsibility for cloud costs across the organization. This turns engineers into cost-conscious architects, product teams into builders of value-oriented features, and guides management toward financially sound organizational strategies.

Maturity assessment

Crawl

• Basic unit economics methods are used to analyze how the overall cost of cloud services relates to the organization's overall value.

• The focus is mainly on specific technical unit cost metrics.

• Business outcome data is difficult to obtain or associate with cloud cost data.

• The organization has a low level of adoption or understanding of unit economics, and it is not used to drive decision-making.

• Direct cloud cost metrics are used instead of total cost of ownership (TCO) or amortized costs.

Walk

• Different product or engineering teams develop team-specific unit economics metrics.

• Business outcome and value data are increasingly used in metrics.

• The organization has a moderate level of trust in and reliance on unit economics metrics, which enables key decisions in important areas.

• Unit economics starts to incorporate all costs, including those not directly related to cloud usage.

Run

• Unit metrics are set for all key cloud usage areas.

• Fine-grained unit metrics are available for both business and technical domains.

• Unit economics metrics are established before building or migrating applications to guide development and pricing decisions.

• The organization has a high level of trust in and reliance on unit metrics, using them as the primary mechanism for making cloud usage decisions.

• Metrics can be integrated with broader unit economics metrics to reflect the costs of specific products or services, such as Software as a Service (SaaS), hybrid architectures, and labor.

Functional activities

FinOps practitioner

• Collaborates with other roles to understand the key metrics relevant to the organization.

• Continuously communicates the importance of linking cloud costs to organizational value through unit economics.

• Sets and documents meaningful metrics related to cloud costs and usage.

• Makes unit metrics and KPIs accessible to all roles through appropriate channels.

Product

• Share with the FinOps team key organizational metrics and goals relevant to your responsibilities.

• Help me create effective metrics to measure the business value of my product.

• Tracks defined metrics to demonstrate the value their products create for the business.

Finance

• Informs the FinOps team about key financial metrics and goals.

• Helps devise financial metrics that effectively reflect the organization's overall cloud costs.

• Tracks these metrics and incorporates them into financial reports to reflect changes in the organization's financial position regarding cloud investment and efficiency.

Procurement

• Keep the FinOps team informed about key organizational metrics and goals within your area of responsibility.

• Uses unit metrics to assist with procurement planning and decisions.

Engineering

• You should keep the FinOps team informed of key organizational metrics and goals relevant to your responsibilities.

• Helps devise metrics that effectively reflect the engineering team's contribution to the organization.

• Uses unit economics metrics to improve organizational efficiency through architectural decisions.

Management

• Inform the FinOps team of the key organizational metrics and goals within your area of responsibility.

• Clearly communicates to all roles which unit economics metrics are critical to the organization's success.

• Provides specific guidance on the timing, format, and scope of unit economics metrics.

• Uses metrics to make better, data-driven decisions.

Success metrics and KPIs

It is a challenge to develop a KPI to measure the validity of another KPI.

The success of this capability can be measured by the percentage of teams, roles, and stakeholders who use unit economics metrics to communicate about cloud usage.

A key metric is the combination of resource utilization unit metrics with business unit metrics to reflect the cost areas that impact business outcomes or drive primary value.

Automation is used to calculate unit economics metrics for key business decisions through a well-archived, easily accessible, and highly relevant repository.

KPIs are periodically reviewed and evaluated for validity. The impact of unit economics metrics is regularly analyzed. Metrics are adjusted, added, or retired as needed to align with the organization's goals.

Inputs and outputs

• Requirements for a repository of cloud cost data, business-related value data, and general usage data from the Data ingestion capability.

• Business performance data for operational areas measured by unit economics.