Freemium vs. one-time vs. subscription: how I chose the pricing model for my Chrome extension

When I launched my first Chrome extension, I had no idea how to price it. I just knew I didn't want to charge a subscription.

Three extensions later, I've learned a lot about what works — and what doesn't. This is the framework I use now.

The three models

1. Subscription (recurring revenue)

Most SaaS advice tells you subscriptions are the only way to build a sustainable business. But for Chrome extensions, subscriptions come with a hidden tax: user fatigue.

Every time a user sees a subscription prompt, they ask: "Is this really worth $X/month forever?" For a tool that saves 30 minutes a day, yes. For a tool that saves 5 minutes a week, no.

When it works:

The tool provides ongoing value (not just one-time)
You have server costs that scale with users
Your users are businesses (not individuals)

When it doesn't:

Your extension is a simple utility
Your users are individuals with limited budgets
Your competition offers a free alternative

2. One-time payment

This is what I chose for PR Focus ($9.50 one-time, lifetime access). It's a bet on two things:

Users trust you enough to buy upfront
You can support the product without recurring revenue

The upside: Users love it. No subscription fatigue. No "I'll cancel after I try it." Just a simple transaction.

The downside: No recurring revenue. You need to keep acquiring new users forever to sustain growth. And if you stop marketing, revenue stops.

3. Freemium (free + paid features)

This is the most common model for developer tools. Give away enough value to build trust, then charge for the premium features.

The upside: Low friction to start. Users can try before they buy. Word-of-mouth spreads the free version.

The downside: Conversion rates are usually 2-5%. You need a large free user base to make the math work. And you need to clearly differentiate free vs. paid.

How I chose for PR Focus

I started with freemium + one-time.

Free tier: multi-account GitHub switching, PR sorting/export, stale notifications. (Enough to be useful, not enough to be complete.)

Pro tier: AI summaries, risk scoring, one-click draft reviews, full stats. ($9.50 one-time.)

Why not subscription?

I'm a solo developer. Subscriptions mean handling churn, dunning emails, payment failures, and support for "I forgot to cancel" complaints. That's a full-time job on top of building the product.
My users are individuals, not companies. A developer on a personal budget is less likely to commit to $10/month forever. But they'll pay $10 once if the value is clear.
AI costs are passed through (BYOK). I don't pay for AI usage — users bring their own key. So I don't have a per-user cost that needs a subscription to cover.

The result: Freemium + one-time Pro has been the right balance. Users get value from the free tier, and the ones who need AI features pay once. No one feels trapped.

What I'd do differently

If I were starting over, I'd:

Launch with a paid beta. I gave away too much for free early on. A small beta fee (even $1) filters for genuine users and gives you early revenue to reinvest.
Charge more. $9.50 is low. I was afraid of pricing too high, but the users who get value from AI features would pay $20-30 easily. Next time, I'm starting higher.
Build the waitlist earlier. I had 0 users before launch. A waitlist of 100 interested developers would have validated the idea and given me launch momentum.

The framework I use now

Before choosing a pricing model, I ask:

Does this tool solve a recurring or one-time problem? Recurring → subscription. One-time → one-time payment.
Do I have ongoing costs per user? Yes → subscription. No → one-time.
Is my target audience individuals or businesses? Individuals → lower price, simpler model. Businesses → higher price, subscriptions acceptable.
Can I give away enough value to build trust? Yes → freemium. No → paid-only.

For PR Focus, the answers were:

Recurring problem (code review is daily) → one-time (because I don't have per-user costs)
No ongoing costs (BYOK) → one-time
Individuals → simple model
Yes, core features are useful → freemium