The Catch-22 of regulated products

We had a genuinely good product. The doctors who used our MedTech device consistently told us it worked. The clinical feedback was positive. The potential market was real. But we couldn't sell it without a license, and we couldn't get a license without clinical data, and we couldn't collect clinical data without — you see where this is going.

The regulatory pathway for medical devices varies by jurisdiction, but the core challenge is consistent: in many categories, you need evidence of clinical effectiveness to receive a license, and you need a licensed product to legally run the clinical trials that generate that evidence. This loop is not a bureaucratic oversight. It exists because regulators are trying to protect patients. But for a startup without institutional backing to navigate it, the loop is effectively a wall.

We explored every route. Compassionate use exemptions. Academic partnerships that would allow limited trials under research frameworks. Markets with different regulatory requirements that might provide a pathway we could use to build data. Some of these moved us forward. None of them moved us fast enough. The real lesson wasn't that the regulation was wrong — it was that we hadn't mapped the regulatory pathway before we built the product. We fell in love with the solution before we understood the constraints.

“A great product in a locked market is not a business. It's a prototype.”

When I evaluate any company operating in a regulated environment, the first thing I look at is the pathway — not the product. What does the journey from prototype to legally sellable product actually look like, step by step? Who has walked that path before? Is there a heavyweight partner — an established institution, a distribution network, an existing licensee — who could provide the access the startup needs? The product is a hypothesis. The regulatory pathway is the business plan.

The takeaway

If you're building in healthcare, fintech, legal, or any heavily regulated space, map the regulatory route before you write a line of code. Not because the regulation will stop you — but because understanding it will show you exactly where your real product needs to be.