How to price SaaS products

The best way to price a SaaS product is to combine value-based pricing with a simple pricing model that scales with customer success. For many B2B SaaS products, that means testing three paid tiers, choosing a value metric customers understand, and validating the offer through real buying behavior.

A strong starting structure is:

A free trial or limited free plan, if users can reach value quickly
Three paid tiers: Starter, Professional and Business
Monthly and annual billing
Pricing based on seats, usage, business size or another clear value metric
Custom enterprise pricing only when implementation, security or support requirements vary

SaaS pricing should reflect customer value, customer usage and the cost of serving each account. Stripe lists subscription, tiered, per-user, usage-based, freemium and hybrid pricing as the main SaaS pricing models.

SaaS Pricing at a Glance

Pricing decision	Recommended starting point
Pricing strategy	Value-based pricing
Number of plans	Three paid tiers
Primary metric	The clearest metric linked to customer value
Billing frequency	Monthly plus annual
Free access	Free trial unless a permanent free plan has a clear acquisition advantage
Usage-based products	Hybrid subscription plus usage or overage charges
Enterprise sales	Custom pricing for complex requirements
Validation method	Customer interviews, sales tests and pricing experiments

1. Define Who You Are Pricing For

Do not set a price for an undefined market. Start with the customer segment, buyer and financial value of the product.

Document:

Company size
Industry
Number of potential users
Current alternative or workaround
Business problem being solved
Financial impact of the problem
Urgency of the purchase
Buyer, user and budget owner
Required integrations, security and support

A marketing automation platform may serve freelancers, small businesses and large marketing teams. Those groups have different budgets, requirements and reasons to buy.

A small business may care most about affordability and ease of use. An enterprise buyer may place more value on governance, permissions, security reviews, dedicated support and procurement flexibility.

Your pricing should reflect those differences.

2. Quantify the Value Your SaaS Product Creates

Value-based pricing starts with the customer's outcome, not your feature list.

Use this calculation as a starting point:

Customer value =
revenue gained
+ costs avoided
+ hours saved
+ risk reduced

Suppose a workflow automation product saves a customer 20 hours per month. If the relevant labor cost is $50 per hour, the direct time value is:

20 hours × $50 = $1,000 per month

That does not mean the product should cost $1,000 per month. It gives you a reference point for customer interviews and price tests.

Ask customers:

What does this problem cost today?
What happens if it remains unsolved?
How much time or money does the product save?
Which result would justify the purchase?
What alternatives did you consider?
At what price would the product feel inexpensive, reasonable or too expensive?

Willingness to pay is the maximum amount a customer is prepared to pay. It changes with the customer segment, buying context and perceived value. Researching it can help you set price points and decide which features belong in each tier.

3. Choose the Right SaaS Value Metric

A value metric is the unit that determines how a customer pays. It should increase as the customer receives more value from the product.

Common SaaS value metrics include:

Users or seats
Monthly active users
Contacts or records stored
API calls
Transactions processed
Messages sent
Data volume
Projects managed
Revenue processed
Locations or business units
AI generations or credits consumed

A useful value metric meets four conditions:

Customers understand it.
It correlates with the value they receive.
It scales as the customer grows.
You can measure it accurately.

OpenView describes the value metric as a central part of SaaS pricing because it connects what customers pay with how they use and benefit from the product.

Examples of Suitable Value Metrics

SaaS product	Likely value metric
Team collaboration software	Active users or seats
Email marketing platform	Contacts or emails sent
Payment platform	Transaction volume
Cloud infrastructure	Compute, storage or requests
Customer support platform	Agents, tickets or conversations
AI API	Tokens, requests or completed tasks
Property management platform	Units, properties or locations

Do not charge per seat when most of the value comes from usage. An API product may create value through requests rather than employee logins. Per-user pricing may make more sense for collaboration software where broader team adoption is part of the product's value.

4. Select the Right SaaS Pricing Model

Per-User Pricing

Per-user pricing charges a recurring amount for each user or seat.

Use it when:

Each user receives meaningful value
More users usually indicate broader adoption
Customers understand the link between seats and price
Your product supports team collaboration

The main risks are shared logins, lower adoption and high costs for large teams. Seat count may also fail to reflect actual usage.

Per-user pricing works well for many collaboration and productivity products, but it can discourage customers from inviting teammates when each additional user creates a noticeable cost.

Tiered or Feature-Based Pricing

Tiered pricing offers packages at different price points.

A typical structure might be:

Starter: Core functionality for individuals or small teams
Professional: Automation, integrations and higher limits
Business: Advanced controls, reporting and support
Enterprise: Custom security, procurement and service requirements

Tiered pricing works when customers have genuinely different needs. Each upgrade should solve a new business requirement rather than lock an arbitrary feature behind a higher price.

Usage-Based Pricing

Usage-based pricing charges according to consumption, such as API calls, storage, messages or transactions.

Use it when:

Usage closely tracks customer value
Customers prefer to pay for actual consumption
Infrastructure costs rise with usage
Customers vary widely in how much they use the product

The risks include unpredictable bills, fluctuating revenue, metering errors and billing disputes.

Usage-based pricing is common for cloud services, communications platforms, data products and AI APIs. Usage allowances, prepaid credits, spending caps, volume discounts and usage reporting can make bills easier to manage.

Hybrid Pricing

Hybrid pricing combines a recurring subscription with usage-based charges.

For example:

$299 monthly platform fee
+ $0.02 per transaction above the included allowance

This model can work well for infrastructure-heavy SaaS products. The base fee provides predictable revenue, while usage charges let revenue grow as customers receive more value.

Freemium Pricing

Freemium provides a permanent free version with paid upgrades.

Use it when:

Users can understand the product without sales assistance
The product has low marginal serving costs
Free users can invite others or create organic distribution
A natural usage or feature limit encourages upgrades

A free plan should demonstrate the product's value without meeting the customer's full commercial need.

Freemium is different from a free trial. A trial provides temporary access. A free plan normally remains available indefinitely.

Flat-Rate Pricing

Flat-rate pricing offers one product at one price.

It works best when:

The target customer is relatively uniform
Usage does not vary much
Simplicity matters more than segmentation
The product has a narrow use case

Flat-rate pricing is easy to explain, but it can undercharge large customers and exclude smaller ones.

5. Create Three Clear Pricing Tiers

Three paid tiers are usually enough for an initial SaaS pricing page.

Tier	Main purpose	Typical buyer
Starter	Prove value with low commitment	Individual or small team
Professional	Support the main use case	Growing company
Business	Add scale, controls and support	Larger organization

Design tiers around customer segments and outcomes rather than an unstructured feature list.

For each plan, define:

Who it is for
The primary outcome
Included usage
Key limitations
Support level
Integrations
Security and administration features
The reason a customer would upgrade

The middle plan should usually represent the main customer you want to acquire. The highest public plan should make the added value clear without forcing every buyer into a sales conversation.

A pricing page should help buyers identify the right plan quickly. Complicated pricing creates friction when customers have to calculate several limits, add-ons and usage charges themselves.

6. Set Actual Price Points

Use three inputs to set your initial price range.

Customer Value

Estimate the financial or operational value the product creates.

Willingness to Pay

Use:

Customer interviews
Pricing surveys
Sales calls
Competitor alternatives
Landing page experiments
Product usage data
Renewal and expansion behavior

Do not rely only on what customers say they would pay. A prospect agreeing that a price is "reasonable" is weaker evidence than a qualified buyer accepting the price and starting a contract.

Cost to Serve

Calculate the cost of serving each account, including:

Cloud infrastructure
Third-party API charges
Payment processing
Customer support
Onboarding
Sales involvement
Compliance and security
Account management

Costs should set a minimum viable price, not determine the entire price. Cost-plus pricing can prevent losses, but it may ignore the larger value created for the customer.

Illustrative Price Test

Suppose research suggests that your target customers receive between $1,000 and $3,000 of monthly value. You could test:

Starter: $99 per month
Professional: $249 per month
Business: $599 per month

These are testing points, not universal SaaS benchmarks. The right prices depend on the customer segment, competitive alternatives, product maturity and sales process.

7. Decide Between Monthly and Annual Billing

Offer monthly billing when customers need low commitment or are still evaluating the product.

Annual billing can make sense when:

The product is part of an ongoing business process
Implementation requires meaningful effort
Customers have predictable budgets
You want to improve cash flow and retention
The product creates recurring operational value

An annual plan can include a discount, extra support or another clear benefit. Do not use discounts to compensate for unclear value. A lower price may increase sign-ups while attracting customers who are less likely to activate, retain or expand.

Show the monthly equivalent of annual pricing clearly. Buyers should understand both the payment schedule and the total annual commitment.

8. Choose Between a Free Trial and Freemium

Use a Free Trial When:

The product requires little setup
Customers can reach the first useful outcome quickly
The product has meaningful serving costs
You need to qualify serious buyers
The purchase decision is relatively direct

Use Freemium When:

The free version has useful standalone value
Users can invite teammates
The product benefits from network effects
Self-service adoption is central to growth
The cost of supporting free users is low

A trial should last long enough for customers to experience the core outcome. The right length depends on implementation time, usage frequency and the customer's buying process.

9. Validate the Pricing Before Committing

Use a staged validation process.

Stage 1: Customer Research

Interview current customers, lost prospects and active users. Focus on the problem, alternatives, value and buying process. "What would you pay?" is only one question, and it is rarely enough on its own.

Stage 2: Packaging Tests

Present different combinations of:

Features
Usage limits
Support levels
Billing periods
Price points

Track which package customers choose and the objections they raise.

Stage 3: Sales Tests

Use the proposed prices in real sales conversations. Track:

Conversion rate
Sales cycle length
Discount requests
Plan selection
Win and loss reasons
Time spent explaining the pricing

Stage 4: Live Pricing Experiments

Test changes to:

Price points
Tier names
Included limits
Annual discounts
Free trial design
Upgrade prompts
Add-ons

Avoid changing price, packaging, trial length and onboarding at the same time. Otherwise, you will not know which change affected the result.

10. Track the Metrics That Reveal Pricing Problems

Monitor pricing performance by customer segment and plan.

Important metrics include:

Visitor-to-trial conversion
Trial-to-paid conversion
Average revenue per account
Revenue by plan
Monthly recurring revenue
Expansion revenue
Upgrade and downgrade rates
Gross revenue retention
Net revenue retention
Logo churn
Discount rate
Support cost per account
Customer acquisition cost
Payback period
Gross margin

Pricing may be too low when customers convert easily, rarely negotiate, reach limits quickly and expand without resistance.

Pricing or packaging may be too high when qualified prospects understand the value but cannot justify the cost, or when customers downgrade soon after purchase.

Do not read conversion rate in isolation. A cheaper plan can produce more sign-ups but less durable revenue.

Common SaaS Pricing Mistakes

Pricing From Competitors Alone

Competitor pricing provides market context, but it does not show what your product is worth. A differentiated product should not automatically copy a weaker competitor's price.

Charging for Features Customers Do Not Value

A feature may be expensive to build but have little commercial value. Put high-value capabilities in paid plans, and do not use engineering effort as the pricing logic.

Using Too Many Tiers

Too many tiers create confusion and make upgrades harder to understand. Start with a small number of plans. Add complexity only when customer segments require it.

Hiding the Price Without a Reason

"Contact sales" is appropriate for genuinely complex enterprise requirements. It creates friction when a product could provide a clear starting price.

Making Usage Impossible to Predict

Usage-based pricing needs transparent measurement, alerts, spending limits and clear overage rules. Unexpected bills damage trust and can cause customers to reduce usage.

Offering Permanent Discounts

Discounts should have a reason, such as annual prepayment, nonprofit status, startup programs or a limited launch offer. Unstructured discounts make it harder to learn the true willingness to pay.

Treating Pricing as a One-Time Decision

SaaS products change. New features, customer segments, infrastructure costs and competitors can alter the right pricing model. Review pricing when the product, market or customer mix changes.

A Simple SaaS Pricing Process

Use this sequence:

Define your ideal customer segment.
Identify the economic buyer and core business problem.
Quantify the value created by solving that problem.
Select one primary value metric.
Choose subscription, tiered, usage-based or hybrid pricing.
Create three plans around distinct customer needs.
Set prices using value, willingness to pay and cost-to-serve data.
Add monthly and annual billing.
Decide whether a trial or freemium model supports acquisition.
Test the offer with real customers.
Track conversion, retention and expansion by plan.
Adjust pricing as the product and customer base mature.

Final Recommendation

For most early-stage B2B SaaS products, start with three paid tiers, one clear value metric, monthly and annual billing, and a free trial rather than a permanent free plan.

Use per-seat pricing when value grows with team adoption. Use usage-based pricing when value and infrastructure costs grow with consumption. Use hybrid pricing when customers need predictable base costs and room to scale.

The goal is not to find one perfect price. It is to create a pricing system that makes the value easy to understand, gives customers a logical upgrade path and increases revenue as they succeed.