All posts
OPERATIONS

iOS subscription revenue forecasting: building a simple model for indie developers

A step-by-step guide to building a 12-month revenue forecast for your iOS subscription app — using trial conversion rate, churn, and ARPU as inputs, with sensitivity analysis and real App Store Connect data sources.

By the AppsOps team · · 8 min read

Revenue forecasting sounds like enterprise finance. In practice, it is a spreadsheet with five inputs that tells you whether your app's current pricing will cover costs in six months — and which lever to pull when the numbers look wrong.

This guide walks through the mechanics of building a simple but realistic 12-month revenue model for an iOS subscription app. It is aimed at indie developers and small teams who have launched or are about to launch, and who want a number they can trust rather than a number that looks good in a pitch deck.

Why every subscription app needs a revenue forecast

A one-time purchase app has a simple revenue model: downloads × price. A subscription app does not. Subscribers join, renew, and churn in an ongoing process that makes revenue in month 12 very different from revenue in month 1 — even if you never change your price or your marketing spend.

Two dynamics drive this complexity.

First, cohort compounding: each month you add a new group of subscribers who churn at different rates depending on how long they have been subscribed. Month-one churn on iOS tends to be substantially higher than month-six churn. RevenueCat's annual State of Subscription Apps reports have consistently shown that the first renewal is the hardest to win, with many apps losing a significant share of new subscribers before that first renewal depending on category and trial design.

Second, trial lag: if you offer a free trial (and for most subscription categories, industry data suggests you should), there is a gap between a user starting a trial and appearing in your revenue. A 7-day trial means a user acquired on day 1 of the month does not become a paying subscriber until day 8 at the earliest.

Without a model that accounts for both dynamics, your monthly revenue projections will be wrong — usually optimistically wrong, because naive models assume all trials convert immediately and no one ever cancels.

A forecast is not a prediction. It is a structured way to surface your assumptions so you can test them against real data as each month closes. The output matters less than the habit of comparing forecast to actual and updating your inputs when they diverge.

The five inputs your model needs

A workable iOS subscription forecast needs exactly five numbers. You can start with educated guesses and replace them with real data as your app accumulates subscriber history.

1. New trials per month (T)
How many users start a free trial in a given month. If you do not offer a trial, this is simply new subscribers. Source: App Store Connect → Subscriptions → Introductory Offer report, or your StoreKit transaction data.

2. Trial-to-paid conversion rate (C)
The percentage of trial starters who become paying subscribers after the trial ends. This varies considerably by app category and trial length. RevenueCat's benchmarks have shown a wide range across categories — productivity and utility apps tend to convert at higher rates than entertainment or lifestyle apps, but these are directional ranges that depend heavily on your paywall, onboarding, and the value delivered during the trial period. The post on iOS paywall design patterns covers the structural changes most likely to move this number.

3. Monthly churn rate (Ch)
The percentage of active paying subscribers who cancel or lapse in any given month. This is distinct from trial churn. A 5% monthly churn rate sounds modest until you compound it: it implies roughly 46% annual churn, meaning you need to replace nearly half your subscriber base each year just to stay flat.

4. Average revenue per user per month (ARPU)
For a single-tier subscription, this is your monthly price × (1 − Apple's commission rate). For apps with both monthly and annual plans, weight by the proportion of subscribers on each plan, converting annual subscribers to a monthly ARPU figure (annual price ÷ 12 × net commission factor). The post on how Apple calculates your net proceeds has the full commission rate breakdown including the Small Business Program's 15% rate.

5. Starting subscriber count (S₀)
If you are pre-launch, this is zero. For an existing app, pull your current active subscriber count from App Store Connect's Subscription Status report.

Building your 12-month forecast

With those five inputs, a monthly model follows a simple recurrence:

Run this forward 12 months and you have a monthly revenue schedule. The table below shows three scenarios for a hypothetical productivity app priced at $9.99/month — net approximately $8.49 after the 15% Small Business Program commission — with 200 new trials per month and a 7-day free trial.

Scenario Trial conversion Monthly churn Month 1 MRR Month 6 MRR Month 12 MRR
Optimistic 60% 3% ~$1,020 ~$5,680 ~$10,400
Base case 45% 6% ~$765 ~$3,950 ~$6,670
Pessimistic 25% 15% ~$425 ~$1,410 ~$1,940

Note that the pessimistic scenario adds only ~$530 in MRR between month 6 and month 12, compared to ~$4,720 in the optimistic case. At 15% monthly churn, the subscriber base is approaching its steady-state ceiling and barely growing despite constant new acquisition. This is the churn trap: high churn absorbs almost every new subscriber you add.

46% annual subscriber loss implied by a 5% monthly churn rate — you need to replace nearly half your base each year just to hold revenue flat

Sensitivity analysis: which input matters most

Not all five inputs are equally important. Changing one at a time while holding others constant reveals which lever has the highest leverage on 12-month MRR.

For most early-stage subscription apps, the ranking tends to look like this:

  1. Monthly churn rate dominates at scale. Because churn compounds monthly against your entire existing base, a 2-percentage-point improvement (say, 6% → 4%) has a compounding effect that, over 12 months, often outweighs doubling your trial acquisition. Research from Phiture and other mobile growth consultancies consistently shows that reducing churn is more capital-efficient than increasing acquisition to offset it.
  2. Trial-to-paid conversion is the highest-leverage input in the first three months, before your subscriber base has grown large enough for churn to dominate. A 10-point conversion improvement in month 1 is pure upside that compounds forward through the subscriber base.
  3. New trials per month matters most once churn is already low. If you have solved retention, volume becomes the primary growth lever. Throwing more users into a leaky bucket first does not solve the underlying problem.
  4. ARPU is consistently underweighted. A 20% price increase is mathematically equivalent to a 20% increase in acquisition volume, but requires no additional marketing spend. The post on how to raise your iOS subscription price without hurting renewal rates covers the mechanics of doing this safely.
  5. Starting subscriber count matters most for established apps. Your current base is your floor, and it earns revenue while you sleep.

The practical implication: if your model shows flat or declining MRR by month 12, diagnose churn before adding acquisition budget. RevenueCat's subscriber data has consistently highlighted that the majority of iOS app revenue at scale comes from retained subscribers, not new-to-paid conversions in the current month.

Calibrating inputs with real App Store Connect data

Estimates are a starting point. App Store Connect provides several reports that let you replace guesses with actuals as your app accumulates history.

Trial conversion: In App Store Connect, navigate to App Analytics → Subscriptions → Subscription Opt-Ins and Conversions. This report shows how many users started a trial and how many converted to paid in a given period. Filter by subscription group to isolate individual plans. Note that Apple's conversion metric uses a slightly different calculation window than raw StoreKit transaction data, so cross-reference the two if you see discrepancies.

Monthly churn: The Subscriber Retention report under Subscriptions → Retention shows cohort-level survival curves — the share of subscribers from a given month still active after 1, 2, 3, 6, and 12 renewal periods. This is the most direct source for churn inputs, broken down by subscription duration. You can also estimate gross monthly churn manually by comparing active subscriber counts month-over-month and adjusting for new subscribers added during the period.

ARPU: The Subscription Revenue report under Sales and Trends → Subscriptions shows proceeds by subscription period. Divide total monthly proceeds by average active subscribers for that month. These figures are already net of Apple's commission and applicable taxes — no further adjustment is needed for forecasting purposes.

Pre-launch calibration: If you have no subscriber history yet, App Store Connect's Peer Group Benchmarks (under Analytics → Peer Group Benchmarks) provide category-level conversion and retention ranges for apps in the Apple Developer Program. These are directional, not prescriptive, but far better than guessing in a vacuum. You can also use RevenueCat's published State of Subscription Apps report for category benchmarks as a secondary reference point.

Build your model in a spreadsheet you will actually maintain. A forecast that lives in your head is not a forecast — it is optimism. Review it monthly, update your inputs with the previous month's actuals, and track the delta between predicted and actual MRR. The divergence tells you which assumption needs correcting.

Connecting the forecast to pricing and planning decisions

A revenue model earns its keep when it informs decisions, not just reports them. Three practical applications:

Price change impact modelling: Before raising your price, run the model with the new ARPU alongside a conservative estimate of short-term churn uplift (price changes typically cause a temporary spike in cancellations among existing subscribers). If your model suggests revenue recovers within three months, the price increase is likely worth taking. Remember that Apple's grandfathering rules mean existing subscribers on a lower price are protected until you actively notify them — see the post on Apple's grandfathering rules for how this affects your timing.

Marketing budget sizing: If your base case reaches a target MRR at month 9 organically, you can calculate the value of accelerating that by two months through paid acquisition. Multiply two months of projected MRR by a simple discount rate that reflects your cost of capital or runway constraints. If the result is larger than the acquisition spend needed to shift your trial volume materially, the campaign has a positive return.

Break-even analysis: Divide your fixed monthly costs by your net ARPU to get the subscriber count needed to break even. Compare that number to your base-case forecast. If you reach break-even at month 8 in the base case but month 14 in the pessimistic case, you now understand your runway exposure concretely — and you know exactly how much your churn rate matters to reaching sustainability.

Sources and further reading

Share this post

Ready to put this into practice?

AppsOps is the first App Store ops dashboardPPP-fair pricing for 175 App Store territories, AI metadata localization in 39 languages, AI screenshot localization for 14 Apple device classes, and one-click App Store Connect API push — all from one dashboard, all for $19/month.

Try AppsOps free — no card →

Related reading