Why underserved doesn't mean unimportant, and what three overlooked ideas have in common.
There's a pattern that keeps showing up in the ideas we find most interesting at PerfectIdeas. It's not the ones with the biggest TAM slides or the most breathless Reddit threads. It's the ones where you look at the competitive landscape and think: why hasn't anyone done this yet?
We call it the underserved market signal. And it's more specific than it sounds.
Underserved doesn't mean "no competition." It means the existing solutions are either solving a different problem for a similar audience, or solving the same problem for a completely different audience. The gap isn't empty. It's just misaligned.
This matters because underserved markets behave differently than zero-competition markets. In a zero-competition market, you have to convince people a problem exists. In an underserved one, people already know the problem exists. They've already tried to solve it. They've bounced off the existing tools and landed somewhere between resignation and workaround.
That's actually better. Resignation is not apathy. People who have given up still remember that they gave up, and they'll talk to you about it.
The three ideas we're looking at this week all share this pattern. None of them are operating in a vacuum. All of them have incumbents nearby. But in each case, the incumbent is pointed slightly the wrong direction, and the gap that's left open is real.
RightsChain — Licensing & Royalty Marketplace for AI Training Data is trying to do something that sounds like it should already exist: let independent musicians license their work directly to AI companies that need training data.
Here's the situation. Shutterstock has $104M in AI licensing revenue. The major labels are suing Suno and Udio. Spawning.ai collected over 100,000 opt-out requests from artists who don't want their work used. There is clearly demand on both sides. And yet there's no open marketplace where an independent musician can set a price, issue a machine-readable license token, and get paid when an AI company trains on their catalog.
Shutterstock and Getty exist, but they're walled gardens serving their own catalogs. ASCAP and BMI handle radio, not AI training. Spawning handles opt-outs, not monetization. The gap is specifically the neutral, open infrastructure that lets a creator with self-owned masters participate in this market at all.
The fatal flaws here are real and worth understanding. The cold-start problem on a two-sided marketplace is brutal: AI companies need hundreds of thousands of tracks in specific styles, not 500 indie albums. And if US courts rule that AI training is fair use, the compliance-driven demand evaporates overnight. The window where mid-tier AI audio companies are scared enough to pay for licenses and funded enough to afford them might be narrower than the 12-24 months it takes to bootstrap this.
But the signal is valid. Independent artists have no equivalent infrastructure for this, and they want it. The unfair insight here is sharp: major labels are suing over the exact use case that independent musicians would happily monetize given the right tools. That tension is RightsChain's best pitch to both sides simultaneously.
Changelog Summarizer & Update Impact Analyzer starts from a problem most developers have felt but probably haven't articulated: Dependabot opens a PR, you stare at it for 30 seconds, open three browser tabs, read two paragraphs of changelog, close them all, and either merge or punt. Multiply that by 15 PRs a week.
Dependabot and Renovate solve the automation side of dependency management. They find updates, open PRs, and get out of the way. What they don't do is tell you whether the update matters for your specific codebase. That's the gap. Not "here's the PR," but "here's what changed and here are the three files in your repo that are probably affected."
Socket.dev covers supply chain security. Snyk covers vulnerabilities. The changelog-to-impact translation layer exists nowhere. And the reason it doesn't exist is that the incumbents' job ends at PR creation. They have no incentive to build past that point.
I'll be honest: the threat model here is concerning. GitHub Copilot could ship this as a feature update and collapse willingness-to-pay overnight. Microsoft has the repo access, the LLM infrastructure, and the developer trust to do exactly that within six months. The Reddit validation signal is also weak (23 upvotes on a "turn Dependabot off" thread is a mild frustration, not a screaming pain point). And teams that feel burned by a single bad impact card, one PR flagged as "safe" that breaks production, will say so loudly in the exact communities you're relying on for growth.
But the codebase-aware differentiation is real. GitHub's generic summary won't know which functions your specific repo calls. If you can make that import-scanning layer fast and accurate, you have something the platform can't immediately copy. The question is whether you can get there before Copilot makes the whole thing moot.
VibeCode Health Auditor is the one I find most interesting, partly because the market it's targeting is genuinely new.
There are probably millions of AI-generated MVPs sitting on GitHub right now that look like apps but aren't. No real auth, no error handling, hardcoded credentials, UI components with no API endpoints behind them. A Reddit thread in r/webdev titled "So when will people realize vibe coding is just..." got 909 upvotes and 249 comments. That's not a fringe complaint.
SonarQube and CodeClimate exist. But they're built for engineering teams reviewing PRs, not for non-technical founders trying to figure out what it would cost to hire someone to fix their Lovable-generated app. The output is wrong for the audience. A non-technical founder doesn't need a cyclomatic complexity score. They need someone to tell them "your app doesn't have real authentication and adding it will cost approximately 20-40 developer hours."
That's the gap. Not technical debt detection, but technical debt translation. The insight that really makes this interesting is buried in the idea: the real buyer isn't looking for code quality metrics, they're trying to avoid getting ripped off by a contractor who inflates scope. A credible third-party estimate gives them negotiating power worth 10-50x the cost of the audit.
The fatal flaw, though, is legitimately hard. Dev-hour estimates for architectural gaps have 3-10x variance depending on the codebase and the developer. One bad estimate that a founder uses to evaluate a contractor quote, and then discovers was off by 5x, becomes a public complaint on exactly the communities driving your growth. And there's a structural economics problem: most users probably have exactly one AI-generated MVP they need audited. If 70% of customers are single-use, the subscription model breaks and the LTV math falls apart.
The per-audit pricing option ($149 one-time) might actually be the honest version of this business. That's worth validating before you build anything.
None of them are trying to beat an incumbent head-on. All of them found a specific sub-segment where the existing tools either can't or won't serve the actual customer.
RightsChain's real target is independent musicians with self-owned masters, a segment that ASCAP and Getty have no reason to fight for. The changelog tool's real target is the "my specific repo" question that Dependabot never asks. VibeCode's real target is non-technical founders making hiring decisions, not engineers reviewing PRs.
The pattern worth internalizing: underserved markets usually aren't underserved because nobody thought of the idea. They're underserved because the incumbents have a different primary customer and the segment being ignored is too small or too weird for them to care about.
That's your opening. Small and weird is fine. Small and weird is, in fact, what you want when you're building alone and need to move fast.
The other thing these ideas share is timing sensitivity. All three of them have a window that could close: AI training fair use rulings, GitHub Copilot shipping features, IDE makers adding native auditing. The underserved market signal is real, but it's not patient. If the gap is obvious enough for you to see, it's obvious enough for someone with more resources to fill eventually.
The question isn't whether these markets are underserved. They clearly are. The question is how long they stay that way.