How to Price Your SaaS (Without Underselling)

You can ship. That part you have handled. The product works, the signup flow works, the Stripe integration works. Then you get to the pricing page and you freeze. You type $9. You delete it. You type $19, feel a flash of guilt, and go back to $9. That flinch is costing you more than any bug in your codebase. The number on that page decides how much every single customer is worth, and you are about to set it based on nothing but nerves.

This guide is about picking that number on purpose. Not with a magic formula, because there isn't one, but with a way of thinking that keeps you from the mistake almost every technical founder makes: charging far too little and then wondering why the business feels so hard.

Where does the money actually come from?#

SaaS revenue is not one sale. It is a monthly amount, repeated, minus the people who leave. Understanding that chain tells you why the price matters so much more than it looks like it should.

Right person sees the product
        |
        v
They believe it is worth more than the price
        |
        v
They subscribe (monthly recurring revenue begins)
        |
        v
They keep getting value each month
        |
        v
They stay (low churn) --> revenue compounds
        |                        |
        v                        v
   Higher price          More customers
   per customer          who stay longer
        \                       /
         \                     /
          v                   v
     Monthly Recurring Revenue (MRR)

Two numbers set your MRR: how much each customer pays, and how many you keep. Price is the first lever and the one you control instantly. You can change it this afternoon, while everything else (more traffic, more features, lower churn) takes weeks or months to move. If the mechanics of recurring software revenue are still fuzzy, how software companies make money walks through the engine, and where does online money come from zooms out to the basics. The point for pricing: because the price repeats every month, a change to it repeats every month too.

The concrete move: before you set a number, write down what a customer gains or avoids by using your product (lost hours, a tool they cancel, a mistake they stop making). That is what you are actually pricing.

Value-based vs cost-plus thinking#

There are two ways people arrive at a price, and only one of them makes sense for software.

Cost-plus thinking asks: what did this cost me, and what markup do I add? That works for physical goods where each unit has a real cost. It is nonsense for SaaS, where your cost to serve one more customer is close to nothing. Price on cost and you are pricing on your server bill, which has no relationship to what the product is worth. This is the trap technical founders fall into: you know exactly what it cost to build, so that number feels real while the value number feels made up.

Value-based thinking asks a different question: what is this worth to the person using it? If your tool saves a freelancer four hours a month, and that freelancer bills $60 an hour, the tool is in the neighborhood of $240 of value every month (a hypothetical, to show the shape of it). Charging $9 for that is not generous. It is a signal that you do not believe your own product, and buyers read that signal.

You do not capture all the value, and should not try to. Price so the customer keeps most of the upside and you take a slice. If the value is $240 a month, something like $29 to $49 is a bargain for them and a real business for you. The gap between $9 and $49 there is the difference between a hobby and something you can live on.

The concrete move: stop deriving the price from your costs. Derive it from a specific number the customer cares about, then charge a fraction of that.

Tiers and anchoring#

A single price is a yes-or-no decision. Tiers turn it into a which-one decision, which is a much easier one to win.

Three tiers is the standard for a reason. The high tier anchors, making the middle tier look sensible by comparison. The middle tier is where you actually want most people to land, so design it to be the obvious choice. The low tier catches the price-sensitive buyer who would otherwise walk.

Say your tiers are $19, $49, and $99 (all hypothetical). Without the $99 tier, $49 looks expensive. With it, $49 looks like the reasonable middle. That is anchoring, and it is not a trick. It is giving people a frame to make a decision they had to make anyway, and the $99 tier does its job even if almost nobody buys it.

Tier on a value metric, not on random feature bundles. The best tiers scale with how much the customer gets out of the product: number of projects, users on the team, volume processed, however your product delivers value. That way a customer who gets more naturally pays more, and the upgrade feels fair. If your tiers are just an arbitrary checklist of features gated behind higher prices, buyers feel nickel-and-dimed and pick the cheapest option out of spite.

The concrete move: build three tiers, put the plan you actually want most people to buy in the middle, and make each tier step up along one thing the customer can feel getting bigger.

Monthly vs annual#

Offer both, and gently push annual. Here is why it matters for a solo founder specifically.

Monthly billing is the low-commitment door. It lowers the barrier to that first yes, and most people start there. That is fine. But monthly customers can leave any month, which gives churn a lot of chances to nibble at you.

Annual billing does two useful things. It gives you cash up front, which for a bootstrapped solo operation can be the difference between affording ads or a contractor and not. And it locks in the customer for a year, which flattens your churn because they are not making a stay-or-go decision every 30 days. The standard nudge is to discount annual by roughly two months, so the annual price is about ten times the monthly. The customer sees a saving, you get the cash and the commitment.

Do not force annual only. Making people commit to a year before they have felt the value is a good way to kill your conversion rate.

The concrete move: show monthly by default, show the annual price beside it with the saving spelled out, and let people self-select.

A clearly hypothetical worked example#

Here is the math that changes how you think. Every number below is invented to illustrate the mechanism. It is not earnings, not typical, and not a promise.

Imagine the exact same product, priced three ways, and you want to reach $5,000 in monthly recurring revenue.

Price      Customers needed for $5,000 MRR
-------    -------------------------------
 $9         556 paying customers
$29         173 paying customers
$79          64 paying customers

Look at what the price actually buys you. At $9, you need to find, convince, onboard, and retain 556 people. At $79, you need 64. Those are not the same business. Finding 64 customers who each get real value is something a solo founder can plausibly do through direct outreach, a small audience, or a niche community. Finding 556 usually needs a marketing machine you do not have.

Now add churn, which underpricing makes worse. Suppose 5 percent of customers leave every month (again, hypothetical). At $9 with 556 customers, you lose about 28 a month and must replace all 28 just to stand still. At $79 with 64 customers, you lose about 3. Replacing 3 is a Tuesday. Replacing 28 every month is a treadmill. And the low price often has higher churn, not lower, because the cheapest plan attracts the least committed buyers. So the $9 product faces both punishments: more customers to find and faster losses.

This is why raising the price is such a powerful lever. Move that product from $9 to $29 and you need roughly a third as many customers for the same revenue, and you likely keep them better. You did not write a line of code. You changed a number. For what it actually takes to stack revenue up over time, see what gets a SaaS to 10k MRR; the pattern there almost always runs through price, not just volume.

The concrete move: run this table for your own product. Pick a revenue goal, divide by three candidate prices, and stare at the customer counts until the cheap option stops looking safe.

What you need and what it costs#

You do not need much to price well. This is thinking, not tooling.

Required: a clear statement of who the product is for and what it is worth to them, a payment processor like Stripe or a merchant of record such as Paddle or Lemon Squeezy, and a pricing page that shows your tiers plainly. That is genuinely it. Stripe takes a small percentage per transaction; a merchant of record takes a bit more but handles sales tax and VAT for you, which is worth real money once you sell internationally.

Optional and useful: analytics to see which tier people pick and where they drop off. Nice to have, not now: usage-based metering, custom enterprise quotes, a billing portal with every bell and whistle. Solo founders love building billing infrastructure because it is a satisfying coding problem. Resist it. A hardcoded three-tier page converts just as well as an elaborate one.

The concrete move: use the simplest checkout that works today and spend your energy on the number and the positioning, not the plumbing.

How long it takes#

Setting the initial price takes an afternoon. Learning whether it is right takes longer, because pricing is a thing you tune, not a thing you finish.

You will not get it perfect on day one, so do not try. Ship a price, watch how people respond, and adjust. If nobody buys, the problem is usually not that the price is too high; it is that the value is not clear or you are not in front of the right people. If everybody buys instantly without blinking, your price is almost certainly too low. A little friction on the buy decision is normal and healthy. Give any price a few weeks and a reasonable number of visitors before you judge it. One quiet weekend is not data.

The concrete move: set a price today, put it in front of real prospective buyers, and give it a genuine run before you touch it again.

What beginners get wrong#

The mistakes are consistent, which is good news, because you can just avoid them.

Pricing on cost instead of value. The big one, covered above. Your server bill is not your customer's problem.

Confusing cheap with easy to sell. A low price does not remove sales objections; it often adds one, because the buyer wonders why it is so cheap. Cheap products still have to be sold, and to more people.

Never raising the price for fear existing customers revolt. You can raise prices for new customers only and grandfather everyone who already signed up. Almost nobody does this and almost everybody could.

Copying a competitor's price without copying their business. Their costs, audience, funding, and goals are not yours. Their $10 might be subsidized by something you do not have.

Treating price as separate from positioning. What you charge is part of what you are saying about the product. If buyers do not understand what it is for, no price feels right, and positioning so people get your product is the fix before you touch the number.

Solving pricing when the real problem is distribution. If not enough of the right people know you exist, a lower price will not save you. Go read how to get your first customers instead.

The concrete move: find the one you are currently doing, and stop this week.

How I would start#

If I were pricing a small SaaS today, here is the sequence.

First, write one sentence naming the specific buyer and the specific value: who they are and what they gain or avoid in real terms. Second, put a rough dollar figure on that value per month. Third, set my middle tier at a comfortable fraction of that value, then build a lower and higher tier around it so the middle is the obvious pick. Fourth, offer monthly and annual, with annual discounted by about two months. Fifth, and this is the part people skip, set the number slightly higher than feels comfortable, because my comfort has nothing to do with the customer's value.

If I already had a live product priced cheaply, my first experiment would be to raise the price for new signups and watch conversion and revenue together. If revenue goes up even as conversion dips a little, the higher price wins, and it wins every month from now on.

What I would not do#

I would not race a competitor to the bottom, because winning that fight still hurts. I would not launch with an aggressive lifetime deal for quick cash, because you trade away all your future recurring revenue for a one-time bump and inherit support costs forever. I would not agonize over whether a price is $29 or $32; that precision is noise next to whether it is $9 or $49. I would not confuse a free trial with a free forever plan, because those are different decisions with different consequences, and free trial vs freemium is where that choice belongs. And I would not treat the first price as permanent. It is a starting point, not a tattoo.

The bottom line#

Pricing feels like a math problem, but the hard part is nerve. The math pushes you toward charging more: a higher price means fewer customers to find, better customers to keep, and revenue that compounds instead of leaking. Your instinct to go cheap is protecting your feelings, not your business.

So do the uncomfortable thing. Base the number on what the product is worth, build three honest tiers, nudge toward annual, and set the price a notch higher than feels safe. Then watch. The lever is right there, and almost nobody your size ever pulls it. For the wider machine this fits into, start with how making money online works; if you are still building, how to build a micro-SaaS covers the product side. But the number on your pricing page is a decision you can improve today, for free, and it will pay you back every month you keep it.