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
I'm struggling at this point these days exactly, gonna launch my new product next week (I don't provide any cloud services, the product runs on users' machine totally.)
Free should make people love you, paid should make people need you.
The threshold I found is "Does removing this feature make the free version feel broken or limited?", both free and pro share the biggest core features of my product and the worst mistake would be putting too much in Pro on day one.
Today's Pro feature becomes tomorrow's free feature, because you built something even better for Pro!
I've gone fully "free" with 800+ utility tools on my site because the SEO and trust they build are worth more to me than a small paywall right now.
My general rule is: If it’s a quick utility that runs in the browser, keep it free to grow the brand. If it requires my manual time, specialized expertise, or heavy server resources, that’s where it becomes a paid service. Free is the marketing; paid is the specialized solution.
Love this thread Nika! Swati and Janefrances really nailed it, free should deliver that quick wow moment and actually create the hunger for the paid version. As a self-funded builder, I keep it simple: free gives instant real value with basically zero cost to me, while scale, depth, and anything expensive goes behind the paywall. The real test is whether users walk away satisfied… or still wanting more. What are you working on?
For something like features or analytics suitable to a more general consumer, it could be something free that gets interest flowing. Casual users would also appreciate and are more likely to spread the word.
Going deeper into features that would require more resources (incl. time) to build and customise definitely makes sense as a paid feature.
As a consumer myself, if the free features are truly useful I often find myself going for a more comprehensive paid option without much deliberation.
My approach was not to leave an entire feature out, but to let the user have a taste of everything up to the point that, if he liked the product, he will want it with the full power of the feature that sits behind the paywall
We struggled with this a lot at ad-vertly, and here is the framework that actually worked for us.
Free should do enough to prove the core value promise. If users cannot experience the "aha moment" on the free tier, they will never trust you enough to pay. So we gave full access to one marketing agent on the free plan, not a crippled version of every agent.
Paid should be the thing that makes the free tier feel incomplete over time. For us that is more agents, more memory, more integrations. The free user hits a wall naturally, rather than us artificially blocking them.
The mistake I see most solo founders make is hiding the best feature behind a paywall before the user even knows why they need it. You end up with a low conversion rate and confusing messaging.
My rule of thumb: if removing a feature from free makes the product worse for paying users (because it stunts word-of-mouth and referrals), keep it free. If it only benefits the individual user who wants more scale, charge for it.
For us it came down to where the habit lives vs where the value gets realized. Privacy matters to us, so everything runs on-device by design. Basic recording is free forever because that's the behavior we need. Output, reports, Schedule C prep, that's where the outcome happens, so that's where we charge.
Still pre-launch so the market hasn't weighed in yet, but that was the logic. Hope this helps.
Limiting factor is always economics. It is wonderful to provide as much compute to customers to keep conversation open. Like Google did with search and Gmail.
For my app, goal was to give access to all product features at free plan, allow for higher resource usage at retail/tech plans. Then when customers come with business, dedicated (compute) or bespoke requests they already have enough access to the product to understand what's realistic.
I still struggle with this. The hardest part is finding the sweet spot where people feel happy to pay, not forced to. Especially with a new product—users don’t yet know how much they’ll use it, so there’s natural hesitation.
I think free should help people build confidence and form a habit. Paid should unlock more value once that habit is there. The goal isn’t to gate features—it’s to time the moment when paying feels like a natural next step.
The "aha moment" rule works well for me: whatever gets users to feel real value should be free. Everything that helps them get more of that value, faster or at scale, is worth paying for.