How to Set Value-Based Pricing for SaaS in 5 Steps

Two customers use the same support agent. One gets 4,000 conversations resolved each month while the other gets 40, and both pay the same flat fee.

Value-based pricing ties the price to the value each customer receives.

You will get the steps for setting value-based pricing for SaaS, examples from real companies, the trade-offs, and a way to pick a value metric you can measure once usage and AI enter the picture.

What is value-based pricing?

Value-based pricing sets prices based on how much customers believe a product is worth, considering the problems it solves, the results it delivers, and what buyers are willing to pay. The goal is to align pricing with perceived customer value while accounting for the costs of delivering it.

Cost-plus pricing adds a margin on top of your costs, and competitor-based pricing matches the market rate. Value-based pricing, meanwhile, asks, “What is the product worth to the buyer?”

SaaS companies express value-based pricing as tiered plans, with each tier built around the value a different kind of customer receives. A solo developer and a 500-person engineering org value different things, so they land on different prices.

The value metric is the unit a customer pays on. A collaboration tool can charge per active user, a CRM per stored contact, and an AI product per token or per completed agent action.

When you pick the metric well, the bill grows as the customer gets more value. Customers see the bill as fair, and your margin holds as accounts grow.

How to set value-based pricing for SaaS (Step by step)

Value-based pricing starts with customer research and produces decisions you revisit as the product changes.

Step 1: Segment your customers

Group customers who get value the same way. Segment by company size, use case, or usage pattern, since a 10-person startup and a mid-market company value your product for different reasons.

Each segment becomes a column in your pricing. Skipping this step produces one tier that fits nobody since it’s too expensive for small customers and cheap for large ones.

Step 2: Choose your value metric

Pick the unit each segment pays more for as that segment grows. The value metric decision carries the most weight in the process, so a full section below covers it.

Run one quick test: Does the metric rise when customer success rises? Seats, contacts, messages sent, and outcomes delivered can all pass.

Metrics that customers can game or consolidate break the link between price and value.

Step 3: Measure willingness to pay

Ask each segment what it will pay through customer interviews and surveys, and confirm the answers with small live tests.

Pricing researchers use the Van Westendorp Price Sensitivity Meter, which asks 4 questions to find the band where a price feels too cheap to trust or too expensive to buy. Run it for each segment, since segments disagree on willingness to pay.

A pilot or an A/B rollout to new signups gives stronger evidence than any survey, because a buyer’s answer changes once the money is real.

Step 4: Build your pricing tiers

Package features and usage into tiers that match each segment’s value and budget. Good, better, best is the common shape, with add-ons for needs specific to some customers.

Anchor each tier to the value metric from Step 2 so each upgrade feels earned. Stigg’s guide to pricing and packaging covers the mechanics of bundling features across tiers.

Step 5: Test and adjust

Roll the new pricing out to new customers and watch how each cohort behaves. Track conversion, expansion, and churn by cohort to separate a pricing problem from a product problem.

Value perception drifts as the product and market change. Plan to revisit pricing once a year and each time a release changes what the product is worth.

How to choose your value metric

The right value metric reflects what customers get from your product, so pricing is easy to understand, and it supports revenue growth as usage increases. A strong value metric passes 5 tests:

1. Value alignment: the metric rises as customer outcomes rise. A customer who gets more value at the same price is a sign of a broken metric.
2. Simplicity: a buyer explains it in 1 sentence. “Per seat” passes. “Per weighted blended compute unit” produces a support ticket.
3. Measurability: you track it to the unit in real time, with no monthly manual cleanup.
4. Predictability: customers estimate the bill before it arrives. A surprise invoice can lose a customer who was happy with the price.
5. Expansion potential: the metric grows as the account grows, so spend expands with no renegotiation.

Value drivers include money saved, revenue gained, time saved, and risk reduced. Choose a metric that reflects what customers value and are willing to pay for, then track conversion, usage, and expansion by cohort.

Value-based pricing examples in SaaS

Each company below charges on a value metric that grows with the customer.

Slack, HubSpot, Twilio, Intercom, and Anthropic publish their pricing units on their official pricing pages. Prices are subject to change without notice. Always visit the official company websites for the most up-to-date pricing information.

These companies show how different pricing metrics can reflect customer value. Slack charges for active users, Twilio measures message segments, Intercom ties charges to successful AI outcomes, and Anthropic bills for token consumption.

Each metric captures a different aspect of usage or value, although consumption-based pricing can also reflect the underlying cost of delivering the service.

Intercom Fin uses outcome-based pricing, which means charging when the AI agent delivers a defined result, such as resolving a conversation or completing a qualifying handoff.

The engineering challenge here is tracking successful outcomes consistently across retries, partial completions, and customer disputes.

Advantages and disadvantages of value-based pricing

Value-based pricing fits some companies better than others. Here are the trade-offs:

Advantages

• It captures more willingness to pay: Your highest-value accounts pay in line with the value they receive.
• It can feel fairer: Customers see a clearer connection between what they pay and the value they receive, especially when the pricing metric is predictable and easy to understand.
• It differentiates on value: You compete on the outcome you deliver and skip the race to the cheapest number.
• It sharpens the company: Pricing on value requires understanding value, so product and customer research improve.

Disadvantages

• Setting it is slow and research-heavy: Interviews, surveys, and pilots take weeks, and you repeat them as perception changes.
• Undifferentiated products struggle: If customers see you as interchangeable with 3 competitors, little perceived value exists to price against.
• Early startups struggle: With no customer data and no brand, willingness to pay is a guess.
• Consumption metrics need reliable tracking: Inaccurate usage records can create billing errors, while AI workloads may need request-time limits to prevent unexpected costs.

Value-based vs cost-plus vs competitor-based pricing

Value-based pricing is one of three common approaches to setting prices, alongside cost-plus and competitor-based pricing.

Each uses different information to determine what customers pay, and the right approach depends on your costs, market position, and how clearly customers recognize your product's value.

Cost-plus pricing starts with the cost of delivering the product and adds a target margin. It can help AI companies account for inference, compute, and infrastructure expenses, although production costs alone cannot tell you how much customers are willing to pay for the result.

Competitor-based pricing works as a sanity check. As a whole strategy, it hands pricing control to the competitor with the deepest discounts.

Value-based pricing wins when you understand your customers and offer something they cannot get for the same value elsewhere. Cost and competitor data inform the edges.

How to make value-based pricing work in AI products

Enforcing value-based AI pricing in production requires accurate usage metering, current commercial entitlements, and request-time controls that keep consumption aligned with what each customer has purchased.

When your value metric involves tokens, model calls, AI credits, or agent actions, every request can create an infrastructure cost. An image generation job that fails at 90% still consumes GPU time, and the cost remains even if the customer never receives a finished result.

The risk grows when several users or AI agents draw from the same credit pool. Two agents can request the remaining balance simultaneously, while plan upgrades, renewals, and promotional grants may change the available allowance during an active session.

Here’s what each one does:

• Accurate usage metering: Every request is counted once, against the right customer, feature, or agent, even when it retries
• Commercial entitlements: Resolve access and consumption limits from active plans, parent plans, add-ons, trials, and account-specific overrides, including changes that take effect mid-cycle.
• Enforcement before the work runs: Each request is checked against the remaining allowance before the expensive job starts, and is stopped or flagged as overage at the limit.

Entitlements define the commercial access and consumption allowances customers receive, while RBAC determines which users have permission to perform specific actions.

The two systems need to work together. A team member may have permission to launch an AI agent, but the account still needs enough credits and an active entitlement to cover the request.

Keeping these decisions consistent under concurrent traffic is what protects the pricing model in production. Engineering teams can update allowances and packaging without rewriting access rules across services, while customers receive predictable limits that reflect their current agreements.

Enforce value-based pricing with Stigg

An AI agent doesn't wait for your billing system to catch up. Once a request starts, tokens get consumed, tools execute, and compute costs accumulate, so the decision to approve that work is just as important as recording its usage.

Stigg is the usage runtime for AI products. It puts entitlements, credits, and spend controls directly in the request path, giving your application current commercial rules before the next expensive operation begins. Your existing billing system continues handling invoices and payments.

Here's what Stigg adds:

• Ledger-backed credits: Atomic debits, grants, refunds, expiry, promotional balances, and configurable burn order.
• Real-time metering: Attribute usage to customers, features, agents, and workloads.
• Entitlement enforcement: Resolve allowances across plans, add-ons, trials, and account-specific overrides.
• Low-latency checks: Stigg Sidecar answers checks from an in-memory cache, with p99 under 10ms. On a cache miss, it fetches from the Edge API in around 100ms. Node.js applications skip the Sidecar and run the same checks in-process through the SDK.
• BYOC metering: Run metering inside your own VPC on AWS, GCP, or Azure, with 1M+ events/sec ingestion capacity.
• AI-native tooling: MCP server, CLI, and agent skills for developer workflows.

Stigg is one platform, so you can start with the capability you need most, whether that’s metering, credits, or entitlements, through a single SDK integration. Add more capabilities as your AI pricing requirements grow.

Curious how Stigg makes an allow-or-block decision before another AI workload runs? Explore the Stigg documentation to see how credits, entitlements, and request-time enforcement work in production.

FAQs

1. What is value-based pricing in SaaS?

Value-based pricing in SaaS sets prices according to the value customers perceive in a product, including time saved, revenue gained, or problems solved. Companies use customer research and willingness-to-pay data to set prices while also considering delivery costs and competitor pricing.

It can appear through tiered plans, subscriptions, or usage-based pricing tied to metrics such as seats, contacts, or completed outcomes.

2. What are examples of value-based pricing?

Examples of value-based pricing include Slack (per active user), HubSpot (per marketing contact), Twilio SMS (per SMS segment), Intercom Fin (per successful outcome), and Anthropic's Claude API (per token).

Each uses a different pricing metric, although how closely those units reflect customer value varies by product and use case.

3. How is value-based pricing different from cost-plus pricing?

Value-based pricing uses customer-perceived benefits and willingness to pay to set prices, while cost-plus pricing calculates delivery costs and adds a target margin. Companies can use both approaches to understand what buyers will pay and whether the resulting price supports healthy margins.

4. What are the advantages and disadvantages of value-based pricing?

The advantages of value-based pricing are higher captured willingness to pay, fairer pricing, and stronger differentiation.

The disadvantages are the research time it takes to set and its weakness for undifferentiated products and early startups with no customer data.

5. How do you choose a value metric for value-based pricing?

Choose a value metric that rises with customer success, stays simple to explain, can be measured in real time, lets customers predict the bill, and grows with the account.

Map the metric to the value driver customers name when they justify the cost, such as time saved or revenue gained.