Moat & Differentiation
Synthesized from layered exploration
The Core Edge
The gap no one bridges:
There's a massive gap between the healthcare world and the tech world.
- No one in healthcare knows how to code
- No one in tech understands healthcare at a deep level — economics, incentives, organizational politics
We bridge it. That's the edge.
The Founding Combination
Founder 1:
- Princeton engineering → technical foundation, can build
- Warburg Pincus healthcare PE → deep understanding of economics, incentives, organizational dynamics
- Bridges business and technology in the same mind
Founder 2:
- Healthcare investing background → understands the space
- Built technical fluency through the partnership → now ships production software daily
- Creative execution, culturally fluent
Together: The rare combination. Most teams have one or the other — tech people who don't understand healthcare, or healthcare people who can't build. We have both, in both founders.
The Partnership
What's really built: the relationship.
- Structurally extremely strong partnership
- High values alignment
- Conceptual alignment
- Both founders now fully technical — repos, GitHub, Claude Code, shipping production software
- One brings engineering depth; the other brings creative execution
- Complementary access to different worlds
The partnership is the moat. Two people who trust each other, think together, and can both build. That's not easily replicated.
The Teaching Flywheel
Why "both founders build" is a major green flag:
We're in the vibe coding era. AI-native development changes what's possible.
This partnership developed technical capability across both founders — one came from engineering, the other built fluency through the partnership. Both now ship production software.
The implication for the business:
- If we can develop this capability within our own team, we can do it for customers
- When we embed with customers, we're not just building for them
- We're teaching them to build — creating AI-native capability inside their organizations
- That's stickier than any software
- The bottleneck for AI transformation isn't models — it's talent
- We're proof the talent gap can be closed with the right approach
The flywheel: We teach → they build → they depend on us for what they can't yet do → we teach more → the capability compounds.
The Infrastructure Moment
The tools caught up to the ambition.
We're not reinventing the wheel. We're standing on the shoulders of giants:
- Claude Code → AI-native development
- Vercel → deployment without DevOps overhead
- Neon → serverless Postgres, scales automatically
- GitHub → table stakes
A two-person team can ship production software that would have required 10 engineers five years ago. This isn't scrappy — it's leveraged.
What this enables:
- Capital efficiency (small team, big output)
- Speed (iterate in hours, not weeks)
- Focus (build the healthcare AI, not the infrastructure)
Why it's part of the moat: The same leverage we use, we bring to customers. If we can do this, we can help them do it too.
How We See
Is the research defensible? Not in the traditional sense. Someone could catch up on facts.
What's defensible: understanding the real issues.
Example — Utilization management:
- Surface view: "Make a bot that sends denial letters"
- Real view: It's about the relationship between payer and provider. Incentives. Information asymmetry. Judgment under pressure.
If you don't understand that, you solve symptoms. You create band-aids. You fail.
The moat isn't what we know. It's how we see.
Against Competition
Incumbents (Epic, etc.): Don't understand AI the way we do. Move slow.
AI Startups: Don't understand healthcare the way we do. Build wrappers. Fail on real problems.
Our position: We're not a typical healthcare startup or a typical AI startup. We bridge a gap that usually kills companies. That's our edge.