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
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?
the real answer nobody here is saying: if your product has variable costs per user (like AI inference), your free tier IS your marketing budget. treat it that way.
i run AI-heavy pipelines and every prompt costs real money. so i structured it as: free tier = enough to hit the wow moment, maybe 5-10 uses. paid = unlimited or high volume. the key insight was tracking exactly where users go from "oh cool" to "i actually need this in my workflow" and putting the gate right after that moment.
what changed everything for me was caching aggressively. i cache outputs with vector similarity search so if someone requests something close to what already exists, i serve the cached version instead of burning another API call. cut my costs by 60-70% overnight. suddenly the free tier became way more generous without actually costing more.
the trial vs freemium debate is a false choice imo. trials work when your product needs time to click (like writing tools or habit apps). freemium works when value is immediate but scales with usage. combining both usually just confuses people about what theyre actually getting.
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.
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.
Starnus
@busmark_w_nika IMO everything must contribute to the main business pipeline, even "free" stuff, are serving the "paid" parts. So, any part that is desired by many, won't put a lot of cost on your table, and can act as "lead magnet" can be free, but well attached to the rest of the paid services/features, so it can convert users to paid clients.
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.
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.
Pretty simple for us, we have a free tier and additional usage is charged. Features are mostly the same for both
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!
Honestly the way I think about it is that free should get someone to the point where it actually changes how they work. Like they do something differently because of your product. Paid is for when they're already hooked and want more.
The mistake I see a lot is gating too early. You never give users a chance to feel anything, so of course they don't convert. But the other trap is being too generous and training people to expect everything for free.
The hard truth is early on it's mostly a guess. You only really know which feature mattered once you have the data to see what actually changed behaviour. Until then you're just making your best call and adjusting.