--- title: What the Term 'Vanity Product' Means and How to Spot One Before You Fund It description: Spot vanity products before you fund them. This guide covers key warning signs, founder blind spots, and how to tell genuine vision from self-deception. image: https://weareaffective.com/hubfs/learning-centre-images/what-the-term-vanity-product-means-and-how-to-spot-one-before-you-fund-it.webp --- [Skip to content](https://weareaffective.com/learning-centre/what-the-term-vanity-product-means-and-how-to-spot-one-before-you-fund-it#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 # What the Term 'Vanity Product' Means and How to Spot One Before You Fund It Table of Contents A founder walks in with a colour-coded spreadsheet. Every competitor product is mapped across forty-three columns. Feature sets, price points, app store ratings, target demographics. The work is meticulous. The energy in the room is high. And somewhere in the back of your mind, a quiet alarm starts ringing. We have seen this moment more than once, and the spreadsheet is rarely the problem. The problem is what it represents: a founder who has already decided what they are building, and who is now looking for confirmation rather than enquiry. The research feels thorough. The conviction feels like confidence. But underneath it, something is missing, and that missing thing is the user. The term "vanity product" gets used loosely, sometimes to mean a product with shallow metrics, sometimes to describe something built for press rather than people. We use it in a more specific sense: a product shaped primarily by the founder's own preferences, built around what they believe the market wants rather than what the market has actually said. Spotting one before significant money goes in is a skill, and it starts with knowing what to look for. ## What a Vanity Product Actually Is A vanity product is one that exists, at its core, to satisfy the founder's vision rather than a genuine market need. The founder may be passionate, experienced, and entirely sincere. The product may be technically well-built. None of that changes the underlying problem, which is that the decision about [what to build came before, and often entirely without, evidence](https://weareaffective.com/learning-centre/how-to-spot-a-product-vision-that-wont-survive-first-contact-with-users) from the people who are supposed to use it. Simon's defining question for founders is worth sitting with here: "Are you solving a real problem that people will pay for, or are you yourself in love with the solution?" That single question does a lot of sorting work. A product built around a real, documented, painful problem has a chance even if the execution is imperfect. A product built around a founder's love of their own idea is exposed the moment it meets the market, however polished the execution. The distinction matters because vanity products tend to absorb disproportionate time and money in design and build, chasing a version of the product that feels right to the founder, rather than a version that has been tested and shaped by actual users. By the time the market responds, the budget is often gone. ## Why Founder Conviction Becomes a Liability Conviction is genuinely useful early on. A founder who does not believe in what they are building will not survive the first difficult month. But conviction has a ceiling, and past that ceiling it stops being a fuel and starts being a filter, one that screens out inconvenient information. We flagged this pattern across two specific projects: a fitness and wellness app and a grassroots football product. In both cases, the founders had strong personal conviction in their vision. In both cases, data from research, focus groups, and surveys pointed in a different direction. And in both cases, the founders did not move. The products kept being refined to match the founder's preferences rather than the emerging evidence. Both projects exhausted their budgets in design and build without ever reaching a fully live product. What makes conviction a liability at this stage is that it feels indistinguishable from clarity. A founder who is certain is often read as a founder who has done the work. Investors respond to certainty. Teams rally around it. But certainty and validation are not the same thing, and a [product development process that cannot tell the difference](https://weareaffective.com/app-planning-strategy) between them is already in trouble. ## 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](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## The Spreadsheet Moment: When Excitement Replaces Enquiry We worked with a pre-launch founder in the football industry who arrived with a colour-coded spreadsheet mapping every significant competitor product across the market. The plan was to merge the best features of multiple existing products into one. The founder was visibly excited, pleased with the thoroughness of the analysis, and ready to move quickly into design. The spreadsheet told us a lot about the competitive landscape. What it told us nothing about was [why someone would choose an all-in-one product](https://weareaffective.com/learning-centre/what-are-the-most-common-mistakes-startups-make-when-building-their-first-app) over the specialised apps they were already using, or whether consolidating features would make each individual feature worse by comparison. When we started asking those questions, the mood in the room shifted. The founder became deflated. Not because the questions were harsh, but because they had not been asked before, and the spreadsheet had provided a kind of comfort that felt like progress. > Founders gravitate towards competitive mapping because a spreadsheet provides immediate, unchallenged validation of opinions they already hold. This is the spreadsheet moment: when excitement about a product replaces honest enquiry into whether the product should exist in its current form. The competitive analysis is tangible, quick to produce, and impossible to argue with in the room. User research is slower, more expensive, and carries the risk of a finding the founder does not want to hear. Before funding any further design work, ask the founder to show you three conversations they have had with prospective users in the last month. Not surveys, not comments, not assumed demand. Actual conversations. ## Research as a Box-Ticking Exercise The harder version of this problem is the founder who does commission research but has no genuine intention of acting on it. We worked with one such founder, a person with deep industry experience and very fixed views about how the product should work. The research process was present in the project plan. The findings were gathered. And then, almost entirely, they were set aside. We presented compelling evidence that a significant portion of the target user base did not want certain features and actively preferred alternatives. The founder did not move. Every finding was met with a reason why that particular segment was not the real target user, or why the research methodology had missed something. The research had become a box-ticking exercise, something to include in an investor deck rather than something to genuinely inform the product. We eventually walked away from that engagement. The product launched roughly a year later, largely unchanged from the founder's original vision. By our account, it did not go anywhere. The reasons the research had flagged were the same reasons the product struggled in the market. The concerning part of this pattern is how professional it looks from the outside. There is a research process. There are findings documents. The boxes are ticked. What is absent is [any genuine curiosity about what the findings mean](https://weareaffective.com/learning-centre/what-curiosity-looks-like-in-a-first-session-and-why-most-products-design-past-i) for the product direction. ## The Specific Signals to Watch For Identifying a vanity product before money is committed requires looking past the energy in the room and at a handful of concrete signals. The founder's affect and the quality of their deck are not reliable guides. These are. - The founder can describe the product in detail but struggles to describe the user's current frustration with precision. - Research has been done but the findings are summarised as confirmation rather than as a set of questions to work through. - Sign-offs keep getting rolled back so that further changes can be made before launch, with the product never quite feeling ready. - The founder responds to challenging questions by explaining the product more thoroughly, rather than engaging with the underlying concern. - The competitive analysis is extensive but user interviews are absent, planned for later, or treated as a minor step. CB Insights has reported that [42% of startups fail due to no market need](https://www.techqware.com/blog/10-common-mistakes-founders-make-before-starting-app-development). That figure points to a fundamental and repeated error: products that exist because a founder believed in them rather than because a market asked for them. The signals above are the early form of that failure, visible well before launch if you know to look for them. ## Insider Bias and Why Founders Mistake Familiarity for Validation There is a particular version of the "the research confirms us" problem that is worth naming on its own. When a founder and their team use a product they have built, everything about it feels intuitive. The navigation makes sense. The terminology lands. The flow feels obvious. And they read that as evidence that the product works. The problem is that they already understand the product's logic. They have been living inside it for months. A new user arriving without that context will experience an entirely different product, and [what feels intuitive to an insider will often feel opaque](https://weareaffective.com/learning-centre/how-to-read-a-user-session-recording-for-emotional-signal-rather-than-task-compl) to someone approaching it fresh. Conflating insider familiarity with user intuitiveness is one of the more common ways that product teams deceive themselves about how ready something is. This is relevant to vanity products because the founder's deep belief in their own product is often, at least in part, a product of how well they know it. Their familiarity generates confidence. That confidence gets read as validation. And because the people around them tend to share similar levels of exposure to the product, the bias rarely gets challenged internally. Ask your founder to watch someone who has never seen the product try to complete one core task without guidance. Not to explain after, just to watch. That observation tends to do more in five minutes than a research report can do in fifty pages. ## What Investor Silence Actually Means One of the subtler risks in the pre-funding stage is treating investor silence as endorsement. We worked with a pre-investment client whose investor conversations covered technology, marketing, and market size in reasonable depth. What never came up was how the product would feel to use, or what [user retention was expected to look like](https://weareaffective.com/learning-centre/why-your-best-users-are-often-your-worst-source-of-product-direction) over the first three months. The founder read the absence of those questions as a sign that investors were satisfied. In practice, investors had not grasped the emotional dimension of the product at all. They were not unconvinced by the retention story; they had simply not encountered it. When we looked at what was actually being communicated in those meetings, we could see that the [emotional value of the product was being assumed](https://weareaffective.com/learning-centre/why-do-some-apps-feel-like-they-were-made-just-for-you) rather than articulated. We had to go back and build that part of the story deliberately, rather than accepting the silence as confirmation. The same dynamic appears when advisors or early team members stop pushing back on a product decision. In a room full of people who share the founder's conviction, the absence of challenge feels like agreement. More often, it means that the challenge has been exhausted, not that the underlying concern has been resolved. ## How to Tell the Difference Between Vision and Vanity Not every founder who is certain about their product is building a vanity product. Conviction grounded in genuine user evidence looks different from conviction that has not been tested. The table below describes where those differences tend to appear. | Dimension | Vision-led | Vanity-led | | --- | --- | --- | | Source of certainty | User interviews, surveys, observed behaviour | Personal experience, competitive analysis, instinct | | Response to contrary findings | Engages with the finding, adjusts or tests further | Dismisses finding or reframes the sample | | Description of the user | Specific, including their current frustration | General, defined by assumed desire for the product | | Launch readiness | Willing to ship imperfect and learn | Keeps refining toward an ideal that keeps moving | | Relationship to research | Genuinely curious about findings | Treats research as something to include, not act on | The question "are you solving a real problem that people will pay for, or are you in love with the solution?" is a useful starting test. But the table above is where you see the answer playing out in practice. Vision-led founders change their minds when the evidence asks them to. Vanity-led founders explain why the evidence does not apply. ## What to Do If You Spot These Signals Early If you are an investor, adviser, or agency partner and you are seeing these signals before a significant financial commitment has been made, the most useful thing you can do is name what you are observing and ask a direct question rather than softening it into a general concern. We have also found that every product launch produces feedback that redirects the product in ways the internal team did not anticipate. That is simply how products actually develop. The problem with vanity products is that the founder's conviction prevents that feedback from doing its job, so the loop never closes. If a founder is resistant to user research, suggest a single two-hour session with five prospective users before the next build phase. Frame it as a way to strengthen the product's story with investors, rather than as a test of the idea. The goal is to get real users into the room, whatever the framing. Where research has already been done and the findings are being dismissed, ask to see the actual findings rather than the summary. Summaries of research produced by teams who have already decided what they think tend to look very different from the underlying data. That gap, when you find it, tells you a great deal. 1. Ask the founder to describe three things the research changed about the product direction. 2. Review the findings document directly, not the summary in the deck. 3. Ask who the [research participants were and how they were recruited](https://weareaffective.com/learning-centre/5-things-that-make-the-difference-between-so-so-apps-and-stellar-apps-what-your-). 4. Request evidence of a decision that went against the founder's initial preference because of what users said. ## Conclusion The vanity product problem is not rare, and it is rarely visible to the people building the product. The founders we have seen fall into this pattern are often among the most knowledgeable people in their space. Their expertise is real. Their passion is real. What is absent is the discipline to hold that conviction loosely enough that user evidence can shape it. Research from MIT Professional Programs suggests that [between 80 and 95% of new products fail within their first two years](https://professionalprograms.mit.edu/blog/design/why-95-of-new-products-miss-the-mark-and-how-yours-can-avoid-the-same-fate/). A significant portion of those failures are products that never genuinely asked the market whether it wanted what was being built. The vanity product pattern is one of the more consistent ways that gap between assumption and reality goes unaddressed until it is expensive to fix. Spotting it early requires watching for the signals: the research that changes nothing, the sign-offs that keep rolling back, the user interviews that never quite happen, the investor silence that gets read as alignment. None of those signals alone is conclusive. Together, they describe a product that is being built for the founder rather than for the market. If you are working with a founder who is showing these patterns, or if you are a founder who recognises some of them in your own process, the conversation worth having is an honest one about what the evidence is actually saying. [Let's talk about your product and what the research should be telling you.](https://weareaffective.com/get-started) ## Frequently Asked Questions What exactly is a vanity product? A vanity product is one built primarily around a founder's own vision and preferences rather than evidence from the people who are supposed to use it. The founder may be skilled and sincere, but the core problem is that the decision about what to build came before, or entirely without, real user research. How is a vanity product different from a poorly executed product? A vanity product can actually be technically well-built and polished. The issue is not the quality of execution but the absence of genuine market validation behind the original concept. Why is founder conviction sometimes a warning sign? Conviction is useful in the early stages, but it can become a filter that screens out inconvenient evidence once it reaches a certain point. A founder who is certain can appear to have done thorough work, even when their confidence is not backed by actual user validation. What is the key question to ask a founder to identify a vanity product? The most useful question is whether they are solving a real problem that people will pay for, or whether they are in love with their own solution. This single question quickly reveals whether the product is rooted in genuine user need or personal enthusiasm. How do vanity products typically drain budgets? They tend to absorb disproportionate time and money in design and build, chasing a version of the product that feels right to the founder rather than one shaped by user testing. By the time the market responds, the available budget has often already been spent. What does a meticulous competitor analysis tell you about a founder? Thorough competitor research can signal that a founder has already decided what they are building and is seeking confirmation rather than genuine enquiry. The research may look impressive, but if the user is missing from the process, the analysis is unlikely to surface the right insights. Can a product survive being a vanity product if the execution is strong? A product built around a real and painful problem has a chance of succeeding even with imperfect execution. However, a product built around a founder's love of their own idea is likely to struggle the moment it meets the market, regardless of how polished it appears. What should investors or collaborators look for before funding a new product? They should look for evidence that the product has been shaped by actual users rather than the founder's preferences alone. If research, focus groups, or surveys point in a different direction from the founder's vision and the founder does not respond to that, it is a significant warning sign. ## Related Articles [![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.