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
A safe rule is to keep the core utility free so users can actually see the value. You charge for "power user" features that save time, provide deep data, or help teams work together. If a feature directly helps a company make more money, it belongs in a premium tier. Some founders use a usage limit instead of a feature gate to keep the user experience smooth. This way, the product stays accessible until the user reaches a certain scale.
My goal is to make the world better and easier, so I try to focus on giving the main benefit of the product for free, and then convenience and upgrade features the paid portion that can be unlocked. It may not make me rich but at least I feel like I'm contributing.