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 us at Hello Aria, the rule of thumb is: free = value that gets users hooked, paid = value that makes them stay.
Core features (basic reminders, todos, WhatsApp integration) are free — because if users don’t experience the core magic, they’ll never convert. But calendar sync, Circles (team features), and priority AI responses are paid, because those are things power users genuinely need and will pay for.
The mental model that helped most: free tier should answer "is this useful?" and paid tier should answer "can I live without this?"
Overcomplicating pricing early kills conversion. Start simple, watch what free users hit the ceiling on, and that’s your natural paywall.
For Hello Aria (AI productivity assistant on WhatsApp/iOS), our rule of thumb is: free = enough to get genuine value and build the habit, paid = the features that make it indispensable.
Concretely, free gives you core reminders, todos, and basic AI chat. Paid unlocks unlimited usage, calendar sync, meeting notes, voice-to-text, and multi-platform (Telegram + WhatsApp together).
The trick we found: don't gate by feature complexity, gate by frequency and depth. A power user hitting limits every day is a natural upgrade trigger. Someone who uses it once a week probably shouldn't be paying anyway.
Also: time-limited trials tend to create anxiety. Usage-limited trials create curiosity. Big difference in conversion psychology.
For my main tool I offer a free plan with features that most of my competitors already ask payments for and introduce more better features with API access for that tool which I put under paid plan with a 3 days free trial and cheaper rates.
minimalist phone: creating folders
@dishantsinghdev That sounds like a competitor's advantage.
@busmark_w_nika Yeah that’s exactly the idea, if the free plan already feels useful, people actually adopt the product instead of just testing it and leaving. Then the paid plan becomes more about scale, automation, and API usage for power users.
one thing i dont see mentioned here is letting your actual infrastructure costs dictate the line. i run an automated video pipeline and the split became obvious once i tracked per-user costs. image generation is basically free at scale (fractions of a cent per image) so that stays in the free tier. but video animation runs about 7 cents per clip, and at volume that adds up fast. so the paywall lives exactly where my costs spike.
the conventional wisdom of "gate your best features" never sat right with me. if your best feature is cheap to deliver, keeping it free is a growth lever. gate the expensive stuff and be transparent about why. users respect "this costs me real money to run" way more than arbitrary feature locks.
minimalist phone: creating folders
@umairnadeem I was just explaning the product we have, so that's why I didn't metion these costs, we do not use AI in our product :)
One approach that worked well for many developer tools is:
Free → core usage so people can understand the value quickly
Paid → advanced workflows, automation, or scale
If the free tier lets people experience the real value, conversion usually happens naturally once they rely on the tool.
minimalist phone: creating folders
@aroido and of course, product needs to be not only useful but also you need to have trust into it.
Real data point from our experience: We built 440 free browser-based developer tools as a portal. Zero revenue for months. Then we packaged the same tools as a Chrome extension with a Pro tier ($4.99/mo for offline access + bookmarks sync). The free version drives trust and traffic, Pro converts the power users who want it always available. The line we drew: if it works in a browser tab, it's free. If it needs to work without a browser tab (offline, extension popup, keyboard shortcut), that's Pro. The key insight was that convenience is worth paying for, but the core utility should never be gated. We also found that giving away 100% of the product for free first made the paid tier feel fair rather than extractive.
minimalist phone: creating folders
@yurukusa were there any psychological "aha" moments that made you realise that "certain changes" convert faster?
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.