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
For me the line is blurry and I don't think there's a clean answer. The mental model I keep coming back to is: free should create/show the problem, paid should solve it.
For content/services like yours, free builds the belief and generates the trust that you can help. Paid is the actual help. You're not giving away too much as long as the free stuff makes people want the paid service more, not less.
When I build products I take a similar approach, FREE should be generous enough that users get real value and trust the product, but the moment they want to go deeper, faster, or at scale, that's where paid comes in play.
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.