Overview
A SaaS pricing model is the structure that determines how customers are charged and how revenue scales
Every pricing model is built from three parts: a pricing metric (what customers pay for), a pricing modality (how they pay), and packaging (how pricing is organized into plans)
Common SaaS pricing models: seat-based, usage-based, tiered, freemium, and hybrid
The right model depends on how the product creates value, how customers want to pay, and how the business needs to scale
Most pricing problems come from models that haven't evolved as the company grew - rarely from the initial choice
SaaS pricing decisions usually start with a label - “we're going usage-based,” “we need tiers,” “let's add freemium.” The label is the easy part.
The harder part is designing the structure underneath the label so revenue scales as customers use the product.
The structure of the pricing model typically matters far more than the price itself.
- Ulrik Lehrskov-Schmidt, author of The Pricing Roadmap
A well-designed pricing model determines whether customers can adopt the product easily, whether revenue is predictable or volatile, and whether expansion happens by design or not at all.
When the model is wrong, the symptoms are hard to ignore. Pricing becomes hard to explain. Sales leans on discounting. Deals slow down. Revenue stops scaling with customer value.
Choosing a pricing model is mostly a structural problem. A small number of models appear repeatedly across SaaS, and most companies land on some version of one of them. The trick is picking - and evolving - the one that fits.
What is a SaaS pricing model?
A SaaS pricing model is the structure that defines how customers are charged for a product. It describes how pricing is organized and how revenue scales as customers grow.
Every pricing model is built from three components:
Pricing metric - what customers pay for (users, transactions, API calls)
Pricing modality - how customers pay (subscription, pay-as-you-go, credits)
Packaging - how pricing is organized into plans, tiers, or limits
Different combinations create different models:
- A seat-based model combines a per-user metric with a subscription modality
- A usage-based model combines a consumption metric with pay-as-you-go billing
- A tiered model layers packaging on top of those first two components
The same label - “tiered pricing,” “usage-based,” “enterprise” - can describe very different structures depending on how those three components are designed. This is why pricing models are best understood as structures, not labels.
Pricing model vs. pricing metric
A pricing metric is what customers pay for. A pricing model is the full structure around it.
If the metric is users, the model might be seat-based subscription pricing. If the metric is API calls, the model might be usage-based with volume discounts.
This distinction matters because many SaaS companies try to fix pricing by changing the model when the real issue is that they're charging for the wrong unit in the first place. Fixing the model without fixing the metric usually just rearranges the problem.
The most common SaaS pricing models
Five pricing models appear repeatedly across SaaS. Each reflects a different way of connecting pricing to how customers use the product.
Seat-based pricing (per user)
Used by: Slack, Salesforce, Notion
Works when: value grows with team adoption and the product is used collaboratively
Breaks when: value scales independently of seat count - usage and outcomes grow, but revenue stays flat because seats don't change
Where seat-based pricing tends to leak revenue: the product gets more valuable over time (more data, more integrations, deeper workflows) but seat count is capped by headcount. Slack's move to charging per active user is one of the cleaner fixes for this pattern.
Usage-based pricing (consumption)
Used by: Twilio, Snowflake, OpenAI
🟢 Works when: usage is a clean proxy for value and customers can forecast their spend
🔴 Breaks when: usage fluctuates unpredictably, finance teams push back, or buyers can't budget for variable cost
Usage-based pricing gets treated as the modern SaaS default, especially in AI and infrastructure. The trade-off lands hardest in enterprise: buyers often prefer budget predictability over perfect value alignment.
Tiered pricing
Used by: HubSpot, Intercom, most SMB SaaS
🟢 Works when: customer segments are clearly different and value increases in discrete steps
🔴 Breaks when: tiers are built around features rather than value, creating arbitrary limits and unclear upgrade logic
Tiered pricing is the most widely used and most commonly misused model in SaaS. The issue usually sits with the packaging, not the model itself. When tiers group features instead of structuring value, customers can't tell why they should upgrade, and sales starts discounting to close the gap.
Freemium pricing
Used by: Notion, Canva, early Slack
🟢 Works when: users experience value quickly and usage creates natural pressure to upgrade
🔴 Breaks when: the free tier is “good enough” - growth looks strong but paid conversion stalls
Freemium often gets treated as a growth strategy. It's really a conversion model. Many SaaS companies acquire users at scale through freemium and then struggle to turn them into revenue. When the free tier doesn't create pressure to upgrade, freemium becomes a cost center rather than a growth engine.
Hybrid pricing
Used by: Stripe, Snowflake, OpenAI, HubSpot
🟢 Works when: value is driven by multiple dimensions and no single metric captures all of it
🔴 Breaks when: the multiple components overlap, compete, or get layered on top of each other to patch unrelated problems
Hybrid pricing gets sold as the best of both worlds. It's also where pricing complexity tends to explode. The rule of thumb: each component of a hybrid model should capture a distinct part of value. If components overlap, complexity goes up without improving monetization.
How SaaS pricing models compare
No pricing model is perfect. Each trades off something. The choice depends on which trade-off fits the product and the business stage.
How SaaS pricing models evolve
Pricing models aren't static. As a SaaS company grows, the pricing model has to evolve to reflect changes in product complexity, customer segments, and how value gets delivered.
Most pricing problems SaaS companies run into don't come from choosing the wrong model at the start. They come from failing to evolve the model as the business scales. Over time, that creates what Ulrik Lehrskov-Schmidt calls commercial debt - pricing that no longer reflects the product or how customers buy.
Stage 1: Early stage - simplicity for adoption
Early-stage SaaS companies prioritize adoption. Pricing at this stage is usually freemium, simple tiered pricing, or low-complexity seat-based pricing.
The goal is to reduce friction, drive user growth, and validate product-market fit. Pricing is intentionally simple and almost always under-monetized. That's fine at this stage.
Stage 2: Growth stage - segmentation and structure
As the company grows, the customer base becomes more diverse. Customers use the product differently, generate different levels of value, and have different willingness to pay.
Pricing models at this stage tend to evolve toward more structured tiering, clearer customer segmentation, improved packaging, and early usage-based components.
The goal shifts from pure adoption to capturing value across segments. This is also where familiar pricing problems start showing up: unclear packaging, discounting pressure, and pricing that feels disconnected from value.
Stage 3: Scale stage - hybrid and value alignment
At scale, SaaS companies move toward more sophisticated models, usually hybrid structures:
- Base subscription plus usage-based components
- Modular or add-on pricing
- Enterprise-specific deal structures
Pricing becomes a core part of the revenue architecture rather than a packaging decision. Expansion revenue starts to matter as much as new ARR.
Where pricing models break
SaaS companies rarely fail because of the initial pricing model. They struggle when:
- The product evolves but pricing doesn't
- New features get added without restructuring pricing
- Enterprise customers get forced into SMB pricing logic
- Usage grows but revenue doesn't scale with it
The symptoms are familiar: heavy discounting, slow enterprise sales cycles, inconsistent deal structures, and internal misalignment across sales, product, and finance. This is commercial debt in action - pricing drifting further from how the business actually creates value.
The principle: pricing has to evolve with value
A strong SaaS pricing model comes from the ability to keep evolving pricing as the product, customer base, and value drivers change.
In practice, that means revisiting pricing metrics as usage patterns evolve, adapting pricing models to new customer segments, introducing new monetization mechanisms over time, and keeping pricing aligned with how customers perceive value.
Companies that treat pricing as static tend to fall behind. Companies that treat pricing as an evolving system scale both adoption and monetization.
Framework for choosing the right pricing model
Choosing a pricing model means designing a structure that aligns with how the product creates value, how customers use it, and how the business scales. There's no universally best model - the right choice depends on a handful of factors.
Five questions cover most of the work:
How do customers experience value?
Different products create value in different ways. Collaboration tools create value as more users adopt the product. Infrastructure products create value through usage. Revenue platforms create value through transactions or outcomes.
The pricing model should reflect this. If value grows with team size, seat-based pricing fits. If value grows with consumption, usage-based is usually stronger. If value varies by segment, tiered or hybrid models are often necessary.
How do customers prefer to pay?
Even a value-aligned model has to match how customers are comfortable paying. Enterprise buyers tend to prefer predictable contracts. Developers often prefer pay-as-you-go. Finance teams push back on unpredictable cost structures.
A strong pricing model balances value alignment, customer expectations, and commercial practicality.
Does the model support the sales motion?
Pricing has to support how the company sells:
- Product-led growth -> freemium or usage-based
- Sales-led growth -> tiered or seat-based
- Enterprise sales -> hybrid and contract-based
When the pricing model conflicts with the sales motion, conversion drops, sales cycles lengthen, and discounting creeps in.
Does revenue scale with customer growth?
A good pricing model makes revenue grow as customers grow. The test: if a customer becomes 10x more successful, does revenue increase accordingly? Or does pricing stay flat while customer value expands?
If revenue doesn't scale with customer success, the model is likely misaligned. This is a common issue with flat-fee pricing, poorly structured tiers, and outdated seat-based models.
Is the model simple enough to sell and flexible enough to capture value?
There's always a trade-off between simplicity (easy to understand and sell) and flexibility (ability to capture value across use cases). Simple tiered pricing is easy to sell but may not capture all value. Hybrid pricing captures more value but increases complexity.
The goal is to introduce complexity where it creates value. Too much simplicity leads to under-monetization. Too much complexity leads to friction.
Treat pricing as a system
Pricing is an ongoing decision. Companies that struggle with pricing often treat it as a one-off project, delay changes because of perceived risk, and watch complexity accumulate over time.
The alternative: regular updates, clear ownership, and structured decision-making. That prevents pricing from drifting out of sync with the business.
Frequently asked questions
01
What is a SaaS pricing model?
A SaaS pricing model is the structure a software company uses to charge customers. It's built from three components: a pricing metric (what customers pay for), a pricing modality (how they pay), and packaging (how pricing is organized into plans or tiers). Common SaaS pricing models include seat-based, usage-based, tiered, freemium, and hybrid.
02
What is the most common SaaS pricing model?
Seat-based pricing is the most common in collaboration and productivity tools. Tiered pricing is standard in SMB and mid-market SaaS. Usage-based pricing is increasingly common in infrastructure and AI products. Many successful SaaS companies end up on hybrid pricing models that combine subscription and usage-based elements.
03
What is the difference between a pricing model and a pricing metric?
A pricing metric is the unit customers pay for - users, API calls, transactions. A pricing model is the full structure combining the metric, the billing modality, and the packaging. For example: metric = users, modality = annual subscription, model = seat-based pricing.
04
How do I choose the right SaaS pricing model?
Start with how the product creates value and how customers use it. Seat-based fits when value grows with users. Usage-based fits when value grows with consumption. Tiered or hybrid fits when there are multiple distinct customer segments. Match the model to the sales motion, and check that revenue scales as customers grow.
05
What is usage-based pricing in SaaS?
Usage-based pricing charges customers based on how much they use the product - API calls, tokens, transactions, or data processed. It's common in developer platforms, infrastructure software, and AI products. Usage-based pricing aligns pricing with consumption but can introduce cost variability for customers.
06
What is seat-based pricing?
Seat-based pricing charges customers for each user that has access to the product. It's common in collaboration tools, CRMs, and productivity software. Seat-based pricing works best when value grows with team adoption, though it can cap revenue when usage and outcomes scale without adding seats.
07
What is a hybrid SaaS pricing model?
A hybrid model combines multiple pricing approaches - typically a base subscription (per user or per tier) plus usage-based components (transactions, API calls, tokens). Hybrid models allow companies to maintain predictable base revenue while scaling with usage, though they increase complexity and require careful design to avoid overlapping components.
08
Why do SaaS pricing models fail?
Most pricing models fail because they don't evolve as the business grows, rather than because the initial design was wrong. Common causes: pricing doesn't keep up with product development, packaging becomes misaligned with customer value, and enterprise customers get forced into SMB pricing logic. The accumulated mismatch is what Ulrik Lehrskov-Schmidt calls commercial debt.
09
What is the best pricing model for SaaS?
There's no single best pricing model. The most effective one aligns with how the product creates value, how customers want to pay, how the company sells, and how the business needs to scale. Many successful SaaS companies end up on hybrid pricing models that combine simplicity, flexibility, and scalability.
