How Can I Show Investors My App Will Actually Make Money?

Showing an investor your app will make money comes down to whether the numbers you present hold together under scrutiny, and whether the behaviour you are describing from users is actually happening, or is something you are assuming will happen once you get more users, more features, or more time. Those two things are very different, and investors know it.

The question founders find hardest to answer is not "how will you monetise this?" It is "why will users keep paying for it?" That distinction matters because acquisition is a cost you can buy, and retention is something you have to earn. An investor who has seen a hundred pitch decks knows that download numbers and monthly active users can look healthy while the product quietly loses the people it worked hardest to acquire.

The acquisition trap

A product that retains well can build a credible commercial case even with modest download numbers. A product that acquires aggressively but loses most of its users within a week is spending money on a leaky bucket. Investors who have seen both patterns will spend far more time on your day-three and day-seven retention numbers than on your total install count.

What strong retention actually signals

Strong retention tells an investor that users found the product's core value quickly enough to come back. It signals that the onboarding works, the value proposition is real, and the product is not relying on habit loops or confusion to manufacture engagement. Each of those things reduces commercial risk, which is exactly what an investor is trying to assess.

How to Read Your Retention Signals Honestly

Not all retention is the same, and reading your own numbers honestly is harder than it sounds. One thing we watch for is the difference between a user staying in a product because they are genuinely getting value from it, versus staying because the product is confusing, or because it has been designed with habit loops that trap rather than reward. Session length is a good example of a number that can tell two completely different stories depending on the product.

On an art-based auction game we worked on, we had strong early retention in the mid-sixties to low seventies. Over time, as the quantity of available games declined, usage became sporadic and retention dropped to around 30 to 35 per cent. The team raised this concern, but the client's response was to add new features rather than address the underlying content supply problem. It was only when retention hit that low point that the focus shifted back to ensuring enough games were available. Retention eventually recovered to the mid-sixties to low seventies, but it took longer than expected because the trust users had built with the product had eroded during the period of degraded experience.

That project illustrated something important. Retention metrics respond to product health, but they also respond to user trust, and trust takes time to rebuild after it has been damaged. A product that fixes its core problem and then presents flat retention numbers a month later is not necessarily failing. It may simply be in the trust recovery phase.

When retention drops, look at what changed in the product or content before assuming the acquisition channel changed. A drop that traces back to a specific product decision is much easier to explain to an investor than a mysterious trend that nobody can account for.

Pricing Logic: How to Justify What You Charge

Pricing a consumer app is partly a market question and partly a psychological one. The market question is what comparable products charge and what the category tolerance appears to be. The psychological question is whether your price point feels proportionate to the value a user experiences, and at what moment in their journey that judgement is being made.

A price that is presented too early, before a user has experienced anything meaningful from the product, will fail at a much higher rate than the same price presented after a moment of genuine value. That is not a new observation, but it is one that founders frequently ignore in the structure of their monetisation flow, asking users to pay before they have any basis on which to decide.

Willingness to pay versus stated preference

Surveys asking users what they would pay for a product are a poor guide to what they will actually pay. This is not a new finding, but it is one that still influences how founders build their pricing assumptions. McKnight's research on online trust shows that stated willingness to transact diverges significantly from actual behaviour when friction or perceived risk increases at the moment of commitment. The gap between "I would pay £5 a month for this" in a survey and the actual conversion rate at that price point can be substantial.

Anchoring and tier structure

Where you place your tiers relative to each other shapes how users perceive the value of each option. A mid-tier that sits between a very basic free level and a high-priced premium looks like a reasonable choice. The same mid-tier presented without an anchor above it looks expensive. The structure of your pricing communicates value before users read a single feature label.

The Gap Between What Users Say and What They Do

User research that asks people about their preferences, habits, or willingness to pay produces data that describes intentions. Behavioural data describes what people actually did. The gap between those two things is one of the most consistent findings in applied psychology, and it has direct consequences for how you build a commercial case.

The correlation between self-reported satisfaction scores and actual behaviours like retention and conversion is consistently weak, meaning high satisfaction ratings rarely translate directly into loyalty or purchase. That is a weak to moderate relationship at best. High NPS or CSAT scores are not reliable predictors of whether users will renew, upgrade, or recommend. They describe how users feel in the moment of being asked, which is not the same thing as how they will behave the next time they open the app or receive a renewal prompt.

An investor who asks "what does your user research show?" is not necessarily asking for survey data. They may be asking whether you understand the difference between stated preference and observed behaviour, and whether your commercial assumptions are built on the latter rather than the former. Presenting NPS as evidence of monetisation potential is one of the ways this question gets answered badly.

Where you have both survey data and behavioural data, present them side by side and acknowledge the gap honestly. Showing an investor that you understand why users say one thing and do another is a stronger commercial signal than presenting only the numbers that look good.

Conversion Assumptions Investors Will Challenge

Most monetisation models rest on a handful of conversion assumptions. The proportion of free users who convert to paid. The proportion of trial users who subscribe after the trial ends. The proportion of one-off purchasers who come back. Each of those assumptions has a number attached to it, and investors will test every one.

The numbers that attract the most scrutiny are the ones that look like industry benchmarks without any product-specific evidence behind them. Saying "we assume a 5 per cent free-to-paid conversion rate because that is typical for this category" is a statement about the category, not about your product. An investor will ask what your current conversion rate is, and if you do not have one yet, they will want to know what you have designed to achieve it.

Between funding rounds on one project we worked on, we made the decision to put in much better tracking of user retention and to ask users proactively how things were going. The driver was the recognition that we had been using investor confidence as a proxy for product health, and that the actual retention picture had not been properly understood. Better tracking changed what we could say with confidence in subsequent conversations, and it changed what we could act on.

How Onboarding Affects Your Commercial Model

Onboarding is where most of the retention story is written, which makes it directly relevant to your commercial case. A user who reaches your product's core value quickly is more likely to stay, more likely to convert, and more likely to renew. A user who experiences friction, confusion, or unmet expectations in their first session is likely to leave before any monetisation opportunity arises.

On a health and wellbeing product we worked on, we tested two versions of a multi-step setup flow. One version showed users a progress bar but gave no indication of how long the process would take. Drop-off rates on that version were around 80 to 85 per cent, typically within the first three or four questions. The second version primed users upfront, telling them what to expect before they began. Completion rates rose to approximately 95 per cent. The change was not in the flow itself. It was in the expectation-setting before the flow started.

That result connects directly to the retention and conversion numbers that underpin a commercial case. According to Business of Apps, 77 per cent of apps lose their daily active users within the first three days of installation. Even strong products typically see a 40 to 50 per cent drop after three days. The gap between those two figures is largely an onboarding problem, and an onboarding problem is a revenue problem.

App store listings as retention levers

One factor that affects early retention that is often overlooked is the accuracy of the app store listing. If a listing accurately communicates what the product does, users who download it arrive with correct expectations. They open the app knowing roughly what they will find, which reduces early abandonment caused by a mismatch between marketing and actual product experience. A user who downloaded an app they did not fully understand is a user who will leave before they pay.

The Questions a Sharp Investor Will Ask First

Experienced investors tend to move quickly to a small number of questions that test whether a monetisation case is real or constructed. The answers to those questions determine how much of the rest of the conversation is worth having. Understanding them in advance means making sure you have the evidence to answer them honestly.

One pattern worth understanding is that investor silence is not the same as investor satisfaction. In investor conversations, when questions stop coming it does not always mean the case has been made. It sometimes means a key part of the story, often the emotional value or the retention logic, has not been understood well enough to generate a question. Silence is a signal worth probing, not one worth accepting.

1. What is your day-one, day-three, and day-thirty retention rate?
2. What is your cost to acquire a user, and what is your current lifetime value?
3. At what point in the user journey does conversion happen, and why there?
4. What does a user who churns look like compared to a user who stays?
5. What has changed in the product as a result of your retention data?

That last question is the one that separates founders who are tracking data from founders who are acting on it. Showing that you have changed something in the product, the onboarding, the pricing moment, or the content supply because your numbers told you to, is the strongest signal that the commercial model is being built on real evidence rather than maintained as a projection.

Conclusion

A credible monetisation case is built from the inside out. It starts with whether users are finding genuine value in your product, moves through whether that value is happening early enough to prevent early churn, and arrives at whether the commercial structure you have designed sits at the right point in that experience. Investors examine that chain, and every weak link in it will be found.

The founders who make the strongest commercial case are not always the ones with the most polished decks or the most aggressive projections. They are the ones who can show what their users actually did, explain honestly why some users left, and demonstrate that the product changed as a result of what the data showed. That combination, real behaviour data, honest interpretation, and evidence of response, is what makes a monetisation case believable.

Retention is commercial evidence. A product that holds users past day thirty, that converts a meaningful proportion of free users, and that can explain why users renew is already telling a better revenue story than most of what investors see. The work is in building that story from what your product actually does, not from what you expect it will do once the conditions are right.

If you are preparing for investor conversations and want to understand what your retention and conversion data is really saying about your commercial model, let's talk about your monetisation case.

Frequently Asked Questions