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
@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?
This is something I’ve been thinking about too while working on a project recently, so the timing of this post is perfect. Really insightful perspective, thanks for sharing this Nika :D
From how you framed it, what clicked for me is:
free = helps people understand the value
paid = helps them actually get results faster or at scale
So basic use cases or smaller usage make sense to keep free. But once it becomes part of someone’s actual workflow or starts saving real time, that’s where paid feels more fair.
Still figuring out the balance though, it’s trickier than it looks.
minimalist phone: creating folders
@naomy_tiara09 How do you apply this approach to your tool? (if you do not mind sharing the tool itself) :)
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.