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
This is something I’ve been struggling with while building WisGrowth. In the early days, the temptation is to put too much behind a paywall because you’re trying to validate monetization. But I realized something important: if users don’t get a real “aha moment” before paying, they simply won’t trust the product.
For us, the free part focuses on helping users discover potential career paths and better understand themselves.
The paid layer only begins when the platform starts doing deeper work, such as detailed career analysis, resume insights, and guided execution.
My current rule of thumb is:
Free → clarity
Paid → transformation
Still figuring it out though. Every week, I question if we’re giving too much away or charging too early.
Curious how other builders think about this balance.
minimalist phone: creating folders
@amit_aggarwal13 :DDDDDD I was the same, monetise straight away, but.. please... this is only big names can afford or only when it is something really needed, like a vaccine or so. Otherwise, you need to hook people with free things.
@busmark_w_nika That makes a lot of sense.
I’m starting to realize that trust probably has to come first, especially when the product is about something as personal as careers. If someone hasn’t experienced real value yet, asking them to pay too early feels like asking for belief rather than proof.
So now I'm trying to think of the free layer less as a teaser and more as something that genuinely helps people move forward a bit. The tricky part is figuring out where that line is so the free experience is meaningful, but the deeper work still has value.
Still experimenting and learning as I go.
Out of curiosity - when you say hook people with free things, do you think it’s more about useful tools or content/community?
minimalist phone: creating folders
@amit_aggarwal13 This is a tricky approach, you can give a lot of free things within your content (building trust) and when it is strong enough, people will trust your tool (which is paid) as well. But I think you need to have a really quality tool.
@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) :)
Really timely question for me — just launched Zeno Finance and wrestled with this exact decision for weeks.
Landed on full product behind a 7-day trial, no freemium tier. Here's my thinking:
Freemium attracts people optimizing for free. A time trial attracts people who actually want to solve a problem. The freelancers I built for aren't looking for a free tool — they're looking for the right one. If 7 days isn't enough to know, the product isn't good enough yet.
Your point about generalized vs tailored is exactly the right framework. The free tax calculator I built gives anyone a general estimate — no signup, instant value. The paid dashboard is the tailored version — your clients, your real numbers, your specific situation.
Free = the concept. Paid = your version of the concept.
The giveaway that converts best isn't a watered down version of your product. It's something genuinely useful that makes people realize they need the full thing.
minimalist phone: creating folders
@pierrekr7 Tax calculator in March is a blessing; you can hook many people with that during this time. Neat! :D
MacQuit
Been writing code for 10+ years and I still don't have a clean answer for this, haha.
I just launched a small Mac menu bar app (MacQuit — batch-quit running apps with one click). What worked for me: don't gate by feature type, gate by scale.
Free version does everything — view running apps, see CPU/memory usage, quit apps individually. But batch quit is capped at 5 apps. So when you have 20 apps open and you're clicking quit one by one... that's when the $4.99 unlock starts to feel worth it.
The key insight for me was: the paywall should hit at the exact moment the user already loves the product. Not before. If they hit the limit and think "fine, take my money" — great. If they think "this app is annoying" — you gated too early.
I also chose one-time purchase over subscription. For a native utility with zero server costs, charging monthly just didn't feel right. I know subscriptions are the trend, but for local-only tools I think users appreciate the honesty.
Still learning though. Curious if anyone else has tried "gate by volume, not by feature type"?
minimalist phone: creating folders
@lzhgus IMO, when you are starting, it is better to also launch a lifetime option so people do not feel like they will be paying constantly to have a value.
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.
I tend to draw the line at utility versus cost.
Free should let people understand the product, trust the thinking behind it, and get genuine value without feeling cornered. Paid should begin where the experience becomes materially more powerful, personalised, or expensive to deliver.
That’s also the balance I’m thinking through with Lucid Report. I want the free layer to be genuinely useful, not a hollow teaser, because the whole point is to help people get a clearer view of the news. The paid layer should come in where the value becomes more intensive and compounding, rather than where basic understanding is artificially gated.
Most answers here are about features, but I think the cleaner split is actually about uncertainty.
Free should reduce uncertainty enough for someone to say:
“ok, I understand the problem and why it matters”
Paid is when the user wants to reduce uncertainty in their specific situation.
That’s where things become expensive:
– interpretation
– consequences
– trade-offs
In my case (I’m building a simulation tool for startup ideas), the free layer shows adoption patterns and friction.
The paid layer is where it answers:
“what does this mean for my idea, my timing, and my risk?”
So it’s less about holding features back, and more about:
where does the output become decision-critical?
If you charge before that point → people don’t convert
If you give that away for free → people don’t need to pay
It's easy for a product, you keep the cheap, valuable, aha moments feature for free, and keep the expensive, high credit/unit economics feature premium.
For us in QueueForm, the only 2 features that we have made paid only, is Custom Domain and the ability to send emails via SES. They cost us for each unit, so they are behind the paywall.
Anything else that just does not cost us much, is free for user to try, play and experiment.