SaaS Market Research Guide: How to Size, Segment, and Validate a Market

Most SaaS market research produces a document nobody uses: a TAM slide, a competitor feature grid, a persona named "Marketing Mary." Useful research produces something else — a decision, backed by evidence a skeptic would accept.

This guide covers the four stages that lead to that decision: sizing, segmentation, competitive mapping, and demand verification. It pairs with our Reddit SaaS validation guide, which covers the community research technique used throughout.

Stage 1: Size the Market Bottom-Up

Skip the industry-report number. "The project management market is $9B" tells you nothing about whether your product for your buyer can find 500 customers.

Build the number from countable parts instead:

1. Define the buyer precisely. Not "small businesses" — "US law firms with 2-10 attorneys," "Shopify stores doing $10K-100K/month," "independent physical therapy clinics."

2. Count them. Industry associations, government business statistics, LinkedIn Sales Navigator filters, directory listings, app-store install counts of adjacent tools. You want an order of magnitude, not a census.

3. Estimate the honest price. Anchor to what the problem costs (hours × wage, revenue leaked) and what buyers already pay for adjacent tools — not to what your revenue goal needs.

4. Apply reality math. Reachable share × achievable conversion. A defensible early model: you can realistically get in front of 10-20% of a niche over a few years and convert 2-5% of those.

The viability floor: roughly 10,000 reachable buyers at a justifiable price. Example: 40,000 target firms × 15% reachable × 3% conversion × $75/month ≈ $162K ARR. Small by VC standards; excellent for a bootstrapper. If the same math yields $15K ARR at full success, the niche is a side project — better to know now.

Stage 2: Segment by Situation, Not Demographics

Classic personas group people by attributes (age, title, company size). Buying behavior follows situations — the context that makes the problem urgent:

• Not "agencies with 10-50 staff" but "agencies that just lost a client to bad reporting"
• Not "e-commerce brands" but "stores whose ad costs doubled and now need retention revenue"
• Not "HR managers" but "HR teams facing their first compliance audit"

Situational segments matter because they tell you three things demographics cannot: what triggers the purchase, what the buyer will search for at that moment, and what message stops their scroll.

How to find the situations: they are described, in first person, in community threads. When you research the niche's subreddits (Stage 4), tag every complaint with its context — "this started when we hired our fifth person," "ever since the platform changed its API." Those recurring contexts are your real segments, and the segment with the most urgent situation is your beachhead.

Stage 3: Map the Competitive Landscape — Including "Nothing"

List every way the problem gets handled today, in four buckets:

Direct competitors — products built for this problem. Find them via G2/Capterra categories, "best X software" searches, and the names users drop in community threads.

Indirect competitors — general tools stretched to cover it: the spreadsheet, the Notion doc, the all-in-one suite's mediocre module.

Service substitutes — the VA, the agency, the consultant currently paid to absorb the problem. Their fees are your price anchor.

Doing nothing — always on the list. For most niches, the status quo has more market share than any vendor.

Then mine for the gap:

1. Read the 1-3 star reviews of each direct competitor, sorted recent. Recurring complaints — not one-off rants — mark the fixable dimensions.
2. Search "[competitor] alternative" and "[competitor] pricing" in the niche's communities. These threads are buyers narrating their own switching triggers.
3. Plot who serves whom. Incumbents usually chase upmarket over time, leaving their original small-customer base under-served on price and simplicity. That abandoned floor is the most common viable entry point in SaaS.

The output of this stage is one sentence: "[Segment] is stuck between [inadequate option A] and [overkill option B], and complains most about [specific gap]." If you cannot write that sentence with evidence behind it, the mapping is not done.

Stage 4: Verify Demand With Primary Signals

Reports and review mining are secondary research — other people's data. The decision needs primary signals:

Community pain scan. Search the niche's subreddits and forums for the problem. You are checking frequency (does it recur across months), intensity (irritation vs. mild preference), and language (the words that will become your copy). PainPointMap automates this — scan the communities where your buyer is active and get back ranked recurring pain points with links to source threads.

Search demand check. Google Keyword Planner on the problem-phrases and "[competitor] alternative" terms. Meaningful volume confirms buyers actively look for solutions; near-zero volume means demand exists only passively (winnable, but with harder distribution).

A dozen conversations. Prospects matching the beachhead segment, asked about their workflow — not pitched. The research from Stages 1-3 tells you exactly who to book and what to probe; our interviews vs research comparison covers how the two methods check each other.

One cheap demand test. A landing page in the segment's own vocabulary, put in front of targeted traffic. Above ~10% signup, proceed; below 3%, revisit the segment or the message before touching code. The full no-code toolkit is in how to validate without building.

The Deliverable: A Decision, Not a Deck

Good SaaS market research compresses to five lines a skeptic can attack:

1. Buyer: [countable, named segment]
2. Size: [bottom-up math with sources]
3. Gap: [the one-sentence positioning from Stage 3]
4. Evidence: [community signal + interview pattern + test conversion]
5. Call: build / reshape / kill

If any line is assertion rather than evidence, that is the next week of research. If all five hold, stop researching — start building.

Related Reading

• How to Validate a SaaS Idea Using Reddit — the community scan technique in depth
• SaaS Idea Validation Checklist — the check-by-check companion to this guide
• Startup Market Research — the broader-scope version for non-SaaS startups
• Niches for SaaS — validated niche candidates to run through this process