How Do Product Managers Evaluate New Market Opportunities?
For Product managers evaluating new product lines at mid-stage startups · Based on Greg Isenberg Startup Opportunity Scanner
// TL;DR
Product managers at mid-stage startups can use the Greg Isenberg Startup Opportunity Scanner to evaluate new verticals and product lines before committing resources. Apply the three-question Niche Qualification Test to filter candidate markets, use the Jobs-to-be-Done Stack to build feature roadmaps, and leverage the Verticalization principle to differentiate against horizontal competitors. The framework transforms vague expansion intuition into structured, evidence-based product briefs that leadership can evaluate with confidence.
Why Do Most Product Expansion Bets Fail?
Most product expansion fails because teams pick new markets based on adjacency to their existing product rather than on niche fundamentals. Greg Isenberg's Startup Opportunity Scanner provides a structured methodology for evaluating whether a new vertical, audience segment, or product line is worth pursuing — before you commit engineering resources.
The framework is originally designed for startup founders, but its principles translate directly to product managers evaluating expansion opportunities at mid-stage companies. The core question is the same: which niche should we commit to, and what product should we build for them?
How Do I Apply the Niche Qualification Test to a Product Expansion?
Before proposing a new product line to leadership, run every candidate market through the three-question Niche Qualification Test:
1. Is this audience underserved? Are there few products built specifically for them, or are existing solutions generic and poorly-fitted? Check competitor depth, not just competitor count.
2. Does this audience have budget? For B2B: what's the department budget? For B2C: what are they already spending on workarounds? The willingness-to-spend signal is critical — look for existing subscriptions, consulting spend, or manual processes that cost time and money.
3. Is the pain sharp and specific? Not 'it would be nice to have' but 'we're losing hours every week to this problem.' Interview users in the candidate niche and look for emotional language around the pain.
Only segments passing all three deserve a product brief. This saves you from the common PM trap of building for 'interesting' markets that lack real urgency.
How Do I Use Verticalization to Differentiate Our Product?
Verticalization is the framework's most powerful tool for PMs at companies with horizontal products. Instead of adding features to your existing platform to serve a new segment generically, build a vertical solution tailored to that segment's specific workflows, language, and pain points.
Example: Your company has an AI writing tool. Instead of adding a 'healthcare template,' build 'the AI clinical documentation assistant for physical therapists.' Go deep on PT-specific workflows: SOAP notes, insurance pre-authorization language, patient communication templates. This vertical approach creates defensibility that generic competitors can't match.
Apply the Jobs-to-be-Done Stack method: enumerate all 30–50 tasks your target persona performs. Identify which ones your product can automate or improve. This list becomes your feature roadmap for the vertical, prioritized by pain intensity and frequency.
How Does the Action App Framework Apply to Product Feature Design?
If your product involves repetitive digital workflows, consider the Action App principle: redesign the UX so AI agents do things on the user's behalf rather than presenting more screens for humans to click through. The best new products won't add more dashboards — they'll show users what's already been done and surface only the decisions that require human judgment.
For a PM at a mid-stage startup, this means evaluating whether your proposed feature should be a traditional UI or an agent-first experience. The framework suggests that 'action' beats 'information' — users want outcomes, not more data to process.
How Do I Build an Internal Case Using This Framework?
Structure your product brief around the framework's outputs:
- Niche: Specific persona and vertical (not 'healthcare' but 'physical therapists at independent clinics')
- Qualification: Evidence that the niche passes all three questions (market analysis, spending data, user interview clips)
- Jobs-to-be-Done Stack: The 30–50 tasks this persona performs, ranked by automation potential
- Product Category: Whether this is best served by an Action App, a vertical SaaS tool, a community feature, or a content play
- Monetization Stack: Free entry (trial, freemium tier) + premium conversion (subscription, enterprise tier)
- Acquisition Wedge: How you'll reach the first 1,000 users in this niche
This structure gives leadership a clear, evidence-based framework for evaluating the opportunity — far stronger than a traditional market sizing slide.
What's My Next Step?
Apply the full 9-step Startup Opportunity Scanner to your company's expansion candidates. Start with your broad category, enumerate sub-niches, run the qualification tests, and present the winning vertical with a complete Jobs-to-be-Done roadmap. The framework turns vague product intuition into a structured opportunity thesis.
// FREQUENTLY ASKED QUESTIONS
Can I use this framework for B2B product expansion, not just consumer startups?
Yes — adapt the terminology. 'Niche' becomes a specific industry vertical or job role. 'CVS Shelf Heuristic' becomes 'look at which business expenses are the biggest line items.' 'Fish Where the Fish Are' translates to targeting industries with legacy software and high switching costs. The core logic — underserved audience, proven spending, sharp pain — applies identically to B2B product expansion.
How do I convince stakeholders to go vertical instead of staying horizontal?
Present the framework's evidence: vertical products win because specificity is the moat. Show competitors in your space that succeeded by going vertical (Veeva in pharma CRM, Toast in restaurant POS). Run the Niche Qualification Test live in a stakeholder meeting — the three questions force a concrete conversation about whether the audience is truly underserved, has budget, and feels sharp pain.
How many niches should I evaluate before committing to one?
The framework suggests enumerating all obvious sub-niches in step one (typically 8–15), then filtering through the Fish Where the Fish Are test and the three-question Niche Qualification Test. Usually 2–4 survive the filters. From those, pick the one with the strongest builder-market fit — which for a PM means the closest alignment to your company's existing capabilities, data assets, and distribution channels.