How Do I Set Realistic Revenue Targets for My App?

Most app revenue targets are built on optimism rather than evidence. A founder sits down, imagines capturing a small slice of a large market, multiplies it by their price point, and arrives at a number that feels reasonable. The problem is that the assumptions buried inside that calculation are almost never tested against reality. They are borrowed from market reports, adjusted for confidence, and presented as a forecast. What they actually are is a wish.

Setting realistic revenue targets requires a different starting point entirely. Rather than asking what share of a big market you could win, you need to ask what you actually know about the people who will pay for your product, how quickly you can reach them, and what percentage will stay long enough to generate meaningful revenue. Those are harder questions, and the answers are usually more sobering. But they are also the ones that lead to targets you can actually build a business around.

At We Are Affective, we work with founders and product teams at different stages of this process, from early validation through to post-launch growth planning. The patterns we see are consistent. The forecasts that hold up are built from the ground up, with real user behaviour at their centre. The ones that collapse are built from the top down, from market size figures that have nothing to do with the friction inside a real product journey.

Good revenue targets start with real user behaviour, not a percentage of a market report figure.

This article walks through how to build targets that are grounded, useful, and genuinely connected to how your app will actually perform.

Why Most App Revenue Forecasts Are Wrong From the Start

The most common forecasting mistake is starting with the size of the market rather than the behaviour of the user. A founder reads that the global fitness app market is projected to reach significant scale by 2031, takes one per cent of that number, and writes it into their financial model as year-one revenue. The logic sounds defensible. In practice, it produces a figure that has no relationship to what the app will actually generate.

Top-down forecasting like this fails because it skips all the friction. It does not account for how difficult it is to acquire a paying user, how quickly most users churn, or how long it takes for an app to build the kind of reputation that drives organic growth. New apps typically capture only a fraction of their addressable market in the first year, yet the planning-table assumption is often multiples of that.

There is also a psychological dimension to this. Founders are, almost by definition, people who believe in what they are building. That belief is necessary for the hard work of building a product, but it is not a good input for a revenue model. When the person doing the forecasting is also the person who came up with the idea, the numbers tend to drift upward. The forecast becomes a reflection of confidence rather than a description of likely reality.

The fix is not pessimism but precision. Forecasts built from specific, observable inputs, such as real conversion rates, real retention data, and honest acquisition cost estimates, produce numbers that are actually useful for planning. That kind of precision requires a different approach from the start.

Understanding Your Monetisation Model Before You Set Any Numbers

Before any revenue target means anything, you need to be clear about how your app actually makes money. The monetisation model shapes every number in your forecast, and different models produce very different revenue curves, even for apps with identical user numbers.

The main monetisation routes

The four most common models for consumer apps are subscriptions, one-off purchases, in-app purchases or microtransactions, and advertising revenue. Subscriptions generate recurring income and, according to RevenueCat, 2024, account for roughly 40 to 44 per cent of app revenue across the market. One-off purchases give you a single payment per user with no guaranteed return visit. In-app purchases depend on a small proportion of users spending heavily. Advertising revenue depends on volume and dwell time, and rarely works at the scale most early-stage apps can reach.

Why model choice changes your targets

A subscription model with strong retention produces compounding revenue over time. A transaction model produces lumpy, unpredictable income. An advertising model produces almost nothing until you reach hundreds of thousands of monthly active users. Your revenue target for month twelve looks completely different depending on which of these you are running, so settling this question before you build any numbers is not optional.

It is also worth acknowledging that many apps layer models together, using a free tier to drive volume, a subscription for core functionality, and occasional in-app purchases for extras. That works, but it adds complexity to the forecast. Each revenue stream needs its own assumptions and its own set of inputs.

How to Size Your Addressable Market Realistically

There is a meaningful difference between the total market for a category and the market that is actually available to your specific product, at this stage of its development, at your price point. Most forecasts conflate the two, and the gap between them is usually enormous.

Start by defining who your product is actually for, not in broad demographic terms, but in specific behavioural terms. Who has the problem your app solves? How frequently do they experience it? Are they already spending money on solutions, and if so, what are they spending? These questions narrow the market from a notional total to an addressable reality.

One of the most consistent patterns we observe is founders assuming that because they personally experience a problem, the market at large shares it at the same intensity. The reality is that market size needs to be validated rather than assumed. Focus groups and surveys are relatively inexpensive ways to test whether a genuine broader need exists before you commit significant resource to a build. Skipping that step means your market size estimate is built on one data point: you.

Your addressable market is only as real as the validated need sitting beneath it, not the category total in a research report.

Once you have a clearer picture of who your real audience is, apply realistic penetration rates. New apps face significant friction in acquisition, and first-year penetration of even a well-defined niche market is almost always modest. Building that modesty into your model from the start is what separates a useful forecast from a flattering one.

Define your audience by the behaviour you are changing, not by broad demographics. "Adults aged 25 to 40" is not a market. "People who log their workouts manually because existing apps feel over-engineered" is a market you can actually size and reach.

The Metrics That Actually Drive App Revenue

Revenue for an app is a product of a small number of interconnected metrics. Understanding which ones matter most, and how they connect, is the foundation of any credible forecast.

The first is user acquisition, specifically how many new users you bring in each month and what it costs you to acquire each one. The second is activation, meaning the percentage of new users who reach a meaningful first experience inside the product. The third is retention, which is the percentage of users who come back after day one, day three, day seven, and day thirty. The fourth is monetisation, meaning the percentage of active users who generate revenue and how much they generate on average.

Retention as the revenue multiplier

Of these, retention is the one that most powerfully shapes long-term revenue, and it is the one most frequently underestimated in early forecasts. Strong early retention is hard to achieve. Around 77 per cent of apps lose their daily active users within the first three days of download, and even well-designed products with clear value propositions typically see a significant retention drop in that same window. The gap between strong and average retention over twelve months, compounded across a growing user base, produces dramatically different revenue outcomes.

The relationship between activation and revenue

Activation is closely linked to retention. A user who does not reach a genuine first value moment in the product is almost always gone within a week. Making that first value moment fast and frictionless is one of the highest-leverage things a product team can do, and it should appear in the forecast as an assumption with a specific number attached: what percentage of new users do we expect to activate, and what does the revenue model look like if that percentage is 40 per cent instead of 70?

Using Benchmarks and Industry Data to Sense-Check Your Targets

No forecast exists in isolation. One of the most useful things you can do once you have built your own bottom-up model is hold it against industry benchmarks and ask whether your assumptions are within a plausible range.

Benchmarks are available for most of the metrics that matter: conversion rates from free to paid, average revenue per user by category, churn rates by subscription type, and cost per acquisition by acquisition channel. None of these figures apply to your product directly, but they give you a reference range. If your model assumes a free-to-paid conversion rate of 25 per cent in a category where the typical range is two to five per cent, that assumption needs defending or adjusting.

It is also worth looking at platform-level differences. iOS users tend to spend significantly more on apps than Android users, with some estimates putting the ratio at two to three times more, according to AppTweak. If your audience skews heavily toward one platform, that shapes your average revenue per user assumption in a concrete way.

The honest use of benchmarks is as a sense-check, not as a shortcut. They tell you whether your assumptions are in the right neighbourhood. They do not tell you whether your specific product, with its specific audience and onboarding experience, will hit the midpoint, the top, or the bottom of the range. That depends on the quality of the product itself, and the only way to know that with confidence is to launch and measure.

When you find a benchmark that your model relies on, note where it came from and what kind of apps it covers. A churn rate benchmark for casual games tells you almost nothing about a professional development app, even if both are "apps".

Building a Bottom-Up Revenue Forecast

A bottom-up forecast builds revenue from the behaviours of individual users rather than from a percentage of a market total. It starts with acquisition, moves through activation and retention, and arrives at revenue as the output of real conversion assumptions at each step.

The structure starts with a monthly new user number, which should itself be grounded in a specific acquisition plan rather than an optimistic assumption. From that number, you apply an activation rate to get the users who genuinely engage with the product. From the engaged users, you apply a retention curve to get the number who are still active at day seven, day thirty, and day ninety. From retained users, you apply a conversion rate to get paying users. From paying users, you apply your average revenue per user to get monthly revenue.

Working through the assumptions

Each step in this chain requires a number you need to defend. Where do the acquisition numbers come from? What is your activation rate based on? What does your retention curve assume, and does that assumption reflect what you know about your onboarding experience? If any of these inputs are guesses, label them as guesses and build a sensitivity analysis that shows what happens to revenue if the guess is wrong by 30 per cent in either direction.

• Monthly new users acquired (from a defined acquisition plan)
• Activation rate (percentage who reach first value moment)
• Retention at day 7, day 30, and day 90
• Free-to-paid conversion rate
• Average monthly revenue per paying user
• Churn rate among paying subscribers

This model will not produce a precise prediction, because no model does. What it produces is a clear map of the levers that drive your revenue, so that when real data arrives you know exactly which assumption needs updating.

Accounting for Churn, Seasonality, and Slow Starts

Three factors consistently cause revenue forecasts to overstate performance in the first twelve months. Getting all three into your model before you lock targets is what separates a forecast from a disappointment.

Churn is the one most founders acknowledge intellectually but underweight numerically. Losing users is a normal part of operating an app. The question is how much churn you will have, and whether your acquisition rate is high enough to grow the user base even after churn is accounted for. A product losing a significant portion of its paying subscribers each month needs to run very hard just to stay flat. Building a net-growth model that ignores this produces revenue projections that are technically correct in month one and increasingly wrong in every month after that.

Seasonality and category patterns

Many app categories have pronounced seasonal patterns that affect both acquisition and revenue. Fitness apps see surges in January and sharp drops in February. Travel apps peak around booking seasons. Education apps follow school calendars. If your category has a seasonal shape, your monthly revenue forecast needs to reflect it rather than assuming flat growth throughout the year.

The slow start problem

New apps almost always grow more slowly in the first three months than founders expect. App store discovery is limited for new products with no ratings history. Word-of-mouth takes time to build. Paid acquisition channels require learning periods before they perform efficiently. The temptation is to model a strong launch and then revise downward if reality does not cooperate. The more useful approach is to model a slow start explicitly, test the business under those conditions, and treat any outperformance as a genuine signal rather than the expected outcome.

Model three scenarios: a slow start with average retention, a moderate start with strong retention, and a fast start with poor retention. The scenario you end up living in will tell you a lot about where your real product-market fit issues are.

Setting Short-Term, Mid-Term, and Long-Term Targets Separately

A single revenue target for year three is not useful. The assumptions required to build it are too uncertain, and the number carries false precision that makes it harder to respond well when reality diverges. Setting targets across three distinct time horizons, with different levels of confidence and different purposes, produces a much more useful planning tool.

Short-term targets cover the first three months. These should be specific, grounded in your actual launch plan, and focused on leading indicators rather than revenue. How many users will you acquire in month one? What activation rate are you targeting? What does retention look like at day seven? These are the inputs that will determine whether your revenue assumptions are right, and getting a read on them early is more valuable than any monthly revenue figure at this stage.

Mid-term targets as learning milestones

Mid-term targets cover months three to twelve. At this point, you have real data, and your targets should be based on observed behaviour rather than pre-launch assumptions. If your actual activation rate in month two was 35 per cent rather than the 60 per cent you modelled, your month-six revenue target needs to be rebuilt around that reality. Mid-term targets should be revised quarterly at minimum, using real data as the primary input.

Long-term targets, covering year two and beyond, are necessarily more speculative. Their value is not precision but direction. They help you understand what scale of business you are building toward, what retention rate you need to achieve to make the economics work, and what acquisition investment is justified at different growth rates. Treat them as planning tools rather than commitments, and hold them loosely enough to update them as the product evolves.

How to Revise Targets as Real Data Comes In

Every launch produces information that the founding team did not have before. User feedback redirects products in ways internal teams do not anticipate. Behaviour inside the app reveals friction points that were invisible in user testing. Conversion rates come in different from model assumptions, and not always in the direction you hoped. The question is not whether the data will change your understanding of the product but whether you have a process for translating that understanding into updated targets.

The first thing to do with real data is compare it against your model's specific assumptions, not against the revenue output. If revenue is below target, the question is which input drove that: lower-than-expected acquisition, worse activation, higher churn, or lower conversion to paid? Each of those has a different fix, and identifying which one is the actual problem is more useful than simply noting that revenue is off.

When to update versus when to persist

Revising targets based on data is not the same as abandoning ambition. The goal is to keep your model honest so that the decisions you make from it, around hiring, marketing spend, and product investment, are grounded in what is actually happening rather than what you wished would happen. A target that has been revised downward based on real data is more useful than an original target that everyone knows is wrong but nobody has officially changed.

There is also a timing dimension to this. Data from the first four weeks of a launch is noisy and reflects the specific conditions of launch week, including any PR, early adopter enthusiasm, and word-of-mouth from the founding network. Resist the urge to revise targets dramatically on the basis of week-one performance, positive or negative. By month three, you have enough signal to update your model with genuine confidence.

1. Compare actual inputs (acquisition, activation, retention, conversion) against your original assumptions
2. Identify which specific input is driving the variance
3. Update that input in your model and observe the effect on downstream outputs
4. Revise targets for the next quarter based on the updated model
5. Document the change and the reason for it, so the revision history is visible

Conclusion

Revenue targets for apps are only useful if they are built from real inputs and revised as real data arrives. A target derived from a market size report, adjusted for optimism, and left unchanged through the first six months of a launch is not a forecast. It is a number that makes planning meetings feel more certain than they are.

The approach that actually works starts with your monetisation model, works through specific user behaviour assumptions at each stage of the funnel, accounts honestly for churn and slow starts, and treats every real-world data point as an opportunity to improve the model. That process is less exciting than arriving at a large revenue number in a spreadsheet. It is also the one that keeps businesses alive long enough to reach the revenue they were hoping for.

The underlying question that drives all of this is whether you are solving a real problem that people will pay for. If the answer to that is genuinely yes, then building a grounded, evidence-based revenue model is how you protect that product long enough to prove it. If the answer is uncertain, the revenue model will surface that uncertainty quickly, which is information you need rather than something to avoid.

We work with product teams and founders at every stage of this process, from pre-launch validation through to post-launch growth modelling. If you are trying to set revenue targets that will actually hold up, let's talk about your app's revenue model.

Frequently Asked Questions