Skip to content
AppDues
Log in
Contact salesSign up

How a Mobile App Raised ARPU 60% in Five Months: Paywall and Pricing Playbook

In a first-person account, Mojo's product growth lead described a 60% rise in ARPU7D — realized lifetime value per new user over seven days — across five months, while keeping engineering effort low. The work centered on three levers: making the yearly plan the default and near-only visible choice, testing country-specific prices, and presenting annual billing as a monthly figure. This guide restates those levers as a testable sequence, adds a decision checklist, and flags the guardrail metrics that tell you whether a lift is real or borrowed from the future.

Context: what the 60% figure measures

The headline number is ARPU7D, defined in the original account as realized LTV per new user within seven days. That window matters: it captures early conversion and plan mix, not full-year retention. A team optimizing only for ARPU7D can look successful while pushing risk into later months, which is why the original team also tracked a 13-month revenue prediction and a 7-day cancellation rate as a proxy for churn.

The reported gains came with minimal engineering resources. The account attributes that speed to paywall infrastructure that allowed rapid deployment and copy/design edits, product analytics for fast insight retrieval, and a subscription platform the author used to monitor cohort-based ARPU across different conversion and lifetime windows. The author notes that this platform's simplicity and accuracy are its strengths, while it does not offer vast filtering and analytical capabilities. Treat the tool names in the original account as that team's stack, not a requirement for yours.

The team launched dozens of paywall and pricing experiments over a few months and reports a success rate above 70%. The author attributes that rate to thorough prior research, ideation, and prioritization rather than to luck, and notes that such a rate is not usual.

Lever 1: Make the yearly plan the default and near-only choice

The paywall previously showed yearly and monthly plans side by side. The team tested showing only the yearly option, with the monthly plan reachable through a "View All Plans" link. The reported result was a 15–20 percentage point increase in the share of yearly subscriptions.

A follow-up experiment isolated the cause: the decisive factor was moving the 1-month subscription option behind the "All plans" link, not the other visual differences between variants. That is a useful lesson — when a layout test wins, rerun a stripped-down version to confirm which element did the work before you build on it.

The team expected the cancellation proxy to rise for two reasons: yearly plans typically carry higher cancellation rates, and a simpler screen invites more spontaneous decisions that users may later regret. In their case the increase was minor. Your result may differ, so measure it rather than assume it.

Lever 2: Test prices by country instead of trusting a default conversion

Changing actual prices had a large effect. In markets such as the USA and Germany, yearly prices for new users rose 50% with little damage to free-to-paid conversion. In Brazil, lower prices proved better in both the short and long run.

The method matters more than the numbers. The team set each test price individually rather than letting the platform mirror USD or EUR automatically. They usually tested one or two alternatives, and when signals suggested a market might be overpriced — low new-to-trial or paid conversion, local purchasing power, competitor comparison — they made sure a lower price point was among the variants.

Two criteria guided each pricing test: impact on new revenue during the 7-day conversion period, and impact on a 13-month revenue prediction that accounts for the yearly/monthly mix and cancellation, using the 7-day cancellation rate as a proxy. Keeping both in view prevents a short-term win from masking a long-term loss.

Lever 3: Anchor the annual price to a monthly figure

Presenting the annual price as "$X/month, billed annually as XX/month" was especially effective in lower-income regions. Reported increases in new revenue per paywall impression were 45% in Brazil, 26% in Mexico, and 8% in the USA. The lift came from higher paywall-to-trial conversion and a larger share of yearly plans.

One constraint: Apple has guidelines and limits on how prices may be presented, so any test has to sit inside what the platform allows. Check the current rules for your storefront before designing the variant.

A decision checklist before you run these tests

Use this sequence to avoid conflating layout, price, and presentation changes:

  1. Define the metric window. Decide whether ARPU7D is your headline or a leading indicator, and name the longer-window metric (for example a 13-month prediction) that guards against borrowed growth.
  2. Isolate the layout variable. If you hide the monthly plan behind a link, rerun a stripped variant to confirm that the link move — not other design changes — caused the shift.
  3. Set prices per market. Do not accept an automatic currency mirror as your test price. Include a lower variant when conversion or purchasing-power signals suggest overpricing.
  4. Watch the cancellation proxy. A rise in the 7-day cancellation rate is expected when yearly share grows; decide in advance what size of rise would reverse the decision.
  5. Respect store rules. Confirm current Apple price-presentation limits before shipping an anchored annual price.
  6. Log the decision. Record variant, market, primary metric, guardrail metric, and the threshold that would trigger a rollback.

Worked example: reading the Brazil annual-anchor result

The Brazil annual-anchor test reported a 45% increase in new revenue per paywall impression. That metric is not the same as ARPU7D. It divides new revenue by impressions, so it rises when more viewers convert, when converters pick the yearly plan, or both. The account attributes the Brazil lift to higher paywall-to-trial conversion and a larger yearly share.

To use this as a template: if your own per-impression revenue rises but trial starts are flat, the gain likely came from plan mix; if trial starts rise but yearly share is flat, the gain likely came from the presentation itself. Splitting the metric this way tells you which follow-up test to run next.

Failure distinction: three different signals, three different responses

A drop in free-to-paid conversion after a price increase usually means the new price exceeded what that market will bear; the response is to add a lower variant, not to abandon price testing. A rise in the 7-day cancellation proxy after hiding the monthly plan is an expected side effect of a higher yearly share; the response is to set a tolerance threshold in advance and compare the revenue gain against it. A flat 13-month revenue prediction despite a higher ARPU7D means the short-term lift is being offset by later churn or plan mix; the response is to hold the change and investigate retention before scaling it.

Treating all three as "the test failed" hides which lever actually needs adjusting.

Why monetization is a product-and-marketing job

The original account stresses that monetization sits between product and marketing. Install quality correlates with monetization, so attribution and budget allocation across platforms, channels, and countries affect how well a paywall change performs. Better monetization raises ROI, which can support higher spend, which in turn produces larger samples for the next round of experiments.

The team also credits a strong product and organic word-of-mouth as foundations; a paywall test cannot rescue weak retention. Treat pricing work as one layer on top of product quality and acquisition quality, not a substitute for either.

What the team planned next

At the time of writing, the team was testing a longer free trial for yearly plans, moving from 3 days to 7 days, with promising early results in key markets. A full rollout would require shifting the effectiveness metric from ARPU7D to ARPU14D and reassessing marketing ROI measurement. Later plans included discount campaigns, adjusting the ratio of gated to ungated features and content, and revisiting price tests. The account cites a Sub Club episode with Headspace practitioners recommending price retesting at least every six months.

These are that team's plans, not a prescription. The transferable point is that changing a trial length changes your measurement window, so update the metric before you read the results.

Frequently asked questions

What does ARPU7D mean in this case?

It is realized lifetime value per new user measured over seven days. It captures early conversion and plan mix, not full-year retention, so pair it with a longer-window metric such as a 13-month revenue prediction.

Why did hiding the monthly plan increase yearly subscriptions?

The reported 15–20 percentage point rise in yearly share followed a test that showed only the yearly option, with monthly behind a "View All Plans" link. A follow-up experiment confirmed the decisive factor was moving the 1-month option behind that link, not the other visual differences.

Should I let the app store convert my prices automatically?

The original team set each test price individually rather than mirroring USD or EUR. They usually tested one or two alternatives and included a lower price when conversion or purchasing-power signals suggested overpricing.

How large was the annual-price anchoring effect?

Reported increases in new revenue per paywall impression were 45% in Brazil, 26% in Mexico, and 8% in the USA. The lift came from higher paywall-to-trial conversion and a larger yearly share. Apple's price-presentation guidelines constrain how the anchor can be shown.

Will hiding the monthly plan raise cancellations?

Expect a possible rise in the cancellation proxy for two reasons: yearly plans typically have higher cancellation rates, and a simpler screen invites more spontaneous decisions. In the reported case the increase was minor, but you should set a tolerance threshold in advance.