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
My rule: free should deliver a complete "aha," paid should remove a recurring friction. If the free tier never lets someone feel the core value even once, they won't convert - and if paid just unlocks what should've been free, it feels like a paywall tax and they churn.
The trap I see most: gating the aha-moment behind paid to "protect revenue." It mostly protects revenue from people who were never going to pay, while blocking the ones who would have. Let people feel the magic for free; charge for the stuff that scales with how much they rely on it.
Also a vote for generous trials over feature-crippled free tiers - let people live in the full product for a bit (we do 30 days, no card). Conviction converts better than FOMO.
Honest answer: there's no single best one, it depends on what the newsletter is meant to become. If it's the product, Substack or Beehiiv get you moving fast. If it's one layer of a bigger business with products, community, or memberships coming later, optimise for owning the audience and your domain over whichever editor you like today. The migration pain almost always shows up in year two, not week one. I work on DukieX.com, so I lean toward the owned-home view, but I'd answer that question before picking any tool.
We made the most technically complex feature in our app free. Here is how we arrived at that.
The blood biomarker layer in Orga Hair reads your existing blood test results in the context of scalp microbiome, cross-references them against clinical literature thresholds, and stores everything on-device. It took longer to build than anything else in the product.
We could have put it behind credits. By any measure of complexity and clinical value it would have justified a price.
The reason we didn't comes down to one observation. By the time someone has entered their blood test results into the app, they have started investing in their own data. The Living Profile already holds their scalp photos and health questionnaire. Now it holds their blood values too. At that point they are not evaluating a product. They are looking at their own health record.
That is a very different person to ask to pay for something.
The rule we ended up with is free for everything that makes the person invested in their own data. Paid is everything that processes that data at depth. The AI analysis that synthesises it all together costs credits. No subscription.
What surprised us is that making the complex feature free actually made the paid feature easier to sell. By the time someone reaches the credit purchase prompt, they already have invested their own data in the app. The value of the deeper analysis is simply the next step to a deeper understanding of why they are losing hair and what they can do about it. We are not convincing them the product is worth it. Their own data and the Tier One results panel they received already built the need to complete their initial and subsequent analysis. As they continue to add to their data, they increase the value of the stored data that no other service can provide them.
I think the free version should let users experience the product’s core value without being blocked before the “aha” moment.
Paid plans should usually charge for scale, automation, collaboration, advanced reporting, integrations, support, or features that save significant operational time.
I’m currently building an API product in alpha and keeping it free while I validate the workflows. Later, I would rather charge for production usage and advanced compliance capabilities than make the basic product impossible to evaluate.
A free plan should prove the product is useful. A paid plan should make it valuable to depend on.
For FounderFlow, the free tier lets you connect one business and see the daily priorities it surfaces, so people feel the actual value before paying anything. Paid kicks in once you want to connect more than one business, which is really the whole point of the product anyway. So the free version proves the idea works, the paid version is for the exact person it was built for.
Fernando's cost-structure point is the one I would build on, because I think it quietly breaks most of the frameworks in this thread.
Nearly every free-vs-paid rule we have inherited - give away the wow, stay free until they form a habit, gate on depth - assumes marginal cost is roughly zero. That holds for software where your 100th free user costs nothing. It stops holding the moment each use burns real money. We run an AI that answers people's phone calls, so every free minute is telephony plus model tokens. At that point a free tier is no longer marketing spend you control, it is a variable cost set by your least-monetisable users - and the heaviest free users are reliably the least likely to ever pay.
What fixed it for us was counterintuitive: gate on volume, not on features.
Feature-gating is the standard advice and I think it is actively wrong for variable-cost products, because your expensive feature IS your wow - which is exactly the bind Fernando describes with virtual try-on. Cripple it and nobody feels anything worth paying for. Meter it instead: full capability, bounded quantity. People experience the real product, your costs stay bounded, and the upgrade trigger flips from "I hit a wall you built" to "I want more of a thing I already like." Those two convert very differently.
One reframe helped more than any pricing model, and it maps onto your creator framing, Nika: our free tier's job was never conversion, it was proof. We are asking someone to let software pick up their actual phone. Free exists so they can verify we are not terrible. We are not giving away value there - we are buying evidence.
Which makes "am I giving away too much?" the wrong question. The better one is whether the person who took the free thing ever needed the paid outcome at all. If they never did, no amount of gating would have converted them - it would just have cost you the proof.