ActivationPal

App Revenue Estimate: How Accurate Is It?

An app revenue estimate is a modelled guess, not a reported figure. An outside tool cannot see an app's store account, so it infers downloads from public signals and multiplies them by an assumed revenue per download. That gives a useful sense of scale and a poor exact number.

How to estimate app revenue

The formula is one multiplication: daily downloads times revenue per download times the number of days. As arithmetic with round numbers, 500 downloads a day at $1.20 per download is $600 a day, about $18,000 a month. That is an explanation, not a typical result.

You supply two inputs:

  • Daily downloads. For your own app, read measured installs in ActivationPal. For a competitor, take the downloads an estimator shows.
  • Revenue per download. For your own app, divide measured revenue by installs. For a competitor, use the estimator's implied figure, or its revenue divided by its downloads.

To run the formula across several scenarios, use the app revenue calculator.

How an app revenue estimate is made

An estimator builds the same two inputs without seeing the app's account, in three links, and each one is an assumption.

  1. A visible signal. The tool reads something public, usually the app's chart rank in one country and category.
  2. A downloads model. It converts that rank into daily downloads with a curve fitted to apps whose numbers it does know. See how App Store ranking works for what moves rank.
  3. Revenue per download. It multiplies downloads by one assumed average.

A download is also not an install. An install is the first time a device opens the app, so a download that never opens the app does not count. RevenueCat makes the same point about its own counts: its New Customers card is expected to differ from the download numbers the stores publish.

Why app revenue estimates are wrong

Four things move an estimate away from real revenue.

  • One rank curve for every app. The model applies a single rank-to-downloads conversion, so apps in different countries and categories get the same treatment.
  • One revenue per download. Free apps, paid apps and subscriptions earn very differently per download. A single average overstates an app with a weak paywall and understates one with a strong one.
  • Revenue that is not a download. A renewal earns money with no new download, a refunded first payment earns none, and a purchase at a web checkout never touches a store chart.
  • Gross is not what the developer keeps. Apple's Small Business Program cuts the commission to 15% for developers under its proceeds threshold, and Apple defines proceeds as sales net of its commission and certain taxes and adjustments. An estimate of gross sales overstates proceeds.

How to sanity-check an app revenue estimate

Test the estimator on an app whose real revenue you know: your own.

  1. Find the estimator's revenue and download figures for your own app, for one country and one month.
  2. Open the same app and period in ActivationPal and read measured Revenue, Purchases and Installs. They come from RevenueCat or Superwall webhooks, with new subscriptions, renewals and one-time purchases split.
  3. Divide the estimate by the measured revenue. That is the error ratio.
  4. Divide the estimator's revenue by its downloads to get its implied revenue per download. Compare it with your measured revenue per install, remembering an install is a first open and a download is not.
  5. Apply the error ratio to the competitor as a range, not a point. Then check the result against the competitor's price and a plausible share of installs that pay.

A worked line, with round numbers: the estimate for your app is $5,000 and your measured revenue is $2,000, so the estimate runs 2.5 times high. A competitor shown at $50,000 by the same estimator would be about $20,000.

Check that both figures are gross or both are net before you divide. RevenueCat's Revenue card, for example, is gross revenue before store fees and taxes, so a net figure will look smaller for no modelling reason.

Competitor app revenue: what you can conclude

Use an estimate for order of magnitude. $2,000 a month and $200,000 a month are different businesses.

Use it to rank apps against each other through the same estimator. The same rank curve and the same revenue per download apply to both apps, so the order can hold even when the values do not.

Do not use it for a point value. Revenue per user depends on what users pay, so read ARPPU versus ARPU before you set a revenue per user for a competitor.

Frequently asked questions

How accurate are app revenue estimates?

No single percentage covers every app, because the error moves with the app's chart position, country and month. An error ratio measured in one month is a starting point, not a constant. Measure it again after a price change or a big move up or down the chart.

Can you see a competitor's real revenue?

No. Real revenue sits in the developer's own store account and in tools connected to it, such as a subscription platform. Nobody else can read it, which is why every public figure for a competitor is modelled.

Why do two estimators give different numbers for the same app?

Each fits its own rank-to-downloads curve and assumes its own revenue per download. The revenue assumption multiplies any gap in downloads.

How do I estimate revenue for a new app with no data?

With no installs yet, every input is an assumption. Start from a similar app's estimated downloads and revenue per download, cut both to what you can realistically reach, and run a low, a middle and a high case in the app revenue calculator. Replace the assumptions with measured installs and revenue as soon as the app has them.