Consumer AI Unit Economics: Managing Margins in Public
A founder-minded look at the shifting cost structures of AI-native products. We analyze how variable compute costs change the traditional SaaS margin profile.
On this page
- The Shift in Cost of Goods Sold (COGS)
- Defining the Unit in Consumer AI
- The Session Unit
- The Task Unit
- The User-Month Unit
- Subscription vs. Consumption Models
- The Case for Subscriptions
- The Case for Consumption-Based Pricing
- Strategies for Margin Protection
- Model Routing and Specialization
- Caching and Data Reuse
- Prompt Engineering for Efficiency
- Building in Public: Our Portfolio Approach
- The Path Forward
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.
Strategies for Margin Protection
Across our portfolio, we have implemented several strategies to ensure that our consumer ai unit economics remain healthy as we ship new features.
Model Routing and Specialization
Not every task requires the most powerful model available. We have moved several of our internal processes to a routing system. Simple tasks—like classification or basic formatting—are sent to smaller, more efficient models. Only complex reasoning tasks are sent to the high-cost frontier models. This approach significantly reduces the average cost per request without degrading the user experience.
Caching and Data Reuse
In many consumer applications, users often ask similar questions or perform similar tasks. By implementing a robust caching layer, we can serve repeated requests from a local data store rather than re-running an expensive inference process. This not only improves latency but also brings the marginal cost of that specific interaction down to near-zero, mimicking traditional software margins.
Prompt Engineering for Efficiency
Long, complex prompts increase the token count and, by extension, the cost. We treat prompt optimization as a cost-saving measure. By refining our instructions and reducing the 'noise' in our calls to the model, we can achieve the same results with fewer tokens. This is a small optimization that, when applied across millions of requests, has a meaningful impact on the bottom line.
Building in Public: Our Portfolio Approach
We believe in being transparent about how we build. This week, we are shipping a product update to our internal dashboard that allows us to see real-time margin data for each feature within our apps. This level of specificity allows us to make informed decisions about which features to expand and which to refine.
When we analyze consumer ai unit economics across our portfolio, we aren't looking for perfection on day one. We are looking for a path to sustainability. We avoid the trap of subsidizing usage with venture capital in the hopes that compute costs will eventually plummet. Instead, we build products that are valuable enough to be margin-positive today.
The Path Forward
Managing an AI-native brand requires a shift from the 'growth at all costs' mindset to a 'sustainable unit' mindset. By focusing on model specialization, efficient pricing structures, and rigorous cost tracking, you can build a product that is both useful to the consumer and profitable for the business.
If you are building in the AI space, the most important metric you can track is not your total user count, but your contribution margin per active user. Everything else is secondary.
defaultCta: See the portfolio — totalventures.io
Builder resources
See the full library →
Playbooks, checklists, and tools from running Total Ventures.
Studio Update
What we're building, in your inbox.
Weekly notes on the brands, the stack, and the loop.

