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
One great idea I'm bouncing around at the moment is to offer paid subscription features for free but with limits. I believe the freemium model greatly increases conversions, and you can see examples of this in applications like Vercel / Expo, even Microsoft has a "only pay when you cross a limit" feature.
I think this works great, because it allows users to build up trust as you mentioned Nika, but it also increases the value proposition. I'd be more willing to pay for something personally that's already working for me.
minimalist phone: creating folders
@minhajulll What will be the "limit?" :)
@busmark_w_nika Like for example: Vercel let's you build websites for free and they will run the hosting but once you hit a certain limit of traffic you have to pay. The same with expo, for more build / faster builds you can pay otherwise you can use the free tier which is just as good. Btw I'm launching tomorrow, would be grateful if you could support :)
minimalist phone: creating folders
@minhajulll i am gonna support your launch :)
This is a million-dollar question for any creator! Personally, I believe the 'Free' tier should offer enough value to solve a core problem, making the user trust your brand. The 'Paid' tier should then focus on scale, automation, or deeper expertise.
I'm curious, for those of you with SaaS products: Have you ever felt that you gave away 'too much' for free? How did you pivot from that? Would love to learn from your experiences!
minimalist phone: creating folders
@faisal_ahmed_rony This is maybe a question for someone in the community because I do not have Saas! :D
@busmark_w_nika Haha, fair point, Nika! :D Content and insights are indeed a different ballgame compared to software.
one thing nobody here is mentioning is that the free vs paid calculus completely changes when your product has real per-user costs. i build AI-powered tools and every single API call costs money. image generation is like $0.003 per image, animation runs about 7 cents per clip, TTS has its own costs. so "free tier" doesnt just mean less revenue, it means actively losing money on every active user.
what worked for me: make the creative/exploratory part free (browsing, planning, basic editing) and gate the compute-heavy stuff behind usage limits. users get enough to feel the product, but the expensive operations are metered. went from burning cash on free users to actually having sustainable unit economics.
the trial vs freemium debate misses the point for AI products honestly. its not about time gates or feature gates, its about cost gates. let people do everything, just cap the volume. they self-select into paying when they hit real usage because by then theyve already built the habit.
minimalist phone: creating folders
@umairnadeem How do you set prices in such case? Like – do users pay immediatelly? Or have you set up like okay, I am okay to lose 0.006 per user and they ask for money?
I usually think about it this way: free should help people reach the “aha” moment, paid should help them get ongoing outcomes.
If the free tier solves the whole problem, there’s no real reason to upgrade. But if it’s too limited, users never experience enough value to care. The sweet spot is letting people feel the core value for free, then charging for depth, scale, speed, customization, or repeat use.
A simple test is:
Would I be okay if thousands of free users only used this part?
If yes, keep it free.
If no, and especially if it creates real cost or delivers compounding value, that’s usually a paid feature.
minimalist phone: creating folders
@aanchal_dahiya This can help me to better customise pricing in the future if I decide to create any tool :) Thank you :)
the thing nobody here is mentioning is how AI changes this calculus completely. when your most valuable features run on inference costs that scale per-use, the old "give away the core, charge for premium" model breaks down fast.
i build tools where every API call costs real money. image generation is like $0.003 per image, animation runs ~7 cents per clip, TTS has its own costs. so the free tier cant just be "unlimited basic" because basic still costs me money on every single request. usage-based pricing or hard caps on free tiers arent just a business strategy, theyre survival math for solo builders.
the counterintuitive thing ive found: being transparent about costs actually converts better than hiding them behind feature gates. telling users "this costs me X to run, heres what you get free, heres what the paid tier unlocks" builds way more trust than arbitrary feature walls. people respect honesty about unit economics more than they respect marketing frameworks about "wow moments" and conversion funnels.
minimalist phone: creating folders
@umairnadeem This is fair. Personally, I would also be more prone to pay if the founder is transparent about costs. Because I share with him some sort of understanding :)
something i rarely see discussed here is that the free/paid boundary should follow your actual cost curve, not some theoretical framework about user psychology. i run a content pipeline that uses multiple AI APIs and the costs vary wildly per feature. image generation is like $0.003 per image so giving that away for free is basically nothing. but video animation runs about 7 cents per 10 second clip and thats where it adds up fast at scale.
so my rule is simple: if the marginal cost of a feature is near zero, make it free and use it as the hook. if theres real per-use cost, thats your paid tier. not because of some conversion funnel logic but because your bank account literally demands it when youre self funded.
the whole "wow moment" framing is fine but it ignores that most solo builders arent choosing between free and paid. theyre choosing between sustainable and bankrupt. i went from spending $150/mo on one service to $40-50 by just caching outputs and checking similarity before regenerating anything. that kind of engineering is what actually lets you offer a generous free tier without bleeding money.
minimalist phone: creating folders
@umairnadeem What amount of cost for you is enough to ask money? You know... "what is close to 0"? Because this means something else to someone who has a salary $15,000/month and someone who has $600/month.
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 :)