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
Simple framework we use: Give away the diagnosis. Charge for the prescription.
We let people check any property address for free — basic zoning info, buildability overview. That's the hook. The moment they want the full risk analysis, detailed setbacks, permit timelines, and compliance report? That's the paid tier.
The free tier exists to create an "aha moment" fast enough that upgrading feels obvious, not forced. If your free tier doesn't make people go "wait, this is actually useful" within 30 seconds, it's not doing its job.
Biggest mistake I see: making the free tier so limited it feels like a demo. Nobody trusts a demo. They trust a tool that already helped them.
I try to keep a balance between free and paid features.
For me, the free version should already be genuinely useful — something that actually helps people make progress, not just a demo.
I’m building a focus/study tool myself, and that’s the approach I’ve been taking: making sure the core experience is valuable on its own.
Then paid features are more about enhancing things — extra tools, more customization, stuff you only really need if you’re already enjoying it.
I don’t like locking all the value behind a paywall. People should get real benefit first, and then decide if they want more
Good rule I follow:
Free = helps you understand the value
Paid = helps you actually get results
If users can fully solve their problem for free, they won’t upgrade. So free should feel useful, but slightly incomplete.
Your “general vs specific” approach is already a very solid way to think about it 👍
I struggle with this all the time. I wish there was a formula to follow on this, but I think it depends on the tools.
That’s a solid way to think about it—free content builds trust, and paid is where you go deeper with more personalized value. I think the balance usually comes down to giving users a complete basic experience for free, but keeping convenience and advanced features as premium.
In my case working around anime users, I’ve noticed people stick when the core experience is simple and useful first. Things like easy access, clean UI, and smooth playback matter more initially. For example, setups like Anilab focus on that basic experience, and once users find value, it becomes easier to think about what could be worth paying for later.
I've been giving out 15+ things for free. First I build trust then make it paid. But I havent decided when to switch yet.
I respect this approach going paid only forces real discipline around value and avoids the free users draining resources trap .
My latest app, I give all features free with limited amounts, or access times. If need more, then have to upgrade the plan.
The benefit of this strategy is user has a chance to try all features and then decide if this product is what he wants.
The key is to offer something free that is easy to consume, and to charge for something that is hard to consume. For example, most successful YouTube creators produce dozens of high-quality one-off videos every year. But if you want a 25-hour course on some deeper subject (how to play piano, speak French, etc) this is a different medium entirely. It is hard to consume vs easy to consume. So you can charge for this, because trying to play piano or speak French via random single YouTube videos is almost impossible. You need an indepth course, which means you need to pay money.
The framework I've seen work best on SaaS products I've built: free = value demonstration, paid = value delivery.
Free gets users to their "aha moment." Paid removes the ceiling once they're already invested. The mistake I see most often is paywalling the aha moment itself — that's what kills conversions.
Tactically: look at which features drive retention at week 4. Those are your paid features. Features that drive activation in week 1 should be free or nearly free.
The other dimension is cost. If a feature has meaningful COGS per user (AI calls, storage, compute), it can't stay free at scale regardless of how it fits the above model. Architecture matters here — I've refactored billing layers on several SaaS products to support hybrid free/paid at scale. It's non-trivial to do right without the right backend structure.
Happy to dig into specifics if anyone's wrestling with this. I'm a full-stack dev (NestJS/Node/React) who works with early-stage SaaS founders — zeescript.com