Medical device development often begins with a strong technical idea.
For startups, that early momentum is important. A prototype, a clinical need, or a promising technology can create the energy needed to move a product forward. But in medical device development, technical progress alone is not enough to create a clear path to market.
The direction of the project is shaped much earlier than many teams expect.
Before development moves too far, companies need to understand what they are building, how the device will be used, what claims they intend to make, and what regulatory path they are preparing for. These early decisions influence product requirements, risk management, clinical evidence, testing, documentation, and eventually the CE marking process.
For startups, this does not mean everything must be fully mature from the beginning. It means the project needs enough structure to move forward in the right direction.
Start with the intended use
One of the most important early decisions is the device’s intended use.
This is not just wording for future documentation. It defines what the device does, what it does not do, who it is for, and what clinical purpose it is expected to support. In practice, intended use affects almost every later decision in the project.
If the intended use is too broad, unclear, or not properly connected to the clinical need, the development path can become unnecessarily complex. The company may end up planning tests, documentation, or clinical work that does not support the actual product strategy. In the worst case, a team may collect clinical data that does not demonstrate the right performance claims.
A more focused intended use can make the development path clearer. It helps define what evidence is needed, what risks must be managed, and what the technical documentation must eventually support. Intended use, requirements definition, and clinical evidence planning are therefore not isolated tasks. They are early decisions that shape the entire CE path.
Define requirements before decisions become difficult to change
Requirements definition and risk management should begin early, not after the product has already taken shape.
This is because requirements are not only documentation outputs. They guide development. They help translate the clinical purpose into design expectations, performance criteria, usability considerations, and verification activities.
Risk management plays a similar role. It helps identify where design decisions may create safety, performance, usability, or regulatory concerns. When risk thinking is introduced early, it can guide development before costly commitments are made.
Without this structure, development may still move forward, but not necessarily in a way that can be documented, justified, or verified later. Teams may make technical choices that appear reasonable at the time, only to discover later that they create avoidable regulatory or quality challenges.
Early structure helps prevent this. It gives the team a common framework for making decisions and for showing why those decisions were made.
Build the regulatory strategy around realistic assumptions
A regulatory strategy should not be based on the most optimistic version of the project.
For startups, time and funding are often closely linked. If the regulatory path is underestimated, the consequences can be significant. Development, testing, notified body interaction, clinical evaluation, and certification activities all take time. If these are not planned realistically, the project can face delays at exactly the point where resources are most limited.
Classification is one part of this. If the device classification is misunderstood, the required documentation and evidence may be underestimated. This can lead to gaps in the technical file, incorrect planning, or late-stage corrective work.
The notified body should also be considered early. For many devices, market access depends on notified body involvement, and timelines may be longer than expected. Treating the notified body only as a final hurdle can create avoidable pressure. It is better to understand early what role they will play, what expectations they may have, and how the project timeline should reflect that.
Overly optimistic assumptions around regulatory strategy, timing, and funding can create serious challenges later in the project, particularly when development and certification activities take longer than expected.
Bring quality and regulatory expertise into development early
Quality and regulatory work should not sit outside product development.
Many important development decisions have regulatory implications. Component choices, material choices, subcontractor selection, usability decisions, test planning, and clinical evidence strategy can all affect the future CE path.
This does not mean every early design discussion needs to become heavy or formal. It means that regulatory and quality perspectives should be available when decisions affect requirements, safety, performance, or documentation.
If these perspectives are introduced too late, teams may need to revisit decisions that have already shaped the product. Examples include unsuitable component choices, missing documentation for in-house testing, unclear design rationale, or materials that do not fit medical device expectations.
When QA and RA are involved early, they can support development rather than slow it down. The goal is not to add unnecessary processes, but to help the team avoid decisions that create rework later.
Define roles and responsibilities clearly
A successful CE path cannot be outsourced entirely.
External experts can guide the process, lead quality and regulatory activities, and help structure the work. But the company developing the device remains the product expert. The startup must stay actively involved, especially when defining intended use, clinical needs, technical decisions, and product requirements.
This is particularly important for early-stage companies. A consultant can provide direction and build the framework, but they cannot replace the company’s understanding of the device and its intended clinical use.
Successful collaboration depends on trust, clear responsibilities, and a shared understanding of how the work will be divided. The company must be committed to quality and regulatory topics, while external experts can guide, structure, and lead the process.
A clearer start supports the full CE path
For startups and companies developing new medical devices, early clarity is one of the most valuable investments.
A well-defined intended use, realistic regulatory strategy, clear requirements, early risk management, and active collaboration between development and QA/RA functions all help create a more controlled path forward.
The goal is not to make the early phase unnecessarily heavy. It is to avoid building too far in the wrong direction.
Once the direction is clear, the next step is building the structure that allows the project to move forward consistently. In the second part of this series, we look at how a proportionate QMS and technical documentation framework can support development instead of becoming a late-stage repair project.
If your team is developing a medical device and needs support with regulatory strategy, quality management, or CE marking preparation, MDS works alongside your team to build a practical and structured path forward.
You can contact us at sales@mdsfinland.com or via Book a Meeting.
