How Solo Developers Find a Startup Niche Worth Building
For solo developers · Based on Greg Isenberg Startup Opportunity Scanner
// TL;DR
Solo developers can use the Greg Isenberg Startup Opportunity Scanner to stop building horizontal apps nobody asks for and instead pick one underserved, high-spending niche. Start with a category you can code for, list sub-niches, apply the CVS Shelf Heuristic and the three-question Niche Qualification Test, then verticalize — 'app for people with GERD,' not 'health app.' Match the niche to a product type like an Action App or vertical health tool, build the Jobs-to-be-Done Stack as your roadmap, and validate builder-market fit before writing a line of code.
Why do solo developers keep building apps nobody wants?
Most solo developers build horizontal, generic products — a 'health app,' an 'AI employee platform,' a 'productivity tool' — because those feel ambitious. The Greg Isenberg Startup Opportunity Scanner flips this. It tells you the niche you serve matters more than the product you build. 'Date the Product, Marry the Niche' means you commit to an audience and iterate the product, instead of marrying a clever piece of code that no specific person needs.
As a solo dev, your scarcest resource is time. Verticalization saves it. Building 'the app for people with GERD' gives you a sharp audience, a clear pain, and a moat, where 'a health app' gives you infinite competitors and no one who feels spoken to.
How do I find a niche I can actually build for?
Start wide. Pick a category you can code in — health tech, creator tooling, elder care — and list every sub-niche without evaluating. Then apply the CVS Shelf Heuristic: which over-the-counter categories fill entire pharmacy aisles? An aisle of antacids points to GERD as a high-pain vertical.
Run the three-question Niche Qualification Test on each candidate:
1. Is this audience underserved — few products built specifically for them?
2. Do they have disposable income or proven willingness to spend?
3. Is the pain sharp — something they already pay to patch via doctors, subscriptions, or OTC products?
Only niches that pass all three move forward. Then apply 'Fish Where the Fish Are' — favor 45–65+ users, niche hobbyists, and condition-sufferers over the crowded 13–35 market.
Should I build an Action App or a vertical product?
Match the niche's pain to the product category. Repetitive digital workflows point to an Action App — an agent-first mobile app where the core UX is agents doing work on the user's behalf, not a UI full of buttons. Health data plus a specific condition points to a Vertical Personalized Health product like 'Zoey for GERD': blood work intake, AI pattern analysis, vertical-specific food recommendations.
As a developer, the Action App path plays to your strengths. Pick a persona — say, a junior podcast editor — and ask Claude to list the 50 jobs-to-be-done: chapter generation, clip selection, show notes, guest research, transcript cleanup. That list is your product roadmap. Build agents to cover 2–3 jobs first, then expand toward a true digital 'Junior.' Position it as handling menial work at a fraction of a human hire's cost — not replacing the creative human.
How do I get my first 1,000 users as a solo dev?
Identify the acquisition wedge that fits your product. For an Action App, reverse-engineer a TikTok skit that dramatizes the pain — a founder buried in post-production busywork versus the same founder with five minutes of oversight. For a vertical health tool, seed a niche subreddit or Discord for the exact condition. For older audiences, Facebook ads are active and underpriced.
Before you commit, stress-test builder-market fit: do you have lived experience of this pain, an existing audience, or a relevant skill beyond coding? A great niche with no builder-market fit is still hard. If you have GERD yourself, or edit podcasts on the side, that lived experience is your unfair advantage.
What's my next step?
Pick one category today, list its sub-niches, and run the three-question Niche Qualification Test on the top three. Choose the winner, generate its Jobs-to-be-Done Stack with Claude, and ship an Action App or vertical tool covering the top 2–3 jobs. Commit to the niche — the product will evolve.
// FREQUENTLY ASKED QUESTIONS
Should I build an Action App or a full SaaS as a solo developer?
Lean toward an Action App if the niche's pain is a repetitive digital workflow. Agent-first products let you deliver value with a thin UI — the agents do the work and you surface only decisions needing human judgment. This plays to a solo dev's strength: shipping agents incrementally from the Jobs-to-be-Done Stack rather than building a sprawling dashboard nobody uses.
How many jobs-to-be-done should my first version cover?
Start with just 2–3 — the highest-pain jobs in your persona's stack. Cover those reliably, then expand to 10, then 50, until you approach a true digital employee. Trying to cover all 50 at launch as a solo dev guarantees you ship nothing. The stack is your roadmap, not your v1 spec.
What if I don't have lived experience in my chosen niche?
Flag it as a builder-market-fit gap and either close it or pivot. You can close it by embedding in the niche's community, partnering with someone who has the experience, or choosing an adjacent niche where your existing skills apply. A great niche with no builder advantage is still hard — don't ignore the mismatch.