How do you decide what features should be free and what should be paid?

something i rarely see discussed here is that the free/paid boundary should follow your actual cost curve, not some theoretical framework about user psychology. i run a content pipeline that uses multiple AI APIs and the costs vary wildly per feature. image generation is like $0.003 per image so giving that away for free is basically nothing. but video animation runs about 7 cents per 10 second clip and thats where it adds up fast at scale.

so my rule is simple: if the marginal cost of a feature is near zero, make it free and use it as the hook. if theres real per-use cost, thats your paid tier. not because of some conversion funnel logic but because your bank account literally demands it when youre self funded.

the whole "wow moment" framing is fine but it ignores that most solo builders arent choosing between free and paid. theyre choosing between sustainable and bankrupt. i went from spending $150/mo on one service to $40-50 by just caching outputs and checking similarity before regenerating anything. that kind of engineering is what actually lets you offer a generous free tier without bleeding money.

For us at Hello Aria, the rule of thumb is: free = value that gets users hooked, paid = value that makes them stay.

Core features (basic reminders, todos, WhatsApp integration) are free — because if users don’t experience the core magic, they’ll never convert. But calendar sync, Circles (team features), and priority AI responses are paid, because those are things power users genuinely need and will pay for.

The mental model that helped most: free tier should answer "is this useful?" and paid tier should answer "can I live without this?"

Overcomplicating pricing early kills conversion. Start simple, watch what free users hit the ceiling on, and that’s your natural paywall.

For Hello Aria (AI productivity assistant on WhatsApp/iOS), our rule of thumb is: free = enough to get genuine value and build the habit, paid = the features that make it indispensable.

Concretely, free gives you core reminders, todos, and basic AI chat. Paid unlocks unlimited usage, calendar sync, meeting notes, voice-to-text, and multi-platform (Telegram + WhatsApp together).

The trick we found: don't gate by feature complexity, gate by frequency and depth. A power user hitting limits every day is a natural upgrade trigger. Someone who uses it once a week probably shouldn't be paying anyway.

Also: time-limited trials tend to create anxiety. Usage-limited trials create curiosity. Big difference in conversion psychology.

For my main tool I offer a free plan with features that most of my competitors already ask payments for and introduce more better features with API access for that tool which I put under paid plan with a 3 days free trial and cheaper rates.

one thing i dont see mentioned here is letting your actual infrastructure costs dictate the line. i run an automated video pipeline and the split became obvious once i tracked per-user costs. image generation is basically free at scale (fractions of a cent per image) so that stays in the free tier. but video animation runs about 7 cents per clip, and at volume that adds up fast. so the paywall lives exactly where my costs spike.

the conventional wisdom of "gate your best features" never sat right with me. if your best feature is cheap to deliver, keeping it free is a growth lever. gate the expensive stuff and be transparent about why. users respect "this costs me real money to run" way more than arbitrary feature locks.

One approach that worked well for many developer tools is:

Free → core usage so people can understand the value quickly

Paid → advanced workflows, automation, or scale

If the free tier lets people experience the real value, conversion usually happens naturally once they rely on the tool.

Real data point from our experience: We built 440 free browser-based developer tools as a portal. Zero revenue for months. Then we packaged the same tools as a Chrome extension with a Pro tier ($4.99/mo for offline access + bookmarks sync). The free version drives trust and traffic, Pro converts the power users who want it always available. The line we drew: if it works in a browser tab, it's free. If it needs to work without a browser tab (offline, extension popup, keyboard shortcut), that's Pro. The key insight was that convenience is worth paying for, but the core utility should never be gated. We also found that giving away 100% of the product for free first made the paid tier feel fair rather than extractive.

Great question! This is something I have thought about a lot. Here is my framework:

1. The "Aha Moment" Test - Free should get users to their first meaningful result. If they don't experience value quickly, they will churn before paying. Whatever gets them to that "aha, this works" moment should be free.

2. Usage-Based Gates Work Better Than Feature Gates - Instead of hiding features, limit usage. 5 exports per month, 3 projects, 100 API calls. Users understand this intuitively and it creates natural upgrade pressure.

3. Team Features Are the Easiest to Monetize - Collaboration, sharing, admin controls, SSO. Individual users can stay free forever, but the moment they want to bring their team, that is where you charge.

4. Follow the Cost Structure - If a feature costs you significantly more to run (AI generation, storage, bandwidth), that should be paid. Do not subsidize power users at the expense of your unit economics.

The key insight: free should demonstrate the problem exists and that you understand it. Paid should be the complete resolution.

I think it really depends on a case-by-case situation.

For CoreSight, our features (like building a business model or analyzing a stock) are free for the users because they are just the starting point for what we're building with our B2B partners.

My current product is completely free and I'm not sure that'll change. The core insight was that trust is the product — if parents have to pay to find out if a game is safe for their kid, they won't use it, and then the whole thing fails. Free removes the friction entirely and lets the tool prove itself first. Revenue conversation comes later once there's real usage to build on.