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
The free boundary should sit just before the point where personal context becomes necessary. Generalized tools and content build trust; the moment the system needs to reason over a user's specific data, history, or goals, that is where the paid layer begins. In my own work on AI advising and research tools, I have found that free tiers work best when they demonstrate the product's reasoning quality without requiring deep personalization, while paid tiers unlock memory, adaptation, and agentic support that only make sense once a user is committed enough to invest their own information.
Honestly, I've gone back and forth on this more times than I can count. My current thinking: free should make someone's life slightly better, paid should make it meaningfully better. The moment you start gatekeeping the thing that actually solves the problem, people just leave. But give everything away and you're basically running a charity. I think the real question isn't 'what do we charge for' — it's 'what would someone genuinely miss if it disappeared?' That's your paid feature. Everything else is marketing.
We did a lot of research with our ICP before launch, then with real users post-launch. We have never shied away from saying this is our MVP, and we're constantly making changes and updates. We're upfront about the costs being low while we are in the early stages. People respond really well to that. I think they like to be part of shaping something. We also researched what we would spend on acquisition and decided that a very low-cost entry point (then quickly upgrade) negates a lot of the acquisition cost.
We free the wedge (MIT importer + local CSV parse + core terminal) and charge for depth (full risk analytics, Insights, unlimited stateless AI). Open Portfolio sells the same boundary into their cloud — generalized OSS in public, tailored infra in contract.
Core editor and documents: free. AI component generation: 20/month free, 200/month for Pro ($8). The logic: free gets you in the door, AI is the value that retains. Anything you can do without AI stays free that's the floor. Anything that creates real output goes behind the limit.
It’s the same pain for creators and builders. How much do I give away before I accidentally become my own free version.
Free is easy. You say general stuff, sound helpful, feel generous, sleep well.
Paid is where it gets awkward. Because now it’s “well it depends” which is just code for I need time, context, and yes money.
And the funny part is, you always feel like you’re giving too much away… until you try charging, then suddenly even your most basic insight feels like a premium feature behind a paywall you forgot to build.
So yeah the line exists. It just keeps moving every time you get slightly better at what you do.
The way I think about it is:
Free = clarity.
Paid = precision.
Free should help people understand the gaps, and paid should help them close it with more context, structure, and support.
I have found this distinction useful while building my own product too: don’t put the first moment of clarity behind a paywall. Put the deeper, more specific transformation there.
I draw the line at trust, not features. Free should be everything it takes to prove the thing actually works on your real input, and paid starts the moment you'd be annoyed to lose it. The mistake I see a lot is gating the proof, because then nobody gets far enough to want the paid part.
memi
My rough rule: free should prove the product’s core value quickly, paid should unlock scale, repeat usage, collaboration, or saved time. If the free tier never reaches the “aha” moment, conversion will be weak no matter how good the paid plan is.
the rule i use. anything that benefits the user gets free. anything that benefits a third party who profits from the user gets paid. for TAM Network the user side is free for life. publishing receipts, browsing, networking. the paid side is for employers who want to search the verified pool. the user never pays. the platform stays on the side of the person whose work is on it.