Pricing wiki · Category

Monetization Models & Metering

Monetization models are less about what price and more about what you charge for.

Published concepts
10
Updated
Jul 2026

Category index

Explore concepts

Start with the decision you need to make, then use the connected concepts to test the logic underneath it.

Monetization model

9 min read

The way a business turns delivered value into revenue—who pays, for what unit, and how the money scales.

Pricing Metric (Value Metric)

10 min read

The pricing unit you charge on (seats, GB, transactions) that ensures your revenue grows as your customers succeed.

Subscription model

8 min read

A pricing model where customers pay repeatedly (monthly/annual) for ongoing access, usage, or replenishment—optimizing predictability and lifetime value.

Seat-based pricing

8 min read

A monetization model where customers pay a fixed recurring fee for each individual user (license) granted access to the software.

Usage-based pricing

10 min read

Charge customers based on measured consumption so price scales with value, improving adoption and expansion.

Transaction-based pricing

7 min read

A pricing model where fees are charged per transaction so revenue scales with usage while lowering adoption friction and aligning to outcomes.

Outcome / performance-based pricing

8 min read

A pricing model where customers pay based on the actual results or value achieved (outcomes) rather than usage, seats, or access.

Freemium model

8 min read

A customer acquisition strategy that uses a free-to-use version of a product to drive low-cost scale and upsell users into paid tiers.

Hybrid pricing

7 min read

A pricing model that combines fixed subscription fees with variable usage charges to stabilize revenue while capturing upside value.

Credits / drawdown model

8 min read

Customers prepay credits upfront, then draw down balances as they consume usage across products, features, and billing meters.

Editorial guide

Use this category

These notes preserve the category’s recommended sequence, decision rules, and practical applications.

Which model fits your product?

Your product's realityBest-fit model(s)The page to read
Value scales with how many people use it (collaboration, CRM)Subscription per seatSeat-based pricing
Continuous value, stable usage, recurring needFlat or tiered recurring feeSubscription model
Usage varies 10× across customers; costs scale with use (API, data, AI)Consumption pricing, usually with a baseUsage-based pricing
Value arrives in discrete, countable events (payments, bookings)Per-event pricingTransaction-based pricing
The result is measurable, attributable, and auditableGainshare / success feeOutcome-based pricing
Buyers need budget certainty AND you need upsideBase + variableHybrid pricing
Procurement wants committed spend; usage is spikyPrepaid walletCredits / drawdown
Near-zero marginal cost, viral loops, huge marketFree tier feeding paidFreemium model
You're not sure what unit to bill on at allStart here firstPricing metric / value metric

Insights

Foundation Insight

Your Monetization model is the broad canvas; your Pricing metric is the specific brush. If you get the model right but the metric wrong, you will face high churn. The perfect pricing metric scales in lockstep with the customer's perceived value.

Revenue Engines Insight

Most software companies operate on a Subscription Model. Historically, the default metric for these subscriptions was Seat-Based Pricing. It's easy to build and highly predictable for both the founder and the buyer. However, it creates friction. Customers share logins to avoid paying for extra seats, which stops your product from spreading virally through their organization. To solve this, the industry is shifting toward Usage-Based Pricing and Transaction-Based Pricing. These models remove user-count friction and align better with realized value—customers pay when usage or transactions happen. The tradeoff is predictability: variable billing can make revenue forecasting difficult for early-stage startups and can scare away enterprise buyers who need budget certainty. Outcome-Based Pricing is the holy grail of value alignment, but it is rarely used because proving attribution (e.g., "Did our software actually generate that $1M, or was it your sales team?") is notoriously difficult.

Advanced & GTM Insight

Hybrid pricing charges a platform fee to cover fixed costs and secure predictable MRR, then adds usage-based components to capture upside as clients scale. The Credits / drawdown model is a practical predictability layer for variable businesses: customers pre-commit budget and consume it over time. Freemium sits outside the revenue debate—it feeds your revenue engines by letting users experience value risk-free before hitting the paywall.

How to use this

Start simple

Choose 1 primary model and 1 value metric a customer can repeat back; complexity can come later.

The "Aha!" Metric Audit

Audit your current pricing metric against your product's "Aha!" moment.

Match pricing to go-to-market

PLG/self-serve often pairs with usage-based, transaction-based, or freemium (low friction), while enterprise buyers tend to prefer seats and/or a hybrid structure, often with credits / drawdown, for budget predictability.

Protect unit economics early

If marginal costs scale, avoid pure flat pricing; add usage or transaction components, and consider credits / drawdown or a hybrid base to prevent margin blow-ups at high volume.

Use pricing to drive expansion

Move from seats to usage, transaction-based, or hybrid to uncap NRR as customers grow, and use credits / drawdown to make that expansion budgetable for procurement-heavy buyers.

Continue through the library

Related categories

Move to the adjacent pricing decision without losing context.

Open license

Reuse with attribution

This content is available for reuse. When referencing or republishing it, please credit Dr. Sarah Zou and link back to the original source.

Licensed under Creative Commons Attribution 4.0 International. You may share and adapt the material with appropriate credit.