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
Great question and something I've been wrestling with as a solo maker building Chrome extensions. My current thinking: the free tier should solve the core problem completely — not a crippled version, but the real thing. If people don't get genuine value for free, they'll never trust you enough to pay. The paid tier should then unlock convenience, power-user workflows, or scale. For example, with browser extensions, the base functionality works for everyone, but features like cloud sync across devices or advanced customization make sense as premium — they cost more to maintain and the people who need them are usually power users who understand the value. The hardest part is resisting the urge to gate too much behind the paywall early on. When you're pre-revenue it feels like you should charge for everything, but I've found that being generous with the free tier builds word-of-mouth that's worth more than a few early conversions.