There's a particular kind of pain that founders know well: the six-month mark. You've built the product. It works. It's actually good. And nobody wants it.
This happens because founders treat building as validation. "If I build it well enough, they will come." But shipping code doesn't test assumptions — research does. And the research doesn't need to take months. It needs to take days.
This is Minimum Viable Research (MVR): the smallest amount of structured inquiry that separates a validated opportunity from an expensive guess. Seven questions. Each one answerable in 2-4 hours. Total investment: one focused week before you write a single line of code.
Question 1: Who Has This Problem?
What you're really asking: Can I describe my target customer with enough specificity to find them?
"Small businesses" is not a customer. "Independent insurance agencies with 5-20 employees in the Midwest struggling with carrier appointment management" is a customer.
Research Methods
- LinkedIn Sales Navigator search: Filter by title, company size, industry, and geography. Can you find at least 500 people who match your description?
- Industry association directories: Trade associations publish member lists. If your target customer has a professional association, that's distribution.
- Reddit and forum analysis: Search for your problem in industry-specific subreddits, forums, and Slack communities. Are real people complaining about this?
- Job postings analysis: Search job boards for roles that exist solely to solve the problem manually. If companies are hiring humans to do what your software could do, that's signal.
Red Flags
- You can't describe your customer without using the word "anyone"
- The problem affects a demographic you've never interacted with professionally
- You need to educate the market that the problem exists
Green Flags
- You can name 10 specific people who have this problem without Googling
- Your target customer has a professional association, conference, or community
- Job postings exist for the manual version of what you're building
Question 2: How Are They Solving It Now?
What you're really asking: What's the current alternative, and why is it inadequate?
The most dangerous answer is "they're not solving it." If nobody is solving the problem, either you've found a genuine greenfield opportunity (rare) or the problem isn't painful enough to warrant a solution (common).
Research Methods
- Competitive landscape mapping: Google the problem. What comes up? Search Product Hunt, G2, and Capterra. Document every existing solution, its pricing, its reviews, and its limitations.
- "How do you currently..." interviews: Call 5 potential customers. Don't pitch. Just ask: "How do you currently handle [problem]?" Document the workarounds — spreadsheets, manual processes, cobbled-together tools.
- G2 and Capterra review mining: Read 1-star and 2-star reviews of existing solutions. These are feature requests disguised as complaints. Look for patterns.
Red Flags
- There are 10+ well-funded competitors and no clear differentiation path
- Existing solutions have high satisfaction ratings (4.5+ on G2)
- The current workaround is "they just don't do it"
Green Flags
- People are using spreadsheets or manual processes (means they care enough to solve it badly)
- Existing solutions have reviews complaining about the specific gap you'd fill
- The last new entrant in the market was 5+ years ago (stale competition)
Question 3: What Would They Pay?
What you're really asking: Is there willingness to pay, and at what price point does this become a viable business?
Research Methods
- The Van Westendorp price sensitivity survey: Ask 10-15 potential customers four questions: At what price would this be too expensive? A bargain? Starting to get expensive? Too cheap to trust? The intersection of these curves gives you your optimal price range.
- Competitive pricing analysis: Document what alternatives cost. Your price needs to be justifiable relative to the current spend on this problem.
- Budget holder identification: Can the person with the problem also approve the purchase? If your user is an individual contributor but the buyer is a VP, your sales motion just got 3x more complex.
- "Would you pay $X" direct asks: During customer interviews, name a specific price and ask directly. Watch their reaction — hesitation is data.
Red Flags
- Nobody in your target segment has budget authority for software purchases
- The problem saves time but doesn't save or generate money (makes ROI hard to quantify)
- Average willingness to pay is under $50/month (unit economics will be brutal)
Green Flags
- Target customers are already spending money on inferior alternatives
- The problem has a directly calculable dollar cost (hours wasted, revenue lost, fines risked)
- Budget authority sits with the user, not a separate procurement department
Question 4: How Would They Find You?
What you're really asking: Do I have a realistic distribution channel on day one?
The most overlooked question. Brilliant products die in obscurity because the founder assumed distribution would "figure itself out."
Research Methods
- Search volume analysis: Use Google Keyword Planner or Ahrefs to check monthly search volume for your problem. If people aren't searching for it, SEO won't work.
- Community mapping: List every online community, newsletter, podcast, and conference where your target customer gathers. Can you access these channels?
- Content gap analysis: Search for educational content about your problem. If there's very little, you can own the SEO category. If it's saturated, you need a different channel.
- Partnership inventory: Which existing tools does your target customer already use? Integration partnerships can be your distribution.
Red Flags
- Your target customer doesn't Google their problem
- No communities, newsletters, or conferences exist for your niche
- The only distribution path is paid advertising (expensive and competitive)
Green Flags
- High search volume with low competition keywords exist
- You're already a member of communities where your target customer gathers
- There's a clear integration partner whose users would benefit from your tool
Question 5: What's the Switching Cost?
What you're really asking: How much inertia do I have to overcome to get someone to adopt my product?
Research Methods
- Workflow mapping: Document the current process step by step. How many tools, people, and dependencies are involved? Each one is a switching friction point.
- Data migration assessment: Is the customer's data locked in a proprietary format? Can you build an import tool? The harder the migration, the higher the barrier.
- Stakeholder count: How many people need to agree to switch? Products that require company-wide adoption are exponentially harder to sell than individual tools.
- Contract analysis: Are potential customers locked into annual contracts with competitors? If so, you need to time your outreach to renewal windows.
Red Flags
- Switching requires IT department involvement or security review
- Data is locked in proprietary formats with no export option
- The current solution is deeply integrated into other workflows
Green Flags
- The current solution is a spreadsheet or manual process (zero switching cost)
- You can run alongside the existing solution during a transition period
- The user can adopt independently without organizational buy-in
Question 6: Is This Market Growing or Shrinking?
What you're really asking: Am I building on rising or receding ground?
Research Methods
- Industry report analysis: Gartner, Forrester, IBISWorld, and Statista publish market size and growth projections. Even the free summaries give directional data.
- Job posting trends: Use LinkedIn or Indeed to track hiring trends in your target industry. Growing industries hire more people — more people means more potential customers.
- Regulatory and technology trend analysis: Are new regulations creating demand? Is new technology enabling what was previously impossible? These are leading indicators.
- Google Trends: Track search interest for your problem and your industry over 5 years. Persistent upward trend is strong signal.
Red Flags
- The industry is consolidating (fewer, larger players who are harder to sell to)
- Technology is eliminating the problem entirely (the problem might not exist in 3 years)
- Search interest has been declining for 3+ consecutive years
Green Flags
- The market is growing 15%+ annually
- New regulations are creating mandatory requirements your tool can address
- Industry job postings have increased year-over-year for 3+ consecutive years
Question 7: Can You Reach 10 Customers in 30 Days?
What you're really asking: Do I have immediate, testable access to my market?
This is the ultimate validation question. Not "can I eventually build a pipeline?" but "can I get 10 people to pay me within a month?"
Research Methods
- Personal network audit: List every person you know who fits your target persona. If you can't list 20 people, you're too far from the market.
- Cold outreach test: Send 50 personalized emails or LinkedIn messages to potential customers describing your planned solution. Track response rate. Below 5% response means your messaging or targeting is off.
- Community engagement test: Post a detailed description of the problem (not your solution) in relevant communities. Does it generate engagement and responses?
- Pre-sale attempt: Offer a "founding member" deal: discounted annual pricing for early access. If you can't get 10 people to commit $500-1,000 against a landing page and a promise, reconsider.
Red Flags
- You don't personally know a single person who fits your target customer profile
- Cold outreach gets zero responses after 50 attempts
- The only interest comes from people who want it for free
Green Flags
- You can get 5+ meetings booked within a week of outreach
- Multiple people ask "when can I buy this?" before you've built anything
- Someone offers to pay you for a manual version of the solution
Putting It All Together
Score each question on a simple 1-3 scale:
- 1 = Red flags dominate
- 2 = Mixed signals
- 3 = Green flags dominate
Total score interpretation:
- 18-21: Strong foundation. Start building.
- 14-17: Promising but with gaps. Address the weakest areas before committing.
- 10-13: Significant concerns. Pivot your approach or target market before proceeding.
- 7-9: Fundamental issues. This idea needs major rethinking or shelving.
One focused week of research. Seven clear answers. The difference between building on conviction and building on hope.
Validate your startup idea with structured research at Vantage \u2192