💳 How to create pricing plans for SaaS products?

And again… the pricing plan =D

Let’s discuss the serious side of product growth.

At first, it seems easy: set some prices, create a few plans, and start selling your product.

But when the time actually comes, a ton of questions appear...

For us, pricing plans are also connected to the architecture of the product. We built a dashboard where we can include or exclude features, storage, and AI tokens for each plan.

But deciding what should actually be included in each plan became the subject of many team meetings.

Especially in our case, where we have a complex product with many different modules and capabilities - where users share large media files, work with AI, and collaborate in shared spaces.

And honestly, the question still remains:

How do you shape pricing plans that actually work?

What's your approach - from both the technical and business sides?

I'd love to hear how other makers have solved this.

434 views

Add a comment

Replies

Best

I've been approaching it like this:
1) Look at large companies that are in similar/adjacent spaces and how they have priced theirs
2) Strip away the free tier. Do a 7 day free trial with credit card
3) Revisit freemium once I've found a distribution channel that works and have perfected the product

 I agree with 1., but sometimes when you look at big companies in a similar space, there’s a question in the air: how can they possibly cover their infrastructure costs with those prices? =D

So I guess there can be a really big difference between pricing at large companies and at startup products.

And I’ve been thinking about 2. as well. I feel like the number of users can immediately drop when you require a card for the trial, because not everyone is ready to do that right away without knowing exactly what they’re going to get or pay for.

I'm focussing on getting adoption first so im using a Freemium strategy.

Ive quite hard rules that time will tell is right or wrong decision:

  • No one gets a paywall until after they have had the "aha moment"

  • Utility feature will always remain free to slowly grow adoption

  • Im hoping adoption leads to word of mouth.

  • After several "aha moments" Ive said 4, the user will only see a paywall when they click on a premium feature like connecting it to spotify to change music everytime you complete a task.

Im measuring this on a seperate dashboard in which I can see how many people have got throught the grace period, how many have clicked a premium feature after that (and what paywall did they see - ive different ones for each premium feature) and then if the use veiwed, started, bought, cancelled or dismissed the paywall and what was the trigger.

 Nice strategy!

Have you started this approach recently? Do you already have some statistics or early results?

For me, it all depends on whether I can support free trials. Solo devs often don't have the resources to be able to run infrastructure at all, so rely on generous free or cheap plans on their various partner offerings. This has a direct decision impact on how you price your own services.

I'm currently trying two different approaches
- I have a fixed price Android/iOS app available, but I'm charging a nominal price, because I have infrastructure I need to pay for
- I have a web service I am launching soon which is free to use, but optionally allows for visitors to buy into it.

The latter is running on Vercel+Neon, using trials and free plans, but that'll only run for so long - the app needs to make money otherwise, I can't fund it.

 What is the service about? And do you think it can actually become profitable for you soon?

 It's sort of an experiment - a digital presence service where visitors can discover brands, studios, indie developers by charting their way through a galaxy. It's very interactive, which I am hoping keeps engagement.

I'm scheduled to launch it next week, but would love to get some feedback from real people, if you would be interested?

Profitability is the question and that's why I am running as lean as possible. In my mind, the service has merit, but I'm working with my own bias.

 I'm really interested.

If you have LinkedIn account you can send links there.

 Sure, my LinkedIn account is on my profile :-)

agree its super hard - ive found a hybrid model for subscription + usage can be very effective

 What kind of usage? tokens, storage?

 yes tokens