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
Building for service businesses (freelancers, consultants, small shops) so we've gone back and forth on this more times than I'd like to admit.
Where we landed: free has to include whatever it takes to get someone to their first actual win with the product. Not a demo, an actual result. For us that's invoicing and proposals - fully free - because our buyers are cost-sensitive and "trust me it'll save you time" is a bad sales pitch for a $50/month tool.
Early mistake: gating features we thought were the valuable ones. Turned out we were just preventing people from seeing why those features were worth paying for.
I have a rule-of-thumb: offer your best for free, and the paid will follow. As a consultant, I often give my best advice away for free, and the person will remember I provided it to them. Half of the time, it comes back to: "Do this for me and I'll pay you to do it." This can be translated into a product mindset. Provide just enough value for free to showcase the benefits, and they'll eventually come around to paying for more. Then again, it depends on the product or service.
Hey Nika！I don't have my own product either but always provide service about marketing and growth for startup company. Here is what my personal experience and hope to engage more meaning discussion with you.
From my perspective，I don’t think the real question is “How much should be free?”
I think it’s: What should be easy to understand, but hard to replicate?
I totally agree with you that the best free value builds trust.
The best paid value compounds with context, customization, speed, and accountability.
So I’m happy to share ideas for free to various startup and people but the paid layer is where people buy precision, leverage, and a shorter path to the result. @busmark_w_nika
The best way to do this is to test it. Often, when a product is being built, whether an app, SaaS, etc. it is essential to give your best input away for free. I had a startup back in 2017 that, after 2 years of development, ended up with my partner placing a paywall before access could be given. We received no signups. I resigned. Point is, when in the startup phase, it is best to give away what you have to gain traction, and focus on monetization later on.
Building something is a process, as you know, and iteration is part of it. Just as you test product features, you should test product pricing :)
Simple framework we use: Give away the diagnosis. Charge for the prescription.
We let people check any property address for free — basic zoning info, buildability overview. That's the hook. The moment they want the full risk analysis, detailed setbacks, permit timelines, and compliance report? That's the paid tier.
The free tier exists to create an "aha moment" fast enough that upgrading feels obvious, not forced. If your free tier doesn't make people go "wait, this is actually useful" within 30 seconds, it's not doing its job.
Biggest mistake I see: making the free tier so limited it feels like a demo. Nobody trusts a demo. They trust a tool that already helped them.
I try to keep a balance between free and paid features.
For me, the free version should already be genuinely useful — something that actually helps people make progress, not just a demo.
I’m building a focus/study tool myself, and that’s the approach I’ve been taking: making sure the core experience is valuable on its own.
Then paid features are more about enhancing things — extra tools, more customization, stuff you only really need if you’re already enjoying it.
I don’t like locking all the value behind a paywall. People should get real benefit first, and then decide if they want more
Good rule I follow:
Free = helps you understand the value
Paid = helps you actually get results
If users can fully solve their problem for free, they won’t upgrade. So free should feel useful, but slightly incomplete.
Your “general vs specific” approach is already a very solid way to think about it 👍
I struggle with this all the time. I wish there was a formula to follow on this, but I think it depends on the tools.
That’s a solid way to think about it—free content builds trust, and paid is where you go deeper with more personalized value. I think the balance usually comes down to giving users a complete basic experience for free, but keeping convenience and advanced features as premium.
In my case working around anime users, I’ve noticed people stick when the core experience is simple and useful first. Things like easy access, clean UI, and smooth playback matter more initially. For example, setups like Anilab focus on that basic experience, and once users find value, it becomes easier to think about what could be worth paying for later.
I've been giving out 15+ things for free. First I build trust then make it paid. But I havent decided when to switch yet.