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
Great question! This is something I have thought about a lot. Here is my framework:
1. The "Aha Moment" Test - Free should get users to their first meaningful result. If they don't experience value quickly, they will churn before paying. Whatever gets them to that "aha, this works" moment should be free.
2. Usage-Based Gates Work Better Than Feature Gates - Instead of hiding features, limit usage. 5 exports per month, 3 projects, 100 API calls. Users understand this intuitively and it creates natural upgrade pressure.
3. Team Features Are the Easiest to Monetize - Collaboration, sharing, admin controls, SSO. Individual users can stay free forever, but the moment they want to bring their team, that is where you charge.
4. Follow the Cost Structure - If a feature costs you significantly more to run (AI generation, storage, bandwidth), that should be paid. Do not subsidize power users at the expense of your unit economics.
The key insight: free should demonstrate the problem exists and that you understand it. Paid should be the complete resolution.
minimalist phone: creating folders
@taylorbrooksops I will keep this in mind! 👆
I think it really depends on a case-by-case situation.
For CoreSight, our features (like building a business model or analyzing a stock) are free for the users because they are just the starting point for what we're building with our B2B partners.
minimalist phone: creating folders
@andreitudor14 what features are paid then?
My current product is completely free and I'm not sure that'll change. The core insight was that trust is the product — if parents have to pay to find out if a game is safe for their kid, they won't use it, and then the whole thing fails. Free removes the friction entirely and lets the tool prove itself first. Revenue conversation comes later once there's real usage to build on.
minimalist phone: creating folders
@jailen_dalton I think you should create 2 or 5 games, and promote them inside the app as approved :D and those games could be priced :D
unpopular take but i think most builders overthink this. the real answer is almost always tied to your cost structure, not user psychology.
if a feature costs you nothing to serve (static content, basic CRUD, local processing), make it free. if it has real marginal cost per user (API calls, compute, storage at scale), thats where the paywall goes. not because youre being greedy but because you literally cant sustain it otherwise.
i run AI-heavy workloads and learned this the hard way. gave away too much compute early on trying to "hook" users, burned through credits faster than signups converted. switched to a model where the expensive stuff (inference, generation) has usage caps on free tier and unlimited on paid. conversion actually went up because people could see exactly what they were paying for instead of some vague "pro" badge.
the freemium advice of "let users hit the wow moment" sounds great in theory but falls apart when your wow moment costs you 50 cents per user per session. at that point youre literally paying people to maybe convert later.
minimalist phone: creating folders
@umairnadeem It is valid for AI products or products where AI is a part of the product. But in our case, there is no AI, and costs are more in the form of salaries, taxes, paid offices, etc.
For marketplaces, the line between free and paid features is tricky.
I’m currently building Zuppibuy, a classifieds platform, and our thinking is:
Free → posting listings, browsing items, contacting sellers.
Paid → features that increase visibility, like promoted listings or boosted ads.
The core value should stay free so the marketplace grows, while paid features help sellers get more reach.
Curious how other marketplace founders here approach this.
minimalist phone: creating folders
@prathiganesh I think that for directories (is it a directory, right)? it is quite obvious :)
Murror
For Murror I went back and forth on this a lot. The core emotional value, feeling heard and less alone, has to be free or nobody trusts you enough to even try it. You cannot gate the thing that proves the product works.
What I ended up deciding is that free should get someone to their first real moment of feeling understood. Paid is for people who want that consistently as part of their life. The free tier creates the need for the paid one.
The trickiest part is when your free version is so good that people feel no urgency to upgrade. Still figuring that out honestly.
minimalist phone: creating folders
@astrovinh So what's included in a free vs a paid tier?
The way I think about it for what I'm building: free should be enough to make someone a believer. Not a teaser, not a hook. Actually useful on its own. If they upgrade, it's because they want more of something that already worked.
Gate the depth, not the discovery. Most products get that backwards.
minimalist phone: creating folders
@marcelino_gmx3c Never lower the bar, only raise :) I like this approach :)
This is something I’ve been struggling with while building WisGrowth. In the early days, the temptation is to put too much behind a paywall because you’re trying to validate monetization. But I realized something important: if users don’t get a real “aha moment” before paying, they simply won’t trust the product.
For us, the free part focuses on helping users discover potential career paths and better understand themselves.
The paid layer only begins when the platform starts doing deeper work, such as detailed career analysis, resume insights, and guided execution.
My current rule of thumb is:
Free → clarity
Paid → transformation
Still figuring it out though. Every week, I question if we’re giving too much away or charging too early.
Curious how other builders think about this balance.
minimalist phone: creating folders
@amit_aggarwal13 :DDDDDD I was the same, monetise straight away, but.. please... this is only big names can afford or only when it is something really needed, like a vaccine or so. Otherwise, you need to hook people with free things.
@busmark_w_nika That makes a lot of sense.
I’m starting to realize that trust probably has to come first, especially when the product is about something as personal as careers. If someone hasn’t experienced real value yet, asking them to pay too early feels like asking for belief rather than proof.
So now I'm trying to think of the free layer less as a teaser and more as something that genuinely helps people move forward a bit. The tricky part is figuring out where that line is so the free experience is meaningful, but the deeper work still has value.
Still experimenting and learning as I go.
Out of curiosity - when you say hook people with free things, do you think it’s more about useful tools or content/community?
minimalist phone: creating folders
@amit_aggarwal13 This is a tricky approach, you can give a lot of free things within your content (building trust) and when it is strong enough, people will trust your tool (which is paid) as well. But I think you need to have a really quality tool.
@Nika Yes — the biggest one was when we audited our own product and realized the free version had MORE features than the paid version. 10 hooks free vs 6 in the paid tier. Nobody would pay for less. That forced us to rethink: paid isn't "premium features behind a wall." It's "everything free, plus the packaging that saves you time." The install script, the pre-tested config, the 15-minute setup guide — that's what people pay for. Not the code itself. Second aha: we had 3,000+ npm downloads/month but zero sales. The traffic was there, the conversion path wasn't. We were building tools but not building a bridge from "this is useful" to "I'd pay for the complete package." Adding one CTA to the CLI output changed more than months of new features.
minimalist phone: creating folders
@yurukusa SO in general, one button (copywriting in button) changed everything? Can you share the website/tool?
Murror
this one is genuinely hard when you're building for people going through something difficult. with Murror, which is about loneliness and isolation in young people, i keep asking myself: if i put this behind a paywall, am i pricing out the exact person who needs it most?
the way i've been thinking about it is whether a feature helps someone understand their situation vs. helps them take action on it. the understanding layer should probably be free. that's where trust gets built. the deeper tools that require ongoing support or sustained engagement can come later once the person is in it and sees value.
also honestly if the core experience isn't free enough to actually reach people, none of the paid stuff matters anyway.
minimalist phone: creating folders
@astrovinh so what is the monetisation model for your tool? How do you earn money?