A Market Opportunity Assessment You Can Do This Week

A market opportunity assessment sounds like something a firm does with a slide deck and a budget. For a solo founder it needs to be smaller than that, or it never happens.

The version below takes one working week, uses discussions that already exist in public, and ends with a decision you can defend: build it, narrow it, or drop it.

What the Assessment Has to Answer

Skip everything that does not feed one of these five answers. Every task you plan should map to one of them.

• Is the problem real? People describe it in their own words, unasked.
• Is it painful enough to change behavior? They have a workaround, a spreadsheet, a script, or a person paid to do it.
• Who feels it most? One group complains more specifically and more often than the rest.
• What do they use today? Existing tools, however bad, are your real competition.
• What would make this a bad idea? The evidence that would kill it, written down before you start collecting.

That last item is what separates an assessment from a search for encouragement.

The Week, Day by Day

Five days is enough if you keep each day narrow. Skip the market size studies entirely; you cannot verify them and they do not change your next step.

1. Day one, define the claim. Write the problem in one sentence and the audience in three words. List the terms a frustrated person would search, not the terms a vendor would use. Aim for five terms.
2. Day two, collect. Run every term through the communities you can reach and save forty to sixty posts and comments. Copy the raw text somewhere you control.
3. Day three, extract. Pull out every sentence that describes a situation, a cost, or a workaround. Keep the words exactly as written, plus the link. Delete opinions about hypothetical features.
4. Day four, group and score. Merge near-duplicates, label each group by the task it describes, and rate each one on how often it returns, what the workaround costs, and whether people already spend money.
5. Day five, challenge and decide. Spend the morning trying to break your top choice, then write the one-page result: claim, evidence, counter evidence, decision.

Two days of reading, one day of honest grouping, and one day of trying to prove yourself wrong.

The Checklist

Print this and cross items off. If an item takes more than an hour, you are doing it too thoroughly for a first pass.

• One sentence claim, written down before searching.
• Five search terms in the language of the person with the problem.
• Forty to sixty saved posts with links.
• Quotes copied word for word, not summarized.
• Groups labeled by task, not by emotion.
• Distinct people counted per group.
• Workarounds listed for the top three groups.
• Existing spend noted anywhere you can find it, such as people paying for a partial fix.
• The same problem found in at least two separate communities.
• A written list of reasons the idea could fail.
• A one-line decision with a date on it.

The date matters. An assessment without a deadline turns into a hobby.

Reading the Result

The output is not a number. It is one of three sentences.

• Build it. The problem appears across communities, people already work around it, and some of them already pay for something that only partly helps.
• Narrow it. The pain is real but scattered. Pick the group with the most specific complaint and re-run the week against them alone.
• Drop it. The complaints are wishes rather than situations, the workarounds are cheap, or the existing tools already solve it well enough.

Dropping an idea in five days is a bargain. The expensive version of this decision is the one you make after four months of building.

The result also tells you what to do next. If the answer is build, the next step is a small paid test, not a full product. If the answer is narrow, re-run day two with the new terms and a tighter audience. If the answer is drop, write the reason in one line so a future version of the same idea does not quietly bring you back here.

Keep the collection and the decision in one document. Splitting them across a notes app, a bookmarks folder, and a chat message is how an assessment dies without anyone noticing.

FAQ

Do I need market size numbers for this?

No. Numbers you cannot verify add confidence without adding understanding. Evidence from real posts is more useful for the decision in front of you.

How is this different from competitor research?

Competitor research asks who else is selling. This asks whether the problem hurts enough that someone would switch, volunteer time, or pay. The second question answers the first one faster.

What if I cannot find forty posts?

That is a result too. It usually means the problem is narrow or you are searching with the wrong words. Try the terms people use when they are stuck, not the terms marketers use.

Can this be done in a day?

A rough version, yes. If you shorten the collection to one community and skip the counter evidence pass, expect a weaker decision. The week exists to remove the shortcuts, not to fill time.

If day two and day three are the parts you would rather not do by hand, the research tool handles them: it collects discussions from Reddit’s public archive, Hacker News, Stack Overflow, and GitHub, merges duplicate problems into clusters, and keeps only quotes it can match against the original text. A report takes two to four minutes and costs 2.99 EUR once. To tighten the method, read Evidence-Based Idea Validation: What Counts as Proof and Reddit vs Hacker News vs Stack Overflow for Research.