Meta Description: The best solo products solve problems the founder personally experiences. Learn why your own pain is a superpower, how to validate that others share it, and when personal frustration misleads you.
Keywords: scratch your own itch, solve your own problem startup, founder problem fit, dogfooding product, validate business idea personal experience
—
There is a reason so many successful solo products start with the same origin story: “I built this because I needed it and nothing else worked.”
Basecamp started because 37signals needed a better project management tool for their own consulting clients. Craigslist started because Craig Newmark wanted a simple way to share local events with friends. Thousands of smaller indie products follow the same pattern — a creator encounters a frustrating problem, builds a solution for themselves, and discovers that other people have the exact same frustration.
This is not a coincidence. Solving a problem you personally have is one of the most reliable paths to building something people actually want. It gives you a built-in testing lab, instant empathy with your customer, and a level of product intuition that no amount of market research can replicate.
But it also comes with traps. And if you do not understand both the power and the danger, your personal itch can lead you somewhere nobody else wants to go.
Concept 1: Why Personal Pain Is a Product Superpower
When you have the problem yourself, several things become dramatically easier:
You are your own first user. You do not need to recruit beta testers, set up feedback surveys, or guess what the user experience feels like. You live it. Every time you use your own product, you are testing it. Every frustration you feel is a bug report. Every moment of delight is a feature that works. This is called dogfooding — eating your own dog food — and it compresses the feedback loop to nearly zero.
You already understand the problem deeply. You know the workflow. You know the workarounds. You know which existing tools almost work but fall short in specific, maddening ways. A founder who does not have the problem needs weeks of user interviews to reach the level of understanding you already possess on day one.
You can spot fake solutions immediately. When someone pitches a solution that looks good on paper but would not actually work in practice, you know — because you have tried something similar and it failed. This intuition saves you from building features that impress demo audiences but disappoint real users.
Your marketing writes itself. When you describe the problem in your own words — the frustration, the wasted time, the anxiety — it resonates with others who share the problem because you are speaking from lived experience, not marketing personas.
As [thenextbatch.substack.com](https://thenextbatch.substack.com/) demonstrates in the craft chocolate space, Mackenzie Rivers built a school from years of actually making chocolate and facing the real challenges — not from reading about them. That lived experience is what makes the teaching credible and the business sustainable.
Concept 2: Built-In Testing — Your Daily Life Becomes Your QA Lab
One of the most expensive and time-consuming parts of building a product is testing. Formal user testing sessions require recruitment, scheduling, observation, and analysis. They happen periodically, and between sessions, you are flying blind.
When you are your own user, testing is continuous. You open the product every day to do real work. You are not performing artificial test scenarios — you are trying to accomplish actual tasks under real conditions. This surfaces problems that staged testing misses:
– Performance issues that only appear with real data volumes.
– Workflow friction that is invisible in a five-minute demo but maddening over months of daily use.
– Edge cases that arise from real-world complexity, not synthetic test cases.
– The subtle difference between “this technically works” and “this feels good to use.”
There is a practical rhythm to this. Use your product for its intended purpose every day. Keep a running note of every moment of friction, confusion, or delight. Review the list weekly and prioritise the friction items. This single practice, done consistently, will make your product substantially better than competitors who rely on quarterly user studies.
Concept 3: Validating That Others Share Your Problem
Here is where personal itch gets dangerous. Just because you have a problem does not mean enough other people have the same problem — or have it severely enough to pay for a solution.
Your problem might be:
– Too niche. You have a very specific workflow that is unusual in your industry. The problem is real but the market is 200 people, none of whom will pay enough to sustain a business.
– Too personal. Your frustration might be driven by preferences, not pain. You want a tool that organises bookmarks in a specific way. Others manage fine without it.
– Already solved well enough. The existing solutions annoy you but are “good enough” for most people. The gap between their tolerance and your standards is not wide enough to support a product.
To avoid these traps, you must validate beyond yourself. The question is not “do I have this problem?” The question is “do enough other people have this problem badly enough to pay money to solve it?”
Validation steps:
1. Search for evidence. Look for forum posts, Reddit threads, Twitter complaints, and review site grievances about the same problem. If strangers are independently describing your pain without your prompting, the problem is shared.
2. Talk to potential users. Not friends who will agree with anything you say. Actual people in your target market. Ask open-ended questions: “What is the most frustrating part of [workflow]? How do you currently handle it? How much time does it cost you?” Do not pitch your solution. Listen for the problem.
3. Check willingness to pay. The ultimate validation is money. Can you get five strangers to pre-order, put down a deposit, or pay for early access? If people who have no social obligation to you hand over cash, the problem is real, the market exists, and you have something.
4. Size the market roughly. You do not need perfect market size data. But do a rough calculation: how many people have this problem? What percentage might realistically become customers? At what price point? If the math does not produce enough revenue to sustain you, the problem might be real but the business might not be viable.
Concept 4: When Your Own Problem Misleads You
Personal experience can become a pair of blinders. You see the problem through your lens and assume everyone sees it the same way.
Two specific ways this goes wrong:
Over-engineering for your own use case. You have advanced needs. You want granular controls, customisable settings, complex filtering, and power-user shortcuts. But most of your potential customers are beginners. They need the simple version — and your instinct is to build the complex version because that is what you want. This is how products balloon in complexity while beginners bounce off the onboarding.
Solving the symptom instead of the root problem. Your frustration might be with a specific step in a workflow, but the real problem is the workflow itself. You build a better tool for step three when what customers actually need is a way to skip steps one through four entirely. Being too close to the current process makes it hard to see the radical simplification.
The antidote to both of these is talking to other people with the problem (covered in Concept 3) and watching them work. When you observe someone else struggling with the same problem, you see it with fresh eyes. Their approach might be completely different from yours, and their ideal solution might look nothing like what you would have built for yourself.
Your Action Item
The Personal Problem Audit. Write down the specific problem your product solves, in plain language. Then answer three questions honestly: (1) How often do I personally encounter this problem? (Daily, weekly, monthly, rarely?) (2) How much time or money does it cost me when it happens? (3) What do I currently do to work around it? Now take those same three questions and ask five people in your target audience — not friends, not family, real potential customers. If their answers mirror yours, you have strong founder-problem fit. If their answers are muted or confused, your personal pain might not be shared widely enough to sustain a business.
CTA Tip: Ask yourself with brutal honesty: would you pay the price you plan to charge if someone else built this product? If you hesitate, your potential customers will hesitate too.
—