How to price a SaaS product without overthinking it

Pricing is the part of building software that founders overthink the most and get wrong the most. They spend months on the product, then decide the price in an afternoon by looking at their own costs, picking a number that feels safe, and never changing it again. The number is almost always too low. And because they treat it as permanent, that too-low number quietly limits the whole business for years. The good news is that pricing is simpler than it looks once you fix the starting point. You are not trying to find the one perfect number. You are trying to price on the right thing and leave yourself room to adjust.

Here is how we think about it.

Price on value, not on your cost

The most common mistake is pricing from your own costs. A founder adds up what it cost to build and run the product, adds a margin, and calls that the price. It feels responsible. It is the wrong question. What it cost you to build a feature has nothing to do with what that feature is worth to the person buying it.

Look at it from the customer's side. A customer does not care that a feature took you a week or a year. They care about the outcome it gives them: the hours it saves, the money it makes, the mistakes it prevents. A tool that took you two weeks to build might save a customer four hours a week for their whole team, which is worth thousands of dollars a month to them. If you price that from your build cost, you charge a tiny fraction of what it is worth, and you have quietly told the customer that your product is cheap. Price on the value instead. Ask what a good outcome is worth to the customer, then set a price that captures a fair share of it. A fair share still leaves the customer clearly better off, which is why value pricing is not greedy. It is just aligned with what you actually deliver.

This does mean you have to understand your customer's business well enough to know what a good outcome is worth to them. That is real work, and it is the same work that tells you what to build in the first place. We wrote about that connection in knowing what to build: once you understand the outcome the customer is paying for, both the product and the price get much clearer.

Start higher than feels comfortable

Once you are pricing on value, the next fix is to set a high price. Most founders set prices low. They are afraid of losing buyers, so they pick a number that feels safe to them, which is usually a number that feels cheap to the buyer. Then they find out, sometimes years later, that customers would have happily paid two or three times as much.

Starting higher gives you options a low price never does. It gives you room to offer a discount to close a deal, which feels good to the buyer and still leaves you above where you would have set the price anyway. It protects your margin, so you can afford good support and steady improvement instead of running the whole company on small profits. And the price itself tells buyers something. A higher price tells buyers the product is serious, the same way a very low price makes people wonder what is wrong with it. There is also a practical reason to start high: it is easy to lower a price and painful to raise one. Lowering a price is an easy email to send. Raising a price on customers who signed up cheap is a difficult conversation you will avoid having, which means the low number tends to stay long after it stops being useful.

You do not need to guess blindly. Talk to buyers, watch how they react, and pay attention to who objects. Which brings up a useful signal.

Let price resistance tell you something

Here is a test that removes a lot of the worry. If nobody ever objects to your price, it is probably too low.

Founders treat any price objection as a bad sign. It is usually the opposite. If every prospect signs up instantly, never negotiates, and you win nearly every deal, you have priced below the highest price customers will accept. Some resistance is healthy. It means you are near the limit of what the product is worth to people, which is exactly where you want to be. The goal is not zero objections. The goal is to win the customers who value the outcome while occasionally losing the ones who were only ever going to buy on price, because those are often the customers who cost the most to serve and leave the fastest anyway.

Price decides which customers you get, and that is worth saying plainly. A low price attracts buyers who are price-sensitive, ask for a lot of support, and leave the moment something cheaper appears. A higher price attracts buyers who care about the result and stay. The number you pick does not just set your revenue. It shapes the kind of business you run and the kind of customers you spend your days with.

Keep the tiers simple

For how you structure the price, simple works best. Three tiers is usually enough. A cheaper entry option, a middle one that most people should pick, and a higher one for larger customers. Make the middle tier the obvious recommended choice and most buyers will take it, which is the whole point of having three.

The reason to keep it simple is that every extra option adds effort for the buyer. When a buyer faces seven tiers with overlapping features, they stop deciding and start comparing, which slows the sale and often stops it entirely. A clear, small set of choices lets someone look at it, see where they fit, and move on. The same logic applies to what you charge on. Pick the thing that grows with the value the customer gets: per user if value scales with the number of people using it, per unit of usage if value scales with how much they use it. That way, as a customer gets more value, your price rises with it, and the price keeps feeling fair as they grow. A pricing model where you charge more while the customer feels they are getting less is a model that makes customers leave, no matter how clever it looks on the page.

Pricing is something you keep changing

The last mistake is treating pricing as a one-time decision. It is not. It is something you keep adjusting as you learn. Almost every successful software company has changed its pricing several times: raised it as the product got more valuable, restructured the tiers as they learned what customers cared about, changed what they charged on as usage patterns became clear. The founders who leave a number in place for years, untouched, are almost always the ones who underpriced at the start and never corrected it.

So set your first price knowing it is a first price. Price it on value, start it higher than feels comfortable, keep the tiers simple, and then watch what happens. Where does price come up as an objection, and where does it not. Which customers stay and which leave. Which plan people actually choose. Every one of those is information, and every so often you use it to adjust. This is the same discipline that makes a product improve after launch instead of staying the same, which we wrote about in how to launch a product with minimal resources: release a first version, learn from real behavior, and keep adjusting on purpose.

Pricing feels risky because it is visible and it touches money directly. But the way to get it right is not to worry for weeks about the perfect number before launch. It is to price on the right thing, set it high enough to have room, keep it simple, and treat the number as something you revisit deliberately rather than a decision you make once and hope was correct.

One assumption underneath a lot of pricing advice is worth re-examining. Pricing was often based, quietly, on what the software cost to build, especially at the low end where founders reasoned from their own effort.

That basis has weakened. Build cost is a much smaller share of what a software business spends, which makes cost-plus reasoning even less defensible than it already was. Price on the value delivered and on what the alternative costs your customer. That was always the right advice. It is now the only advice that still has a sound basis.