What's the Typical Customer Acquisition Cost for Apps

Ask five app founders what their app customer acquisition cost is and you'll get five numbers that aren't measuring the same thing. One divides last month's ad spend by installs. One counts registrations. One counts paying subscribers and quietly leaves out the agency retainer, the creative production and the discount codes. The figures look comparable. They aren't.

That's the first problem with benchmarks. The second is that a cost per install only tells you what it costs to get your app onto a phone, and a phone isn't a customer.

An install is a stranger with your app open, and the real cost sits in everything that happens next.

We build and fix apps for lifestyle brands, so we see the same pattern repeatedly. A team buys installs at a sensible rate, watches the download graph climb, and three months later can't work out why revenue hasn't followed. The media was fine. The product lost the users before they ever became worth anything.

This article covers what a realistic app user acquisition cost looks like today, what you should budget at launch, why the same number means very different things in different categories, and how to tell whether your cost problem sits in your media buying or in your product. We'll use our own projects to show where the money actually goes.

What Counts as Customer Acquisition Cost, and What Most Teams Are Actually Measuring

Customer acquisition cost is everything you spend to turn a stranger into a paying customer, divided by the number of paying customers you got. Everything means the media, the creative, the agency or freelancer fees, the tooling, the influencer gifting, the launch discount and the time your own team spent on it.

What gets reported in the weekly update is usually cost per install. That's a different measurement with a different job. Cost per install tells you how efficiently you're buying attention. It says nothing about whether the people arriving are the right ones.

Three numbers, not one

We ask clients to track the chain rather than a single figure. Cost per install, then cost per activated user, then cost per paying customer. The gaps between those three are where your product is either earning its media spend or burning it.

The gaps also move. Acquisition costs have risen close to 60 per cent over six years according to Profitwell, which means a benchmark you wrote down two years ago is already describing a cheaper market than the one you're buying in.

So when someone tells you their app customer acquisition cost is four pounds, the useful next question is simple. Four pounds for what, exactly.

Typical Cost Per Install by Category

Published averages put app installation costs in the region of $3.40 to $4.70, with total acquisition cost per customer sometimes passing $77, according to Userpilot. That spread between the install figure and the customer figure is the honest part of the data. Getting the app downloaded is the cheap bit.

Category matters because you're bidding against whoever else wants the same person's attention that week. A pet care app and a beauty app can sit on the same ad platform and pay very different rates, purely because of who else is in the auction and how much they can afford to lose.

Read the third column against the second. A low cost per install in home and interiors isn't a bargain if those users take four months to buy anything.

Why iOS and Android Figures Look So Different

Almost every benchmark you'll find is a blend of two platforms that behave nothing alike, which is why your own numbers rarely match the published ones.

Android gives advertisers far more cheap inventory, across more devices, in more countries. You can buy installs there at rates that look excellent on a dashboard. iOS inventory is tighter, the tracking is thinner since Apple changed how apps ask permission to follow people around, and the people bidding against you tend to be the ones with the highest revenue per user. So iOS costs more per install, often by a lot.

The temptation is to shift budget to whichever platform shows the lower cost per install. That decision deserves a second look, because the cheaper install isn't always the cheaper customer.

A cheap install on the wrong platform is still money spent on someone who was never going to pay you anything.

What we tell clients is to hold the two platforms apart in reporting and judge each on cost per paying customer, not cost per install. Then look at the gap. If Android installs cost a third of iOS installs but convert at a tenth of the rate, the maths has already answered the question for you.

There's a design angle here too. The same onboarding often performs differently on each platform because of permission prompts, payment habits and device speed, and that difference shows up in your acquisition cost before it shows up anywhere else.

What You Should Budget for New Users at Launch

The honest answer is that your first budget buys information, not growth. You're paying to find out what an install costs you, which creative works, and how many of those installs survive the first week.

We'd plan a launch budget in three parts rather than one pot.

1. A learning budget, spent across two or three channels, large enough to get a few hundred installs per creative so the numbers mean something.
2. A patience budget, which is the same spend again, held back for the four to six weeks after launch when you'll want to fix what the first round exposed.
3. A product budget, reserved for the onboarding and core journey changes the data will ask for.

That third one is the part founders cut, and it's the one that decides what the other two were worth.

Before you spend anything on media, agree with your team what an activated user is. One specific in-app action, not "signed up". Every acquisition number you report afterwards depends on that definition.

Scale matters too. If your whole launch budget buys fifty installs, you've learned nothing you can act on, because fifty people tell you almost nothing about which creative worked. Either save until the budget can produce a readable result, or spend it on the product and grow through the store and word of mouth first.

Why the Same Benchmark Means Different Things in Different Categories

A five pound app user acquisition cost is cheap for a wellness subscription at ten pounds a month. It's ruinous for a free utility with a one-off two pound upgrade. Same number, opposite verdicts.

So the benchmark only means something once you've put it next to what a customer is worth to you over time, and how long you have to wait for that money.

We built a water tracking app, and a product like that has a very different economic shape to a dating product or a marketplace. The water app earns its keep through habit and daily use. A marketplace earns through transaction volume. A subscription earns slowly and steadily, which means you can afford a higher acquisition cost but you need a longer runway to survive it.

Three things that change the verdict

Purchase frequency changes it, because a coffee subscription customer buys monthly and a furniture app customer buys every few years. Margin changes it, because a supplements brand keeps more of each sale than a travel booking app does. Referral changes it, because a product people use in groups brings people with them and effectively splits the cost.

Borrowing a competitor's benchmark without matching all three is how teams end up confident and wrong at the same time.

Organic Acquisition, ASO and the Users You Never Pay For

Every user who finds you through search in the store is a user your media budget didn't buy, and they're usually better than the ones it did, because they went looking for something your app does.

We worked on a gifting and wishlist platform where the client was reluctant to put any effort into App Store Optimisation. Their thinking was reasonable on the surface. The product is social and group-based, so people will share it with each other and referral will do the work. Our view was that the listing still decides everything, because the icon, the copy, the category and the screenshots are what let someone rule themselves in or out before they download. We don't want people downloading the app and then realising it isn't for them at all.

Category choice is part of the cost conversation as well. Where a product could sit in two categories, we generally advise starting in the less competitive one. Ranking is easier from there, which produces more organic impressions, more downloads and more usage, and later you can move into the more competitive category once you've built some traction.

Work out what share of your installs are organic before you judge your paid performance. If paid media is lifting your store ranking, some of those free installs were caused by the spend and belong in the calculation.

The Listing Decides Who Downloads, and Who Leaves on Day One

Your store listing is doing two jobs at once. It persuades people to download, and it filters out the people who'd have left on day one anyway. The second job is the one that lowers your acquisition cost.

If the listing says plainly what the app does, the people who download it already know what they're getting. They've aligned themselves to the product as users. They open it with the right expectations, and the early abandonment that comes from a gap between the marketing and the actual experience drops right down.

The opposite is expensive and very easy to do by accident. Beautiful screenshots that show a feature you built for a future release, a tagline written for investors, a category chosen because it sounded more ambitious. All of those buy you installs you then pay to lose.

A listing that turns the wrong people away is cheaper than a campaign that brings them in.

We treat the first screenshot the way we treat a shop window. Someone scrolling the store gives it a second at most, so it has to carry the single thing your app does for them, in plain words, with no setup required.

When you change that first screenshot, watch your day one retention alongside your install rate. A listing change that drops installs and lifts retention has usually made you money.

Onboarding: Where Paid Installs Quietly Disappear

We think about app abandonment in three windows. The first three or four seconds is immediate abandonment, caused by slow loading, sluggish interactions, crashes and freezing. From about sixty to a hundred and twenty seconds it's the onboarding itself, so forced registration before anyone has seen value, too many tutorial screens, permission requests with no explanation attached. Beyond that comes the first three days, where there's nothing pulling anyone back.

Paid installs die in that middle window more than anywhere else, and the loss is invisible in a media report. The campaign did its job. The app lost the person while they were still deciding whether to care.

Lowering app customer acquisition cost through onboarding

Every extra step you add can raise churn by around 20 per cent, according to UXCam. So the cheapest acquisition work available to most teams is removing screens they already built.

The order matters as much as the length. Show someone what the app does for them, then ask for the account. Ask for location when the feature needs it and explain why in one short line. Save anything that isn't needed for the first useful moment.

Count the taps between opening your app for the first time and the first moment it does something useful. If the answer is more than five, you're paying media rates to lose people at tap six.

Core Experience Problems That Look Like Acquisition Problems

When growth stalls, the instinct is to buy more installs. Sometimes the product has quietly stopped being worth opening, and more installs just means paying to repeat the same loss.

We worked on an art-based auction game with real money prizes. Retention started strong, in the mid sixties to low seventies. Over time the quantity of available games started to drop, and usage became sporadic instead of ongoing. Retention fell to around 30 to 35 per cent. We raised it, and the client wanted to add new features instead. It was only when retention hit that low point that we refocused on the core journey and made sure there were enough games available to play. Retention climbed back to the mid sixties and low seventies, though rebuilding the trust took far longer than breaking it did.

No amount of media spend fixes that. If the core loop has thinned out, every pound you spend on installs lands on a product that can't hold anyone.

The diagnostic question is whether your returning users are still doing the main thing. If daily actives are falling while installs hold steady, you have a product problem wearing an acquisition problem's clothes, and more budget makes it worse.

Trust and Clarity at the Point of Payment

You can buy the install, survive onboarding, build the habit, and still lose the customer in the last ten seconds over a number nobody explained.

On a marketplace checkout project, we saw confusion around platform fees cause real hesitation and drop-off. The question people couldn't answer was whether the fee was being added on top of the price or was already included in it. The amounts were small. The hesitation wasn't about the money at all, it was about not understanding what was being charged, and people who don't fully understand a charge don't feel comfortable carrying on. Even a small financial difference makes quite a big impact on trust.

That matters for acquisition cost because the checkout is where installs finally become customers. A drop-off there multiplies straight through your whole funnel. Lose a tenth of people at payment and your cost per paying customer rises by more than a tenth, because you've already paid for every step before it.

What clarity looks like in practice

Show the full amount early, including any fee, delivery or tax, rather than revealing it at the last screen. Use the same word for the same charge everywhere. Say when the first payment leaves the account, and say what happens after a trial, in the same size type as everything else.

The Rework Costs That Never Appear in a Media Report

The most expensive acquisition cost we've ever watched a client pay didn't come from an ad platform at all. It came from skipping discovery.

We worked on a dating app built around verified profiles and keeping bots out. The client wanted to skip discovery on the messaging side and focus purely on the onboarding process. What we ended up building was a generic messaging feature, and it contradicted the whole premise of the product, because it allowed automated and fake messages. All the verification work done during onboarding was undone by the next screen. The messaging section had to be rewritten, which cost roughly £15,000 of extra budget and about two months of extra work.

Rework doesn't show up in a media report, but it's paid for out of the same budget as every install you buy.

Two months is the part that stings. That's two months of paid installs landing on a product that undermined its own promise, and a cohort of users forming an opinion you then have to spend again to change.

So when you're calculating what a customer costs you, the build decisions belong in the sum. Discovery on a feature looks like an expense until you price the version where you skip it.

Retention as the Multiplier on Every Pound Spent

Retention decides what your acquisition spending was worth. Everything else is arithmetic.

Most mobile apps lose 77 per cent of their daily active users within three days of install, according to Andrew Chen. Good products do considerably better than that, and the distance between the average and the good is the entire financial case for spending money on onboarding and early value.

Our rule of thumb is that anything under half your users returning on day one is borderline. Push it higher, and push it past day thirty, particularly when you're paying for those users in the first place.

The trap is reading silence as approval. On the water tracking app we developed, it was very easy to assume no news was good news, and with mobile apps it's quite the opposite. People leave without complaining, without a support ticket, without telling you why. Your download graph keeps climbing while day three, day five and day seven quietly fall away, and the product looks healthy right up until the revenue doesn't arrive.

So track the cohort, not the total. A rising install count with a falling day seven is a product getting more expensive to run, one campaign at a time.

Working Out Your Own Realistic CAC Target

Benchmarks are useful for sanity checks. Your target has to come from your own maths, because only you know what a customer is worth to you.

1. Work out the average revenue a customer produces over twelve months, after your costs.
2. Decide how long you can wait to get your acquisition spend back, given your cash position.
3. Set your ceiling for cost per paying customer from those two numbers.
4. Work backwards through your funnel to find the cost per install that ceiling allows.
5. Compare that to what the ad platforms are actually charging you, and close the difference through the product.

A common target is a customer acquisition cost to lifetime value ratio of around 1:3, which Userpilot lists as a healthy benchmark. Treat it as a direction rather than a law. A product with strong referral and low serving costs can live happily at a tighter ratio. A product with long gaps between purchases needs more headroom.

Run the same calculation twice, once on your best performing cohort and once on the average. The gap between them is the size of the prize sitting in your product rather than your media plan.

Write the target down and date it. Media costs move, your conversion rates move, and a target set last spring is describing a market that no longer exists.

How to Tell Whether Your Cost Problem Sits in Media or in Product

Both problems look identical on a finance report. They have completely different fixes, so it's worth separating them before you spend anything else.

The fastest way to prove it to yourself is to compare organic users against paid users through the same funnel. If organic users convert and stay at a similar rate to paid, your product is doing its job and the work sits in media. If both groups fall away at the same screen, no amount of better targeting will help.

On a fitness social network, we redesigned the location-sharing flow so people shared approximate proximity rather than a precise location, and so conversation came before any location disclosure. Conversion from signing up to actually meeting someone went from about 20 per cent to around 60 to 70 per cent. No change in spend, and roughly three times the customers for the same money.

Conclusion

There's no typical app customer acquisition cost that will tell you whether yours is good. Published averages put installs somewhere in the low single digits of dollars and full customer costs an order of magnitude above that, and the honest use of those figures is to show you how much of the cost sits after the download.

What you can control is the distance between an install and a customer. The store listing that lets the wrong people walk away before they cost you anything. The onboarding that reaches something useful before it asks for an account. The core experience that stays worth opening, which is the lesson the auction game taught us the slow way. The checkout that explains every charge in plain words. The discovery you don't skip, because £15,000 and two months is what skipping it cost on the dating app.

Buy installs by all means. Just make sure the product behind them is ready to earn that money back, because media spend lands on whatever you've built and amplifies it either way.

If you're looking at a cost per install that doesn't add up and you're not sure whether the problem is your media or your product, we're happy to take a look with you. Let's talk about your app acquisition costs.

Frequently Asked Questions