How do you decide what features should be free and what should be paid?
Let me start from the creator’s perspective:
I personally don’t have a product (apart from hiring people for creative work or offering personal consultations).
But as a creator, I constantly share content, insights, and information, value that helps me build trust (for free). Based on that perceived expertise, people eventually decide to work with me (a paid service).
So some things I share for free to eventually move toward a paid collaboration.
Personally, it’s sometimes hard to judge when I might be giving away too much for free.
And I assume it’s similarly tricky for builders.
You want users to try the product, but then comes the question of paid features, or a trial limited by time or usage.
How do you decide which parts of your product or service remain free, and which become paid?
When I share content publicly, I usually provide generalised advice. But when it comes to a specific case or a tailored strategy that requires a personal approach, that’s where it becomes paid.
Replies
OpenOwl
My rule of thumb: free should solve the pain well enough that users keep coming back, but paid should remove the friction that makes the free version annoying at scale.
For example if your tool lets you track 3 projects for free but charges for unlimited, the limit itself becomes the sales pitch once users are hooked. You never have to "sell" them on it, they sell themselves when they hit the wall.
The worst thing you can do is make the free tier so good nobody ever needs to upgrade. Learned that one the hard way lol.
minimalist phone: creating folders
@mihir_kanzariya That's why I am trying to come up with more useful features I can label with the price tag :D
A safe rule is to keep the core utility free so users can actually see the value. You charge for "power user" features that save time, provide deep data, or help teams work together. If a feature directly helps a company make more money, it belongs in a premium tier. Some founders use a usage limit instead of a feature gate to keep the user experience smooth. This way, the product stays accessible until the user reaches a certain scale.
minimalist phone: creating folders
@oliviajames True, the worse is that my tool doesn't help to earn money. 🫣
My goal is to make the world better and easier, so I try to focus on giving the main benefit of the product for free, and then convenience and upgrade features the paid portion that can be unlocked. It may not make me rich but at least I feel like I'm contributing.
minimalist phone: creating folders
@cybercraftsolutionsllc what is the main free feature of your tool?
Great question! this was actually something I wrestled with a lot on my latest side project
My general rule: if a feature already exists somewhere else for free, I make my version free too. The way I see it, if someone wants that functionality, they can already get it elsewhere. So why would they pick mine? Because mine comes with more built in, even at the free tier.
From there, any additional settings or customization layered on top of that feature becomes paid. The goal is to offer a solid free baseline thats enough to be useful while reserving the deeper control and extra capabilities for paid users.
minimalist phone: creating folders
@smoothies949 What if the product is unique, so then, how to decide which features will be free when you are the trendsetter?
I think in B2C products the core experience has to stay free, otherwise users won't even get to the point where they understand the value. The goal of the free tier shouldn't be to tease, but to genuinely solve a problem so adoption feels natural and frictionless.
For paid features, I've found it works best when they add to the experience rather than restrict it. Things like higher limits, more customization, or entirely new capabilities on top of the core product tend to feel fair and intuitive for users.
A practical principle I follow is tying monetization to cost: if a feature creates direct ongoing costs on our side (infrastructure, APIs, storage), it's a strong candidate for premium. That way the business stays sustainable without compromising the base experience.
And one thing I'd avoid at all costs: moving previously free features behind a paywall. It breaks trust very quickly. If anything, it's better to introduce new premium layers or expand existing ones, rather than taking value away from users.
minimalist phone: creating folders
@andrasczeizel But CapCut did this after 2 years (moving the free features behind a paywall), and I bought their product, in my opinion, it was a brilliant marketing move.
The framing that helped us most: free gets them to the win, paid lets them keep or scale it.
If someone can't experience the core value for free, they won't convert. But if the core value IS the whole product, there's no reason to pay.
So we ask: what's the smallest slice that proves the promise? That's free. Everything that builds on the result — saving, customizing, repeating — that's paid.
Your content example is spot on. Generalized insight = free, because it builds trust. Tailored strategy = paid, because now you're doing the thinking for them.
minimalist phone: creating folders
@oana_clopotel At least you reassured me a little that I'm not giving away so much for free. :D
On the product I am launching today, Sour Mango https://www.producthunt.com/products/sour-mango-nomads, I decided to give each user who is not subscribed the ability to use the premium feature for a set number of times per day. The AI Travel Assistant, the Wi-Fi speed test, and the local price check all have a combined limit of 10.
More detailed features, such as the destinations that provide you with accurate information about different cities, from the apps to use, to visa, tax, safety information, are restricted.
minimalist phone: creating folders
@ibrahim_zarifeh1 Cool! I supported the launch :)
Pretty simple for us, we have a free tier and additional usage is charged. Features are mostly the same for both
minimalist phone: creating folders
@karan_kankariya1 How many features are for free? :)
@busmark_w_nika All of them are, our customers only pay more for more usage!
For our SaaS products, i think everyone follow a simple rule: free features bring users in, paid features help them get more out of it. The free tier is enough to show real value and build trust, but the features that save time, unlock scale, or solve a specific pain point — those are where the paid tier earns its place.
Your framing resonates — generalised value for free, tailored depth as paid. I think the same logic applies to products: if a feature solves a generic need, it can be free. If it solves your specific problem efficiently, that's the paid layer.
The tricky part, as you said, is knowing when you've given too much away. I've found a useful gut-check is asking: "Would a user feel they've already solved their problem with the free tier?" If yes, the paid tier has no pull.
Great question! As a builder of a personal safety app (Lifeline: SOS Countdown App), I struggled with this too. Here is the framework I used to decide:
1. The "Essential Survival" Tier (Free) I believe some things should never be behind a paywall. In my case, a basic Manual SOS should be free. If someone is in danger right now, they need a tool that works immediately. This builds the core trust. If the free version can save a life, you've won a user for life.
2. The "Automated Guardianship" Tier (Paid) We decided to charge for features that require ongoing server costs and provide proactive (rather than reactive) safety.
The "What If" Logic: Our core paid feature is the Automated SOS Countdown. It’s for those "silent" emergencies where you can’t reach your phone (e.g., a sudden fall or a robbery).
Two-Way Guardianship: We also put the "Guardian Link" in the Pro tier. It allows loved ones to check your real-time status and GPS without you needing to do anything.
My takeaway: Free features should solve the immediate pain point. Paid features should provide the ultimate convenience or automated protection.
I’ve been testing this with Lifeline: SOS Countdown App, and it’s interesting to see that users are willing to pay $19.99 not just for a button, but for the "Peace of Mind" that someone is watching over them even when they can't call for help.
Curious to hear if others think safety features should ever be monetized differently!
minimalist phone: creating folders
@pan_zo Can you see already paying users open to pay 19.99?
@busmark_w_nika My $19.99 data actually comes from my early user interviews with solo travelers and beta testers. When we discussed pricing, a recurring theme was that they associated a "cheap" subscription (like $2/month) with "cheap servers"—which is the last thing you want for a life-saving tool. But you hit the nail on the head: people saying they will pay in an interview is very different from actual credit card swipes. That is exactly why I need real-world validation right now. Since you brought up this great point, I’d love to run an experiment with this community: I’m giving away 100 LIFETIME free promo codes ($19.99 value each) to anyone here willing to help me test the app in the real world. I need to know if the "Deadman's Switch" logic actually provides that peace of mind before I focus on monetization. If you (or anyone reading this thread) wants a code, just reply here or DM me, and I’ll send one over. I'd love your harsh feedback on it!
minimalist phone: creating folders
@pan_zo wait... is it 19.99 lifetime or monthly? Because I first thought that monthly.