How to size a market using community signals (no analyst reports required)

Traditional market sizing involves buying a Gartner report, adjusting a TAM calculation, and presenting a hockey stick slide to investors. It tells you almost nothing about whether your specific niche is large enough to build a business on.

Community-based market sizing is different. It starts with real people who have the problem, counts how many there are and how frequently they surface, and produces an estimate grounded in observable demand, not in analyst projections.

Why community signals are better than top-down market sizing

A top-down analysis says "the project management software market is $8 billion." That's true and useless. You're not competing in the whole market. You're competing for a specific segment, a specific job title, problem framing, or use case.

Community signals tell you how active that specific segment is. If you search for a niche problem and find five posts per week from engaged users, that's a different market than finding five posts in total. Volume and recurrence are the proxies you actually need.

Step 1: Count the active problem-seekers

Open the bing.ly Ideas tool and search your specific problem framing. Not the broad category, the specific painful version. Count the number of unique posts from unique users in the last 90 days.

This is your floor estimate for "actively struggling with this problem right now." The real number is much larger, most people don't post. A common rule of thumb is that for every person who posts, 10 others have the same problem silently. Use this as a multiplier cautiously, but it gives you a sense of scale.

Step 2: Measure recurrence, not just volume

A market that had lots of posts three years ago and silence now is a declining market or a solved problem. A market where posts appear consistently every week is an unsolved, active market.

Filter the feed by time period and look at consistency. Are posts appearing at a steady rate? Is the volume growing or declining? Consistent volume over 12+ months is the strongest signal that you're looking at an evergreen problem.

Step 3: Count the source communities

How many distinct communities are discussing this problem? A problem discussed in one subreddit is a niche. A problem discussed in thirty subreddits, across multiple platforms, in different industries, that's a market.

The bing.ly feed pulls from Reddit, Hacker News, G2, App Store reviews, and other sources. A problem that surfaces across all these platforms is one that doesn't belong to a single community, it's structural.

Step 4: Measure buying signal density

Volume tells you how many people have the problem. Buying signal density tells you how many are actively spending to solve it.

Filter to Buying Signals and note the ratio of pain posts to buying-signal posts. A market where 30% of pain posts are accompanied by spending references is healthier than one where 95% of people describe the problem but nobody mentions paying for solutions. High buying signal density means the problem is already monetised, you're competing for wallet share, not creating a market from scratch.

Step 5: Estimate the minimum viable market

For a bootstrapped SaaS, you typically need 500-1,000 paying customers to build a sustainable business. For a VC-backed product, you need a clearer path to 10,000+.

If your 90-day active user count (posts × multiplier) is well above 50,000, you have enough market for either. If it's 5,000 to 50,000, you have a viable bootstrapped market. Below 5,000, reconsider whether the niche is large enough or whether you need to broaden the problem frame.

What this analysis can't tell you

Community-based sizing is excellent for validation but imperfect for absolute numbers. It doesn't account for enterprise buyers who don't post publicly, or for international markets that underindex on English-language communities.

Use it as a directional filter, not a final answer. If the signal is strong, consistent volume, cross-platform presence, high buying signal density, you have enough evidence to start building. If the signal is weak, you need to answer "why is this problem invisible in communities?" before proceeding.