Product Hunt Market Scan · May 2026

Five Underserved Spaces Hiding in Plain Sight on Product Hunt

A scan of the rolling 30-day Product Hunt window (Apr 10 — May 10, 2026), clustered into pain-point themes and ranked for the constraints of a solo developer with ten to fifteen hours a week and a strong agentic-AI hand.

WindowApr 10 → May 10, 2026
Samplen = 50
MethodJTBD → cluster → score
Generated14 May 2026
n=50
Launches sampled across the rolling 30-day PH window, Apr 10 → May 10, 2026
32/50
Launches falling into the five saturated, VC-backed themes — poor positioning bets for solo devs
5/5
Buildability score for the MCP cluster — the highest of any cluster in the scan
<6mo
Time for the MCP ecosystem to go from zero to a fragmented paid market with multiple PH launches

01Method & data caveats

How the sample was assembled

The brief specified the Product Hunt GraphQL API as the preferred data source. The PH GraphQL API requires an authenticated developer token, which was unavailable in this run. The fallback method:

  1. Fetched the PH monthly leaderboard (April 2026, Featured + All views) directly.
  2. Fetched four weekly leaderboards covering the rolling 30 days — weeks 14, 16, 17, 18 of 2026 (Mar 30 → May 3).
  3. Cross-referenced the May 2026 month-to-date rankings via Hunted.space, an independent PH tracker, to pick up early-May launches that hadn't yet aggregated on PH's monthly view.
  4. Pulled one full product page (Brila) for representative comment sampling.

The result is a deduplicated n = 50 launches spanning Apr 10 → May 10, 2026, selected by featured upvote rank within each week. The sample is biased toward launches that PH's ranking algorithm featured prominently — it under-counts low-vote launches and ad-supported “Promoted” placements.

Caution

Data caveats — read this before quoting any number

  • Upvote / comment counts are point-in-time snapshots and continue to drift after launch day. Treat all counts as ±5–10%.
  • Comment quality is uneven. Most PH comments are makers responding to other makers; substantive critiques are the exception, not the rule.
  • “Top 50 by upvotes” is a proxy. Without API access I sorted by leaderboard position (Featured order), which mostly tracks upvotes but is also influenced by PH's curation, ad placement, and category boost.
  • JTBDs in the appendix are written from launch tagline + description. Where the maker explicitly stated a problem, I quote it. Where I inferred, the JTBD is marked [hyp].
  • Confidence in cluster scoring is moderate, not high. Each dimension is a 1–5 judgment call. Treat scores as ordinal (good/better/best) rather than cardinal.

Scoring rubric

Each cluster is rated 1–5 on five dimensions:

  • Demand — cluster size in the sample × upvote/comment intensity.
  • Underserved — quality and concentration of existing solutions; negative comments on incumbents.
  • Buildability — solo dev, <8 weeks to MVP, off-the-shelf APIs, no infra ops or hardware.
  • Market — adjacent funded categories, search volume, Reddit/HN signal.
  • Distribution — clear, cheap GTM channel a solo dev can run alone.
Inference

Composite score: 0.30·Build + 0.25·Underserved + 0.20·Demand + 0.15·Market + 0.10·Distribution. Buildability is weighted heaviest because solo-dev shape, not market size, is the gating constraint.

02Cluster table — all 15 clusters, scored

The 50 launches grouped into 15 thematic clusters. Cluster size = number of sampled launches that match. Top-5 ranked rows are highlighted; full opportunity write-ups follow in the next section.

#ClusternBuildUnderDemandMarketDistribScore
1Local / Private AI for vertical SMB3444444.00
2MCP / Context layer for AI agents3543333.85
3LLM evals, guardrails & cost obs.5434443.75
4Vertical AI receptionist / support5434443.75
5Niche consumer autopilot agents4444333.75
6AI site/landing-page builders3533333.60
7Vertical compliance docs (tax, legal)4334433.35
8Productivity micro-tools (menubar/tasks)7523233.20
9AI outbound / SEO / GTM automation7324433.10
10Voice-as-interface / dictation6315433.05
11AI hiring / recruiting3333333.00
12Multi-agent orchestration8225422.90
13AI meeting intelligence / repurpose7314432.85
14Agentic coding IDEs9215522.80
15Hardware AI / wearables4143322.55

Cluster sizes sum to >50 because some launches hit two clusters.

What the table is telling us

The cluster sizes and the rankings disagree, which is the whole point. The four largest clusters — agentic coding IDEs (9), multi-agent orchestration (8), AI meeting intelligence (7), AI outbound/SEO (7) — all rank in the bottom half because they're the hottest VC categories of the moment. Cursor, Claude Code, Granola, Fathom, Clay — these incumbents have raised tens to hundreds of millions and ship full-time. Solo-dev competition there is a fool's errand.

The top-5 clusters are quieter: 3–5 launches each, no breakout leader, but enough activity to prove people are paying for tools in the space. That gap is the whole bet.

03Top 5 opportunities + demand validation

Each opportunity card covers the unmet need with PH evidence, a 4–8 week MVP scope, lean stack, first-100-users plan, and week-1 risk invalidations. Paired directly below each is a Reddit demand investigation — unfiltered language from the people with the pain.

Caution

Honest constraints on this Reddit pass

  • Reddit's official search API is not authenticated in this run. I'm using web-search-indexed Reddit content, which surfaces high-engagement threads that Google has indexed but cannot cleanly enumerate “top 10 by upvotes in the last 12 months.” Where the haul is thin, I say so.
  • Subreddit subscriber counts are point-in-time, ±10%, drawn from public sidebars at scrape time.
  • Some quotes are sourced via aggregator articles — marked “via aggregator” where this applies.
  • Original phrasing preserved verbatim — including typos, slang, sarcasm, and the occasional ALL-CAPS. The cleanup is the signal-loss.
4.00Composite
Opportunity #1

Local / private AI suite for one trust-heavy SMB vertical

"Private GPT for therapists / small law firms / accountants — bundled Ollama, opinionated workflows, your client data never leaves the laptop."

Build4/5Under4/5Demand4/5Market4/5Distrib4/5

Unmet need + evidence

The local-AI cluster is small (Ollama v0.19, Pioneer, Subgrapher) but the makers ship as horizontal infrastructure — runtimes, fine-tuners, knowledge graphs. None of them ship a vertical-shaped product for a profession that genuinely cannot send client data to OpenAI/Anthropic: therapists (HIPAA), small law firms (privilege), independent accountants (client confidentiality), small medical practices. The gap visible in the sample: every product treats 'local LLM' as the headline feature rather than treating it as a compliance unlock for a specific buyer who's currently forced to choose between 'use ChatGPT and break our agreement' or do this by hand.' Closest adjacent funded category: cloud 'private GPT' platforms (Glean, Hebbia) that solve the same trust problem for enterprises with dedicated VPCs. They start at >$50k. Solo-targetable SMBs are not their ICP.

Ollama v0.19 · 264 upvPioneer · 112 upvSubgrapher P2P · 79 upvBeezi AI BYO-Ollama · 393 upv · 40 comments

4–8 week MVP scope

  • Pick one vertical. Recommendation: independent therapists — HIPAA is the cleanest forcing function, the workflow set is small, and there's an active community on r/therapists / r/psychotherapy.
  • Tauri desktop app (macOS first; Windows in week 7 if there's pull).
  • Bundled Ollama runtime, ships Llama 3.1 8B + Phi-3 quantized; first-launch downloads weights with progress UI.
  • Three opinionated workflows: session-note summary, treatment plan draft from SOAP notes, de-identification before any export.
  • Local SQLite for session metadata (client names hashed by default); no cloud sync in v1.
  • On-device transcription with Whisper.cpp (small.en model).
  • One-click PHI redaction step before any copy/export action — this is the trust feature and should be visible on every screen.
  • License-file activation (no account required; sells the trust story).

Lean stack

Tauri + React shell · Ollama runtime (llama-server) · whisper.cpp · SQLite · Stripe for one-time license + maintenance. No backend in v1 — the entire app is offline-capable. License server is one Hono route on Cloudflare Workers.

First-100 users acquisition

  • Personal LinkedIn DMs to 200 therapists in your network's 2nd-degree connections (~15 replies → 5 paying betas).
  • r/therapists, r/psychotherapy, r/psychotherapyresearch — show real session-note demos with synthetic data; lead with the trust story, not the AI story.
  • Sponsor one episode of a therapy-business podcast ($300–$800 range).
  • White-paper-style blog post: "Why I won't use ChatGPT for client notes — and what I built instead." HN/Hacker Therapist crossover.
  • One-on-one onboarding call with first 20 customers — high-touch, gives you the design backlog for v2.

Top 2 risks & week-1 invalidation

R1 — Trust-vertical buyers won't trust an unknown indie tool

Invalidate by Friday wk1: 5 LinkedIn calls with practicing therapists. Ask: "if a tool ran 100% on your laptop, never sent data anywhere, and saved you 30 min/day on notes — would you pay $40/mo? What would block you from trying it?" If <3 of 5 say yes and name a credible blocker, pivot the vertical (try small accounting firms — same forcing function, easier sales).

R2 — On-device model quality is below the bar for production notes

Invalidate by Friday wk1: assemble 20 synthetic SOAP notes, run Llama 3.1 8B and Phi-3 against GPT-4o on summary quality. If on-device is >25% worse on clinical accuracy, the v1 is not a "private alternative" — it's a worse product. Mitigation: ship a "BYO API key" mode where the user supplies an Anthropic/OpenAI Zero Data Retention key, but redaction happens client-side first.

Opp #1 · Local AI for trust-heavy SMBs

Therapists, lawyers, accountants — privacy-forced AI buyers

Verdict: Moderate

Subreddits identified

SubredditSubsActivityFitWhy
r/therapists~110k~80/wkbroadPrimary buyer identity; documentation pain is a recurring weekly thread
r/Psychotherapy~95k~30/wkbroadOverlaps r/therapists; more clinical / less business-of-practice
r/Psychiatry~140k~40/wkproblemAI scribe debates have been recurring per aggregator scrapes
r/medicine~600k~150/wkproblemGeneral MD scribe pain — adjacent but applicable; large signal pool
r/privatepractice~12k~10/wkadjacentSolo-practice business owners — sales-cycle and tooling pain

Posts retrieved

Direct top-post enumeration was not possible (no API). The named Reddit usernames below were surfaced via two independent therapist-tooling roundups (s10.ai and trytwofold.com) which cite specific r/therapists, r/Psychiatry, r/medicine, r/Residency commenters. The original threads exist; the snippets are real but indirect.

6 representative threads
  • u/TherapyNoteNerd — Upheal review (r/therapists) [via aggregator]
  • u/FamilyMedFan — Heidi Health review (r/medicine / r/therapists) [via aggregator]
  • u/EveningPatient4895 — Mentalyc review (r/Psychiatry) [via aggregator]
  • u/mindful_therapist — Upheal review (r/therapists) [via aggregator]
  • u/old_college_student — AutoNotes review (r/therapists) [via aggregator]
  • u/Fit-Astronaut6464 — Twofold Health review (r/Psychiatry) [via aggregator]

Repeated vocabulary

documentation×8+HIPAA / BAA×6privacy×5consent×4train(ing) on data×3burnout×3notes~constant

Language buckets

Pain — how they describe it
Workaround — what they&apos;re doing now
Failed solutions
Wish — desired outcome
Willing-to-pay signal

Strong but indirect. Mentalyc, Upheal, Twofold, Heidi, Freed, Nabla, Abridge are all paid SaaS with reported five- to eight-figure ARRs in this niche. The market exists; therapists are already paying $40–$100/mo for cloud-AI scribes. The remaining question is whether they'd pay similar money for a fully-local alternative — that has not been directly validated.

Verdict: Moderate. The general pain (documentation burnout) is loud and consistent. The specific "must-be-local-because-cloud-BAA-isn't-enough" framing is a hypothesis without organic evidence yet — therapists are buying cloud tools with BAAs and largely accepting that trade. The wedge is real but narrower than the PH-only signal scored it.
Three candidate headlines, built from verbatim phrases
  1. Therapy notes that never leave your laptop.
  2. Get your evenings back without trading client privacy for a faster note.
  3. The AI scribe that doesn't ship your sessions to a cloud you've never heard of.
Recommended additional channels for week-1 validation

Direct LinkedIn DMs to therapists remain primary. Add: the Practice of the Practice Facebook group (~25k members, business-of-therapy focus); Tara Vossenkemper's Therapist Resource Substack comment threads; and one paid 30-min call with a HIPAA compliance consultant to surface the actual regulatory edge cases before talking to therapists.

3.85Composite
Opportunity #2

A drop-in MCP server for one high-value workflow

"npx-installable MCP that gives Claude Code / Cursor first-class access to your Postgres schema + query history — your AI agent finally writes SQL that respects your data model."

Build5/5Under4/5Demand3/5Market3/5Distrib3/5

Unmet need + evidence

The MCP ecosystem went from zero to a small, fragmented market in <6 months. The launches in the sample are infrastructural (Notion MCP) or vertical entry-points (Lovie Formation Incorporation MCP) rather than well-shaped tools for narrow workflows. Every Claude Code / Cursor user hits the same wall: agents write code that compiles but ignores their actual data shape. Recommended wedge: "Postgres MCP" — a single MCP server that lets a coding agent introspect your live schema, run safe read-only queries, and reference past query patterns when generating SQL. A solo dev can ship this in 3 weeks. It is so narrowly scoped that no one funded would build it as a standalone product. It is so useful that a Claude Code user who tries it once will install it on every project.

Notion MCP · 475 upv · 45 cmtLovie Formation MCP · 124 upv · May SaaS#4Beezi AI BYO-Ollama · 393 upvPH forum: "Cursor or Claude Code?" trending

4–8 week MVP scope

  • TS implementation against the official @modelcontextprotocol/sdk.
  • Tools exposed: describe_schema, list_tables, find_similar_queries, explain_query_plan, safe_select(query, limit).
  • Read-only enforcement via a SET TRANSACTION READ ONLY guard rail and a regex denylist for DDL/DML — verify with pg_query_state.
  • Local-only mode: npx postgres-mcp --connection postgres://...
  • Cloud mode: ship a tiny Hono service for shared team query-history + a Web UI to review what the agent has been running.
  • One demo video per integration: Claude Code, Cursor, Continue.dev. Demo the same task in all three.

Lean stack

TypeScript + node-postgres + @modelcontextprotocol/sdk. OSS package on npm + GitHub. Cloud: Hono on Cloudflare Workers + Neon for the team-history store + Clerk for auth + Stripe for subscriptions.

First-100 users acquisition

  • List on Anthropic's MCP showcase + the awesome-mcp-servers GitHub list (>5k stars).
  • One Twitter demo thread per week for 4 weeks: "watch Claude Code write a correct migration in 3 turns instead of 12."
  • r/ClaudeAI, r/cursor, r/programming. Lead with the demo GIF, not the install command.
  • Submit a HN "Show HN" post with the OSS announcement.
  • Hand-write 10 dev.to / Hashnode posts ("Postgres-MCP + [popular ORM]") for SEO.

Top 2 risks & week-1 invalidation

R1 — Anthropic / Cursor ship an "official" first-party Postgres MCP

Invalidate by Tuesday wk1: read every public Anthropic/Cursor roadmap signal, scan their existing first-party MCP set, and look for "database" mentions in recent staff posts. If a first-party shipped or is signaled, narrow scope further: ship a Postgres + Sentry + Linear MCP that triangulates production errors with code and tickets. The compounding context is harder for an incumbent to copy.

R2 — MCP adoption stalls and the addressable market stays a few thousand devs

Invalidate by Friday wk1: count the awesome-mcp-servers repo's commits, Anthropic's "MCP servers I use" tweet engagement, and the npm download trajectory of existing servers. If MCP-server downloads aren't >50% MoM, monetization needs to be team-cloud heavy. If they are, the OSS-first strategy is fine.

Opp #2 · Postgres MCP for AI agents

Cursor & Claude Code users — agents that hallucinate schemas

Verdict: Strong

Subreddits identified

SubredditSubsActivityFitWhy
r/cursor~150k~300/wkbroadPrimary buyer; "Venting" flair is a default category
r/ClaudeAI~120k~250/wkbroadParallel buyer; MCP discussions concentrated here
r/LLMDevs~60k~80/wkproblemTechnical pain articulated; MCP-server show-and-tell common
r/LocalLLaMA~400k~500/wkproblemLarge pool, but mostly local-model focused; some agent overlap
r/PostgreSQL~270k~120/wkadjacentDBA-side perspective on AI-generated bad SQL

Posts retrieved

4 representative threads

Repeated vocabulary

hallucinat(e/ion)×6+schema×5truth source / context×4frustrated / fed up×3invents / makes up×3confidently×2

Language buckets

Pain — how they describe it
  • Working with LLMs and SQL can be a total headacher/LLMDevs OP
  • it confidently suggests customer_id when your table actually uses cust_pkr/LLMDevs OP
  • Or worse, it just invents tables that don't even exist. Sound familiar?r/LLMDevs OP
  • I've been frustrated with Cursor occasionally hallucinating when generating React components, especially when dealing with complex database schemasr/cursor (Feb 13 2025)
  • Every time, I try to fix the hallucination like the doctor in Shutter Island. And it falls back again and again.r/cursor "Despaired" Venting post
Workaround — what they&apos;re doing now
  • I got so fed up copy-pasting schemas into ChatGPT, I decided to build ToolFrontr/LLMDevs OP
  • creating a dedicated MCP server that acts as a "truth source" for Supabase schema informationr/cursor
  • I stopped expecting AI to just "figure it out" and started treating it like a smart intern who can code fast, but needs constant directionr/cursor "Cancelled sub" Venting post
Failed solutions
Wish — desired outcome
  • Real-time, accurate schema informationr/cursor
  • Generated React components are always in sync with the actual database structurer/cursor
  • Schema changes are immediately reflected without needing to update context filesr/cursor
Willing-to-pay signal

Strong indirect. r/cursor users are paying $20–200/mo for AI tools and venting at length when ROI breaks. They are not the "wouldn't pay for it" cohort. The OSS-first strategy in the original opp card looks correct: free OSS as adoption funnel, $10/mo cloud version for team-shared query history.

Verdict: Strong. The pain is named, repeated, and has produced multiple OSS attempts already (ToolFront, the Supabase-MCP write-up). Vocabulary is consistent — "hallucinate" and "schema" co-occur constantly. The wedge is concrete enough to ship and demo in <3 weeks.
Three candidate headlines, built from verbatim phrases
  1. Stop your AI agent from inventing tables.
  2. Real-time schema. Real SQL. No more cust_pk vs customer_id.
  3. The truth source for Postgres your Claude Code agent has been missing.
3.75Composite
Opportunity #3

Per-feature, per-customer LLM cost & eval tracking for indie AI builders

"Stripe-style cost dashboards for the AI features in your SaaS — see exactly which features and which customers burn the most tokens, get alerted before anything blows up."

Build4/5Under3/5Demand4/5Market4/5Distrib4/5

Unmet need + evidence

The LLM eval / observability cluster is the second-most-active in the sample: Plurai, traceAI, Beezi AI, ClawMetry, PandaProbe, Radar. Almost all of them frame around quality (evals, traces, hallucination detection) rather than unit economics. Every indie founder shipping AI features hits the same problem: who's burning my budget and on what? Helicone and Langfuse partially solve traces; nobody slices well by feature × customer × environment for the sub-$100k ARR builder. The funnier signal: Claude Code & Codex Usage Trading Cards by Rudel (172 upv, May) landed as a joke product — and got real engagement. The community is anxious about LLM spend, and the joke confirms the latent pain.

Plurai · 738 upv · 227 cmtBeezi AI · 393 upvPandaProbe · 378 upvRadar · 378 upvtraceAI · 194 upvClawMetry · 161 upv

4–8 week MVP scope

  • SDK wrapper for OpenAI / Anthropic / Mistral / Google in TS + Python (3 days each — the SDKs are nearly identical surface).
  • Required tagging on every call: feature, customer_id, env. Refuse to record untagged calls in dev mode (forces hygiene).
  • Postgres-backed metrics table with hour rollups; daily/monthly aggregates as materialized views.
  • One canonical dashboard: "top 10 customers by spend (this period vs last)", "top 10 features by spend", "cost per active user", "p95 cost per request by feature".
  • Alerting via webhook (Slack, Discord, email): per-customer threshold, per-feature threshold, week-over-week delta >2x.
  • One eval feature in v1: tag a subset of outputs as "reviewed-good" / "reviewed-bad" from the dashboard, train a cheap classifier per feature, get pass-rate on every new release.

Lean stack

Next.js on Vercel · Postgres on Neon · Drizzle ORM · Clerk auth · Stripe billing. SDKs published to npm + PyPI. No queue infrastructure — write straight to Postgres with batched inserts; tune to handle 10 events/sec per customer (2.5M/mo) before needing real infra.

First-100 users acquisition

  • HN "Show HN" with a screenshot of one of your own projects: "I shipped an AI feature, here's the customer that cost me 60% of my budget."
  • Twitter / Bluesky thread: "I tracked LLM spend by customer for a month. The top 3% of users were 71% of spend. Here's what I changed." (Real numbers from your own data.)
  • r/SaaS, r/microsaas, r/SideProject — DevTool-shaped audience overlaps perfectly.
  • Free tier: 100k events/mo, no auth required for OSS SDK use; $29/mo team tier. Lead with the free tier in every post.
  • Sponsor one issue of Bytes or TLDR AI ($1.5–$3k) once you have 20 paying customers — measurable funnel by then.

Top 2 risks & week-1 invalidation

R1 — Helicone or Langfuse ships per-customer dimensions and erases the wedge

Invalidate by Tuesday wk1: create accounts on both, try to slice cost by a custom customer_id tag. If both already do this well, the wedge isn't "per-customer slicing" — it's "opinionated for indie builders + alerting on top." Reframe the positioning to be the opinionated tool, not the missing-feature tool.

R2 — Indie devs don't pay for observability until they've already been burned

Invalidate by Friday wk1: tweet a single demo screenshot, link to a landing page with pricing + free tier, ask for waitlist signups. If <5% of 200 unique visitors leave an email, willingness-to-pay is weak — pivot to a free OSS + cloud team plan model where the pull is "I want to share this with my team," not "I'm worried about cost."

Opp #3 · LLM cost & eval for indie AI builders

"The math doesn't add up" — opaque LLM billing

Verdict: Strong

Subreddits identified

SubredditSubsActivityFitWhy
r/cursor~150k~300/wkbroadCost-anxiety venting is a daily flair (literally tagged "Venting")
r/SaaS~250k~400/wkbroadIndie founders shipping AI features; cost-shock posts recur
r/LangChain~50k~50/wkproblemProduction LLM operators; eval/observability discussion
r/LocalLLaMA~400k~500/wkproblemCost-driven motivation for going local; cost benchmarks
r/microsaas~85k~100/wkadjacentSolo-founder cost economics; smaller signal pool

Posts retrieved

4 representative threads

Repeated vocabulary

tokens~constantlimit / quota×5+burn / burning×4math doesn't add up×3overnight×3vibe coded (sarcastic)×3bait and switch×2

Language buckets

Pain — how they describe it
Workaround — what they&apos;re doing now
  • I have set "Usage-Based Pricing" as "Off". And now I have used more than 20$ tokens without any limitsCursor forum
  • switch to Auto model which is not chargedCursor forum staff response
  • Sometimes I start a request off with Claude 4 then switch to Auto for the minor [tasks]Cursor forum
Failed solutions
  • They vibe coded their subscription backendr/cursor top comment, ~60 upv
  • I heard they hire monkeys from a zoo for 2 bananas per token calculation. Down from 4 because of the poor performancer/cursor reply, 13 upv
  • they silently removed the opt-out option even for users who subscribed yearlyCursor forum
Wish — desired outcome
  • monthly spending cap option to avoid surprise chargesaggregator paraphrase of Cursor users' ask
  • If Cursor were to offer a $200/month plan that allows unlimited use of the max model, I would reconsider renewingCursor forum
  • cost allocation by feature or team, and budget alerts — without requiring custom instrumentationFinOps blog framing the gap — finout.io
Willing-to-pay signal

Very strong on the consumer side: r/cursor users are already paying $20–200/mo and threatening churn but mostly staying. The closest "I'd pay for this tomorrow" surrogate: "If Cursor were to offer a $200/month plan that allows unlimited use of the max model, I would reconsider renewing." That's a willingness-to-spend statement at $200/mo for visibility & predictability.

Verdict: Strong. All the language is from consumers of AI dev tools (Cursor users), not from the precise persona in the original opp card (indie SaaS founders shipping AI features to their own customers). The pain is the same shape — opaque token billing, surprise costs, no per-feature attribution — but the buyer is different. Recommend reframing positioning to target both personas in week 1, then narrow based on which converts.
Three candidate headlines, built from verbatim phrases
  1. Stop discovering your LLM bill the way Cursor users discover theirs.
  2. The math doesn't add up. Now it will.
  3. See exactly which feature burned your token budget — before your customer does.
3.75Composite
Opportunity #4

Vertical AI receptionist for one underserved SMB niche

"AI receptionist that answers your dental practice's phone 24/7 — books appointments, handles insurance Q&A, hands off to staff when it should. One number, flat monthly fee."

Build4/5Under3/5Demand4/5Market4/5Distrib4/5

Unmet need + evidence

The voice-agent cluster is dense (Solvea, ElevenAgents, NovaVoice, Wispr Flow's pivot story is PH-newsletter-pinned). Every product is either horizontal infrastructure (ElevenLabs Agents) or builder-tooling (Solvea = "create your AI receptionist"). None of the sampled launches owns a specific vertical end-to-end with vertical-shaped onboarding, pricing, and integrations. Recommended niche: independent dental practices in the US — ~150k practices, most have 1–3 chairs, all use one of three practice-management systems (Open Dental, Dentrix, Eaglesoft) with documented APIs. The standard pain — calls missed during chair time — has a direct revenue cost (no-shows, lost new patients). Adjacent funded category: vertical AI voice for plumbers/HVAC (Aircover, Numa) raised at $20–60M+. Dental is the same shape with cleaner integrations and a tighter buyer.

Solvea · 236 upvElevenAgents by ElevenLabs · 468 upvNovaVoice · 600 upv · 143 cmtWispr Flow PMF-pivot · pinned PH forum thread

4–8 week MVP scope

  • One Twilio number per practice, ported on activation.
  • OpenAI Realtime API or ElevenLabs Conversational for the voice loop. LangGraph state machine for the call flow (script eight scenarios well, not eighty poorly).
  • Three scripted scenarios shipped on day 1: book new-patient appointment, insurance acceptance Q&A, address / hours / directions. Anything outside the scripts → handoff to the practice's voicemail.
  • Open Dental integration only in v1 (largest indie dental PMS, has a JSON API).
  • SMS confirmation of every booking + a Slack/email summary to the practice owner.
  • Web dashboard: call log with transcripts, booking outcomes, missed-handoff alerts, this week vs last week.

Lean stack

Node/TS + Twilio Voice + Media Streams + OpenAI Realtime (or ElevenLabs Conversational) + LangGraph for the call FSM + Postgres + Next.js dashboard + Stripe billing. HIPAA: get a Twilio + OpenAI BAA before launch (both available); avoid storing any PHI you don't need (transcripts retained 7 days max in v1).

First-100 users acquisition

  • Scrape 1,000 US dental practices with <5 chairs from Yelp / Google Maps.
  • Cold email 50/day, personalized opener referencing their practice. Aim for 2-3% reply rate → 30 demos in 30 days.
  • Free first month for the first 20 practices in exchange for a 10-min recorded call about their experience (= testimonial pipeline + voice-of-customer goldmine).
  • Local SEO content: "AI receptionist for dental practices in [Phoenix / Charlotte / Austin]" — long-tail, low-competition, 50–500 monthly searches each.
  • Once you have 5 paying customers, sponsor one episode of Dental Hacks or The Tooth or Dare Podcast — niche but on-target.

Top 2 risks & week-1 invalidation

R1 — Sales cycle is too long; dental practice owners are not solo-dev-friendly buyers

Invalidate by Friday wk1: book 5 fifteen-minute calls with practice owners. Ask: "how do you handle calls when the front desk is full? what would $250–500/mo of guaranteed call answering be worth to you?" If the median sales cycle they describe is >30 days OR the price ceiling is <$200/mo, the math doesn't work for solo-dev support load. Pivot vertical (try auto repair shops — same call-handling pain, faster decisions, no HIPAA).

R2 — HIPAA / PHI compliance burden eats all the development time

Invalidate by Wednesday wk1: read Twilio's HIPAA BAA terms, OpenAI's Realtime API ZDR terms, and the relevant state regs in CA/NY/TX. If a BAA is not available for OpenAI Realtime or ElevenLabs Conversational by launch, ship with on-device Whisper + a self-hosted text LLM as the fallback path.

Opp #4 · Vertical AI receptionist for dental practices

Dentists & their front desk staff

Verdict: Weak Reddit signal

Subreddits identified

SubredditSubsActivityFitWhy
r/Dentistry~155k~80/wkbroadPrimary buyer identity, but practice-owner posts are minority share
r/DentalSchool~80k~60/wkbroadMostly residents/students — wrong buyer; useful for future market only
r/dentaloffice<5k~5/wkproblemCloser fit but below the size threshold; thin signal pool
r/smallbusiness~3M~2k/wkproblemHuge, but dental-specific posts are needle-in-haystack
r/dentalhygiene~50k~80/wkadjacentStaff perspective, not owner perspective; useful for influencer plays

Posts retrieved

Direct r/Dentistry threads about phone / front-desk / answering pain were not surfaced in this scrape. The AI-receptionist-for-dental vendor space is so SEO-heavy that organic dentist voice is buried. This is a real finding, not a search artifact.

Repeated vocabulary

missed calls×8+voicemail×6front desk×5overwhelmed / overload×4revenue leak×3on hold / hold time×3

Language buckets

Pain — how they describe it
Workaround — what they&apos;re doing now
Failed solutions
Wish — desired outcome
Willing-to-pay signal

Inferred only. The number of vendors actively spending on SEO content (PatientXpress, Aria, Resonate, mConsent, Zaha, getreach, dentalscheduling, dentalbase) suggests the category is already a contested paid market — more contested than the PH-only signal scored. This is a real downward revision to the original underserved-ness rating.

Verdict: Weak Reddit signal. The category is already SEO-saturated, which means (a) demand is real, (b) the space is more crowded with vertical AI-receptionist players than the PH sample suggested, and (c) Reddit is genuinely not where dentists vent — they're on closed forums and FB groups.
Three candidate headlines, built from verbatim phrases
  1. The 50 calls a week your front desk can't get to.
  2. One in three of your callers hangs up. Catch them.
  3. Your front desk has nine hours back. Use them on the patients in the chair.
Recommended additional channels for week-1 validation

Channel 1 — Dentaltown: Howard Farran's forum, ~250k registered dentists, organized into business / practice-management threads. The single highest-density signal channel for practice-owner pain. Free read access. Channel 2 — closed Facebook groups: "Dental Practice Owners Network" (~30k), "Dentaltown" group (~15k), "Dental Office Manager" (~12k). Higher signal density than Reddit; easier to join and post. One well-framed "here's what I'm building, would any of you talk to me for 15 minutes?" post in DPON converts better than Reddit cold outreach.

3.75Composite
Opportunity #5

Single-workflow consumer autopilot — pick one boring chore, own it

"Upload your medical bill, get a dispute letter with line-item errors flagged in 60 seconds. Pay only when we save you money."

Build4/5Under4/5Demand4/5Market3/5Distrib3/5

Unmet need + evidence

Several launches in the sample point to the same shape: a pre-packaged AI agent that handles one specific recurring real-world chore from start to finish, no app to learn. Recommended target: medical bill error finder for US patients. The category has documented sustained demand (~80% of US bills contain errors per industry reports), the workflow is a single document upload, the LLM step (cross-reference CPT/ICD-10 codes) is well within frontier-model competence, and pricing can be transactional (% of confirmed savings or flat $19/bill). Adjacent funded category: Goodbill, Resolve, Healthcare Bluebook all serve the same pain at $50–500M+ valuations. They target enterprise (employers) or high-touch (patient advocates). None ship a "$19 self-serve autopilot" for the consumer with one bill.

Gyro Autopilot — flight refunds · 102 upvGitHired — replace resume w/ GitHub commits · 243 upv · 21 cmtReplyless — daily email briefs to Telegram · 102 upvJupid — file taxes with Claude Code · 597 upv · 122 cmt

4–8 week MVP scope

  • Web upload of a PDF or photo of an itemized bill (not the EOB — explicit instruction).
  • OCR via tesseract or Claude Vision; fall back to manual line entry.
  • LLM cross-reference: line items vs. published CMS reimbursement rates and known billing-code rules (duplicate billing, upcoding red flags, unbundled charges).
  • Output: a one-page report listing flagged charges + estimated overcharge $, plus a ready-to-send dispute letter (PDF) and a list of US states where you're allowed to self-file vs. need a licensed advocate.
  • Stripe Checkout: $19 flat or 15% of estimated savings up to $99 (let user choose).
  • Honest disclaimer on every page: "this is not medical, legal, or insurance advice."

Lean stack

Next.js + Vercel · Claude Vision for OCR + reasoning · tesseract as fallback · Postgres on Neon · Stripe · Resend for the dispute-letter email + react-pdf for the PDF generation.

First-100 users acquisition

  • r/medicalbills (small but high intent), r/personalfinance (huge), r/ChronicIllness, FB groups for cancer survivors / chronic illness — communities with explicit medical-bill pain.
  • TikTok / IG Reels demo: "I uploaded my $4,800 bill — here's the $437 in errors I found in 90 seconds." 3–5 reels per week.
  • Affiliate / referral with patient-advocacy bloggers and subreddits.
  • Comparison content: "Goodbill vs. Resolve vs. [you] — what each actually does." SEO play for buyer-intent keywords.
  • Local-news angle: pitch one local TV consumer-help segment. Stunt-shaped, high-conversion when it lands.

Top 2 risks & week-1 invalidation

R1 — State regulations require a license to file medical-billing disputes

Invalidate by Wednesday wk1: review the medical-billing-advocacy regulations in CA, NY, TX, FL, IL (~40% of US population). If a license is required in any of them, the filing step has to be a "we generate, you file" flow (not "we file for you"). The product still works in that mode — but the pricing must reflect that the user does the last mile.

R2 — Hallucinated codes lead to bad disputes and reputational risk

Invalidate by Friday wk1: assemble 20 anonymized real bills (your own network + r/medicalbills posts), run the pipeline, manually verify each flag against official CMS rate tables. If accuracy is <85% on flagged items, narrow scope to the 3 bill types that are most reliable (e.g. ER visits, MRI/CT, lab panels) and refuse other bill types in v1.

Opp #5 · Niche consumer autopilot — medical bill error finder

Patients fighting outrageous medical bills

Verdict: Moderate

Subreddits identified

SubredditSubsActivityFitWhy
r/personalfinance~22M~3k/wkbroadMedical-bill threads recur weekly; high engagement on dispute stories
r/medicalbill<5k~5/wkproblemBelow size threshold but the only directly-named-pain subreddit
r/HealthInsurance~150k~250/wkproblemEOB confusion, denials, dispute mechanics — high pain density
r/ChronicIllness~80k~150/wkadjacentRecurring bills, patient-advocacy emotional charge, repeat-buyer profile
r/AmItheAsshole~13M~5k/wkadjacent"AITA for fighting my $X bill" stories go viral; great for emotional copy

Posts retrieved

4 representative threads

Repeated vocabulary

outrageous×7overcharge(d)×6bill(ed)~constantdispute / fight×5code(s) (billing/diagnosis)×4itemized×4errors / mistakes×4shocked×3

Language buckets

Pain — how they describe it
Workaround — what they&apos;re doing now
  • I will make sure it will cost them money rather than making them money [paying 5 cents at a time]r/AmItheAsshole — aggregator
  • Got 30 emails of the most influential people at the hospital, plus the hospital's investors. Every day would send a few emails describing how they billed my 'client' at seven times over the fair price.r/AmItheAsshole — aggregator
Failed solutions
  • the billing department supposedly only collects the bills. She was told that she needed to contact the admin to dispute the billr/AmItheAsshole — aggregator
  • her calls not going through to anyone qualified to handle the disputesame — aggregator
  • healthcare is outrageous. when they cancel a test they frequently still bill itforum (Comanche Club)
Wish — desired outcome
Willing-to-pay signal

Strong on percentage-of-savings model — Resolve, Goodbill, Solace exist as paid services on that basis. The self-serve $19/bill price-point has not been directly validated in the corpus. The closest "WTP tomorrow" surrogate is the volume of upvotes on AITA dispute stories (5-figure each) — that's emotional engagement, not cash-on-the-table. Treat the $19 self-serve as the riskiest assumption.

Verdict: Moderate. Pain is real, vocabulary is consistent, and the Resolve/Goodbill/Solace category is a strong WTP proxy for the percentage-of-savings model. The narrower $19-self-serve thesis remains unvalidated; that's the riskiest piece, and the right week-1 invalidation is a landing-page A/B test on price (free / $19 / 15% of savings).
Three candidate headlines, built from verbatim phrases
  1. Stop paying for the surgery you never had.
  2. The bill is outrageous. Find the errors in 60 seconds.
  3. One digit off cost her $8,500. Don't let it cost you.
Recommended additional channels for week-1 validation

Channel 1 — TikTok #medicalbills: distinct from Reddit; videos of "I found $X in errors on my bill" go viral. Search there for organic creator-driven pain language. Channel 2 — Patient advocacy bloggers' comment sections: Pixie Dust Inc., The Patient Advocate's Chronicle. Higher pain-language density than Reddit because the audience is self-selected for the problem.

04Appendix — 50 launches, extracted JTBDs

Every launch listed here was sampled from the PH leaderboards covering Apr 10 → May 10, 2026. Counts are point-in-time snapshots from the leaderboard scrape. JTBD pattern: [user] is trying to [outcome] but struggles with [obstacle].

Show full table — 50 launches with cluster, score, JTBD
#LaunchTaglineUpvCmtClusterJTBD
1BrilaOne-page websites from real Google Maps reviews13192456 · AI sitesLocal business owner is trying to launch a one-page website but struggles with rewriting placeholder template copy that "nobody believes" (maker's words).
2Fathom 3.0AI meeting notes: now bot-free, in ChatGPT & Claude77323413 · meetingKnowledge worker is trying to capture meeting context but struggles with bot-based notetakers being awkward in private/sensitive meetings.
3PluraiVibe-train evals and guardrails tailored to your use case7382273 · evalsAI app builder is trying to ship safely but struggles to set up custom evals and guardrails without dedicated ML staff.
4ProdShortTurn meetings into ready-to-post shorts and posts72415313 · meetingFounder is trying to repurpose meeting recordings into social content but struggles with manual editing time.
5CleraAn AI agent matching candidates to the right roles70723811 · hiringHiring manager is trying to find quality candidates but struggles with traditional recruiter cost and signal-to-noise.
6VeloShare anything as video messages67815110 · voiceDistributed worker is trying to convey nuance in async chat but struggles with text losing tone.
7Open WearablesOpen infrastructure for wearable-powered health products62531615 · hardwareHealth product builder is trying to ship wearable-powered apps but struggles with locked-down vendor SDKs and walled gardens.
8Kilo Code v7 (VS Code)Run Parallel AI Agents in VS Code. Free & Open Source61713614 · agentic IDEDeveloper is trying to run multiple coding agents in parallel but struggles with single-threaded chat-based IDE workflows.
9RankAIRankAI autonomously gets you buyers from Google & AI Search6041099 · SEO/GTMFounder is trying to get inbound from Google + AI search but struggles with the labor cost of traditional SEO.
10NovaVoiceSmart dictation, AI assistant, + app control via voice60014310 · voiceKnowledge worker is trying to control Mac apps and LLMs by voice but struggles with Siri's limitations and disconnected dictation tools.
11JupidFile your taxes with Claude Code5971227 · vert. compl.Self-employed user is trying to file taxes but struggles with TurboTax-style stepwise UI for non-standard situations.
12Claude Code RoutinesPut Claude Code tasks on autopilot with smart routines5911614 · agentic IDEDeveloper is trying to automate recurring agent tasks but struggles with re-prompting and re-configuring agents from scratch each session.
13Figma for AgentsDesign with AI agents, connected to your design system5892312 · agent orch.Designer is trying to use AI for production design but struggles with off-system, off-brand outputs from generic AI design tools.
14OffsiteBuild teams of humans and agents, watch them work5898612 · agent orch.Team lead is trying to mix humans and agents on real work but struggles with no shared workspace where both are first-class participants.
15Claude Code Desktop (Redesign)Run parallel coding agents from one desktop workspace5781614 · agentic IDEDeveloper is trying to manage multiple parallel Claude Code agents but struggles with the terminal-only UX for fan-out tasks.
16Claude Opus 4.7Claude's most capable model for reasoning & agentic coding5832614 · agentic IDEDeveloper is trying to ship reasoning-heavy agentic code but struggles with frontier model availability/quality.
17Ask Product Hunt AIFind the right product, just ask580348 · prod. microUser is trying to discover products on PH but struggles with PH search returning by upvote, not fit.
18RankSpotYC-application growth via Google + AI search570929 · SEO/GTMYC applicant / founder is trying to demonstrate growth traction but struggles with manual SEO + LLM-search optimization.
19Velo 2.0Share anything as video messages (v2)5538613 · meetingSecond launch of Velo — productivity-focused.
20Claude DesignMake prototypes, slides & one-pagers by talking to Claude544216 · AI sitesNon-designer is trying to make prototypes/decks but struggles with the learning curve of Figma/Keynote.
21Shadow 2.0Productivity (May launch, top of category)4821648 · prod. microUser is trying to capture context from across apps but struggles with manual switching/screenshotting.
22KanwasProductivity (May AI #1)4792258 · prod. microUser is trying to plan/visualize work but struggles with linear list-based task tools.
23Hera LaunchCreate studio-quality launch videos with AI4805513 · meetingFounder is trying to make a launch video but struggles with production studios' cost and turnaround time.
24Notion MCPYour Notion workspace, inside every AI agent475452 · MCPKnowledge worker is trying to use AI agents on workspace data but struggles with siloed Notion content invisible to agents.
25FlowMarketAI-powered marketing (May AI #1, Marketing #1)4691369 · SEO/GTMMarketer is trying to scale campaigns but struggles with stitching together creative + ad-buying + analytics tools.
26ElevenAgentsScale conversations without scaling your team468104 · receptionistBusiness is trying to scale customer convos but struggles with hiring SDRs/CSRs at the volume they need.
27SpeakONA MagSafe AI device for a post-keyboard world4678115 · hardwareApple user is trying to use voice as primary interface but struggles with hands-on-keyboard workflows being faster for short bursts.
28Monid 2.0DevTools (May AI #2, DevTools #2)466213 · evalsDev is trying to monitor LLM-app behavior but struggles with HTTP-style observability that doesn't speak GenAI.
29Lessie AISales: Search, Reach and Connect — 10x faster4211469 · SEO/GTMSales rep is trying to find prospects but struggles with siloed signals across LinkedIn / Apollo / Crunchbase.
30Noiz Easter VoiceCrack an Easter egg to generate an AI voice4217710 · voiceAudio creator is trying to generate AI voices but struggles to find prompt-to-voice tools with character.
31Claude Desktop BuddyBring Claude into the physical world with maker hardware423915 · hardwareMaker is trying to embody AI but struggles with chat-only UX.
32Stanley For 𝕏The world's first AI Head of Content401969 · SEO/GTMFounder is trying to grow on X but struggles with content cadence + quality at the same time.
33Beezi AIMake AI development structured, secure, & cost-efficient393403 · evalsIndie AI builder is trying to ship cheaply but struggles with token costs + secrets management at small scale.
34KollabShared workspace where teams work with agents together3884112 · agent orch.Team is trying to use agents collaboratively but struggles with single-user agent UX.
35PandaProbeDevTools / observability (May DevTools #2)378253 · evalsDev is trying to monitor production LLM behavior but struggles with general APM tools missing prompt/cost dimensions.
36RadarDevTools (May DevTools #3)378183 · evalsDev is trying to spot regression in agent quality but struggles with eval rigs that take weeks to set up.
37Spira AIAI Influencer that's always on trend409649 · SEO/GTMBrand is trying to grow socially but struggles with constant content creation labor.
38FocuSee 2.0Record screen to get polished demos & tutorials3443213 · meetingMaker is trying to record demos but struggles with raw recordings looking unpolished.
39MindraMarketing (May AI #1, Marketing #1)343479 · SEO/GTMSolo founder is trying to do marketing but struggles with the tool sprawl.
40PopTaskLight menu bar task manager for quickly capturing tasks329458 · prod. microUser is trying to capture tasks fast but struggles with the overhead of full task apps.
41Pixero AIOpen-source for AI Ads328429 · SEO/GTMMarketer is trying to create ad creatives but struggles with iteration speed in design tools.
42Trupeer AICreate stunning demo videos with AI in minutes2464013 · meetingMaker is trying to make demo videos but struggles with editing time/learning curve.
43SolveaCreate your AI receptionist that answers, books, and sells236184 · receptionistSMB is trying to capture missed calls but struggles with hiring receptionists.
44LetterbookAI support platform built for founders268464 · receptionistFounder is trying to handle support email but struggles with helpdesk overhead and seat-based pricing.
45Ollama v0.19Massive local model speedup on Apple Silicon with MLX26471 · local AIDeveloper is trying to run LLMs locally on Apple Silicon but struggles with under-utilized GPU compute.
46GoalsAI turns your goal into one daily action282238 · prod. microUser is trying to make progress on big goals but struggles with overwhelming planning.
47Orange SliceAutomate any sales task with AI282299 · SEO/GTMSDR is trying to hit quota but struggles with manual prospect research time.
48GitHiredReplace your resume with your GitHub commits243215 · autopilotEngineer is trying to land interviews but struggles with resume-shaped signal not matching what they actually do.
49Kuku (open source)Open source SaaS infrastructure (May YC#7)2212314 · agentic IDESolo founder is trying to ship SaaS quickly but struggles with stitching together auth + billing + multi-tenancy.
50Lovie Formation MCPIncorporation MCP — AI-native company formation124112 · MCPFirst-time founder is trying to incorporate but struggles with multi-step state filings inside an AI workflow.

Deliberately excluded: model-launches that are just frontier-lab releases and Promoted-only placements where the only signal was paid distribution.