How to Know If the Problem You Want to Solve Is Real
Three strangers, in three different places, complaining in the past few months, each having paid for a workaround. That is the test for whether a problem is real. Without it, the problem is yours alone, and a weekend of building will not change that.
The exercise below runs in twenty minutes, on your phone, for free. It is mechanical. It does not need taste, conviction, or a co-founder's opinion. It needs a count.
Where do strangers complain about this without naming your idea?
Search for the problem in Reddit threads, app store reviews, community forums, and social media. Look for people describing their pain without naming what you plan to build. Their exact words become your evidence that the problem lives outside your head. Do not search for your idea. Search for the frustration.
Three search patterns catch what polished intros miss. The "how do you deal with" form — people asking how to cope with something they wish did not exist. The low-star app review on an adjacent tool, where the complaint is "I love this but the export step is hell." The unsentimental question on Hacker News or a niche subreddit, asked briefly, that gets a thread full of agreement.
The phrasing matters more than the source. Phrase the problem in the words your target customer would actually type, not in the words you would use to describe your product. If you are building invoicing for freelancers, do not search "freelancer invoicing tool." Search "I just spent hours chasing a late invoice." If those two sentences appear in the wild, the problem lives somewhere other than your notes.
The independence rule
A complaint from a co-founder, an early user you interviewed, or a colleague does not count. They have been primed by your enthusiasm. You need strangers who complained without ever hearing your idea. Unsolicited complaints from unconnected people are the only evidence that survives.
The primed-confirmation problem is older than startups. Ask a friend whether they would use your product and you have learned nothing about the problem; you have learned how polite your friend is. The clean signal is a complaint posted recently by a stranger in a forum you have never posted in, who has no reason to flatter you, and who is asking for help.
Three different people, in three different places, who have never heard of you — that is the floor. One person is anecdote. Two might still be coincidence. Three, in different communities, with no path to your idea, is the smallest pattern worth believing.
People paying for a workaround proves the problem has value
A complaint is an opinion. A paying customer is a decision. If strangers are spending money or significant time to work around the problem—even with an imperfect tool—they have demonstrated willingness to pay. Find where they pay. That is your market.
Time is money here, and the rule does not flinch when the workaround is ugly. A sprawling spreadsheet that someone updates every Friday is a workaround. A template someone shares on a forum is a workaround. A subscription tool that almost solves the problem is a workaround. A freelancer on a gig platform charging a fee to do the task is a workaround. All of them prove the same thing: someone decided the pain was worth exchanging something for.
The market you want is the workaround, not the absence of a workaround. People who currently pay for something imperfect are reachable, accustomed to opening a wallet, and already aware of the problem in language that sounds like theirs. Replace their current tool and you have a buyer. Sell to people who currently do nothing and you have a sales call.
How recent is recent enough?
A complaint from three years ago may reflect a problem that platforms, regulations, or new tools have already solved. Focus on signals from the past few months. Recency confirms the problem is alive today, not archived frustration from a market that moved on.
Software markets move fast. A platform bug that broke a workflow last year may already be patched. A platform policy that annoyed a community a while back may have been rewritten. A workaround that was the only option then may now sit next to newer alternatives. Old pain is not the same as current pain, and treating a stale thread as live evidence is how founders spend a year building for a problem that quietly ended.
Sort by recency. Filter to the recent posts. If the complaints dry up after the date filter, the market has moved on or the problem was seasonal. If the same complaint keeps reappearing in fresh posts, you have a live signal.
Three independent, recent, paying mentions or it stays a hobby
Find three different strangers, in three different places, complaining recently about the same problem, and each having paid for a workaround. That is your pass condition. If you cannot find three in an afternoon of searching, the problem is not ready to be a business. It stays a hobby until it is.
The number three is small on purpose. One is anecdote. Two is coincidence. Three is the smallest pattern a person can defend without sounding convinced. A larger sample is more rigorous but rarely required, and the cost of finding more is the same as the cost of finding three — a phone, an hour, and a careful filter.
The pass condition is mechanical. Three strangers. Three different places. Recent posts. Each paying something — money, time, attention — for a workaround. Every box ticked: pass. Any box missing: hobby, for now, until the evidence changes. The decision does not need taste, conviction, or a co-founder's opinion. It needs a count.
A twenty-minute check, on your phone, for free
State the problem in one sentence. Search it on Reddit, in app store reviews, on GitHub issue trackers, and on social media. Read what strangers wrote. Count three qualifying signals or stop. No tools required. No credit card. No sign-up. The evidence is public and free.
The twenty-minute budget is the point. With a weekend, you can find anything you want to find. With a month, you can talk yourself into a market that does not exist. With twenty minutes and a phone, you are forced to look at what is actually there.
| Source | Search form | Qualifying signal |
|---|---|---|
| "how do you deal with X" in topic subs | Top comments agreeing, no one naming your product | |
| App Store reviews | Low-star reviews of adjacent tools | "I wish it would…" or "the only reason I keep paying…" |
| GitHub issues | Issues on libraries your users would touch | "+1 me too" stack on the same complaint |
| Hacker News / X | "Ask HN" or "spent an hour on" | Commenters trading their own workarounds |
The check is the same regardless of idea. The sources are free. The pass condition is mechanical. The hobby framing is not a verdict on the founder — it is a verdict on the evidence available today. The problem can graduate later, when more signals appear. Until then, the weekend stays unscheduled.