Fixed Pricing vs Usage Pricing: Architecting Your Revenue

1. Fixed Subscription Pricing Explained

Fixed pricing is exactly what it sounds like. A customer pays a set recurring amount (e.g., $99/month) for access to the software, regardless of whether they log in once or one thousand times.

This is the traditional SaaS model popularized by Salesforce and Netflix. It relies heavily on "breakage"—a percentage of users who pay the subscription but use the platform very lightly, subsidizing the heavy power users.

The core advantage of fixed pricing is radical predictability. You can model your MRR (Monthly Recurring Revenue) with near-perfect accuracy based on historical retention rates. Test these curves using our Product Pricing Simulator.

2. Usage-Based Pricing Explained

Usage-based pricing (also known as metered billing or pay-as-you-go) charges the customer strictly based on their consumption of a specific metric.

If you send 10 emails, you pay for 10. If you send 10 million, you pay for 10 million. There is usually no flat fee.

This model perfectly aligns the price of the product with the value the customer is actively extracting. It removes the friction of "shelfware" (paying a flat fee for software sitting unused) and allows for infinite "expansion revenue" without ever requiring a sales rep to upsell the account.

3. The Pros and Cons Comparison

Fixed Pricing

• Pros: Predictable revenue, easy to collect annual cash upfront, simpler billing engineering, clearer value proposition to CFOs.
• Cons: Artificial ceiling on revenue (power users don't pay you more), massive friction to sign up (high upfront commitment), forces customers into rigid tiers.

Usage Pricing

• Pros: Zero friction to start, infinite upside revenue, perfectly aligns cost with customer value, zero shelfware.
• Cons: Highly unpredictable revenue, hard for enterprise customers to budget for, complex billing architecture, punishing if usage drops seasonally.

4. When to Use Each Model

You should lean toward Fixed Pricing if your product requires significant human behavioral change. If you are selling project management software, the value comes from the team adopting the habit of logging in. If you charge per login, you actively disincentivize adoption. Flat seats work better.

You should lean toward Usage Pricing if your product operates mostly in the background via API, or scales clearly alongside the customer's transaction volume. Data storage, SMS sending, AI generation, and payment processing are all perfect candidates for usage pricing.

5. Real SaaS Case Studies

Stripe (Pure Usage)

Stripe's 2.9% + 30¢ model is the pinnacle of usage pricing. They don't charge you a monthly fee to look at your dashboard. You only pay them when you process a transaction yourself. This means Stripe essentially acts as an automated tax on internet GDP. When their customers grow, Stripe automatically grows without hiring a single salesperson.

Slack (Hybrid Fixed)

Slack charges a fixed rate per user (e.g., $8/seat/mo). This allows IT departments to easily budget for a 500-person company ($48,000/yr). However, Slack introduced a "Fair Billing Policy," which acts as a gentle usage mechanism: if an employee doesn't log in for two weeks, Slack automatically pro-rates or refunds that portion of the seat fee.

Snowflake (Consumption Commit)

Enterprise data companies often use "commits." A company commits to spending $1M over a year on a usage-based data plan, securing a massive discount compared to the standard metered rate. It gives Snowflake the predictable cash of Fixed Pricing, but the architectural flexibility of Usage Pricing.

Frequently Asked Questions

Related Pricing Strategy Guides

• The Pricing Strategy Pillar Hub
• How to Conceptually Price a SaaS Product