Skip to content
Expert Guide Series

What Do Venture Capitalists Want to See in My App?

Venture capitalists see hundreds of pitches a year. Most of those pitches describe a product that sounds plausible, addresses a real-ish market, and has been built by a team that seems capable. Most of them do not get funded. The gap between a product that sounds good in a room and one that earns a term sheet is usually found in the details: the specifics of how users behave, what the numbers actually show, and whether the product has been tested against reality or just against the founder's own assumptions.

The question investors are really asking is: are you solving a real problem people will pay for, or are you in love with the solution?

The question founders often ask us is what investors want to see. The honest answer is that investors want to see evidence. Not projections dressed as evidence, not feature lists dressed as traction, and not a competitor grid that quietly ignores the two most dangerous players in the space. They want to see that you have spoken to real users, that those users came back, and that the business behind the product makes sense at scale.

What follows is what we think about when we work with founders preparing for investment conversations, drawn from our app planning and strategy projects and the gaps we have seen. It covers the product, the business, the emotional dimension that investors rarely name but always notice, and the silence in pitch rooms that founders too often mistake for agreement.

Evidence of Real User Demand

The most common mistake we see at pre-launch stage is a founder who has mapped every competitor product in detail but has not spoken to a single prospective user. We worked with a founder in the football industry who arrived with a colour-coded spreadsheet showing how existing apps compared across a dozen features. The plan was to merge several of those products into one. The founder was visibly pleased with the work.

When we started asking questions about why a user would choose an all-in-one product over three specialised apps they already trusted, and whether consolidation risked making each feature weaker, the energy in the room shifted. The spreadsheet felt safer than user research because nothing in it could push back. User research can tell you the idea is wrong, and that is exactly why founders avoid it.

Investors have seen this pattern too. They will ask how you know users want this, and "I think they will" is not an answer. What they are looking for is structured evidence: focus groups, surveys, usability tests with people who are not your friends or colleagues. The gap between what people say they will do and what they actually do is wide. Research from AppTweak puts stated positive intent at 60 to 80 per cent, with actual usage often sitting between 10 and 20 per cent. That gap is the reason user testing matters before you build, not after.

Run at least one round of usability testing with five to eight people who fit your target profile but have no relationship with you. Ask them to complete the core task without guidance and watch where they pause, hesitate, or give up. That data is worth more in a pitch than any projection.

A Market Opportunity Worth the Risk

Investors are buying a bet on a market. The size of the opportunity has to justify the risk, and the framing of that opportunity needs to be credible. Founders often present total addressable market figures that are technically accurate but practically meaningless, citing a global figure for a product that will realistically only compete in two countries for the first three years. Investors see through this quickly, and it costs credibility in the room.

The sharper question is not how big the market is in theory, but how much of it you can realistically reach and when. A product targeting independent physiotherapy clinics in the UK has a smaller addressable market than a general health app, but the specificity is an asset, not a liability. It tells investors you understand your customer, your channel, and your competitive position. A vague "we're targeting the global wellness market" tells them the opposite.

According to Harvard Business School, around 35 per cent of startups fail because they do not find sufficient product-market fit, often having gone to build without an MVP. The market opportunity chapter of your pitch is where you demonstrate you have done the work to avoid that outcome, not just assumed the market exists because the problem feels real to you.

Design that understands your users

We build app experiences around real user behaviour, not assumptions. Research, psychology-driven design and technical specs that turn users into loyal advocates.

See how we work Get started

No commitment

A Business Model That Holds Up to Scrutiny

A product without a credible revenue model is a prototype, not a business. Investors will probe your business model hard, and the questions they ask are designed to test whether you have thought it through or whether you have copied a structure that works for a different product in a different market.

The most common failure here is a subscription model applied to a product where the user has no reason to keep paying after month three. Subscriptions work when users receive ongoing value. If your product solves a one-time problem or delivers diminishing returns after the initial use, a subscription framing will prompt questions you will struggle to answer.

On a genetics wellness app we audited, part of the retention problem was structural: users received their results, absorbed the initial insight, and then had no compelling reason to return. The product had been built by a developer team that had stripped out the narrative and storytelling that would have given users a sense of ongoing identity within the product. Without that, the data felt like a one-time report rather than a continuing relationship. The business model cannot be separated from the product experience.

A subscription model applied to a product with no reason to return after month three is a revenue model without a product.

Investors will also test whether your pricing reflects what users will actually pay, not what you need them to pay to make the model work. If your unit economics only function at a price point that is twice what comparable products charge, that is a problem. Show that you have tested price sensitivity with real users, not just modelled it.

Map your business model against a simple question: what does the user get from you in month six that they did not get in month one? If you cannot answer that concretely, your model needs rethinking before it goes in front of investors.

Competitive Clarity Without Wishful Thinking

The competitive landscape slide is where many decks lose credibility fastest. A grid that positions your product as superior across every dimension to every competitor tells an experienced investor that you have either not done the research or you are not being honest about it. Neither reading is helpful.

Real competitive clarity means naming the two or three products that users would actually consider instead of yours, being specific about where those products are strong, and being precise about the one or two things you do meaningfully better. Not differently. Better, in ways that matter to the specific user you are targeting.

What investors are also looking for here is a credible moat: something that makes your advantage durable rather than temporary. That might be proprietary data, a distribution advantage, network effects that compound as you grow, or a regulatory position that competitors would struggle to replicate. According to Evalyze's analysis of over 8,000 pitch decks, 67 per cent had at least one issue that would surface as a flag in formal due diligence, and missing competitive moat detail was one of the most common. The moat question is not optional, and a vague answer to it will be noted.

Onboarding That Works for Strangers, Not Just the Founder

Founders know their product completely. That knowledge makes them almost useless as a judge of their own onboarding. When you build something, you cannot unknow it, which means you cannot experience it the way a first-time user does. The screens that feel obvious to you are often the ones where real users stop and give up.

We worked on a map-based fitness social network designed to connect people for runs and cycle rides. Users were dropping off at the point where they were asked to share their precise location with a potential match. The request came before users had any chance to have a conversation with or learn anything about the other person. Sharing location is a high-trust action, and the product was asking for it before trust had been established. Moving that step later in the flow, after some exchange had taken place, changed the dynamic entirely. The problem was invisible to the team who built the product because they understood the intent behind the request. A stranger did not.

The test that matters is whether a person who has never seen your product can reach the first moment of genuine value without help. That is what investors want confirmed, and what a well-run onboarding test will tell you. The five core things we check before recommending a product for investor readiness cover validated user need, a tested onboarding flow, a value proposition visible within 60 seconds, the ability to complete the first value-generating action without friction, and no overwhelming of users with too much too soon.

Retention: What Keeps Users Coming Back

Retention is where most investor conversations eventually land, because retention is where business models either hold or collapse. Business of Apps data shows that on average 77 per cent of daily active users stop using an app within the first three days of installation. That figure is a baseline problem the entire industry faces, and investors know it. What they want to see is how your product is designed to be different, and why.

The distinction that matters here is between stickiness and genuine resonance. A product can keep users engaged through confusion, compulsive loops, or gamification mechanics that have nothing to do with the core value. Session length, for example, goes up when users are lost just as it does when they are getting real value from a product. Reporting high session length without explaining what users are actually doing in those sessions is a flag, not a win. The question investors are quietly asking is whether your users come back because the product is genuinely useful to them, or because it has been designed to be hard to leave.

On the genetics wellness app we audited and then reworked, the issue was exactly this. Users were not returning because they had no narrative pulling them forward. After we rewrote the product to create a more sequential, story-driven experience and pre-framed potential confusion points (for instance, telling users that unexpected genetic results are normal and expected rather than letting them interpret those results as errors), a second round of user testing showed measurable improvements in clarity, sense of purpose, and retention. Retention is a design problem before it is a marketing problem.

In your investor conversations, separate your retention metrics by cohort and by action. Users who completed the core onboarding task retain differently from those who did not. Showing that split tells a far more convincing story than a single retention percentage.

The Emotional Dimension Investors Rarely Ask About, But Notice

Most investor due diligence covers the rational layer of a product: the technology, the market, the financials, the team. What is rarely asked about directly, but is always present in the room, is how the product feels. Does it create a genuine emotional connection with its users? Does it feel trustworthy? Does the experience match the promise the brand makes?

We worked with a pre-investment client whose investor conversations had covered technology, market size, and marketing without ever touching on what the product would feel like to use or what the retention targets looked like from an emotional design perspective. The founding team took the absence of questions in those areas as confirmation that investors were satisfied. We read it differently. The silence meant investors had not grasped the emotional dimension of the product, not that they had assessed it and approved. We had to go back and build that layer of the pitch explicitly rather than assuming it was implied by the product itself.

The genetics wellness app is the clearest example we have of what happens when emotional design is removed from a product that depends on it. The brand promise was genuinely good: a real inside look at how your body works, how it is ageing, and what you can do to improve. The developer team who built the product had stripped out the storytelling in favour of functional delivery. Users were receiving accurate data but not connecting with it emotionally. Comprehension was low, purpose was unclear, and users did not return. Reintroducing narrative, giving users a sense of identity within the product rather than just a dashboard of results, changed what the product meant to the people using it.

Technical Architecture and Defensibility

Investors with technical backgrounds will probe your architecture in specific ways. Those without will still ask questions designed to surface whether your technical foundations are sound or whether the product is sitting on choices that will become expensive problems at scale. Either way, you need to be able to speak to your technical decisions with clarity.

The questions that come up most often cover how the product scales under load, what the data model looks like and whether it creates lock-in for users, what happens if a third-party dependency changes its pricing or terms, and how quickly the team can respond to a security issue. These questions are designed to test whether the technical team has built with foresight or whether the architecture is a set of shortcuts that made sense at prototype stage and will cost heavily later.

The dating app project we worked on is a direct example of what happens when architectural decisions are made without full discovery. The client wanted to skip discovery on the messaging component and focus entirely on onboarding. The result was a generic messaging feature that allowed automated and fake messages, directly contradicting the verified-profile premise the entire product was built around. The mismatch required a full rewrite of the messaging section, at a cost of approximately £15,000 in additional budget and two months of extra time. Decisions that look like savings at the start of a build frequently cost far more at the end of one.

The Team Behind the Product

Investors are investing in the people who will make the thousand decisions that come after the pitch. The team slide is often treated as a formality, but experienced investors read it carefully for specific signals.

What they are looking for is complementarity. A founding team of three engineers building a consumer product has a gap. A team of two designers and a growth marketer building enterprise software has a different one. Gaps are not disqualifying, but pretending they do not exist is. Naming the gap and explaining how you are addressing it (through an advisor, a planned hire, or a partnership) is a far stronger position than presenting a team as complete when it clearly has missing capability.

Domain credibility matters too. If you are building a product for independent pharmacies, investors want to see evidence that someone on your team understands that world from the inside, whether through work history, research, or sustained contact with the people you are building for. General capability is not the same as specific credibility.

The property developer who came to us with a pre-formed concierge app concept had strong domain knowledge of high-rise property but limited understanding of digital product design. Recognising that gap and bringing in the right support was part of what made the discovery process productive: the team understood the problem deeply, and we brought the product thinking. That kind of complementarity is what investors are looking for in a founding team.

Financial Projections and Unit Economics

Financial projections in a pitch deck are understood by everyone in the room to be estimates. Investors do not expect them to be accurate. What they do expect is for the assumptions behind them to be coherent, and for you to be able to defend those assumptions under questioning.

The numbers investors look at most closely are unit economics: customer acquisition cost, lifetime value, and the relationship between them. A product with a £60 acquisition cost and a £40 lifetime value is not a business yet, and presenting it as one will end the conversation. What investors want to see is a clear understanding of those numbers at current state and a credible explanation of how they improve as the product scales.

Metric What investors want to see Common mistake
Customer acquisition cost (CAC) Broken down by channel, with real test data Blended average with no channel detail
Lifetime value (LTV) Based on observed cohort behaviour Modelled from assumed retention, not measured
LTV to CAC ratio 3:1 or better at target scale Ratio only reaches target in year four projections
Burn rate Linked to specific milestones and hires Presented as a flat monthly figure without context

Aggressive projections without supporting cohort data are the single most common flag in formal due diligence. Show your working, name your assumptions, and be prepared to explain what changes if one of those assumptions turns out to be wrong.

What Silence in the Pitch Room Actually Means

Silence in a pitch room is rarely neutral. When investors stop asking questions, founders sometimes read that as a sign that everything is clear and satisfactory. In our experience, it more often means one of two things: either the investor has already made a decision and is mentally elsewhere, or there is a dimension of the product they have not fully understood and do not yet know how to probe.

The second case is the one that founders can do something about. We saw this directly with the pre-investment client whose investor conversations had covered technology, market, and marketing without ever touching the emotional experience of the product or the retention design behind it. The investors were not satisfied with those areas, they simply did not have the framework to ask the right questions. Silence in those areas was not approval. It was absence.

When investors stop asking questions, founders often read it as approval. More often, it means a dimension of the product has not been understood well enough to probe.

The practical implication is that you should not wait for investors to surface every concern. If you know your product has a strong emotional design rationale, explain it without being asked. If your retention numbers are unusual for your category, contextualise them before the question comes. Proactive clarity on the dimensions investors find hardest to articulate is a signal of founder maturity, and it prevents silence from being misread in either direction.

  1. Prepare a short explanation of your retention design that you can deliver even if nobody asks.
  2. Know which parts of your product are emotionally distinctive and be ready to name them specifically.
  3. If a topic generates no questions, probe gently: "I want to make sure I've covered the emotional side of the product clearly, do you want more on that?"

Conclusion

Investor readiness is a product skill. The founders who get to term sheets are the ones who have done the hard work before the pitch: speaking to real users, testing onboarding with strangers, understanding why people come back, and being honest about the gaps in their competitive position and their team.

The emotional dimension of a product is one of the areas where founders most often leave value on the table. It is rarely asked about directly, but it shapes how an investor feels about a product after the meeting, and that feeling influences decisions. The genetics wellness app we reworked did not fail because the brand promise was wrong. It failed because the product had been built without the narrative that would have made users feel something when they used it. Fixing that changed what the product was capable of.

The questions worth sitting with before any investor conversation are simple ones. Do you know, from real evidence, that people want this? Do they come back? Does the business make sense at scale? And are you solving a real problem that people will pay for, or are you in love with the solution? Those questions will not all have perfect answers at pre-launch stage, but having thought them through carefully, and being able to show the work you have done to address them, is what separates a fundable product from an interesting idea.

If you are preparing for investment conversations and want a clear-eyed view of where your product stands, let's talk about your pitch readiness.

Frequently Asked Questions

What kind of evidence do venture capitalists actually want to see?

Investors want to see concrete evidence that real users have engaged with your product and found it valuable. This means structured research such as usability tests, surveys, and focus groups with people who have no personal connection to you or your team, not projections or feature comparisons.

Why is user research more important than competitor analysis?

Competitor analysis tells you what already exists, but it cannot tell you whether users will actually choose your product over what they already trust. User research can reveal that your core assumption is wrong before you invest in building, which is precisely why investors value it so highly.

How many people do I need to test my app with before pitching?

Running at least one round of usability testing with five to eight people who match your target user profile is a practical starting point. The key is that these participants should have no existing relationship with you, so their feedback is genuinely unbiased.

What is the gap between stated user intent and actual usage, and why does it matter?

Research suggests that while 60 to 80 per cent of people may express positive intent towards an app, actual usage often falls between 10 and 20 per cent. This gap is exactly why testing how users behave in practice matters far more than asking whether they think they would use something.

How should I frame my market size figures for investors?

Global total addressable market figures can sound impressive but often lack credibility if your product will realistically only compete in a specific region or segment. Investors respond better to figures that are honestly scoped and clearly justified, rather than technically accurate but practically misleading.

What mistake do founders most commonly make before pitching?

The most common mistake is spending significant time analysing competitors in detail while never speaking to a single prospective user. Competitor spreadsheets feel safer because the data cannot push back, but investors will immediately ask how you know users actually want what you are building.

What is the core question investors are trying to answer when they review an app pitch?

Investors are fundamentally trying to work out whether you are solving a real problem that people will pay for, or whether you have simply fallen in love with your own solution. The distinction matters because founders who are attached to a solution often miss clear signals that the market does not need it.

What does silence in a pitch room usually mean?

Founders often interpret a quiet room as a sign that their pitch is landing well, but silence can indicate that investors are unconvinced and choosing not to probe further. It is important not to mistake a lack of challenge for agreement, as investors who are genuinely interested tend to ask specific, detailed questions.