We've backed 34 companies at this point, and when we look back at the ones that made it past the critical early inflection — the ones that got to first clinical deployment, survived their first payor negotiation, found product-market fit in an actual hospital system — the MD/PhD founders show up disproportionately in that group. Not because credentials predict success. They don't. But because the clinical training leaves a particular imprint on how someone builds.
It's worth being precise about what we mean, because there's a lazy version of this argument that just says "clinician founders understand the problem better." That's technically true but incomplete. The more important difference is operational. It changes what they do first, who they trust, and what they're willing to cut.
They validate differently
The instinct drilled into physicians and researchers is skepticism toward your own conclusion. A clinician who's been through residency has ordered hundreds of tests and waited for results that forced them to revise their working diagnosis. That habit carries into product development in ways that aren't immediately obvious.
When a clinician-founder says "we need to validate this," they usually mean something more specific than a survey. They mean controlled conditions, defined endpoints, a comparison group. They ask: compared to what? For how long? In which patient population? These are the right questions, and many non-clinical founders get to them eventually, but the MD/PhD founders often arrive there faster because the questions are already in the muscle.
In our experience, this leads to tighter early clinical evidence packages. Not necessarily more expensive ones. Tighter. They're not trying to prove everything — they're trying to prove the right thing for the next decision gate. That efficiency matters at Series A, when investors are evaluating whether the clinical evidence is credible.
They hire for the right reasons
Here's a pattern we've seen more than once: a non-clinical founder at a digital health company hires a Chief Medical Officer early, puts them on the website, and then largely ignores them. The CMO becomes a credentialing exercise. The product decisions keep getting made by the engineering team.
Clinical founders don't do this. They hire clinicians because they want to argue with them. The CMO or chief of clinical affairs becomes an internal critic, not a validator. We have one portfolio company where the clinical affairs lead has killed three features that were technically complete and had good user engagement metrics — because she identified workflow problems that would have created liability in a hospital setting. The founder listened. It was painful. It was right.
This kind of internal friction is healthy, and clinical founders tend to welcome it because they understand what the alternative looks like. They've seen it in the hospital: the expensive piece of equipment that gets installed and never used because the purchasing decision was made by administrators, not clinicians.
They scope for regulatory early
The 510(k) or De Novo pathway doesn't appear as a surprise when a clinician-founder is driving. It's usually part of the product architecture from day one. They've lived in regulated environments. They understand that documentation isn't overhead — it's the residue of good process, and the FDA wants to see evidence of good process.
Non-clinical founders often treat regulatory strategy as something that happens after product development. Clinician founders are more likely to let regulatory requirements shape the product roadmap. That's a real competitive advantage. FDA clearance timelines are one of the most consistent sources of delay in our portfolio companies, and the delays almost always trace back to decisions made in the first 18 months of building.
The constraint they have to fight
There's a counterweight, and good clinical founders acknowledge it. Medical training selects for risk aversion in clinical settings — the incentive structure in medicine punishes errors far more than it rewards speed. That same instinct can slow down product iteration, delay go-to-market decisions, and create analysis paralysis at moments where the right move is just to ship something and learn.
The best clinician-founders we've backed are explicit about this. They have a business co-founder, or they've surrounded themselves with operators who push them. Dr. Priya Sharma, our managing partner, spent eight years as an attending at MGH before moving into investing, and she's the first to say that the discipline of clinical medicine and the discipline of company building conflict on timing. Both are necessary. Neither alone is sufficient.
When we see a team with an MD/PhD founder and a strong commercial or operational partner, that's a combination we take very seriously. The scientific rigor is there from day one. The willingness to move fast on the commercial side keeps the company from becoming a research project.
What this means for founders pitching us
We don't require clinical credentials. We have portfolio companies founded by engineers, computational biologists, and former hospital administrators. What we look for — in every founder, regardless of background — is evidence that they've done the clinical work anyway. They've interviewed 50 nurses. They've watched the workflow. They can describe exactly where their product sits in a patient care pathway and what happens three steps before and three steps after it's used.
That's the behavior we're looking for. The MD/PhD founders often come with it pre-installed. Everyone else has to build it deliberately. Some do. When they do, the distinction between a clinical and non-clinical founder largely disappears.
Interested in what we look for in founding teams? Reach out directly.
