Introduction
Most SaaS founders ask the wrong question. They want to know if the market is "big enough" instead of asking whether a specific customer has a painful, recurring problem they'll actually pay to fix.
That distinction matters more than it sounds. CB Insights' 2026 analysis of failed VC-backed startups found that poor product-market fit was an identifiable cause in 43% of shutdowns, right alongside running out of cash.
The failures weren't because the market was too small on paper. They happened because nobody confirmed the pain was real, widespread, and worth paying for before building.
SaaS market research fixes this. It connects customer pain, buying behavior, competitors, pricing, and go-to-market feasibility into one evidence-based picture.
This guide walks through the full process: defining your research question, gathering primary and secondary evidence, sizing the opportunity, validating willingness to pay, and turning all of it into a clear, defensible decision.
Key Takeaways
- Start with a specific business decision, not an open-ended "learn about the market" request.
- Pair customer interviews and behavioral data with secondary research and competitor analysis.
- Segment by industry, company size, role, and urgency before estimating opportunity size.
- Treat pricing and retention as research questions, not assumptions baked into your pitch deck.
- Let the evidence decide whether to proceed, pivot, narrow the niche, or stop.
How to Conduct SaaS Market Research
Step 1: Define the Research Objective and Hypotheses
Before you talk to a single prospect, state the decision this research needs to support. Are you selecting an ICP? Validating an MVP? Setting pricing? Choosing between a sales-led or self-serve motion?
Vague goals produce vague findings. A specific decision forces specific evidence.
Next, write testable hypotheses about:
- The customer and the pain point they experience
- Their current workaround (spreadsheet, agency, manual process, or nothing at all)
- The expected outcome if your product solves the problem
- The buying trigger that pushes them to act now
Y Combinator's guidance on customer interviews is blunt: ask what prospects actually do today and how often, not whether they'd "like" your idea. Hypothetical questions invite polite lies.
For each hypothesis, decide in advance what evidence would confirm it, weaken it, or kill it outright. Then build a short research brief naming the target segment, geography, timeline, evidence sources, and the date you'll make a final call.
Skipping this step is how positive-sounding feedback quietly becomes a "go" decision nobody can defend later.
Step 2: Define and Segment the Target Market
B2B SaaS buying is rarely a single person. Separate the end user, problem owner, champion, decision-maker, budget holder, and economic buyer—even when one human fills several of those roles.
This isn't academic. Gartner's 2025 research found unhealthy conflict in 74% of B2B buyer teams, based on a survey of 632 buyers. A product that delights the end user can still stall for months if the budget holder and the security reviewer disagree.
Segment your market using more than demographics:
- Industry and vertical workflow
- Company size and operational maturity
- Technical environment and existing stack
- Geography and buying culture
- Severity and frequency of the problem
Build an ICP and persona document that captures goals, recurring tasks, existing tools, and adoption barriers for each role. Then prioritize the segment with the strongest combination of urgent need, reachable buyers, ability to pay, and genuine product fit. Chasing the broadest possible market usually means chasing none of it well.
Step 3: Collect Primary and Secondary Research
Start with secondary sources: category definitions, analyst reports, public filings, review sites, job postings, and competitor messaging. This builds context fast and cheaply, though it's rarely specific enough to your exact segment.
Then move to primary research: interviews, surveys, usability tests, concept tests, and reviews of sales or support conversations. The SBA's market research guidance draws this same line: secondary data is quicker, primary data is more tailored to your actual audience.
The key is what you ask. Don't ask if someone "likes" your concept. Ask:
- What happened the last time this problem came up?
- What did you try?
- What did it cost—in money or time?
- Who approved the workaround or purchase?
Interviews reveal motivation. They don't prove behavior at scale, so triangulate across sources: compare what people say in interviews with what your analytics show and what secondary data suggests.
Record the source, date, sample size, and confidence level for every finding in a shared repository. If you can't trace a claim back to its origin six weeks later, treat it as unverified.
Step 4: Analyze the Opportunity and Convert Findings into Decisions
Size the opportunity using a transparent bottom-up model rather than a top-down industry percentage pulled from a slide deck.
| Measure | Calculation | Key Validation Question |
|---|---|---|
| TAM | All plausible buyer accounts × realistic annual spend | Do these accounts actually have the problem? |
| SAM | TAM accounts serviceable with your current product and geography | Which filters exclude buyers you can't reach? |
| SOM | Realistic share of SAM you can capture in a defined period | Can your sales capacity support that share? |
Next, map alternatives honestly:
- Direct and indirect competitors
- Internal tools, spreadsheets, and agencies
- Doing nothing
Compare positioning, pricing structure, onboarding, integrations, and customer complaints across each.
Don't skip the pricing question. OpenView's 2021 SaaS pricing dataset found that only 6% of participating companies reported sophisticated willingness-to-pay research. Most set prices based on gut feel or competitor mimicry. Testing an actual paid offer, even a small pilot, tells you more than ten rounds of feature-enthusiasm interviews ever will.
Translate everything into a positioning statement, priority use case, MVP requirements, and measurable validation criteria. End with one of five decisions:
- Proceed
- Narrow the ICP
- Reposition
- Run another validation cycle
- Stop
Document the evidence behind whichever one you choose.
When to Conduct It and What You Need
Research isn't a one-time milestone before launch. Run it at these points:
- Before building an MVP
- Before entering a new segment
- Before changing pricing
- Whenever conversion or retention signals weaken
Customer expectations, substitutes, and regulations shift constantly. Evidence from eighteen months ago can mislead you today.
Research Inputs and Sources
Before starting, prepare:
- A research brief and ICP assumptions
- An interview guide and survey instrument
- A competitor list and market-sizing model
- A source log and consent language
- A system for storing notes and evidence
Combine qualitative sources (interviews, support conversations, sales calls, reviews) with quantitative ones (product analytics, funnel data, survey results, search demand). Check that every source is current, relevant to your actual segment, and sufficiently independent. Label estimates as estimates, not facts.
Operational and Compliance Readiness
Get proper consent before recording interviews or using customer data, and avoid collecting more personal information than you need. Use neutral, consistent interview questions across a varied participant pool to reduce confirmation bias toward enthusiastic early adopters.
For Israeli SaaS companies researching the US market specifically, don't assume Israeli customer evidence transfers directly. Buyer expectations, procurement steps, communication norms, and sales cycle length can differ meaningfully between the two markets.
HaGesher Group's go-to-market strategy consulting helps Israeli founders turn those findings into an ICP, positioning, and sales approach built for American buyers—not assumptions carried over from the home market.
Key Variables That Affect Research Quality
Reliable conclusions depend on the quality and interpretation of your evidence, not the volume of data you've collected.
Research question and scope. A vague question produces an unstructured pile of facts that may not answer the decision you're actually facing. A narrow, specific question generates usable evidence; an overly broad study invites scope creep and makes conflicting findings nearly impossible to resolve.
Sample and segment fit. Feedback from people who experience the problem, influence the purchase, or control the budget matters more than general opinions. Role, company size, industry, and current workaround all shape responses. Report your sample's limitations rather than hiding them.
Evidence quality and triangulation. Interviews reveal motivation. Analytics show behavior. Secondary research provides context. Compare what people say against what they actually do and what the market data shows before calling anything "validated."
Market size and willingness to pay. A large theoretical market can still be unattractive if the reachable segment is small or buyers lack budget and urgency. Research pricing benchmarks, current spending, and switching costs directly. Never infer willingness to pay from a compliment about your demo.
Interpretation and decision thresholds. Teams cherry-pick encouraging comments more often than they'd admit. Define thresholds in advance for urgency, buyer access, pricing acceptance, and pilot interest. Record disconfirming evidence just as carefully as the supportive kind.
Common Mistakes, Troubleshooting, and Alternatives
Most research problems trace back to weak questions, poor participant selection, or a failure to connect findings to an actual decision.
Common Mistakes
- Researching only friendly contacts. Warm intros skew positive and rarely represent your real buyer.
- Asking leading questions or pitching too early. This produces polite agreement, not evidence.
- Treating feature requests as purchase intent. Wanting a feature isn't the same as budgeting for it.
- Relying on one competitor, one report, or one survey. Verify important claims against multiple sources.
- Confusing a large user count with a viable market. Reachability, buyer authority, acquisition cost, and retention all matter more than raw headcount.
Troubleshooting and Alternatives
| Problem | Fix |
|---|---|
| Interview feedback conflicts | Segment by role, company type, and urgency before averaging responses |
| Weak response rates | Shorten the survey, improve targeting, offer an incentive, try new channels |
| Research feels too slow | Use a leaner sequence: desk research, targeted interviews, concept testing, small paid pilot |
| Evidence stays weak after multiple methods | Narrow the niche or revisit the problem; don't pile on more analysis to justify an unsupported idea |
When research stalls, AI tools can help with transcription, clustering themes, and monitoring competitor messaging. They shouldn't replace human verification of the claims that matter most.
Conclusion
Effective SaaS market research starts with a clear decision, focuses on a specific segment, and combines direct customer evidence with market and competitor data. The goal is to reduce uncertainty enough to make a disciplined call on product, pricing, and go-to-market.
For Israeli SaaS companies entering the US, that last step often means translating research into hiring and execution. HaGesher Group works with founders on this transition. We pair go-to-market strategy consulting with recruitment and executive search for the sales, customer success, and marketing leaders who turn validated research into US traction.
Document your assumptions. Revisit the research as the market shifts. And when the evidence disagrees with your plan, act on it before committing more build or sales resources to a theory nobody's tested.
Frequently Asked Questions
What is the Rule of 40 in SaaS?
The Rule of 40 compares revenue growth rate plus profit margin, with a combined score of 40% or higher considered healthy. It's a company-performance benchmark, not a substitute for customer, competitor, or market research.
How often should a SaaS company conduct market research?
Research should happen before launch, before entering a new segment or geography, and during any pricing or positioning change. Beyond that, treat customer and competitor feedback loops as continuous, not one-time events.
What is the difference between primary and secondary SaaS market research?
Primary research is first-hand data you collect through interviews, surveys, and usability tests. Secondary research uses existing sources like industry reports and review sites. Secondary builds context fast; primary confirms it fits your buyer.
How do you calculate the market size for a SaaS product?
Build a bottom-up TAM, SAM, and SOM: count eligible accounts, multiply by realistic annual revenue per account, then narrow to what your sales motion can reach. Label every assumption clearly.
What questions should you ask potential SaaS customers?
Ask about recent workflows, pain severity, current alternatives, the cost of the problem, and who approves purchases. Focus on recent, specific behavior rather than hypothetical future preferences.
How do you analyze SaaS competitors?
Compare direct and indirect alternatives, including spreadsheets and "doing nothing," across segments, features, pricing, onboarding, integrations, and customer complaints. Include substitutes prospects already use, not just named category competitors.
