I made the wrong paywall call once. We gated a feature that a significant portion of our free users relied on daily — not because the revenue math demanded it, but because “premium users should get more.” Six weeks later, support tickets had doubled, free-to-paid conversion had flatlined, and we’d punished the most engaged segment of our user base. We reversed the decision. It cost us three months and a lot of trust.
The freemium paywall framework I use today came out of that mistake. Here’s how I think about what should be free — and why getting this wrong kills mission-driven products faster than anything else.
The Wrong Question Behind Most Paywall Decisions
Most freemium decisions start from the wrong end. The instinct is reasonable: if you’re building a paid tier, paying users should get more. But when that logic drives every decision, you end up asking “what should go behind the paywall?” instead of “what must stay free?”
That inversion matters more than it sounds. When you start from the free side, you’re forced to defend every gate. When you start from the paid side, you’re incentivized to move things behind walls because it feels like value creation. In my experience, it usually isn’t.
The freemium products that last built genuinely useful free tiers first, then built paid tiers that made useful things faster, deeper, or scalable. The free tier wasn’t a demo. It was a product. If your free tier is deliberately limited to drive upgrades, you’re not running a freemium model — you’re running a time-limited trial. Those are different businesses, and they attract different users with different expectations.
Two Jobs, One Product
The framework starts with a question that sounds simple and isn’t: what job is the user trying to do?
In most digital products — especially mission-driven ones — at least two distinct user jobs show up at the same front door. The personal user and the professional. The student and the practitioner. The occasional reader and the daily power user. These aren’t tiers of the same job. They’re different jobs entirely.
Conflating them into a single pricing decision produces a product that serves neither well — and a paywall that frustrates the users most likely to become your strongest advocates.
Once you’ve mapped the jobs clearly, the paywall question becomes cleaner. For each feature, you’re really asking: does this serve the user who can’t pay, the user who won’t pay, or the user who pays because the tool is genuinely worth it?
Can’t pay: Gate this, and you’ve excluded someone with no alternative. If your product serves a global audience, this is a mission failure disguised as a pricing decision. Won’t pay: Gate this, and you’ll generate complaints with minimal conversions. The feature isn’t their tipping point. Pays because the tool is worth it: Gate this correctly and you have a sustainable model.
The Four Paywall Tests
For every feature — new or existing — I run four tests in order. The order matters.
Test 1: Access. Does gating this feature prevent someone from doing the core job they came here to do? If yes, it stays free. Not “probably free” — free, as a hard constraint. A product that charges for its core value has confused its business model with its purpose.
Test 2: Job. Is the primary user of this feature a personal user or a professional? Personal = free. Professional = paid. Students are a gray zone — check your analytics to see who actually uses it week over week. The data is almost always less ambiguous than the internal debate.
Test 3: Majority World. Would someone with limited income — a volunteer, a practitioner in a lower-income country, a student without institutional backing — need this feature to accomplish meaningful work? If yes, it belongs in the free tier or needs a genuine no-cost path. Scholarship programs, geographic pricing, and educator access are all legitimate answers. “We’ll figure that out later” is not.
Test 4: Revenue sufficiency. Is there a paying segment large enough and motivated enough that this feature can sustain itself economically? A feature behind a paywall that generates no conversions is worse than a free feature. It signals to free users that you’re extracting value while delivering no business result. As OpenView’s SaaS benchmarks consistently show, freemium-to-paid conversion depends heavily on the perceived value gap — not the friction gap.
The Ideology Under the Framework
The four tests are pragmatic. But there’s an ideology underneath them that determines how you handle the hard cases — and in mission-driven products, most hard decisions are edge cases.
The ideology I work from: subscribers are mission partners, not just customers.
When a professional user pays for a tool, they’re making it possible for others who can’t pay to access something valuable. That framing only holds if the free tier is genuinely good. If the free tier is deliberately weak to force upgrades, you’re not distributing access — you’re withholding it and calling it generosity.
This connects directly to how I think about subscription products for ministry — the paywall philosophy and the subscription model are two sides of the same decision. Get one wrong and you’ve undermined both.
Where AI Makes This Harder
Every product team is about to face a version of the same question: where does AI land in the framework?
The professional-tools category is relatively clear. AI features that accelerate professional workflows — research assistants, document generation, structured analysis — belong in paid tiers. The value is concrete, the willingness to pay is real.
The personal-use category is harder. An AI that helps someone understand a difficult concept or access something they couldn’t reach before — is that a professional tool, or is it closer to a core access feature? If you gate it, you’ve made a decision. That decision might be right for the business. It might not be right for the mission. Those aren’t the same thing, and pretending they always align is how you end up making the wrong call at the edge cases.
The products that age well are the ones that answered that question from the mission side first and built the revenue model around the answer.
The Clarity You Owe Your Users
The mistake I described at the start wasn’t really a pricing mistake. It was a clarity mistake. We hadn’t named what we believed about our users, so we defaulted to what we thought premium users deserved instead of what free users needed.
The framework above doesn’t eliminate that tension. It makes it visible. When you can map the jobs, run the four tests, and state the ideology out loud in a room with your team, you at least know what tradeoff you’re making.
Your Turn: Apply This Today
Walk your current or next paywall decision through this framework before your next pricing review:
- Categorize every feature as acquisition or retention. Go through your feature list and sort each into: “this brings users in” vs. “this keeps users coming back.” Acquisition features belong in free. Retention features belong in paid.
- Identify your “aha moment” and protect it. What is the single experience that converts a skeptic into a believer in your product? Make sure every user reaches it before they hit a paywall. If the aha is behind a gate, you’re metering the wrong thing.
- Map your mission-critical users. Who are the users whose engagement creates value for everyone else — contributors, creators, community members? Consider whether paywalling them is worth the cost to the overall ecosystem.
- Run a “free tier audit.” List everything currently free. For each item, ask: is this generating acquisition or just giving away margin? Remove or gate anything that isn’t actively driving new user acquisition or ecosystem health.
- Test your paywall message before your paywall decision. Show users a description of your paid tier before you build it. Does the value proposition make them lean in or shrug? If they shrug, you haven’t found the right gate yet.
- Set a paywall conversion benchmark. Decide in advance what free-to-paid conversion rate would validate your model. Build toward that number. If you hit 6 months without reaching it, revisit what’s behind the gate.
Navigating freemium strategy, pricing philosophy, or subscription model design? These are decisions I’ve made across multiple faith-tech products. Let’s think through it together.