Consumer AI Unit Economics: Managing Margins in Public

For a decade, the software industry operated on the assumption of near-zero marginal costs. Once the code was written and the server was provisioned, the cost of adding one more user was negligible. This reality allowed for the high-margin profiles that defined the previous era of software.

With the shift toward AI-native products, that assumption has changed. Every interaction now carries a direct, variable cost. Understanding consumer ai unit economics is no longer an exercise for the finance team; it is a core product requirement for any founder building in public today.

The Shift in Cost of Goods Sold (COGS)

In traditional software, COGS primarily consisted of hosting, third-party APIs for communication, and perhaps a small data storage fee. In an AI-native portfolio company, the COGS profile looks different. Every time a user generates a response, summarizes a document, or creates an image, you are paying for compute.

This compute cost is often tied to the volume of data processed or the complexity of the model used. Unlike traditional database queries, these costs do not drop to near-zero as you grow. While infrastructure providers may offer volume discounts, the fundamental relationship between usage and cost remains linear. If you do not account for this in your initial product design, growth can become a liability rather than an asset.

Defining the Unit in Consumer AI

To manage your margins, you must first define what a 'unit' is for your specific product. In our portfolio, we look at this through three lenses:

The Session Unit

For products focused on chat or iterative discovery, we track the cost per session. This includes the total tokens consumed across multiple turns of conversation. This helps us understand the average cost of a user 'solving a problem' rather than just the cost of a single message.

The Task Unit

For utility-based products—such as a tool that cleans a data set or generates a specific report—the unit is the completed task. This is easier to price but requires a deep understanding of the failure rate. If a task requires three attempts to get right, your unit cost is effectively tripled.

The User-Month Unit

This is the standard for subscription models. We calculate the total compute costs incurred by a user over thirty days and compare it against their subscription fee. This is where the variance in user behavior becomes most apparent. A 'power user' can easily become a net-negative asset if their consumption exceeds the margin provided by their monthly fee.

Subscription vs. Consumption Models

Choosing a pricing model is the most significant lever you have for managing consumer ai unit economics.

The Case for Subscriptions

Subscriptions offer predictability for both the user and the company. They provide a steady stream of revenue that can cover fixed costs and provide a buffer for variable compute. However, subscriptions in the AI space require 'guardrails.' We have found that implementing soft limits or daily quotas is necessary to prevent a small percentage of users from eroding the margins of the entire cohort.

The Case for Consumption-Based Pricing

Consumption-based pricing—often referred to as 'pay-as-you-go'—aligns your revenue directly with your costs. This is the most honest way to build an AI product. It ensures that every transaction is margin-positive. The challenge here is user friction. Consumers generally prefer the 'all-you-can-eat' nature of subscriptions. Moving to a consumption model requires a product that provides enough specific value that the user is willing to consider the cost of each action.