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
For something like features or analytics suitable to a more general consumer, it could be something free that gets interest flowing. Casual users would also appreciate and are more likely to spread the word.
Going deeper into features that would require more resources (incl. time) to build and customise definitely makes sense as a paid feature.
As a consumer myself, if the free features are truly useful I often find myself going for a more comprehensive paid option without much deliberation.
My approach was not to leave an entire feature out, but to let the user have a taste of everything up to the point that, if he liked the product, he will want it with the full power of the feature that sits behind the paywall
We struggled with this a lot at ad-vertly, and here is the framework that actually worked for us.
Free should do enough to prove the core value promise. If users cannot experience the "aha moment" on the free tier, they will never trust you enough to pay. So we gave full access to one marketing agent on the free plan, not a crippled version of every agent.
Paid should be the thing that makes the free tier feel incomplete over time. For us that is more agents, more memory, more integrations. The free user hits a wall naturally, rather than us artificially blocking them.
The mistake I see most solo founders make is hiding the best feature behind a paywall before the user even knows why they need it. You end up with a low conversion rate and confusing messaging.
My rule of thumb: if removing a feature from free makes the product worse for paying users (because it stunts word-of-mouth and referrals), keep it free. If it only benefits the individual user who wants more scale, charge for it.
For us it came down to where the habit lives vs where the value gets realized. Privacy matters to us, so everything runs on-device by design. Basic recording is free forever because that's the behavior we need. Output, reports, Schedule C prep, that's where the outcome happens, so that's where we charge.
Still pre-launch so the market hasn't weighed in yet, but that was the logic. Hope this helps.
Limiting factor is always economics. It is wonderful to provide as much compute to customers to keep conversation open. Like Google did with search and Gmail.
For my app, goal was to give access to all product features at free plan, allow for higher resource usage at retail/tech plans. Then when customers come with business, dedicated (compute) or bespoke requests they already have enough access to the product to understand what's realistic.
I still struggle with this. The hardest part is finding the sweet spot where people feel happy to pay, not forced to. Especially with a new product—users don’t yet know how much they’ll use it, so there’s natural hesitation.
I think free should help people build confidence and form a habit. Paid should unlock more value once that habit is there. The goal isn’t to gate features—it’s to time the moment when paying feels like a natural next step.
The "aha moment" rule works well for me: whatever gets users to feel real value should be free. Everything that helps them get more of that value, faster or at scale, is worth paying for.
This is something we’ve been thinking through while building SpeakUp.
Our framework is:
free = understand the product and get the first value
paid = get more speed, more reach, better workflow, and better outcomes
If someone can’t feel the core benefit for free, conversion usually suffers. But if you give away the full workflow that drives business value, monetization becomes weak.
For us, the hardest part is deciding where “useful” ends and where “commercial advantage” begins.
I’d be curious how other founders define that line in their own products.
Struggling with the same questions right now for our new launch - thank you all for the productive discussion. Freemium models are great as they can create community, which leads to product improvements for both power/paid and casual/unpaid users.
my rough heuristic for builders: free = whatever demonstrates the "aha" moment on a single unit of work. paid = anything that scales that aha across volume, teams, or time (seats, runs, automations, history, integrations). mario's point about margins is real though — if you're self-funded and every free user costs you real infra $, you almost have to gate the expensive compute behind a plan or at least a meaningful usage cap. a time-limited trial of the full thing usually beats feature-gating for this, because users judge you on the ceiling of what you can do, not the floor.