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
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 :)
@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?
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.
MultiDrive
As for the app, we may add some paid B2B features in the future, we’re currently exploring that. When it comes to services, it really depends on the level of involvement and the time required. If something takes a meaningful amount of your time, it should definitely be paid. A simple task or quick advice can be free, but work that requires more time, effort, and investment should be paid for.