Pricing

How to price a micro SaaS

Price is one of the most powerful decisions a small software business makes, and one of the most often guessed. This guide covers how to choose a price, what to charge for, how to structure plans and how to change prices without upsetting customers.

By the Twarx Micro SaaS Boutique team5 min read

Founders often spend months on features and minutes on price. Yet for a small software product, price decides who buys it, how many customers you need to make it worthwhile and how much you can spend on support and improvements.

There is no formula that gives you the right number. There is a sensible way to reach a good first price, test it and improve it. This guide sets out that approach in plain terms, with the decisions you will need to make in the order you will meet them.

Price on value, not on cost

Software costs very little to deliver to one more customer, so pricing by adding a margin to your costs usually produces a number that is far too low. Customers do not care what the product costs you. They care what the problem costs them.

Start with the value. If your product saves a business several hours of staff time each month, prevents a costly mistake or helps win more work, that has a value you can describe in money. Your price should be a comfortable fraction of that value, so the decision to buy is easy to justify to whoever signs off on it.

Then look at the alternatives. What does the customer pay today for tools, people or workarounds that solve the same problem? Your price will be judged against those, not against an abstract idea of what software should cost.

Choose what you charge for

Every subscription product charges for something: a seat for each user, a number of projects, a volume of usage, a set of features, or simply a flat fee. This choice matters more than the exact price, because it decides how revenue grows as customers get more out of the product.

The best option is usually the thing that grows as the customer gets more value. If the product is more valuable to larger teams, charging per user makes sense. If value comes from volume, such as documents processed or bookings handled, charging by usage tiers may fit better. If customers are small and similar, a flat fee is simple and easy to understand.

Be careful with pure usage pricing in a small product. Customers like paying only for what they use, but bills that change every month are hard for them to budget for and hard for you to forecast. Tiers with a clear allowance, and a simple rule for what happens when a customer goes over it, usually give both sides more certainty.

  • Choose something customers can easily understand and predict.
  • Avoid charging for something that discourages people from using the product.
  • Make sure you can measure it reliably inside the product.

Keep the plans simple

Most micro SaaS products need between one and three plans. One plan is perfectly acceptable at the start, and it makes buying very easy. If you offer more, each one should be aimed at a clearly different kind of customer, not just add a few extra features.

A common shape is a plan for individuals or small teams, a plan for growing teams, and a higher plan for customers who need more control, support or volume. Name the plans after who they are for, and make it obvious within seconds which one a visitor should choose. If people have to compare long tables of features to decide, you have too many plans or too many differences between them.

Trials, free plans and annual billing

A free trial lets people try the full product for a limited time before paying. It suits products where the value becomes clear quickly. Asking for card details at the start of a trial usually means fewer sign-ups but more serious ones, while not asking means more sign-ups and more work to convert them. Either can be right, so choose deliberately and measure the result.

A free plan that lasts forever is a bigger commitment. It can bring in users who later upgrade or recommend the product, but it also brings support costs and people who will never pay. For a small product with a small team, a free plan is often more expensive than it looks. Start without one unless you have a clear reason.

Offering an annual plan with a modest discount for paying up front is usually worth doing. It improves your cash flow and keeps customers longer, and many business buyers prefer one invoice a year.

Test your price before and after launch

Your first price is a hypothesis. Test it during validation by showing real prices on a landing page or asking interviewees what they would expect to pay and how they would decide. Watch reactions, not just answers. Hesitation, questions about what is included and comparisons with other tools are all useful.

After launch, keep watching. If almost everyone who sees the price buys without question, it is probably too low. If interested visitors leave as soon as they reach the pricing page, look at whether the price, the plan structure or the explanation of value is the problem. Change one thing at a time so you can tell what made the difference.

Change prices without losing trust

Most founders charge too little at first, so expect to raise prices as the product improves. The safest approach is to apply new prices to new customers and give existing customers either their current price for a period or clear advance notice with an explanation of what has improved.

Set up your billing so that prices can change without rebuilding anything. A good payment provider lets you add new prices alongside old ones, so existing subscriptions are not affected until you choose to move them.

  • Give existing customers notice before any increase.
  • Explain what has improved since they joined.
  • Never change the price of a subscription silently.

The short version

Price your micro SaaS on the value it creates and the alternatives customers already pay for, not on what it costs you to run. Choose a simple thing to charge for that grows with the customer, keep to a small number of clearly different plans, and think carefully before offering a free plan. Treat the first price as something to test, expect to raise it as the product improves, and change it in a way that keeps the trust of the customers you already have.

Have an idea worth testing?

Tell us the problem and who has it. We will reply with how we would validate it and what an MVP could look like.