There's a debate almost every consumer app ends up having: growth and marketing want to show the paywall earlier. Product and design push back. Someone says the users need to experience value before being asked to pay. Someone else pulls up the paywall impression numbers, and the argument continues ad infinitum…

Ekaterina has been in that meeting on the growth side, across multiple apps in education, health, productivity, and finance. Olha has been in the same meeting on the opposite side, representing onboarding, monetization, and product across 20+ B2C apps. Her version of events sees growth ask for an earlier paywall (or a paywall before any value is shown), and the product team refuse on principle.

What both Ekaterina and Olha agree on is that the argument persists not because one side is wrong, but because neither side has defined what ‘value’ actually means for their product and its users. Often, both sides are using the same word to mean completely different things.

We decided to work through the debate together. We’re not going to tell you where to put your paywall, but we will show you that once you define what ‘value’ actually means, the placement question mostly answers itself.

Freemium vs. curiosity: start by getting your definitions straight

The debate over showing a paywall earlier or later conflates two genuinely different growth models.

  1. Curiosity gap model: a user arrives at the paywall without having experienced the product at all
  2. Freemium model: the user has had a real experience with the product

Each model calls for a different paywall placement. Treating them as the same is where most of the confusion starts. Let’s get a few definitions straight.

The curiosity gap model is what Olha calls the flow when a user arrives at the paywall without having experienced the product at all — they might have answered questions, perhaps seen a result or a projection, but the app itself is still largely unknown to them. In short, they’re being asked to pay for something they haven’t used yet, even if they believe in it or are curious about it.

The second is the freemium model. The user has had a real experience with the product; they’ve completed something, tracked something, learned something. The paywall arrives to say: now pay to keep what you have, or to unlock what comes next.

Bonus info

There’s also a hybrid in-between model, where the user gets an idea of the value or a preview of functionality (e.g. a mock-up result or app screenshot shown during onboarding) but doesn’t experience the product personally. We’ll unpack this in-between model later.

The reason the paywall placement debate goes in circles is that (often, but not always) teams are thinking about two different strategies. Product teams are usually thinking about the freemium model: aiming to get the user to an aha! or habit moment before asking them to pay. Meanwhile, growth is thinking about the curiosity gap: looking to get a conversion signal before they lose the user, or trying to show the premium offer while motivation is highest.

Both models require different things from your onboarding, paywall copy, pricing, and the way you measure success. And what works in one model can undermine the other. Neither side is wrong, but the teams might be optimizing for different models without realizing.

Agree on what ‘value’ actually means

When your product team says "users need to experience value before they pay", they usually mean something specific: the user should complete a certain action, track something, learn something. It might be 10 lessons. A week of exercising. Fifteen logged meals. Whatever it is, the paywall should only arrive after this ‘value’ — after the product has earned the user’s attention.

Your growth team might want to show the paywall earlier because, for many apps, motivation is highest at install. So showing the paywall quickly might mean a better conversion rate. Growth will also be thinking about paid user acquisition, which needs early conversion signals. In short, not every app has the luxury of waiting for the user's peak readiness to commit.

Both of these are justified positions. They just aren't actually in conflict, and that becomes clear once both sides agree on what ‘value’ means.

Six examples of pre-paywall value

Pre-paywall value can take different shapes, depending on your growth model, your vertical, and your app itself. Here are some examples:

1. A personalized projection

The user hasn't touched the product. But they've provided enough input (e.g. their interests, their goal, their timeline) that the funnel can show them what their situation will look like once they have the app. The abstract desire becomes concrete. The paywall arrives after that moment of recognition.

Noom built its conversion model around this. After a long onboarding that asks about weight, goal, and timeline, a projection appears with a specific date attached. The outcome feels real and personal, even before the user has paid for anything.

What makes projections work is building the realization gradually rather than delivering it in one moment. At one app Olha worked with, a user who entered their weight was first shown a BMI scale on a traffic-light spectrum with plain-language copy explaining each zone. The next screen pre-filled a realistic goal rather than the aggressive number the user had entered, and flagged their own target as unsafe. By the paywall, the user felt the product was already working in their favor, even though it hadn't technically started yet.

The takeaway: the projection (or result, graph, calculation etc.) doesn't have to be the product. It just has to be real, and specific to this user's situation.

2. An emotional micro-moment

Ekaterina believes that sometimes value doesn't require a user to complete anything. A user can feel something real in four seconds on a loading screen. Or they can also go through 20 screens and feel nothing, because it wasn’t designed to deliver a feeling.

Calm and Headspace are good examples: a user opens the app looking for meditation. While the app loads, the screen shows a slow animation, instructing the user to breathe in and out. In a few seconds — during a time when the user is normally waiting around, like a loading screen — the product has already worked. Not because they accessed a library of content or completed a meditation (though this definitely brings value), but because this experience already delivered something real.

Calm has taken this beyond the app, too. As Ravi Mehta pointed out at App Growth Annual 2026, in 2024 they used a TV ad slot to give 30 seconds of silence and Calm on during the elections.

And even though we mostly talk about paywalls and early user experience in this article, it’s worth mentioning that emails can also be a great way to deliver value without the user opening the app.

Another app that does this (in a very different way!) is Death Clock. During onboarding, based on the user's answers, it shows them a statistically likely date of death. Morbid, yes. Viral? Absolutely. It might be unexpected, but that signals value too: a micro-moment so confronting that users began posting it online, even before they got through onboarding.

It’s the same with other ‘wake up’ screens, like Opal, which shows the user how many years of their life they’ll spend on social media — and how many Opal can save for them. It’s saying “What’s the cost of a subscription compared to giving back years of your life?”

Teams often miss this definition of value because they’re looking at value as a big, ongoing experience. They think “but the user hasn't experienced enough yet". Sometimes one screen that’s designed deliberately to evoke a feeling is enough.

The takeaway: value is not volume. Define the earliest-possible moment a user could feel “this app is for me”.

3. Learning something new

Some apps deliver genuine learning as a value moment inside onboarding. Noom asks whether a grape or a raisin has more calories, and the user learns something they didn't know before. They feel smarter, and associate that feeling with the product even before they’ve paid anything.

This technique works best for health, nutrition, and education apps where the subject matter itself is the draw.

The takeaway: if your product's core job is to provide knowledge or make users feel informed, you can start doing that job in onboarding.

4. Bridging the curiosity gap with empathy

The curiosity gap model that Olha identified is typical of web funnels — the difference being that the user hasn’t seen an app or store screenshots yet. Depending on your type of web funnel, what users experience before the paywall is often a set of very precise, personalized questions.

In the early days of Flo’s web funnels, the web onboarding ran under what Olha describes as a ‘curiosity gap-like funnel’. Nothing explained how the tracking worked, what the calendar looked like, or what insights users would receive. The funnel just asked carefully crafted, resonating questions about the user’s needs. It then branched based on the user's goals: for example, someone trying to conceive received a different sequence than someone who was just tracking their cycle.

This ‘just tracking’ segment was hardest to convert, as their underlying reasons for using the app were so varied. The solution wasn't to explain the product more. It was to make the questions precise enough that each user felt the app was designed for them.

A more recent example illustrating onboarding questions that illicit a feeling of 'this was made for me'

Copy plays a crucial role in this. While working on a glucose-tracking app, Olha gathered the exact phrases users used to describe their problem. She mined reviews, interviews, and Reddit threads to find real users’ problems in their own words: "I'm scared of missing a spike", "I don't know how to get unstuck", "I don't trust my tracker” rather than “I need to manage my metabolic health” and other perfectly crafted product marketing copy.

The team used those phrases as answer options in the onboarding copy. Users would read through every option, recognize their problems reflected on the list, and arrive at the paywall feeling heard. Conversion improved without any changes to the paywall itself.

This type of value isn’t just about users feeling understood by the app; it has the hidden benefit of them understanding the app. For example, in the period-tracking app, asking “Are you trying to conceive, are you pregnant, or are you just tracking?” shows everything the app can help with. A user who isn’t pregnant won’t be persuaded to convert by pregnancy features today, but it might change whether they stay subscribed a year from now, when their first ‘job’ is successfully done. It signals a longer value timeline.

This model has a failure mode, though. If the paywall behind that curiosity is too steep, e.g., with a high annual price, no trial, no evidence that the product can deliver, curiosity turns into caution. The user starts the trial, immediately cancels it, and waits to see whether the product earns their trust before they actively pay.

The takeaway: let the onboarding questions do the selling by making users feel understood. Trust breaks when the paywall asks for more than the questions have earned. Established and trusted brands escape this trap more easily.

5. A preview of the hero feature

There’s a middle ground between giving users a glimpse of the value, and giving away a full product experience: you show the user the product working, without letting users run the experience themselves.

Wispr Flow does this well: it shows you the product in action rather than listing features, and lets you see the output before you've invested much effort in the setup.

Another example is an ovulation-tracking app where users arrive mid-onboarding, after having scanned a QR code on a physical ovulation test kit. The screen shows a mock scan animation: the kit appears on screen, the scan plays out, and a result follows. Not a pregnancy promise, which would be misleading, but the answer to the question the user actually showed up with — today looks like a high-likelihood window; here is what to do with that.

The idea here is not that the animation is persuasive. It is that the user recognizes exactly what they came for, and pays because the product already feels like it works.

The takeaway: a product preview doesn't need to be functional, so long as it makes the user feel like the product already does what they need it to.

6. Freemium: experiencing the core value and getting the aha! moment

This is the freemium model: let users do the thing, reach the moment where it clicks and they fall in love with your app, and then ask them to pay to unlock more. Duolingo is the clearest example: you select a language, and you're doing exercises and translating sentences within 60 seconds. You don’t even need an account yet.

In Ekaterina’s experience, the trap teams fall into here is underestimating what it takes for a user to reach that moment in their app. Duolingo's first lesson takes a few minutes to finish and little cognitive effort. At the same time, other apps require users to connect a device (or an instrument like a guitar, which they might not even be physically near), get to a gym, make an account, or invest 15 minutes of focused attention before they get into the app’s core value.

Mobile users are often simply not in the right physical or mental place when they first open the app. The cognitive and physical effort required to reach the aha! moment is part of the equation, and teams optimizing for a generous free experience sometimes forget to ask whether users can actually get there, or whether most of them will drop off along the way.

The takeaway: if your aha! moment requires real effort or setup, map the drop-off between install and that moment before you assume the paywall placement is justified.

Two variables that impact where your value should sit

Once you've defined which type of value applies to your app and your user segments, check if these two external factors change your answer.

1. User context at install

A user who clicked a Meta ad and is sitting on a couch has a tolerance for longer onboarding. They're curious, they have time, and you can build toward a result with over 40 questions.

A user who scanned a barcode on a physical product in the middle of the grocery store wants to know right now whether it contains an allergen. Making that user go through a long flow is ignoring their context, who the user is, and what they need.

Users’ motivation follows the same logic. For many health, fitness, education, and other personal development apps, motivation is highest at the moment of install: a health scare, a new year, a friend's transformation.

But the motivation won’t stay there. In these instances, making a user solve multiple math exercises or complete a 15-minute assessment on a musical instrument isn’t better just because it can deliver more ‘value’ — it delays conversion, ignores the user's context and the effort needed to reach the paywall, and wastes the window when they're most ready to commit.

Jakub Chour writes well about the time vs. value dilemma in this old but gold piece.

The takeaway: don’t fight to show value at the expense of ignoring user context. Tailor onboarding and paywall placement to user motivation and mindset.

2. Your distribution strategy and growth engine

This is the variable that is almost always absent from the debate. If your traffic is mostly organic and branded, you can afford to be patient with the paywall. A long free experience costs you nothing in terms of campaign efficiency.

If you are running paid advertising on Meta, TikTok, or Google, you ideally need early, high-quality conversion signals. If a paywall on screen 47 generates those signals within the window, that’s great! But if not, you need to figure out how to make the acquisition model and your monetization strategy compatible. You need channel <> model fit.

You can also make the ad <> onboarding <> paywall alignment deliberate. Ultimate Guitar did it a few years back. Their Facebook ads featured specific songs. The paywall featured that same song. Users were arriving at the paywall not just to “learn to play guitar” but to master the specific song that they always wanted to play. The thread from ad to conversion was unbroken, and conversion reflected it.

Getting it right is harder now with iOS attribution gaps. But the principle applies: personalize the paywall based on what the user engaged with or told you during onboarding. The information is already there. Most teams just don't use it.

The takeaway: if you run paid acquisition, marketing should be in the room when you decide paywall placement.

Three questions to answer before you run paywall placement experiments

We won’t tell you where your paywall should be. The right answer depends on your app, your users’ context at install, and your acquisition model. But these three questions cut through the debate faster than most other approaches we've tried.

  1. What does value feel like for this specific user, before the paywall?Define it in concrete terms. Which of the six value types applies here? What is the earliest moment this user could feel “this is for me”? Name it, design it into onboarding, and put it before the paywall.
  2. What are your users doing when they open your app? What’s their context? The time-to-value should reflect their level of motivation.
  3. What does your growth model require? If you're running paid campaigns, what conversion signal can you send back, in what volume, and within what window? If you grow through virality or referrals, what is the time-to-value for those users? Either way, the acquisition model belongs in the decision, not only the product principles.

The teams that resolve the ask for money upfront vs. deliver value first debate fastest are the ones bringing definitions and data into the room. The paywall is not the villain of this story. Misaligned assumptions about what users need, and the habit of defending those assumptions without testing them, are where most of the trouble actually lives.