TL;DR: Your pricing model determines everything about your business: customer acquisition costs, retention rates, gross margin, and cash flow. Per-user pricing is simple but limits expansion. Usage-based pricing aligns value with cost but creates revenue volatility. Tiered pricing maximizes revenue capture but requires more complex infrastructure. Each model creates different unit economics and growth trajectories. Most companies choose pricing based on what competitors do without understanding the financial implications. Smart companies choose pricing models that align with how they want to grow and how customers derive value.
We review financial models from SaaS companies weekly. Founders obsess over whether to charge $49 or $79 monthly. Almost none think deeply about whether per-user, usage-based, or tiered pricing better aligns with their business model and growth strategy.
The pricing model you choose determines your entire financial trajectory. It affects how customers expand, what it costs to acquire them, how they churn, and what gross margins you achieve.
A company with per-user pricing at $20 per user has completely different economics than one with usage-based pricing averaging $20 per customer. The first gets predictable expansion as customers add headcount. The second gets unpredictable expansion tied to customer growth and product usage.
Both can work. But you need to choose deliberately based on what behavior you want to incentivize and what financial profile you want to build.
Most SaaS companies use one of five pricing models or combinations of them:
Flat rate: One price regardless of usage, users, or features. Simple but limits expansion revenue. Common for very small businesses or specialized tools. Example: Basecamp charges $299/month for unlimited users.
Per-user (seat-based): Price scales with number of users. Creates natural expansion as customers grow their teams. Predictable but can create adoption friction. Example: Slack at $7-12 per user monthly.
Usage-based (consumption): Price scales with actual usage of the service. Aligns price with value but creates revenue volatility. Example: AWS charges based on compute, storage, and bandwidth consumed.
Tiered (good-better-best): Multiple packages at different price points with different features. Maximizes revenue capture across customer segments. Example: Most SaaS offers Basic, Professional, Enterprise tiers.
Feature-based: Price scales based on which features customers use. Similar to tiered but more granular. Common in API businesses. Example: Stripe charges different rates for different payment features.
Each model creates different financial dynamics. Understanding these determines which model fits your business.
Per-user pricing ties revenue directly to how many people use your product. Add a user, add recurring revenue. Remove a user, lose recurring revenue.
Financial characteristics:
Expansion revenue is predictable and automatic. Customers naturally add users as they grow. We see 3-5% monthly expansion rates from companies with per-user pricing in growth-stage B2B segments.
CAC payback improves over time. You acquire a company with 5 users at $50 per user ($250 MRR). Over time they grow to 15 users ($750 MRR) with minimal additional sales effort.
Churn is sticky. Removing individual users is less disruptive than canceling entirely. Companies often retain accounts long after they should churn because a few users still get value.
Gross margins stay high. Per-user pricing rarely affects infrastructure costs much. Your 10th user at a company costs nearly nothing more to serve than the 5th user.
But per-user pricing has downsides:
Creates adoption friction. Customers resist adding users because each one costs money. This slows viral spread and limits expansion velocity.
Penalizes customer success. If your product makes customers more efficient (they need fewer people), you get punished with lower revenue.
Vulnerable to seat sharing and workarounds. Customers share logins to avoid paying for additional seats. You need usage enforcement which frustrates users.
Limits price increases. Raising prices means every existing user becomes more expensive. A 10% price increase on a 100-seat customer is $10K annually. Hard to push through.
Despite these challenges, per-user pricing works well when users each get independent value from the product, account expansion correlates with company growth, and you can enforce one-user-per-login.
Usage-based pricing charges customers based on consumption. The more they use your product, the more they pay.
Financial characteristics:
Revenue grows automatically with customer success. If your product drives value, customers use it more and revenue expands organically. Best-case scenario: 5-10% monthly expansion rates from increased usage.
Price aligns with value delivered. Customers pay proportionally to value received. This reduces friction and increases willingness to expand usage.
Low initial friction. Customers can start small and scale usage as they get comfortable. This helps with acquisition.
Natural revenue retention. Customers who grow their business naturally increase usage and revenue without explicit upsell conversations.
But usage-based pricing creates challenges:
Revenue volatility. Customer usage fluctuates monthly. A customer might do $1,000 in usage in January, $600 in February, $1,400 in March. This makes forecasting harder and revenue less predictable.
Gross margin pressure. Higher usage often means higher infrastructure costs. You need to price to maintain margins as customers scale.
Complex packaging and pricing. Determining what to meter and how to price it requires sophisticated analysis. Price too high and usage stays low. Price too low and you leave money on table.
Forecasting is difficult. Traditional cohort analysis based on signup month matters less. You need usage forecasting that accounts for customer growth patterns.
Implementation complexity. You need robust metering infrastructure to track usage accurately and bill fairly. This requires engineering investment.
Usage-based pricing works well when value scales clearly with usage (data storage, API calls, transactions processed), infrastructure costs scale proportionally with usage, and customer success depends on product adoption.
Tiered pricing offers multiple packages at different prices with different feature sets. Typically Good-Better-Best structure.
Financial characteristics:
Maximizes revenue capture. Small customers buy Basic. Mid-market buys Professional. Enterprise buys Premium. Each pays what they can afford.
Creates upgrade path. Customers naturally expand from Basic to Professional to Enterprise as they grow. This provides expansion revenue without seat growth.
Allows price discrimination. Charge enterprise customers 10x more than small customers for fundamentally the same product with a few additional features.
Enables land-and-expand. Start customers on cheaper tier to reduce acquisition friction, expand them to higher tiers after they see value.
But tiered pricing has costs:
Complexity in packaging. Deciding which features go in which tier requires deep understanding of customer value perception. Get it wrong and you either give away value or prevent adoption.
Support costs vary by tier. Enterprise customers expect white-glove support. Basic customers get knowledge base and email. This segments gross margin by tier.
Revenue forecasting complexity. Different tiers have different retention, expansion, and contraction rates. Your model needs to track cohorts by tier.
Upgrade friction. Customers resist upgrading because it feels like paying more for what they already had. You need to add enough features to justify the price increase.
Feature access creates product complexity. You’re maintaining multiple versions of your product with different features enabled. This is engineering overhead.
Tiered pricing works when customers have clearly different needs and budgets, features can be cleanly separated by value, and you can create meaningful differentiation between tiers.
Many successful SaaS companies combine pricing models to optimize economics:
Per-user with usage fees: Base price per user plus additional charges for heavy usage. Salesforce does this with platform fees on top of seat pricing.
Tiered with usage: Different tiers with usage allowances, overage charges above limits. Mailchimp does this with subscriber counts in tiers.
Flat rate with feature upsells: Base platform access plus a la carte pricing for premium features. Common in developer tools.
The right hybrid depends on your value drivers and customer behavior. We worked with a client who combined per-user ($50 per user) with usage-based storage fees ($0.10 per GB). This let them capture expansion from both team growth and increased product usage. Their expansion rate went from 3% monthly (per-user only) to 7% monthly (hybrid model).
Different pricing models create different financial profiles that investors care about:
Per-user pricing typically delivers:
– Net revenue retention: 105-115%
– CAC payback: 10-16 months
– Gross margin: 75-85%
– Revenue predictability: High
Usage-based pricing typically delivers:
– Net revenue retention: 110-130%
– CAC payback: 8-14 months (customers start small)
– Gross margin: 60-75% (infrastructure scales with usage)
– Revenue predictability: Medium
Tiered pricing typically delivers:
– Net revenue retention: 108-120%
– CAC payback: 12-18 months (customers start on low tier)
– Gross margin: 70-80%
– Revenue predictability: Medium-high
These ranges matter for valuation. Investors value high net revenue retention and gross margin. If your pricing model delivers 105% NRR when usage-based competitors deliver 120% NRR, that’s a competitive disadvantage unless you have other strengths.
Select your pricing model based on these factors:
How customers derive value: If value comes from number of users, use per-user. If value scales with usage, use consumption. If value varies by features, use tiered.
Customer growth patterns: Fast-growing customers naturally expand per-user or usage-based pricing. Slower-growing customers are better with tiered (they upgrade for features, not volume).
Your cost structure: If your costs scale with usage, you need pricing that scales similarly or gross margin gets crushed. If costs are mostly fixed, you can use any model.
Competitive dynamics: If competitors use per-user and customers expect that, fighting it is hard. You can differentiate on pricing model but you need clear value story.
Sales complexity you can handle: Usage-based and tiered pricing require more sophisticated sales conversations. Per-user and flat rate are simpler.
Engineering resources: Usage-based requires metering infrastructure. Tiered requires feature flagging. Per-user requires license enforcement. Factor in the build cost.
We typically recommend per-user pricing for companies selling team collaboration tools, usage-based for infrastructure or API businesses, tiered for horizontal SaaS with diverse customer segments.
Your initial pricing model doesn’t have to be permanent. Many companies evolve as they learn:
Start simple, add complexity. Launch with flat rate to eliminate friction. Add per-user once you understand adoption patterns. Add usage-based once you have metering infrastructure.
Grandfather existing customers. When you change models, let existing customers keep old pricing. This prevents churn while you optimize for new customers.
Test with segments. Try usage-based with new customers while keeping per-user for existing. Measure which creates better unit economics.
The key is being intentional. Don’t change pricing models because you read an article saying usage-based is hot. Change because you have data showing it will improve your unit economics or expansion rates.
—
Q: Can we change our pricing model after we have customers?
Yes, but carefully. Existing customers should typically be grandfathered on old pricing to avoid churn. New customers get new model. Over time, your customer base shifts to new model. Some companies offer incentives for existing customers to switch (discount for annual prepay, additional features). The key is not forcing existing customers onto new pricing that hurts them. We’ve seen companies lose 20-30% of customers by forcing pricing model changes. Do the math on whether new model’s improvements offset that churn risk.
Q: How do we decide what features belong in which tier for tiered pricing?
Start with customer research. What features do different segments value? Your Basic tier should have features that small customers need. Professional adds features mid-market needs. Enterprise adds features only large customers use. Common pattern: Basic has core product, Professional adds collaboration/automation, Enterprise adds security/compliance/controls. Validate by looking at which customers request which features. If everyone requests a feature, it should be in Basic. If only enterprise customers request it, it’s an Enterprise feature.
Q: Does usage-based pricing work for small customers or only enterprise?
It works for both but with different dynamics. Small customers love usage-based because they can start at $50/month and scale as they grow. Enterprise loves it because pricing scales with their business. The challenge is small customers create higher support costs relative to revenue, so your gross margins on small usage-based customers might be lower. Some companies set minimum monthly commitments ($500/month) to ensure customers are large enough to be profitable even at low gross margin. Pure usage-based with no minimums works best when onboarding is self-serve and support is automated.