What to Make Free, and What to Charge For

The price tag is the easy part. The decision that actually makes or breaks a freemium product is the value gate: what does free do, and what requires payment?

Get it wrong in one direction and users never form a habit — they see so little value they never understand why they'd upgrade. Get it wrong in the other and they never need to pay, because free already solved their whole problem. Both failures look like "low conversion" on a dashboard. They're actually the same mistake: a badly placed gate.

Good free vs. bad free

A good free tier solves the core problem well enough to be genuinely useful, and leaves the user wanting more. It builds a habit before it asks for money.

A bad free tier either does so little that no habit forms, or so much that no reason to pay ever appears.

The four principles I keep coming back to:

Free should solve the primary use case for casual users.
Paid should solve it for power users, teams, or time-critical situations.
The upgrade moment should be triggered by the user's own success, not by an arbitrary wall.
Never gate the aha moment — the first experience of core value — behind payment.

That last one is the one founders violate constantly. If someone has to pay before they ever feel the product work, you haven't built freemium. You've built a paywall with a demo.

Spotify is the cleanest example

Spotify's free tier gives you the full music catalog — with ads and no offline playback. You experience the entire product's value, then upgrade to remove the friction. You are never paying to unlock value you haven't already felt; you're paying to stop being interrupted.

That's the move: let people reach the "oh, this actually works" moment for free, then charge to make it smoother, faster, bigger, or shared.

Gate on cost, not on spite

When you do draw a limit, the ethical (and effective) version ties the limit to something that reflects real cost — storage, API calls, active projects — not an arbitrary feature you switched off to be annoying.

Good limits are:

Tied to value, not friction. Gate on usage that actually costs you money to provide.
Transparent. The user should understand exactly why they hit the wall.
Generous enough to prove value. A limit reached before the product delivers its promise produces churn, not upgrades.
Tied to a success moment. The best limits trigger right when the user just felt the value — Dropbox: storage full right after you shared a folder. Canva: out of premium elements right after you finished a design.

How I gate my own products

For ResistGate, free is the whole core loop: blocking, schedules, and local analytics — no account required. You get the full "this genuinely helps me focus" moment without paying. Pro is for the people who've already felt that and want more control over it.

I hold one rule sacred: never gate the first successful block. That's the aha moment. The day I put it behind Pro is the day the extension stops earning trust in the Web Store.

There's a failure mode on the other side too — giving away so much that you train an entire user base to expect free forever. That's a real trap, with real casualties, and it's the next note in this series.

The lesson: the gate isn't where you hide features. It's where the user's success meets your real costs. Put it there and upgrades feel earned. Put it anywhere else and you're either subsidizing strangers or extorting fans.

Part 2 of From Free to Premium. Next: the conversion-rate reality that the Spotify story hides.