Three ideas that prove competitive doesn't always mean impossible.
Most builders I know avoid competitive markets like the plague. "Why build another profiler when Datadog exists?" or "Mobile testing is solved, look at all these companies." I get it. Competition feels like a red flag.
But I've been looking at three ideas that share an interesting pattern: they're all entering crowded spaces, yet they each have a realistic path to winning. Not because they found some magical blue ocean, but because they understand something specific that existing players miss.
The pattern is this: mature markets with execution gaps. These are spaces where the fundamental problem is real and well-established, existing solutions have obvious limitations that users complain about regularly, and the technical or business model innovation needed to fix those gaps is achievable by a small team.
Let me show you what I mean with three examples. Mobile Playtest SDK & Companion Hub is entering a space with PlaytestCloud, UserTesting, and a dozen other mobile testing platforms. C++ Memory-Safety Migration Assistant would compete with Coverity, PVS-Studio, and other static analyzers. Amdahl Profiler — Automated Bottleneck Analyzer is going up against Datadog, New Relic, and the entire observability industry.
Sounds insane, right? But look closer at what each one does differently.
The mobile playtest idea isn't trying to replace PlaytestCloud's managed service. It's solving a different workflow: developers who want to use their own testers (Discord communities, beta users) but can't get decent recordings on iOS because the tooling is broken. PlaytestCloud's business model depends on providing the testers, so they'll never build a "bring your own testers" SDK that cannibalizes their core value prop.
The C++ memory safety tool isn't competing with Coverity on detection. It's solving the "now what?" problem that comes after static analysis finds 500 memory bugs. Coverity tells you about the bugs. This tool would actually fix them with automated codemods. Coverity could build this, but their enterprise sales model makes more money selling seats for manual remediation than shipping tools that reduce the time customers spend in their platform.
The Amdahl profiler isn't replacing Datadog's production monitoring. It's solving the pre-production problem where engineers optimize the wrong bottlenecks because they don't have an easy way to see that I/O dominates their "CPU-bound" workload. Datadog's focus on production observability means they're not incentivized to build dev-loop performance tools that might reduce production monitoring needs.
What these ideas share is that they're not trying to dethrone incumbents directly. They're solving adjacent problems that incumbents can't or won't address because of their existing business constraints.
This creates three advantages:
Different customer conversation. Instead of "why not just use Datadog?" you get "oh this solves the thing Datadog doesn't do." You're not asking people to replace their existing tools. You're filling a gap in their workflow.
Lower switching costs. Since you're not displacing existing tools, adoption is additive rather than disruptive. Teams can try your SDK alongside their current testing setup, or run your profiler without ripping out their production monitoring.
Focused product surface. You can build something genuinely better at the specific thing you do because you're not trying to match feature parity across an entire platform. The mobile SDK can focus obsessively on iOS recording reliability. The C++ tool can focus entirely on safe automated transforms. The profiler can focus on pre-commit bottleneck analysis.
I think there's a broader lesson here about how to evaluate competitive markets. Instead of asking "how many competitors are there?" ask:
You're not looking for empty markets. You're looking for markets where the incumbent solutions have structural constraints that create execution opportunities.
This strategy isn't without downsides. All three of these ideas are vulnerable to incumbents eventually closing the gap they're targeting. Apple could fix iOS recording APIs and commoditize the mobile SDK's value prop. Coverity could add automated codemods to their platform. Datadog could build an Amdahl breakdown view.
The defensive play is speed and focus. Get to market faster than a large company can shift priorities. Build something genuinely better at the narrow thing you do. Create switching costs through workflow integration and historical data before the giants notice you exist.
But that's a more interesting risk than "no one wants this" or "the market doesn't exist." It's the risk that you succeed enough to attract attention from players with more resources.
What makes these opportunities available now is often external pressure that incumbents can't ignore. The mobile testing gap exists because Apple keeps changing iOS recording APIs and managed services have to maintain compatibility across their entire platform. The C++ memory safety demand is accelerating because of CISA deadlines and regulatory pressure. The profiling workflow gap exists because modern distributed systems create bottleneck analysis problems that weren't relevant when current tools were designed.
These external forces create cracks in established markets. Incumbents have to choose between maintaining their current value proposition and adapting to new constraints. That choice often leaves execution gaps.
The question isn't whether competitive markets are good or bad for new entrants. It's whether you can identify the specific gaps that competition has created, and whether you can execute on fixing those gaps faster than existing players can adapt.
Sometimes the best markets are the ones where everyone else is already fighting, but they're all fighting the wrong battle.