Value-Based Pricing Strategy vs Cost-Plus for SaaS

SaaS pricing starts with a choice between what a product costs to serve and what it is worth to customers. Because the marginal cost of serving one more customer is near zero, cost-plus pricing asks what it costs when the price should reflect what it is worth. Value-based pricing offers a stronger foundation, even when a first-time founder has only enough evidence to make a rough, testable start.

Why cost-plus pricing is structurally broken for SaaS

Serving one more SaaS customer usually costs very little. Hosting, infrastructure, and support do not grow with each user in the same way that materials and production costs grow with physical goods. That breaks the logic behind cost-plus pricing, which adds a desired margin to the cost of production. In manufacturing, that cost provides a meaningful anchor. In SaaS, the anchor may barely touch the bottom.

A product that costs almost nothing to serve per user can still be worth hundreds of dollars a month to that user. Adding a markup to delivery costs cannot show that difference because it leaves out what the customer gets from the product. It can leave high-value customers paying far below what the product is worth while charging low-value customers more than their benefit justifies. The spreadsheet balances, but the business logic does not. The gap between a cost-anchored price and a value-anchored price can be an order of magnitude, enough to separate a lifestyle project from a scalable business.

What value-based pricing actually means and how it differs from the buzzword version

Value-based pricing bases the price on what customers get from the product, including ROI, time saved, or pain relieved. It does not mean choosing a higher price and adding “premium” to the pricing page. The benefit has to be understood and measured. A notable advantage can justify premium positioning, but that requires evidence of the advantage in the customer's workflow or business results beyond the founder's enthusiasm.

Stripo's 2026 pricing research finds that only roughly two in five SaaS companies say they use value-based pricing. Even that claim is not the same as putting it into practice. Doing so requires quantified ROI models built from customer research, a billing metric that grows with customer benefit, and continued experiments informed by usage data. A request says what someone wants but may say little about what it is worth to solve the problem.

This difference between what people want and what it is worth to them also helps explain why standard willingness-to-pay surveys and conjoint analysis borrowed from consumer markets work poorly for B2B SaaS. Business value depends on usage and operational impact that buyers cannot always describe before using the product. A founder therefore needs more than an answer to “Would you pay for this?” The work is harder than the slogan suggests. Before product-market fit, the evidence may support only a provisional price, but provisional does not have to mean arbitrary.

How the choice of pricing model shapes customer behavior, retention, and expansion

The billing unit determines how a customer experiences growth. When price scales with useful consumption or measurable outcomes, small customers can pay less while larger customers pay more for benefits they actually receive. Intercom's Fin AI Agent uses outcomes as its billing unit. The unit connects the bill to a result. That makes pricing model choice part of both retention architecture and revenue arithmetic.

Per-seat pricing still has a place when each new user adds value of their own. However, the same research finds that it is in structural decline, despite remaining the most common model at roughly 58% of SaaS products. Buyers pushed hard for better terms on unused seats during the 2022–2024 correction, while AI-native tools brought new patterns of use that flat per-seat billing cannot capture. An empty seat is a particularly unconvincing line item. Counting people works less well when the benefit no longer follows the headcount.

A decline in usage offers an early warning before renewal, whereas a flat bill can mask disengagement until the cancellation email arrives. In the other direction, growing usage can produce expansion revenue without a manual upsell. The research also finds that a large majority of vendors now charge separately for AI features, most commonly through add-on fees, with a meaningful share using hybrid models. Charging per qualified result extends that shift by attaching payment more directly to what the customer gets.

Why the pricing paradox hits early-stage founders hardest

Early-stage founders face this decision when their evidence is thinnest. They may have spent hundreds of hours building features and only a fraction of that time deciding how to charge for them. Pricing becomes a launch-day checkbox, excluded from product design. Cost-plus feels safe because costs are legible and a margin is easy to calculate. Unfortunately, a tidy sum is not customer research.

That false safety often meets an understandable desire to make the product accessible. A low price feels like one less obstacle between the founder and a paying customer. Yet undercharging can attract tire-kickers who create support work without providing useful engagement signals. Paid users offer a different kind of evidence from free users because their purchase tests whether the product is worth paying for. A bargain price can blur that test if it attracts customers whose needs do not match the product's intended value.

By then, pricing decisions may already be embedded in the product. Monetization logic shapes feature access, user roles, and which usage behaviors get tracked. Treating it as an afterthought leaves those choices disconnected from how the business intends to earn revenue. The consequences compound as the customer base grows. Support volume that looks manageable at a low monthly price can become a margin problem at scale, while repricing established customers is harder than setting a sound price at the beginning.

How to identify the value metric that makes pricing defensible

The practical response begins with customer interviews before the price is set. Ask what the economic value of solving the problem would be, rather than relying on what someone says they would pay. The latter invites an understated answer that may misrepresent the benefit. Work through how the product changes the customer's workflow, then translate those changes into revenue growth, cost savings, or efficiency gains. Build a rough ROI model for each customer segment from those answers.

Next, identify the unit that grows as the customer succeeds. Seats fit when each user adds value of their own, usage volume fits when customers gain more as they use more, and outcomes fit when the product gives them a distinct result they can measure. The unit is the hard part. Brightpearl moved to pricing tied to the value of merchandise flowing through its platform, connecting the charge to a metric customers already track and care about. That is more defensible than a unit chosen because it happens to be easy to count.

Then decide how that metric should shape the offer. A price can reflect value without every product having to use fully consumption-based billing. Tiered plans can keep core processes in lower tiers and put the features with the largest benefits that can be measured in higher tiers, so the offer grows with the customer. For AI features, the research finds that 53% of companies monetizing AI defaulted to subscription-based AI tiers as a faster workaround while pursuing a real value metric. That is a reasonable bridge, as long as it stays a bridge and does not quietly become the destination.

Once customers are paying, use their actual usage to test the proposed connection between benefit and billing. Refine the ROI model and experiment with pricing as the evidence improves. The first metric need not be permanent. It does need to show a link that makes sense between how well the customer does and what the customer pays.

The legitimate objection — when value-based pricing is premature

Before product-market fit, there may be no value metric that can be trusted yet. Customers have not used the product enough to reveal its benefit, and the founder cannot measure what has not happened. Demanding a fully optimized pricing model at that point turns a useful principle into a launch blocker. Simple tiers with a reasonable price are usually sufficient. The immediate purpose is to get paying customers and learn what they value.

An intentional starting price rests on a hypothesis about customer value, even if that hypothesis is rough. Charging from the beginning creates evidence with which to revise it. The research finds that roughly 24% of SaaS companies use competitor-benchmarked pricing, which can provide a reasonable initial anchor in crowded markets with established buyer expectations. But copying competitors' numbers also imports their mistakes, so benchmarking is a starting point to move beyond rather than a substitute for understanding the customer.

How pricing connects directly to fundraising thresholds and investor perception

Pricing also affects whether a company can reach the ARR benchmarks investors use. ARR and growth rate are central to how investors assess a pre-Series A SaaS business, and a cost-anchored price can leave a product with strong engagement but insufficient revenue. A price that reflects customer value can change that position with the same customer count, without proportional cost growth.

Smaller ARR growing quickly with strong net revenue retention can be more attractive than larger ARR growing slowly with churn, which makes built-in expansion economically important. A founder's explanation of the price adds another signal, because connecting it to a measurable customer outcome demonstrates an understanding of the value proposition. Most pre-seed and seed fundraising happens on SAFEs without a formal valuation, while the implied valuation at conversion depends on the ARR trajectory then, so early pricing decisions echo into the cap table at the first priced round.

Putting it together — a practical starting framework for first-time SaaS founders

For a first-time founder, the sequence starts before the pricing page. Interview potential customers about the economic value of the problem, and turn those conversations into a rough ROI model for each segment. Use that model to choose a provisional unit of benefit that tracks customer success. Then set the price at a fraction of the value that can be explained, rather than at whatever markup feels least frightening. Charge from day one, and use the first paying cohort to inform the next iteration.

This sequence also belongs in the co-founder conversation. A technical co-founder using cost-plus logic and a business co-founder pursuing value-based pricing can deadlock product and go-to-market decisions before launch. Agreement on the number is not enough. When both founders agree on why that number makes sense, they can use that reasoning to decide on features, access, and what to measure.

Once the first price is set, establish the expectation that it will be reviewed as the evidence changes. The research finds that 73% of SaaS providers raised prices between August 2022 and August 2023, and that the cadence has continued. Periodic updates are easier to introduce as part of the customer relationship from the start than as a surprise later. Structured work with peers and experienced practitioners can also shorten the learning curve compared with solving every pricing question alone. The aim is not a perfect price at launch, but a price whose logic can survive contact with paying customers.