Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Revenue Model

Pattern

A reusable solution you can apply to your work.

Understand This First

  • Customer – different customers expect different models.
  • Value Proposition – the model must reflect the value delivered.

Context

At the strategic level, a product that solves a real Problem still needs a sustainable way to fund its existence. The revenue model is the basic structure by which money flows into the business. It’s distinct from Monetization, which is the practical mechanism for collecting payment. The revenue model answers “what are we selling?” while monetization answers “how do we collect the money?”

Choosing a revenue model is a product decision, not just a finance decision. The model shapes what you build, who your Customer is, and what behaviors you optimize for.

Problem

How will this product generate money? Without a clear answer, the product either depends on perpetual outside funding, burns through savings, or quietly dies. The choice of revenue model also creates incentive alignment (or misalignment) between the product team and the customer. A model that charges per seat incentivizes features that drive adoption across an organization. A model based on advertising incentivizes engagement and attention capture. The model shapes the product.

Forces

  • Revenue must be proportional to value delivered, or customers will feel cheated and leave.
  • Some models favor growth over profitability (freemium, advertising) while others favor margin (enterprise licensing).
  • Switching revenue models mid-stream is extremely disruptive to existing customers.
  • The model must be legible. Customers need to understand what they’re paying for and why.
  • AI-native products face unique pricing challenges because costs scale with usage in ways traditional software doesn’t.

Solution

Choose from a small set of proven revenue model archetypes, then adapt to your specific market:

  • Subscription (SaaS): Recurring payment for ongoing access. Works when the product delivers continuous value. Most common for software products today.
  • Usage-based: Pay per API call, per compute hour, per document processed. Natural for AI products where cost scales with usage. Aligns revenue with value but makes costs unpredictable for customers.
  • Transaction fee: Take a percentage of each transaction (marketplaces, payment processors). Works when you sit in the flow of money.
  • Licensing: One-time or periodic payment for the right to use the software. Common in enterprise and on-premise deployments.
  • Advertising: Free to the user, paid by advertisers. Works at massive scale but misaligns incentives. The user becomes the product.
  • Services: Professional services, consulting, or implementation alongside the product. High-margin per engagement but hard to scale.

The best model is the one that aligns your incentives with your customer’s success. If the customer succeeds when they use your product more, usage-based pricing is natural. If success means using it less (a tool that reduces incidents), subscription pricing avoids penalizing your own success.

How It Plays Out

A startup builds an AI agent that reviews pull requests. They consider two models: a per-seat subscription and a per-review usage fee. Per-seat pricing gives customers cost predictability and incentivizes wide adoption within a team. Per-review pricing aligns cost with value (more reviews = more value) but scares large teams with high PR volume. They choose per-seat pricing for teams under fifty developers and negotiate custom usage-based pricing for larger organizations.

A developer building a side project with AI agents adds Stripe subscription billing. She uses an AI agent to generate the billing integration code, including webhooks for subscription lifecycle events. The agent scaffolds the entire Stripe integration in under an hour, but the choice of subscription vs. usage-based billing was a product decision she had to make herself, based on how her customers think about value.

Tip

When using AI agents to build billing and payment systems, be explicit about the revenue model in your prompt. “Implement a per-seat monthly subscription with annual discount” gives the agent enough structure to generate correct billing logic. “Add payments” does not.

Consequences

A well-chosen revenue model creates sustainable funding and aligns team incentives with customer outcomes. It simplifies pricing conversations and makes financial planning predictable.

The cost is commitment. Once customers are on a pricing model, changing it is painful. Migrating from per-seat to usage-based pricing, for example, creates winners and losers among existing customers. Choose thoughtfully before launching, and treat the revenue model as a product decision that requires the same rigor as feature design.

Revenue models for AI products carry a specific risk: the cost of serving customers (LLM inference, compute) may not scale favorably with revenue. A usage-based model where each additional unit of usage costs you almost as much as the customer pays is a trap. Understand your unit economics before committing.

  • Depends on: Customer — different customers expect different models.
  • Depends on: Value Proposition — the model must reflect the value delivered.
  • Refined by: Monetization — the practical mechanism for collecting payment.
  • Enables: Go-to-Market — pricing is a core element of the GTM strategy.
  • Contrasts with: Distribution — free distribution models (open-source, freemium) require a separate revenue model for the paid tier.