--- title: How Much Money Can I Make From an App? description: Find out how much apps actually make, which revenue models pay best, and what it really takes to build an app that turns a profit. image: https://weareaffective.com/hubfs/learning-centre-images/how-much-money-can-i-make-from-an-app.webp --- [Skip to content](https://weareaffective.com/learning-centre/how-much-money-can-i-make-from-an-app#main-content) [![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com) - [Home](https://weareaffective.com) - About Us - [Our Story](https://weareaffective.com/about) - [How We Work](https://weareaffective.com/how-we-work) - Our Services - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy) - [App Design](https://weareaffective.com/app-design-agency) - [App UX Design](https://weareaffective.com/app-ux-design) - [App UI Design](https://weareaffective.com/app-ui-design) - [App Technical Architecture](https://weareaffective.com/app-architecture) - [Existing App Audits](https://weareaffective.com/app-audit) - [Case Studies](https://weareaffective.com/case-studies) - [Pricing](https://weareaffective.com/pricing) - [Learning Centre](https://weareaffective.com/learning-centre) - [Get Started](https://weareaffective.com/get-started) Expert Guide Series # How Much Money Can I Make From an App? Table of Contents The question founders ask us before design, before features, before anything else, is how much do apps make. It deserves a straight answer, and the straight answer is that the range is enormous and the middle is thin. A small number of products earn serious money every month. The long tail earns close to nothing, because the long tail gets downloaded by friends, family and a few curious strangers, and then sits unopened on a home screen. What we can tell you with more confidence is what separates those two outcomes, and almost all of it is [decided early, in the weeks before](https://weareaffective.com/app-planning-strategy) anybody opens a design file. > Your revenue model is a design decision, and it gets made before the first screen. We've built revenue models for a commission-based trading platform, priced a music backing track app, watched a social football product abandon subscriptions after launch, and argued with Apple for months over a currency exchange app. Those projects taught us more about app profits than any benchmark report has. So this piece covers what apps realistically earn, which models return what, how to price, which platform to launch on, how to build a forecast an investor accepts, and the warning signs that tell you the numbers won't work before you've spent the money finding out. ## What Apps Actually Earn: The Honest Numbers When somebody asks us for a number, we ask what they're comparing against. An app with 2,000 loyal users paying £4 a month is a healthy little business. An app with 200,000 downloads and no paying users is a cost centre with good vanity figures. The download number tells you almost nothing about the money. #### How much do apps make in practice The global pot is huge and still growing. In-app purchase and paid app revenue reached $167 billion in 2025, up 10.6 per cent year on year, while downloads grew only 0.8 per cent, according to [Sensor Tower, 2026](https://www.getpanto.ai/blog/mobile-app-statistics). The market is getting better at making money from the people it already has, rather than finding new ones. That shift matters for anybody asking are apps profitable today. Growth is coming from how well a product converts and retains, which is exactly the part founders tend to leave until after launch. On the niche trading platform we worked on, we produced one, three and five year forecasts for investors, and the honest spread between the cautious case and the optimistic case was wide enough to change what the business was. We'd rather show a client that spread than a single confident number nobody can defend. ## The Revenue Models and What Each One Can Realistically Return There are only a handful of ways an app brings money in, and each one asks something different of your audience. Freemium looks generous and depends entirely on conversion, which sits at roughly 3 to 5 per cent according to [Databox](https://databox.com/freemium-conversion-rate). At that rate, 10,000 free users gets you a few hundred payers, so the free tier has to be cheap to run. | Model | Suits | What it needs | Where it breaks | | --- | --- | --- | --- | | Paid download | Tools, niche utilities | Instant, obvious value | No second chance to sell | | Subscription | Habit and content products | Reason to open weekly | Small user base | | Freemium plus purchases | Large audiences | Cheap free tier | Low conversion rates | | Advertising | High-frequency use | Very large volume | Low value per user | | Commission on transactions | Marketplaces, trading | Repeat transactions | Complex forecasting | | Affiliate referral | Content and discovery | A natural upsell moment | Partner dependency | Commission was the model on the trading platform, and it's the hardest of the lot to predict, because revenue depends on how often each user transacts rather than a flat monthly fee. Advertising is the fallback that tempts teams who can't make subscriptions work. It pays, but it pays per thousand impressions, so it only becomes real money at a scale small products rarely reach. ## UX/UI design built around *real* psychology We design app interfaces around how people actually think and behave. User research, psychology-driven UX/UI design and technical specs delivered as one complete package. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## Why Your Monetisation Choice Has to Come Before Your Build On the social football platform we worked on, the plan was subscriptions. After launch the user base was simply too small to support that, so the client had to bring in [features they'd explicitly ruled out, including advertising, and cancel the subscription model altogether](https://weareaffective.com/learning-centre/what-scope-creep-actually-costs-a-sports-club-app-that-spent-twelve-months-growi). Advertising then had to be retrofitted into screens that were designed assuming no ads existed. That retrofit costs money twice. You pay to build the thing, then you pay again to unpick it, and in between you've trained your early users to expect something you've now taken away. > Retrofitting a revenue model means paying for the same screens twice and disappointing your earliest users. Budget sits in the same conversation. A lower budget doesn't buy a slightly smaller version of the same product, it buys less flexibility and a sharper focus on getting to market inside the time you've got. We say that out loud at the start, because the painful projects are the ones where a client wants the low budget without the limitations that come with it. So the sequence we use is simple. Decide how the product earns, then design the screens that carry that model, then price it, then build. Every step after that gets cheaper. ## Pricing: Why Production Cost Is the Wrong Starting Point We worked on a music backing track app where the client came from the music world and knew exactly what the recordings had cost to produce. They wanted that money back within weeks. Our read of the market was that it was niche, spanning professional musicians and casual players, and that it needed a low price point to drive mass adoption. Our advice to them was blunt. Nobody will actually pay what you think it should be worth, and instead we should be looking at this as purely a volume product. They disagreed, pushed for the high price, and sales came in low, which is what we'd told them to expect. Lower introductory pricing or a volume model would have produced more downloads and more total revenue. Write down your production costs on one sheet of paper and your price on another, and never let them sit on the same desk. Customers don't know what your content cost and they don't care. What buyers pay for is the problem you solve for them this week. A backing track app competes with free videos and cheap alternatives, so the price has to sit where a casual player reaches for their card without thinking. Volume then does the work your price point can't. ## Choosing the Right Platform for Where Your Money Is The football platform launched iOS-only, and the audience was younger and skewed heavily towards Android. Day one adoption came in at around half of what it should have been. We'd built the more polished version of the product for the smaller slice of the market, and the subscription model never got the user numbers it needed to survive. The received wisdom is that iOS users spend more, and the figures support it. Non-gaming iOS apps generate $8.39 per user against $1.54 for Android, according to [Userpilot](https://userpilot.com/blog/mobile-app-metrics/). That gap is real, and it's also the reason teams launch on iOS without checking whether their own audience lives there. #### Spend per user against reach Higher spend per user only pays if the users exist. Grassroots sport, younger audiences and a lot of international markets sit on Android, and a subscription model needs volume before it needs high spenders. An advertising or affiliate model needs volume even more. So check the demographic before the platform, and if your audience is split, price the cost of launching on both against the revenue you lose by reaching half of them. ## How to Build a Revenue Forecast You Can Defend The hardest forecast we've built was for the niche trading platform, because revenue came from commission on trades rather than a flat fee. A subscription model needs two or three inputs. Commission needed a dozen, and every one of them had to be defensible in front of investors. Here's the order we worked in. 1. User acquisition at the start of each month 2. Monthly churn against that cohort 3. Conversion from download to active, revenue-generating user 4. Average transactions per user per month, across their whole lifetime 5. Commission rate and platform fees taken off the top 6. Estimated dispute and refund amounts Mapping those out gave us one, three and five year projections that held up under questioning. The value wasn't the headline number at the end. It was that we could show which single assumption moved it most, and that assumption was almost always retention. Build your model so a reader can change one cell and watch the five year figure move. Investors trust a founder who knows which input is fragile far more than one with a confident total and no working. ## Benchmarking Against Comparable Products When Nothing Matches Yours No direct equivalent to the trading platform existed, which is the position almost every founder claims to be in and a few genuinely are. So we analysed the market for similar products in adjacent spaces, found ones performing some aspect of what the platform would do, and looked at their revenue and subscription models as a baseline. Then we adjusted. Where a comparable product already had strong traction, we scaled our projections right down, because a new product entering that space starts from zero against an incumbent with an audience. > A comparable with traction is a ceiling, not a starting point, and your first year sits well below it. Founders tend to do the opposite. They find a successful product, assume a small percentage of its market, and present that as conservative. One per cent of a big number is still a made-up number, and investors have seen that slide a thousand times. The useful version names the products, shows their pricing and their likely scale, and explains the uplift or downlift you've applied and why. That turns a guess into an argument somebody can disagree with properly. ## Retention: The Number That Decides Whether Any Model Works Every model above runs on the same fuel. Subscriptions need people to stay past the renewal. Commission needs repeat transactions. Advertising needs sessions. In-app purchases need users who've been around long enough to want the upgrade. Our rule of thumb is that anything below 50 per cent retention after day one is borderline, and the higher you get it the better. What matters more is keeping people past day thirty, especially if you're paying for user acquisition, because every pound spent bringing in users who leave on day two is a pound burned. Work out what one retained user is worth over twelve months before you spend anything on acquisition. If that figure is smaller than your cost per install, no amount of downloads fixes it. Early drop-off is usually a promise problem. People downloaded expecting one thing, opened the app, found another, and left. Fixing that starts outside the product, in the store listing, and continues in the first thirty seconds after opening. So when a forecast disappoints, the fix is rarely a new revenue model. It's getting the right people in and giving them a reason to come back on day two. ## Getting Downloads That Convert: The App Store Listing On a gifting and wishlist platform we worked on, the client was hesitant to put any effort into the store listing, because the product was social and group-based and they assumed word of mouth would carry it. Our position was that referral and the listing do different jobs, and you need both. People have to understand what the product is from the very first screen. [The icon, the title, the first two lines of copy](https://weareaffective.com/learning-centre/the-meditation-app-opening-screen-that-asks-nothing-and-earns-everything), the category and the opening screenshots all have to say the same thing. Get that right and the people who download already know what they're getting, and they've aligned themselves to it as a user before they ever open the app. That's the quiet reason a good listing cuts churn. We don't want somebody downloading and then realising this isn't for them at all, because that user costs you a rating, a slot in your analytics and nothing in return. Show your first screenshot to five people who've never heard of the product and ask what the app does. If two of them get it wrong, the listing is costing you money. ## Secondary Revenue Streams and Partner Integrations We did proof-of-concept work for a company building an app where people share memories with audio attached. We looked at Spotify first, which is where everybody starts, and the API didn't support short clips properly, plus users needed their own Spotify account, which chewed up the experience before it began. Deezer had a robust API, supported clips, and didn't require users to be logged in. So people could search a catalogue larger than Spotify's and attach a clip inside our app without leaving it. The commercial part came almost free. When somebody wanted to hear the full track rather than the clip, there was [a natural upsell to a Deezer subscription, which opened up affiliate referral revenue](https://weareaffective.com/learning-centre/what-email-types-work-best-for-app-user-onboarding) running alongside whatever the product itself earned. That's the shape worth looking for in a partner integration. Find the moment a user already wants more than your app gives them, and make the partner's product the answer. Bolted-on affiliate links in a settings menu earn nothing, because nobody wanted anything at the moment they saw them. Secondary streams rarely carry a business on their own. They do change the maths on marginal users who'd otherwise contribute zero. ## Costs, Fees and Compliance: What Comes Off the Top Before you count app profits, take the platform cut off. In-app purchases through Apple or Google retain 15 to 30 per cent per transaction, according to [SplitMetrics](https://splitmetrics.com/blog/google-play-apple-app-store-fees/), with the lower rate applying to smaller developers and to subscription renewals after the first year. A £5 subscription is not £5 of revenue. Compliance is the cost nobody forecasts. On a currency exchange app we worked on, the client spent serious money on legal counsel and compliance work to satisfy Apple's review process, and each time they resolved an objection a fresh one appeared. > Compliance costs arrive after your budget is set and they don't wait for your launch date. It became clear something else was going on and that Apple didn't want the product on the store, whatever the stated reason was. There's no real mechanism for a developer to challenge that, which is worth knowing before you build in a regulated space. After the product pivoted to an in-person model, Apple raised money laundering concerns, and we ended up imposing a limit of around €100 to €150 on any single exchange. A rule written to satisfy a reviewer became a cap on revenue per transaction, which is how compliance quietly rewrites your forecast. ## Making an App Pay for an Existing Business If you already have customers, the app doesn't have to charge them anything to earn its keep. It earns through order frequency, basket size, repeat purchase and the support calls it stops. A skincare brand with a reorder reminder and a saved routine doesn't need a subscription fee to make the build pay back. The maths is different and usually kinder. You know your customer lifetime value already, you know your repeat purchase rate, and you can model what a few percentage points of improvement on either is worth across your existing base. That's a far safer forecast than guessing at cold downloads. Pick one number the app has to move, such as second-order rate within 90 days, and agree it before the build. Everything else in the product gets judged against it. The trap is building a smaller copy of your website in an app wrapper. Customers already have the website, so the app has to do something the browser can't, whether that's notifications they actually want, saved preferences, loyalty that's visible, or a [faster path to reordering the thing they always buy](https://weareaffective.com/learning-centre/how-to-diagnose-which-stage-of-the-emotional-arc-your-reorder-flow-is-losing-cus). Get that right and the app stops being a marketing cost and starts behaving like a retention channel. ## Warning Signs Your Revenue Model Will Not Work Some of these we've watched play out, and the pattern is consistent enough to name. - The price is set by what the content cost to make, as with the music backing track app - The launch platform doesn't match where the audience actually is, as with the football platform - The forecast relies on a percentage of a very large market rather than named comparables - Day one retention sits below 50 per cent and the plan is more advertising spend - The model assumes advertising revenue at a user volume you've no route to reaching - Nobody has subtracted platform fees, compliance work or support costs from the headline figure Two or more of those together is a serious problem, because they compound. A high price with the wrong platform means low volume and low conversion at the same time, and no marketing budget fixes both. The good news is that all of them are visible before launch. Each one is an assumption written down somewhere, which means each one can be tested cheaply while changing your mind still costs a conversation rather than a rebuild. ## Conclusion So, how much do apps make? Enough to build a real business on, if the model, the price, the platform and the retention all point the same way. The projects we've worked on that earned well got those four decisions right early. The ones that struggled got one of them wrong and spent the next year paying for it. The music app priced against production cost and sold little. The football platform launched on the wrong platform for its audience and lost its subscription model. The trading platform got a forecast built on named comparables and defensible assumptions, and that forecast survived investor questions. None of those outcomes were decided by the quality of the code. If you're weighing up whether to build, start with the money question and work backwards into the product. Write down how it earns, what it costs to serve a user, what that user is worth over a year, and what has to be true for those numbers to meet. Then design the thing. If you'd like a second pair of eyes on those numbers before you commit a budget, [let's talk about your app revenue model](https://weareaffective.com/get-started). ## Frequently Asked Questions How much money can I realistically make from an app? The honest answer is that the range is enormous and the middle is thin. A small number of apps earn serious money each month, while the long tail earns close to nothing because it gets downloaded by friends and family and then sits unopened. What separates the two is decided early, in the weeks before anyone opens a design file. Do downloads tell me anything useful about revenue? Very little. An app with 2,000 loyal users paying £4 a month is a healthy little business, whereas 200,000 downloads with no paying users is a cost centre with impressive vanity figures. Focus on conversion and retention rather than install counts. Is the app market still growing? Yes, but the growth is coming from monetisation rather than new users. In-app purchase and paid app revenue reached $167 billion in 2025, up 10.6 per cent year on year, while downloads grew only 0.8 per cent according to Sensor Tower. The market is getting better at earning from the people it already has. When should I decide on my revenue model? Before the first screen is designed. Your revenue model is a design decision, because the way you charge shapes the features, the onboarding and the whole product experience. Leaving it until after launch is one of the most common and most expensive mistakes. What conversion rate should I expect from a freemium app? Freemium conversion sits at roughly 3 to 5 per cent according to Databox. That means 10,000 free users might give you only a few hundred payers, so your free tier has to be genuinely cheap to run or the maths stops working. Which revenue model is right for my app? It depends on what you are asking of your audience. Paid downloads suit tools and niche utilities with instant, obvious value, subscriptions suit habit and content products that people open weekly, freemium needs a large audience and a cheap free tier, advertising needs very high volume and frequency, and commission models suit marketplaces with repeat transactions. Why do subscriptions sometimes fail after launch? Subscriptions need a genuine reason for people to open the app weekly, and they break down when the user base is too small. We watched a social football product abandon subscriptions after launch for exactly this reason. If your product is used occasionally rather than habitually, another model will usually serve you better. What should a revenue forecast for investors look like? It should show a range rather than a single confident number. On a niche trading platform we produced one, three and five year forecasts, and the spread between the cautious and optimistic cases was wide enough to change what the business was. Showing that spread is more credible than a figure nobody can defend. ## Related Articles [![What happens to my business if my app performance is poor](https://weareaffective.com/hubfs/learning-centre-images/what-happens-to-my-business-if-my-app-performance-is-poor.webp)](https://weareaffective.com/learning-centre/what-happens-to-my-business-if-my-app-performance-is-poor) ### [What happens to my business if my app performance is poor](https://weareaffective.com/learning-centre/what-happens-to-my-business-if-my-app-performance-is-poor) A user downloads your app, opens it, and within ninety seconds decides whether they will ever open... by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee) [![What 'Permission Readiness' Means and Why It Decides Whether Users Grant Access](https://weareaffective.com/hubfs/learning-centre-images/what-permission-readiness-means-and-why-it-decides-whether-users-grant-access.webp)](https://weareaffective.com/learning-centre/what-permission-readiness-means-and-why-it-decides-whether-users-grant-access) ### [What 'Permission Readiness' Means and Why It Decides Whether Users Grant Access](https://weareaffective.com/learning-centre/what-permission-readiness-means-and-why-it-decides-whether-users-grant-access) You tap an app icon for the first time and before anything has loaded properly, a grey box asks... by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee) [![How Much to Budget for App Marketing](https://weareaffective.com/hubfs/learning-centre-images/how-much-to-budget-for-app-marketing.webp)](https://weareaffective.com/learning-centre/how-much-to-budget-for-app-marketing) ### [How Much to Budget for App Marketing](https://weareaffective.com/learning-centre/how-much-to-budget-for-app-marketing) The question usually reaches us late. The build has been quoted, a launch date already sits in... by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee) [![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com) 20-22 Wenlock Road London, N1 7GU United Kingdom +44 20 4572 8062 [hello@weareaffective.com](mailto:hello@weareaffective.com) Services [App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit) Legal [Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70) Case studies [TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift) About us [Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work) Guides [Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth) Copyright © 2026, weareaffective.com. All rights reserved.