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
Most of the time I try to keep one principle very clear: all core value should be free.
For example with my project routebook.io, the main purpose is to track and manage your flight history. That core functionality is available for free, because without it the product wouldn’t make sense. I don’t want users to hit a paywall before they even get value.
Where I draw the line is on convenience and automation. If someone wants more comfort—like automatically adding flights, syncing data, or reducing manual effort—then it makes sense to charge once it goes beyond a certain level. That way casual users can enjoy the product fully, while power users who get more value help support it.
I’ve found this balance keeps things fair and also builds trust early on.
One thing I’m still curious about: has anyone here seriously considered using ads to keep everything free?
Or does that usually hurt the experience too much for a product like this?
Genuinely good question and I don't think there's a clean answer, but one thing I'd push on: the worry about giving too much away for free usually overestimates how much people retain from public content. Most readers won't act on generalised advice even when it's excellent, they need the accountability, the framing for their specific case, and someone to tell them which 20% of the advice actually applies to them. That last part is the paid work.
So I'd almost flip the framing. Give away more than feels comfortable on the educational side, because the people who'd self-serve their way out of needing you were never going to hire you anyway. The ones who do hire you are paying for the part that can't be generalised.
This keeps me up at night, honestly. I'm launching my first product tonight at midnight, and I ultimately decided to offer a 100% fully featured version, storage gated. My product, PictaBase is a digital asset manager which allows boot-on-the-ground teams to find, share, and comment on photo assets quickly. Because its a team-focused tool, I ultimately opted to un-gate the entire functionality, but limit the number of seats and hard clamp the storage so I don't get soaked. Looking forward to seeing folks' critiques of it when it launches tonight.
For me the line is simple: free should be enough to actually solve a small piece of the problem and build trust. Not a teaser, not a watered-down demo. A real, working slice.
If someone gets real value from the free tier, three things happen: they come back, they're willing to pay when they need more, and they tell their friends. That's the goal.
Paid is for the parts that take serious time, compute, or depth, the things people are willing to pay for once they already trust you. But you don't earn that trust with a feature locked behind a paywall.
Interestingly, my first users paid before I even had a free tier — the login was the paywall. That told me the pain point was real.
I later moved toward freemium to accelerate growth. More people experiencing the product led to much stronger word-of-mouth.
Turns out access matters as much as value. 😄
I am trying to offer a small but sticky product feature. I think a free feature should be something people can easily start using and experience your general ecosystem. This feature is used to decrease the friction that appears when a person start using a new product. After that experience people feel more comfortable to move to a paid tier I think.
Truly
This is context-dependent, but here is how I think about it.
For any product, there is a cost of marketing (awareness), a cost of sales (getting to 'aha' this solves my problem and i need this) and then a cost of value delivery (ongoing).
Stuff that's free should only be free because it's lowering the cost of marketing/sales. From the point that that job is done, everything should be paid.
Conversely, if making something free does not measurably help with awareness or getting to 'aha', then it should not be free.