The Four-Question Filter
Once you have found the itch and met your person, you need to figure out whether this idea can survive contact with reality before you hand it months of your life.
I have a filter I use. Four questions.
If your idea cannot answer all four with a clean yes, you either need to keep digging or you need to walk away.
That is not pessimism. That is discipline.
Question 1: Are People Already Paying for Something in This Space?
This sounds backwards at first.
Most builders think competition is bad. It is not. Competition is a signal. Competition means a real market already exists. If you have an idea and you look around and find ten people already making money from some version of it, that is good news, not bad news.
The bad news is when you have an idea and you cannot find anyone making money from anything close to it. That is not usually an untapped market. That is usually no market.
For MemeScanr, this part was easy. There were hundreds of photo cleanup apps in the App Store. Multiple of them had subscription revenue. Some had millions of users. The market was proven.
My job was not to prove that a market existed. My job was to find a wedge inside a market that already existed.
Wedge beats invention, almost always.
Invention is expensive. Invention is slow. Wedge is faster, clearer, and much more realistic for a solo builder using AI.
If you are building alone, you usually do not want to invent a category. You want to enter a real category with a sharper angle.
Question 2: Can You Reach the People Who Would Pay?
You can have a good idea in a real market and still fail if you have no believable path to the people who would pay for it.
This is the distribution question, and most solo builders underweight it.
Ask yourself this:
If this app existed tomorrow, how would the right people find out about it?
If your answer is “App Store search,” that is not a strategy. That is a prayer.
App Store search rewards established apps. You are not established yet.
Better answers sound more like this:
“My target user spends time in this specific subreddit, TikTok niche, or Instagram community.”
“My target user searches this exact phrase on Google, and the current results are weak.”
“My target user already follows this creator, newsletter, or account.”
“My target user is someone I can literally show this to.”
For MemeScanr, my answer was clear enough to work with: my target user spends time on photo, phone, and aesthetic TikTok, watches content about iPhone storage tips, and searches phrases like “best photo cleaner app for iPhone” on Google at least once in her life.
That gave me three real distribution bets: TikTok content, SEO pages on memescanr.com, and App Store optimization around specific search phrases.
None of those required paid ads. All of them were achievable for a solo builder.
If you cannot name three believable ways to reach your person without buying ads, your idea probably is not ready yet.
That does not mean the idea is dead. It means the path is still blurry.
Question 3: Is the Problem Painful Enough to Pay to Solve?
Some problems are real, but not painful enough to motivate payment.
These are the problems where the user says, “yeah, that is annoying,” and then goes back to their life.
The easiest test is this:
What is the user currently doing to solve this problem?
If the answer is “nothing,” or “they complain about it sometimes,” that is usually a low-pain problem, and low-pain problems are hard to monetize.
If the answer is “they pay for a bad solution,” or “they waste real time on an ugly workaround,” now you are looking at something more promising.
For MemeScanr, the pain was real. People were already doing things like:
- Ignoring the problem and paying for bigger iCloud storage plans
- Trying to delete photos manually for twenty minutes, getting frustrated, and giving up
- Paying for cleanup apps they did not even like
- Running out of storage at the exact moment they were trying to take a new photo
That last one matters a lot.
The “I am out of storage right now” moment is not abstract pain. It is acute pain. It is stressful, time-sensitive, and emotional. That is when someone opens the App Store and looks for help.
If your app is the solution they find in that moment, you are in a very strong position.
Question 4: Can You Maintain This for Two Years Without Giving Up?
This is the question most builders skip, and it kills a lot of products.
You are not building a one-week project. You are building something that needs time in the world to have a real chance.
That means you need to ask a harder question:
When the excitement fades, are you still going to care enough to keep going?
The answer usually depends on three things.
First: is the problem genuinely interesting to you? Not just the act of building. The actual problem. If you are bored of the problem by month three, you will quit. Pick a problem you can think about for two years without wanting to crawl out of your skin.
Second: does the product require you to be someone you are not? If your app is about fitness but you hate fitness, you will burn out. If your app is about journaling but you never journal, you will probably drift. Build things that fit the way you already live, think, or care.
Third: is there a version of success that would actually matter to you? Imagine the app makes $2,000 a month. Would that feel meaningful to you? Or would it feel like failure? That answer matters more than people admit. If your own success threshold is much higher than what the product is realistically likely to do, resentment will show up early.
For MemeScanr, the answer to all three was yes.
I am genuinely interested in the phone-as-clutter problem. I like thinking about it. I like reading about it. I use my own app. I am not pretending to care.
And the level of success that would feel meaningful to me is realistic for a solo builder in this space.
If you cannot pass all four questions, go back to Chapter 6 and keep looking.
That is not wasted effort. That is the filter doing its job.
The ideas you walk away from are often the ones you saved yourself from dragging for two exhausting years.
The One-Week Validation Sprint
The four questions are the filter.
The one-week validation sprint is how you answer them with something better than vibes.
This is the structure I use. Five to seven days. Not longer. Longer usually turns into procrastination wearing a research outfit.
Day 1 — Competitor archaeology. Open the App Store. Search the category your app would live in. List the top twenty results. Then go deeper on the top five: read the recent reviews, note the pricing, note the subscription structure, note the screenshots, note the last update date, and pay attention to where the complaints cluster. By the end of day one, you should know who is winning, what they are winning at, what they are weak at, and where users are already dissatisfied.
Day 2 — The bad review mine. This is the highest-value day. Go back to those same top five competitors and read one-star and two-star reviews only. Read a lot of them. Enough to notice patterns, not just anecdotes. Write down every complaint that shows up more than once. By the end of the day, you should have a list of recurring frustrations across the category. Those complaints are not random noise. They are the gaps in the market. They are the closest thing you will get to users writing you a roadmap before you even build.
Day 3 — Community immersion. Find three places where your target user actually spends time. Not where you think they should spend time. Where they really are. For a Gen Z photo cleanup app, that meant specific subreddits, specific TikTok corners, and certain Twitter or X conversations. Spend the day reading, not posting. Pay attention to the language people use when they talk about the problem. By the end of day three, you should be able to describe the problem in their words, not yours. That matters. Because if your marketing sounds like you wrote it from a conference room and your user lives on TikTok, you are already losing.
Day 4 — The show-one-person test. Pick one real human who fits your target user description and explain your idea in two sentences. Then watch their face. Not their politeness. Not their encouragement. Their face. Polite interest usually means the idea is weak. Real curiosity sounds like, “wait, tell me more.” Confused curiosity usually means the idea is fine, but the pitch is wrong.
Day 5 — The Google search test. Open an incognito browser and search the exact phrase your target user would type when they hit the problem you solve. Read the top ten results. What kinds of pages are ranking? What apps are being recommended? Are the results good? Are they weak? Is there a clear SEO opening? This tells you whether the problem already has search demand and whether there is room for you to show up.
Day 6 — The pricing check. Go back to the top five apps from day one and study the monetization. What do they charge? What do they gate? What do they give away? What feels fair? What feels too aggressive? What feels strangely underpriced? You are looking for the market-accepted range and the emotional logic behind it.
Day 7 — Go / Refine / Drop. Now make the decision. Do the four answers feel like real yeses? Or do they feel like wishful thinking?
If it is a solid yes on all four, go. If it is a solid yes on three and a shaky yes on one, refine. If two or more answers are weak, drop it and go back to Chapter 6.
Not every idea deserves your next six months.
Case Study — The Wedge Angle I Almost Missed
When I first started building MemeScanr, I was thinking of it as “an iPhone photo cleanup app.”
That was the problem.
That is a category, not a wedge.
The category had hundreds of apps in it. I could not explain why someone would pick MemeScanr over any of the others. And because I could not explain it, I could feel the weakness in the idea.
For about three weeks, I was stuck. Every feature I sketched looked like something every other cleanup app already had. I could not find the reason this product needed to exist.
Then I did the bad-review mine.
Two patterns jumped out.
First, people kept saying cleanup apps felt boring. Users described them as chores. Homework. Taxes.
Second, multiple users described them as judgmental. They already felt embarrassed about their chaotic camera rolls, and the apps made them feel worse.
That was the wedge.
Nobody was really building a cleanup app that felt good to use. Nobody was leaning into humor. Nobody was positioning the app like a friend who was in on the joke instead of a digital hall monitor.
The category had a blind spot, and that blind spot was exactly the thing I cared about.
From that point on, MemeScanr had a much clearer wedge:
photo cleanup that does not judge you
Everything started flowing from there. The voice. The Phone Therapist. The celebration screens. The Memory Lane swipe deck. Even the screenshot language.
That wedge is also why changing the first screenshot from “Smart Scan” to “your phone needs therapy” mattered so much. It was the first time the difference was visible before download.
I would not have found that wedge from imagination alone.
I found it in the complaints.
That is the lesson.
Your wedge is often hiding inside what your competitors’ users are tired of.
Go read the complaints.
> Think Before You Move On
Run your idea through all four questions. Be honest. Where is the weakest yes? That is the part of your idea that needs the most work before you start building.