5 Critical pitfalls Medical Device Startups must avoid (and how to fix them)

Most medical device startups underestimate the regulatory journey under the EU MDR or other regulatory frameworks by 12–18 months. Here's where they go wrong:

1. Misusing Regulatory Terminology

Every professional field has its own vocabulary that experts use to communicate with each other. However, some words in one field may have a different meaning. Even within the regulatory field, the same abbreviation may have different meanings across jurisdictions. Therefore, it is wise to review the definitions of all regulatory frameworks you work with and create a glossary for the company. This will help later when talking to different experts.

2. Poor Design and Development documentation 

The second pitfall concerns the entire D&D process. This is a complex topic, but it is equally critical to get it right. If you cannot reproduce why certain design features have made it into the device, or show which requirements were defined upfront and where they come from, you will get a lot of questions from the authorities.

It is crucial to start as early as possible by documenting which design decisions have been made and why. Therefore, you should aim to implement a D&D procedure aligned with ISO 13485 sooner rather than later. With this, you can show that the design process was controlled. With this, you should also implement a design traceability matrix to keep track of which design outputs meet which inputs and how you verified them. Finally, you need to freeze your design to start testing your device. If your device meets the requirements you set at the beginning and can deliver the clinical benefit (on paper), you can freeze your design and start testing and validation. Further improvements can be made in a 2^nd or 3^rd version of your device.

 3. Misjudging when to build your QMS 

There are generally 2 different pitfalls:

• A startup buries itself in administration, while not yet necessary, and implements too many procedures early on.
• A startup does not have crucial procedures in place on time.

You should aim to document basic procedures during the design stage to control this process from the start and ensure compliance. Other procedures which are important early on are:

• Risk management
• Document and record control
• Supplier control

4. Understanding time investment

If you bring a medical device to market for the first time, there are many uncertainties, one of which is how long it will take to pass regulatory assessments, including the time required for preparation. It is impossible to put a number on this, as it will depend heavily on the type of device. Factors to include:

• Is a clinical trial needed?
• Device testing: Is long-term testing necessary?
• Some tests cannot be performed in parallel but must happen after each other
• Retesting
• QMS building and record generation
• TD writing and assessment of authority

To get a good estimate of the required testing and timeline, talk to experienced professionals. This will help with fundraising, as realistic timelines are necessary to convince investors to invest in your company.

5. Incomplete submissions

Incomplete submissions are among the most common causes of delay in bringing your medical device to market. It appears that many manufacturers, not just startups, submit incomplete application forms and entire submission files to Notified Bodies (NBs). This leads to additional review rounds, higher costs, and significant time lost on both sides.

The most frequently missing or poorly prepared elements include:

• Clinical evaluation report (CER): Often submitted too thin, lacking sufficient clinical data or a clear equivalence argumentation. NBs will reject or heavily question underdeveloped CERs.
• Risk management file: Incomplete risk-benefit analyses or missing post-market risk updates are a red flag for reviewers.
• Technical Documentation (TD) gaps: Missing test reports, incomplete labelling documentation, or absent instructions for use (IFU) are surprisingly common. Also, the linkage between the TD summary and the different in-depth reports is an aspect that many manufacturers can improve.
• Software documentation: If your device contains software, IEC 62304 compliance documentation is frequently missing or incomplete.
• UDI and labelling compliance: Errors or omissions in labelling against the applicable regulation (MDR/IVDR) cause unnecessary back-and-forth.
• Declaration of Conformity: Incorrectly drafted or referencing outdated standards.

The fix is straightforward: before submitting, run your technical file against a pre-submission checklist mapped to the relevant regulation. Better yet, have an experienced regulatory consultant review your file before it lands on the NB's desk. The cost of that review is almost always lower than that of a rejection round, and a consultant may suggest improvements or rewording for certain sections. In contrast, an NB reviewer can simply ask about missing items without offering suggestions for improvement.

Are you not sure where you are and need help avoiding those pitfalls? Please book a free consultation: