App market research: how to size the opportunity before you build

Founders research the product obsessively and the market barely at all. That's backwards — the market decides more than the product does.

Ask a founder about their app and you'll get a fluent tour of features. Ask about the market — who exactly needs this, how many of them there are, what they use today, whether they'll pay — and the answers get vague fast. That gap is dangerous, because the market determines an app's fate more than the feature set does. A great product in a market that doesn't want it still fails.

Here's how to research the opportunity properly, without a research budget or an agency.

Start with the problem, not the size

Before estimating how big the market is, confirm the problem is real and painful for a specific group. Market research that starts with a giant number — "the app market is worth billions" — is working backward. Start narrow: who has this problem, how acutely, and what does it cost them today? A small market of people in real pain beats a huge market of mild indifference. This overlaps directly with validating the idea.

Define the audience concretely

"Everyone" is not a market and "small business owners" is barely better. Define your target user tightly enough to find and describe them: their situation, the specific job they're trying to do, how they solve it now. The tighter the definition, the more real the research becomes — you can actually go find these people and learn from them, rather than theorizing about an abstraction.

Study how people solve it today

Every problem worth solving already has a current solution — a competitor app, a web tool, a spreadsheet, or a manual workaround. Studying the status quo tells you what you're really competing against and what "good enough" already looks like to users. The status quo is usually your toughest competitor, and "free and familiar" is harder to beat than any rival app. This is the heart of a proper competitor analysis.

Mine the sources that are free and honest

You don't need paid research to learn a great deal. The richest free sources:

• App store reviews of competing apps — especially the one- and three-star ones, which are a validated list of unmet needs someone else already paid to discover.
• Search behavior — what people search around your problem reveals demand, language, and intent.
• Communities — forums, subreddits, and groups where your target users discuss the problem in their own words.
• Direct conversations — the single best source, and the one founders most avoid because it risks hearing no.

Size it, roughly, from the bottom up

Once the problem and audience are real, estimate the opportunity — but build it from the bottom up, not the top down. Top-down ("1% of a huge market") is a fantasy number. Bottom-up starts from your reachable audience: how many people fit your specific target, how you'd reach them, and what they'd plausibly pay. A rough, defensible bottom-up estimate is worth more than an impressive top-down one, because you can actually act on it. It feeds directly into your unit economics and pricing.

Decide what the research is telling you

Research is only useful if you'll act on it. Strong signals — a specific group, real pain, weak incumbents, reachable audience — mean proceed. Mixed signals mean adjust the target or the solution. Weak signals — no clear audience, mild problem, entrenched free alternatives — mean reshape or stop before you spend a build budget. Killing a weak opportunity at the research stage is the cheapest win available; discovering it after launch is the most expensive.

Where this fits in the plan

Market research isn't a phase you do once and file away — it shapes everything downstream: your positioning, your MVP scope, your pricing, your launch. That's why it belongs early, in the planning work before you build, not as a slide you assemble to justify a decision already made. The full arc is in planning your app and reading the market.