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
Im building an ecosystem of apps and I've built my first product almost launch ready. It won't have a free tier but a 7 day free trial and after that a subscription. Pay gating adds a lot complexity to setting up onboarding and paywall so I chose the shortest way to market. Interesting to see how that works with my project.
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.
By primarily answering two questions -
Is this feature really helping them expereince enough of the core value to realize the product works for them - Free. e.g a live chat widget on the website with basic bot flow to handle real conversations
Features that help them address the pain point at depth and scale - Paid - eg. Advanced Handoff to human, Multilanguage support, integration with existing tools like CRM etc.