# Paywall moved to the start of onboarding: revenue up 5x

- Outcome: Won
- Page type: Paywall (App)
- Elements: Paywall timing
- Date shared: 2020
- Test run by: [Rootd](https://liftarchive.com/practitioners/rootd/)
- Commentary by: LiftArchive (our analysis, not theirs)
- Original source: https://www.revenuecat.com/blog/growth/paywall-tests-grow-app-revenue/
- Page: https://liftarchive.com/test/rootd-paywall-at-start-of-onboarding/

Rootd moved its paywall from later in the app to the very start of onboarding, and revenue grew 5x. Rootd, a panic attack and anxiety relief app, made the change in 2020; founder Ania Wysocka told the story on Sub Club, and it was later published on the RevenueCat blog. This was a before-and-after change, not a split test.

## Result

**Revenue 5x**

- Revenue: up 5x after the move. This is the only number shared.
- User reaction: the founder reported almost no negative feedback, since people are used to seeing paywalls early.
- Not shared: trial start rate, trial-to-paid, refunds, retention, sample size or how long the before and after periods ran.

## Control

The paywall was kept out of the early journey. The founder worried that a paywall up front would get in the way of users who wanted relief right away.

## Variant

The paywall was moved to the beginning of onboarding, so every new user saw the offer before going further.

## Why it likely won (our reading)

- Many users never reached a paywall placed later in the app. Putting it first means every install sees the offer at least once.
- Right after install is when intent is highest. A user who just downloaded an anxiety app has a clear reason to want it to work.
- The fear of putting users off seems to have been overstated. Paywalls early in onboarding were already common, so the screen felt normal.
- Other things may have changed in the same period. A before-and-after comparison can't separate the paywall move from seasonality or traffic mix.

## Caveats

This is a before-and-after change retold from a Sub Club podcast episode, not a controlled A/B test, and the test design, sample and duration were not shared.

## How to run this test

- Hypothesis: If we show the paywall at the start of onboarding instead of later in the app, then revenue per install will rise because every new user sees the offer while intent is highest.
- Primary metric: Revenue per install (or install-to-paid conversion)
- Guardrail: Onboarding completion rate
- Guardrail: Trial-to-paid conversion
- Guardrail: Day-7 and day-30 retention
- Who should test it: Apps whose current paywall is reached by only a share of new users, or is hidden behind feature use. It may fit less well if the app needs to deliver value before the user can judge it, or if a big share of revenue comes from users who convert weeks later.

---

Credit: Rootd ran this test and owns the result. Summary and commentary by LiftArchive (https://liftarchive.com/test/rootd-paywall-at-start-of-onboarding/).
Usage: Free to use, quote and build on, with credit and a link: name the practitioner or organization that ran the test and link to its LiftArchive page. The results belong to the practitioners who ran and shared them; the summaries and commentary are LiftArchive's.