Customer discovery in MedTech is much broader than asking a physician whether they like your idea.
A device can solve a genuine clinical problem and still fail commercially if it does not create enough value for the people who need to use, purchase, implement, or pay for it.
Meaningful customer discovery requires both breadth and depth. Before investing heavily in development, map every stakeholder who could influence whether the device succeeds. That could include clinicians, patients, nurses, hospital administrators, procurement teams, value analysis committees, payers, distributors, and hospital staff.
Even stakeholders who seem peripheral can create barriers if their needs are overlooked.
One practical approach is to create a stakeholder mind map around the device. Start with the obvious end user, then work outward. Who pays for it? Who approves the purchase? Who stores it? Who trains people to use it? Whose workflow needs to change? Who could prevent adoption even if the clinician or user loves the product?
QuickVault’s guide to customer discovery for MedTech startups explores this process in more detail, including how to translate what you learn into product, regulatory, risk, and commercial decisions.
The next question is harder: does your product provide enough value to justify the purchase and also change what people already do?
Founders naturally compare their technology to the problem they are trying to solve. Customers compare it to their current standard of care, competing products, existing workflows, and the cost and disruption required to switch. A solution that is incrementally better may not be compelling enough to warrant the cost of the product nor change behavior.
Axel saw this firsthand while mentoring a company developing a surgical preparation device. The technology could make orthopedic surgical prep easier for nurses by moving part of the process outside the operating room. The nurses liked the concept.
But the team had focused too narrowly on that user group. When the entire hospital workflow was considered, moving the preparation process created new logistical challenges elsewhere. The benefit to one group did not outweigh the disruption to the larger system. By the time those barriers became clear, significant time and capital had already been invested.
That is exactly what early customer discovery is supposed to uncover. Before building further, do not just ask, “Who will use this?” Ask, “Who has to say yes, spend money, change behavior, or alter a process for this product to succeed?”