The Deferral Problem

Ask most early-stage SaaS founders how they arrived at their pricing and you will hear one of two answers. Either they looked at what competitors charge and set a similar number, or they picked something that felt reasonable and have not revisited it since.

Both approaches are understandable. Pricing feels risky to get wrong, and in the early days there are always more urgent things to focus on. But deferring pricing decisions does not make them go away. It means they get made by default — by the first customer who pushed back on price, by the competitor whose positioning you unconsciously anchored to, by the instinct that lower prices mean more customers.

None of these defaults are reliable. And the longer they persist, the harder they are to change.

Cost-Plus Is Not a Strategy

The most common pricing mistake in SaaS is cost-plus pricing: calculating what it costs to deliver the product and adding a margin. This approach is intuitive and feels financially responsible. It is also almost entirely disconnected from the value the product creates for customers.

SaaS products do not create value in proportion to their cost to deliver. A workflow automation that saves a customer ten hours a week has the same delivery cost whether the customer is a solo operator or a team of fifty. But the value it creates — and therefore the price it can command — is very different in each case.

Pricing based on cost tells you the floor. It tells you nothing about the ceiling, and it tells you nothing about where in the range between floor and ceiling you should actually be.

Value-Based Pricing: The Principle and the Practice

Value-based pricing starts from a different question: not "what does this cost us to deliver?" but "what is this worth to the customer?"

Answering that question requires research. It means talking to customers — not to ask them what they would pay, which rarely produces useful answers, but to understand the problem they were solving before they found your product, what it was costing them (in time, money, or risk), and what has changed since they started using it.

From those conversations, patterns emerge. Certain customer segments get significantly more value than others. Certain use cases are worth more than the price you are currently charging. Certain features that you thought were differentiators turn out to be table stakes, while features you underinvested in are the ones customers actually care about.

This information does not just inform pricing. It informs product strategy, positioning, and where to focus development effort.

Packaging and Tiers: The Architecture of Choice

Most SaaS products eventually move to a tiered pricing model. Done well, tiers allow you to serve different customer segments at different price points, capture more value from customers who get more value, and create a natural upgrade path as customers grow.

Done badly, tiers create confusion, force customers into packages that do not fit their needs, and generate support overhead as customers try to understand what they are and are not getting.

The most common packaging mistake is building tiers around features rather than around customer outcomes. A tier that includes "up to 10 users, 5 integrations, and priority support" is describing product attributes. A tier that is designed for "growing teams who need to coordinate across departments" is describing a customer situation. The second approach is harder to build but significantly easier to sell.

The other common mistake is creating too many tiers. Three is usually the right number. More than that and customers spend their decision-making energy comparing options rather than evaluating whether the product is right for them.

The Freemium Question

Freemium is one of the most debated topics in SaaS pricing, and one of the most frequently misapplied. The appeal is obvious: a free tier lowers the barrier to entry, drives acquisition, and creates a pool of users who might eventually convert to paid.

The problem is that freemium only works when the free tier creates genuine value for users while leaving meaningful value on the paid side of the line. If the free tier is too limited to be useful, it does not drive acquisition. If it is too generous, it undermines conversion.

Freemium also has a hidden cost that is easy to underestimate: the operational overhead of supporting a large base of non-paying users. Customer success, infrastructure, and support all scale with user count, not revenue. For early-stage products with limited resources, that overhead can be significant.

The honest question to ask before introducing a free tier is not "would freemium help us grow?" but "do we have the resources to support it, and do we have a clear model for how free users become paying ones?"

Pricing as an Ongoing Practice

The most important shift in how founders think about pricing is from treating it as a one-time decision to treating it as an ongoing practice.

Pricing should be reviewed regularly — at minimum annually, and whenever there is a significant change in the product, the competitive landscape, or the customer base. Each review should include conversations with customers, analysis of conversion and churn data, and a deliberate assessment of whether the current pricing is capturing the value the product creates.

This does not mean changing prices constantly. It means staying close enough to the market and to customers that when a change is warranted, you can make it with confidence rather than anxiety.

Founders who treat pricing as a practice rather than a decision tend to end up with pricing that reflects the real value of their product. That is not just good for revenue. It is good for the clarity of the product itself.