Most health care startups don’t fail because the technology is bad. They fail because of mistakes that happen long before the product ever reaches a clinical setting. After seven years of evaluating health care companies as a physician-scientist turned venture investor (and making over 20 investments across digital health, biotech, medical devices, and therapeutics), I’ve started to see the same patterns repeat.

These aren’t obscure business school failures. They’re patterns that any physician would recognize instantly if someone showed them the pitch deck. The problem is that most of the people writing the checks aren’t physicians.

Here are the patterns that kill health care startups most often.

Pattern 1: They solve a conference problem, not a clinical problem

The most common failure I see is a startup that builds a solution for a problem that sounds urgent on a panel stage but isn’t actually painful at the point of care.

I’ve reviewed devices designed to prevent rare procedural complications that surgeons already manage with existing technique. I’ve seen platforms that automate a clinical workflow nobody was complaining about. I’ve evaluated AI tools that generate reports clinicians didn’t ask for and don’t trust.

In each case, the founding team had often done “customer discovery,” but they’d talked to department chairs at conferences rather than the frontline physicians and nurses living inside the workflow every day. There’s a meaningful difference between a problem a thought leader finds intellectually interesting and a problem that makes a floor nurse want to throw her badge at the wall. The first gets you a nice advisory board. The second gets you a customer.

Pattern 2: They build the product before understanding who actually buys it

Health care has a unique challenge that most industries don’t. The person who uses the product, the person who decides to purchase it, and the person who pays for it are often three different people.

A surgeon might love a new device, but the hospital’s value analysis committee has to approve the purchase. A patient might benefit from a remote monitoring app, but the health system’s IT security team has to clear it first. A physician might want to prescribe a new therapeutic, but the insurer has to agree to reimburse it.

I’ve seen startups spend years perfecting a product that physicians loved, only to discover that the hospital procurement process required an 18-month evaluation cycle they hadn’t budgeted for. I’ve seen patient-facing apps with strong clinical data fail because the reimbursement pathway didn’t exist and patients wouldn’t pay $50 a month out of pocket.

The companies that succeed in health care aren’t just building a product that works. They’re mapping every stakeholder who touches the purchase decision and designing their go-to-market strategy around the hardest bottleneck in that chain, not the easiest.

Pattern 3: They confuse FDA clearance with market adoption

This one is particularly dangerous because it creates false confidence. A founder tells you the product is “FDA-cleared” and investors hear “ready to sell.” But in most cases, FDA clearance (especially a 510(k)) means the product is substantially equivalent to something already on the market. It doesn’t mean it’s better. It doesn’t mean hospitals need it. And it definitely doesn’t mean physicians will switch from what they’re already using.

I’ve reviewed companies with FDA-cleared devices, published clinical studies, and thousands of units sold that still couldn’t break into the operating room ecosystem. The reason was straightforward. Hospitals buy integrated suites of equipment from a single vendor. Displacing one component of that suite, no matter how innovative, requires a level of clinical superiority that most single-feature devices can’t demonstrate.

Clearance gets you permission to sell. Adoption requires you to change behavior. Those are very different problems, and the second one is almost always harder.

Pattern 4: They underestimate how entrenched the existing workflow really is

Health care is one of the most change-resistant industries on the planet, and for good reason. When you’re managing a crashing patient at 3 a.m., you rely on muscle memory and systems you’ve used a thousand times. Nobody wants to learn a new interface during a code.

The startups that fail here often have a technically superior product that requires clinicians to change how they work. Maybe it adds two extra steps to a procedure. Maybe it requires a new documentation flow. Maybe it needs a dedicated IT integration that the hospital’s already-stretched technical team has to support.

I’ve watched companies with genuinely better technology lose to inferior incumbents because the switching cost (measured not in dollars but in cognitive load, training time, and workflow disruption) was too high. The most successful health care products I’ve invested in didn’t ask clinicians to change their behavior. They eliminated a pain point within the existing workflow so seamlessly that adoption felt like relief, not effort.

Pattern 5: They treat the regulatory and reimbursement strategy as an afterthought

This is the failure pattern I find most frustrating because it’s entirely preventable. A founding team spends two years building a product, raises capital, hires a team, and only then starts asking questions about how the product will be regulated and how it will be paid for.

In health care, the regulatory pathway and the reimbursement strategy should be designed alongside the product, not after it. The choice between a 510(k) device pathway versus a drug-device combination pathway can change the timeline by years and the capital requirement by tens of millions. The difference between having an existing CPT code and needing a new one can determine whether you have revenue in 12 months or 36 months.

The companies I’ve invested in that have done well all had one thing in common. The founding team understood the regulatory and reimbursement landscape from day one. In several cases, we built the regulatory strategy and reimbursement analysis ourselves before committing capital, because if the pathway doesn’t work, nothing else matters.

Why this matters for physicians who aren’t investors

You don’t need to invest in startups to benefit from recognizing these patterns. Every physician encounters them.

When a device rep walks into your OR with a new product, you can ask: does this require me to change my workflow, or does it fit into what I already do? When your hospital announces a new digital health partnership, you can ask: who decided to buy this, was it clinicians, or was it administrators responding to a sales pitch? When a colleague joins a startup’s advisory board, you can ask: have they figured out who pays for this?

These are the questions that separate health care products that succeed from the ones that quietly disappear after burning through their funding. Physicians already have the clinical instinct to spot these failures. The question is whether anyone is asking them before the money is spent.

Harsha Moole is an internal medicine-trained physician-scientist with more than 100 peer-reviewed publications, including work featured in the New England Journal of Medicine. After years of clinical practice and gastroenterology outcomes research, he made an unconventional transition from the bedside to the boardroom by founding PhysicianEstate, a health care-focused venture capital firm.

Over the past seven years, Dr. Moole has made 22 early-stage health care investments across digital health, medical devices, biotech, and therapeutics. He has also built a network of more than 200 physicians from institutions such as Johns Hopkins and Stanford who help source opportunities and provide clinical diligence before capital is deployed. His core thesis is that physician-scientists with firsthand clinical experience are uniquely positioned to identify health care investments that generalist investors often miss.

His research background is reflected in his publication record on Google Scholar, and he shares professional updates on LinkedIn.