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
CharpstAR
Great question, Nika. I think about this a lot because I'm building in this exact space.
I built Signbee — an e-signature API designed for AI agents. So literally my product lets agents handle legally-binding documents. Which means I've had to sit with this question deeply: where does the trust boundary actually sit?
My take: trust the agent with execution, never with authority.
What I mean is — an AI agent can draft a contract, send it to a signer, and track the status. That's execution. But the human still has to read and sign it. That's authority. The agent never holds the pen. That distinction matters.
Same principle applies to your examples:
Finances: I'd let an agent prepare an invoice or flag an anomaly. I wouldn't let it approve a transfer. (The Sapiom news is interesting but notice — it's agents buying tools, not making investment decisions.)
Health: Let an agent summarise your lab results. Don't let it decide your treatment.
Communication: Let an agent draft a message. Don't let it send without review. At least not yet.
The pattern is: AI handles the workflow, humans hold the checkpoints.
That's actually why I built Signbee the way I did — the agent can orchestrate the entire signing flow via API, but there's always a human at the signature step. The protocol itself enforces the trust boundary.
As for the Sapiom raise — I think it's less about "trusting agents with money" and more about infrastructure catching up. Stripe just launched MPP (Machine Payments Protocol) this week. Cal.com has Cal.ai for scheduling. AgentMail handles email. We handle signatures. The stack is forming, and each layer has its own trust model baked in.
The real question isn't if we'll trust agents — it's whether the tools they use are built with the right guardrails. That's on us as builders.
minimalist phone: creating folders
@michaelbeckett But with this agentic-led approach, doesn't it make people lazier and not care about the content they are about to agree upon?
CharpstAR
@busmark_w_nika with a human in the loop it shouldn't be the case, but as we can see from AI generated LinkedIn content these days laziness might become an issue
minimalist phone: creating folders
@michaelbeckett well, LinkedIn is weird. I can see many AI comments, many AI posts and me, who contributes manually, so they restricted me.
I'm about to launch a desktop app called Notion Launcher and dealing with this exact question right now. Can't decide between limiting features or limiting usage count on the free tier. Feature-gating feels cleaner, but usage limits let people try everything before they commit. Anyone here tried both and found one converts better?
minimalist phone: creating folders
@ray_artlas What will be the tool about?
@busmark_w_nika It's called Notion Launcher. A macOS app that lets you save stuff to Notion databases with keyboard shortcuts without ever opening Notion. Memos, highlighted text, screenshots, bookmarks, all from any app. Working on Windows support too. Still figuring out where to draw the line between free and paid features, which is why this thread really resonated.
This is such a real problem.
As creators (and builders), we’re constantly walking a thin line between building trust and giving away too much.
Free content/products bring attention and credibility.
But if you overdo it, you risk removing the need to convert.
What’s worked for me (and what I’ve seen work well):
Free = demonstrate value
Paid = deliver outcomes
Free should make people say “this is useful”
Paid should make them say “this solves my problem”
Curious how others here think about this,
Do you draw the line based on usage, features, or outcomes?
minimalist phone: creating folders
@pratham_khodwe How do you solve this for content creation? Since getting information is really cheap and accessible in this AI era.
I run a website that sells phone cases with AI generated designs. This is how I split the free and paid "tiers":
- Let users create the designs for free (even though it costs me a substantial amount of money)
- Only charge users when they buy a case.
Requesting payment is always a source of friction. If you do it too early customers will walk away without getting to know your product. For example, if I charged people money just to design a case, most people wouldn't even try it. In my opinion, the best approach is to give the customer the opportunity to fall in love with your product, then offer a paid option. When it comes to my business, the customer is most likely to open their wallet when they're looking at their dream phone case design, which is why I absorb the AI token costs and let them design it for free.
minimalist phone: creating folders
@spencermoon99 This is a cool model + also the option to receive something physically, I think you have a goldmine :D how many users use this service? + where do you manufacture cases? I think it would be interesting to see the process.
@busmark_w_nika The user base is still very small because I stink at marketing, but it's slowly growing as I learn how to better promote it. I use a print on demand service to handle manufacturing and shipping.
minimalist phone: creating folders
@spencermoon99 I need to say, that admire this... not many people do also physical in this space, usually see people building only online :)
I would suggest looking at it the other way around: Define what's the conversion rate you want to see, and work from there.
The Freemium model is always a trade-off: Collecting users vs making income. The balance dictates the conversion rate.
I'm currently thinking about the exact same question for a product I'm working on, and this is how I try to think of it:
When considering the free/paid features, I always imagine it as a giant slider, where its left side point to free users, and the right one - to paid ones. Now, what do I prefer? So on the one hand - paying users are always great. On the other hand - a not-so-happy free users will never become paid ones, and users, even free ones, are a great resource that can be used for other endeavors.
So first I think about the goal - free users vs paid users - and from there I take it to the features parity.
minimalist phone: creating folders
@memi_lavi What product are you working on? :)
@busmark_w_nika A Chrome extension that analyzes the page you're in and makes it easier to understand across countries / timezones etc. A bit vague, I know, but I'm still working on the main idea...
This is an interesting post. I'm struggling with this today. Its definitely harder as a bootstrapped founder trying to find that balance to drive traffic and create revenue. Each part of the product has to have value. Value to get the traffic, then depth to expand the following and increase revenue. Its a delicate balance, but critical and could also be the factor in either success or failure of your new company.
minimalist phone: creating folders
@wereframe Bootstrapped usually give a price tag from day one (esp. when they do not have well-paid jobs) and maintenance costs something too.
The framework I've settled on after a few product cycles: free = diagnosis, paid = prescription.
Free content shows the user their problem clearly. Paid content gives them the exact fix. The moment your free tier solves the problem, you've destroyed the reason to upgrade.
For micro-SaaS specifically, I've found the usage-based gate converts better than feature-gating — let users access the full product, but limit runs/outputs/reports. They get to feel the full value before hitting the wall. The conversion conversation becomes 'do you want more of this?' rather than 'unlock this feature you've never seen.' Much easier sell.
One thing that's underrated: validate that your paid tier is solving a real bleeding pain *before* building it. I run thevibepreneur.com which validates micro-SaaS niches with buyer proof — the same lens applies to pricing tiers. What are people already paying for? Start there.
minimalist phone: creating folders
@vatsmi What you said... maybe I am giving too much value because people started talking whether I want to create some paid community lol
I usually stick to the "How vs. What". The "What" is free, but the "How" is paid
minimalist phone: creating folders
@yisak_mebrate I wish to have it so easy in content products! :D
Okan
Your general versus tailored approach translates perfectly to how I think about SaaS pricing, where it usually comes down to core utility versus convenience. I always make sure the free tier solves the user's primary problem completely so they actually experience that "aha" moment without hitting a frustrating paywall. Once they need to scale their volume, automate workflows, or invite team members, that creates a natural friction point where upgrading feels like a no-brainer.
minimalist phone: creating folders
@y_taka I think that I need to reconsider my pricing strategy, i think that I am offering too much for free :D
I personally think if it is not using much of any infrastructure like server cost or anything else and its gonna help people, I would make it free.
But on the other hand there are also people who think Free = cheap stuff or just want limelight, so you have to put a minimum so they understand the value, only if they and then serious people will be at your platform who actually understands and value your product.
minimalist phone: creating folders
@anshumaanvishnu Well, in that case, when I wanna charge, I need to come up with more features I will put behind the paywall.