How to Create a Pricing Strategy for a New SaaS Product: Framework and Examples

How to create a pricing strategy for a new SaaS product starts with one decision that everything else flows from: your value metric — the unit that scales with the value customers receive, and that your pricing should track as customers expand their usage.

Most SaaS pricing mistakes trace back to choosing the wrong value metric. If your value metric is seats but your customers receive value based on outcomes, you'll have a pricing model that misaligns incentives: customers try to minimize the number of seats while maximizing usage, and you can't grow revenue without a sales motion.

This guide walks you through the value metric decision, the pricing model options, and the tier design choices that make or break SaaS monetization.

Step 1: Choose Your Value Metric

A value metric is the dimension of your product that customers pay for. It should grow naturally as customers get more value from the product.

Common SaaS value metrics:

| Value Metric | Best for | Examples | |-------------|----------|---------| | Per seat / user | Collaboration tools where each user adds unique value | Slack, Notion, Figma | | Per usage unit | Tools where value scales with consumption | API calls, emails sent, AI tokens | | Per outcome | Tools where value is tied to a measurable result | Revenue generated, leads converted | | Flat rate | Simple tools with binary value (you use it or you don't) | Single-function utilities | | Per company / account | Enterprise tools where org size drives value but user count doesn't | Compliance, security tools |

H3: How to Choose the Right Value Metric

According to Lenny Rachitsky's writing on SaaS pricing, the value metric question has one correct answer for most products: what does the customer's business look like when your product is working well? If the answer is "more revenue," consider an outcome-based metric. If the answer is "more people collaborating effectively," seats may be right. If the answer is "more API calls completing successfully," usage is right.

Three tests for your value metric:

Natural expansion: Does the metric grow naturally as the customer succeeds with your product? (Without a deliberate sales motion?)
Customer alignment: Does the customer feel the metric is fair? Does a customer who gets 5x the value pay 5x more?
Predictability: Can customers predict their bill? (Usage metrics that spike unpredictably create pricing anxiety.)

Step 2: Choose Your Pricing Model

Once you have your value metric, choose the pricing model that packages it most effectively for your target customer.

H3: The Four SaaS Pricing Models

Model 1: Flat Rate (Single Tier) One price, all features, for all customers.

Pros: Simple, no tier decision fatigue
Cons: No segmentation, leaves revenue on the table from high-value customers
Best for: Simple products with a homogeneous customer base

Model 2: Tiered Pricing 2–4 price points with different feature sets or limits.

Pros: Segments customers, creates upgrade path
Cons: Tier design is hard; wrong cutoffs create churn or missed revenue
Best for: Products serving 2–3 distinct customer segments with different needs

Model 3: Usage-Based Pricing Pay for what you use. No seat minimums.

Pros: Removes adoption barrier; aligns revenue with customer value
Cons: Revenue is unpredictable; high-volume customers may feel penalized
Best for: Infrastructure, APIs, AI tools where consumption varies widely

Model 4: Hybrid (Tiered + Usage) Base fee for the platform + usage fees for consumption.

Pros: Predictable base revenue + upside from high-value customers
Cons: Complex to communicate; requires careful CAP design
Best for: Products where some features are high-value regardless of usage and others scale

According to Shreyas Doshi on Lenny's Podcast, the most underused pricing model for B2B SaaS is outcome-based pricing — where customers pay as a percentage of the value they generate. "Every time a vendor pitches me on outcome-based pricing I'm immediately more interested. It aligns incentives perfectly. The problem is that measuring outcomes is hard, which is why most vendors retreat to seats."

Step 3: Design Your Tiers

If you choose tiered pricing, tier design is the most consequential product decision you'll make for a year. The typical mistakes:

Mistake 1: Too many tiers — Four or more tiers create decision paralysis. Use three: Free/Starter, Professional, and Enterprise.

Mistake 2: Wrong feature gating — Gating features that are needed for core adoption in the paid tier prevents activation. Gate features that are valuable after adoption, not before.

Mistake 3: Price anchoring on cost, not value — Your costs are irrelevant to what customers will pay. Anchor prices on the value delivered, which you measure through customer interviews: "How much would you pay for X monthly if it saved you Y hours per week?"

H3: The Good/Better/Best Tier Structure

| Tier | Target Segment | Value Prop | Upgrade Trigger | |------|---------------|-----------|----------------| | Free/Starter | Individual users, early exploration | Core job, basic features | Hitting limits; needing team features | | Professional | Growing teams, established use case | Full features, reasonable limits | Needing enterprise governance | | Enterprise | Large organizations, complex compliance | Custom, SSO, SLA, admin controls | Annual contract; dedicated support |

The upgrade triggers tell you what features to gate at each tier — they should be features that the next tier's customers genuinely need, not arbitrary restrictions.

Step 4: Test and Iterate

Pricing is a hypothesis, not a decision. Test it:

According to Gibson Biddle on Lenny's Podcast, every major pricing change at Netflix was preceded by controlled testing in specific markets. "We never changed pricing globally without first understanding the price sensitivity curve in smaller markets. The data always surprised us — customers valued things differently than we assumed."

Pricing test methods:

Van Westendorp Price Sensitivity Meter: Four-question survey to find acceptable price range
Conjoint analysis: Customers choose between feature/price bundles to reveal true preferences
A/B pricing test: Different prices to different segments (requires careful ethical and legal consideration)
Win/loss analysis: Why did deals close or fail? Price objection frequency reveals ceiling

FAQ

Q: How do you create a pricing strategy for a new SaaS product? A: Start with your value metric (the dimension that scales with customer value), choose a pricing model that packages it effectively, design 2-3 tiers with upgrade triggers that match your customer segments, and test pricing as a hypothesis rather than declaring it as a fixed decision.

Q: What is a value metric in SaaS pricing? A: The unit customers pay for that grows naturally as they get more value from the product — per seat, per usage unit, per outcome, or per account. The right value metric aligns your revenue expansion with customer success.

Q: What are the best pricing models for a new SaaS product? A: Flat rate for simple single-segment products, tiered pricing for products serving 2-3 distinct segments, usage-based for infrastructure and APIs, and hybrid (base fee plus usage) for products where some value is baseline and some scales with consumption.

Q: How many pricing tiers should a SaaS product have? A: Three tiers is the default: Free or Starter, Professional, and Enterprise. More than four tiers creates decision paralysis. The tiers should map to distinct customer segments with different needs, not artificial feature restrictions.

Q: How do you test SaaS pricing? A: Use the Van Westendorp Price Sensitivity Meter for acceptable range, conjoint analysis for feature-price tradeoff preferences, win/loss analysis for price objection frequency, and controlled market tests before global price changes.