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
I think the hardest part is that “value” and “pricing” don’t align linearly.
The way I personally think about it is:
Free = proves capability. Paid = removes friction or scales impact.
If something helps users understand or trust you, it’s usually better as free.
If something helps them save time, avoid effort, or get a result faster, that’s where monetization feels natural.
The mistake I see (and have made) is trying to monetize value too early, instead of monetizing leverage.
In the end, people don’t pay for information—they pay for execution, speed, or certainty.
Reading through this, it feels like most teams don’t really struggle with ideas — they struggle with confidence in what to commit to.
Almost every option sounds reasonable in isolation.
What makes it hard is:
– not knowing what you’re implicitly deprioritizing
– and whether you’re solving the right problem at the right time
I’ve noticed that the moment things get clearer is when we stop asking “what should we build?”
and start asking “what are we okay not doing right now?”
Totally get that struggle. I usually draw the line at Convenience. > If a feature is 'nice to have' for a casual user, I keep it free to build trust. But if a feature is a 'must-have' for a professional workflow—like deep-dive analytics or automation—that’s the paid tier. You show them the 'what' for free, and charge for the 'how fast.
As a marketer I would clearly separate "free" into two buckets.
Things that cost me nothing to give (education, frameworks, light features) go free forever.
But things that cost me per user (compute, API calls, storage, SMS) get metered.
Example from a tool I just built (PostMine — a Chrome extension that turns social posts into content packs): the capture itself, the scheduling, the history, the AI tokens, Brand voice, different lengths— are all free and included.
AI credits above a threshold, BYOK integrations, bulk processing — come as paid. In that way users never feel nickel-and-dimed on the core app, but the cost-heavy parts pay for themselves.
I think it was Dan Kennedy who said this line and it stuck with me years ago: "when you pay, you pay attention."
I have experienced myslef, that fully free audiences are the most demanding I've ever served.
Not sure if this is also your experience, would love to know :-)
That is the golden question every builder faces!
With my app, I’ve always followed a simple rule: The free version must be valuable enough to use without feeling constant frustration.
I believe that if you provide a 'decent' baseline experience where the user can actually feel the benefit, you build real trust. Users who are ready to invest in their growth will still upgrade to the premium features for the full experience, but they do it because they love the product, not because they are forced by a paywall.
For me, it’s about generosity as a marketing strategy. If the free part is great, the paid part must be amazing.
Good luck with your decision!
I see a lot of apps these days with free tiers that are not useful. I try the free tier to figure out if it's useful, realize there are no useful features in the free tier, get frustrated and uninstall. I think a free trial or a proper demo and a hard paywall is the way to go.
Great question. My rule of thumb has been: free tier should solve the problem once or twice, paid tier removes the friction at scale. The free stuff has to actually work, not be a crippled demo, otherwise people bounce before they trust you. Curious how others handle the "too generous" trap though — anyone found a clean signal that you've gone too far?
The way you described your own content strategy actually nails it, give enough to build trust, hold back enough to create a reason to pay. Most builders just need to ask, would someone pay for this or are they only using it because it's free? very different users.
If I'm doing freemium, I like for the free version to be genuinely useful to my audience.
Too many people publish completely useless versions of their thing as the "free version" which I find incredibly off-putting.
As for paid features, I try to think of enhancements that not everyone will need, but that those who do need it will be willing to pay for, e.g. stuff that will help them use the product to make more money, upsell their clients, or similar.
Team/collab features are usually paid; the single-user core should stay free.