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
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?
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.
@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.