A great prototype means you’re ready for market
❌ The myth: Once we have a working prototype and positive user feedback, we can quickly move through CE marking and launch
✅ The reality: A functional prototype is merely the foundation – regulatory readiness requires complete traceability throughout your entire development process. The MDR demands that every design decision, every specification change, and every verification test is documented, approved, and linked within a structured Quality Management System. Without this infrastructure in place from day one, even the most innovative product will face significant certification delays.
Design control is not bureaucratic overhead – it’s the backbone of certifiable development. According to ISO 13485:2016 (Chapter 7.3) and MDR Annex II Section 3, your development must follow a structured process where user requirements flow into design inputs, which generate design outputs, which are then verified and validated before release. Each step requires formal documentation and approval. This creates a Design History File that proves your product was developed systematically and meets all General Safety and Performance Requirements.
Equally critical is your Quality Management System. Article 10(9) MDR requires a functioning QMS covering development, manufacturing, monitoring, and traceability before any conformity assessment begins. This isn’t documentation you can create retroactively when approaching a notified body – it must be actively implemented throughout development, with clear processes for document control, risk management, corrective actions, and design control.
The challenging reality: if your development history cannot be reconstructed with formal approvals, traceable specifications, and documented verification, your technical performance won’t be recognised by regulators – regardless of how well your prototype works. Many start-ups discover this gap only when engaging with notified bodies, forcing them to rebuild their QMS retroactively and delaying market access by many months.
→ Regulatory compliance must be built into your development process from the first design decision, not assembled as an afterthought when seeking certification
Real-world scenario:
A start-up develops an inhalable drug delivery system controlled by a smartphone app. Development progresses rapidly through iterative prototyping, with strong user feedback and impressive performance metrics. The team feels ready for CE marking and engages a notified body.
During the conformity assessment, critical gaps emerge. Design specifications exist across different files but lack formal approval signatures. Risk analyses were conducted during team meetings but never systematically documented. Verification testing was performed, but test protocols aren’t traceable to specific design inputs. The development timeline cannot be reconstructed, and GSPR compliance evidence is fragmented.
The consequence: The entire Quality Management System must be established retroactively. Design documentation requires reconstruction and formal approval. The CE conformity assessment, expected to take months, extends beyond a year. Investor confidence wavers as launch dates slip repeatedly, and the market opportunity begins to narrow.
The preventive approach: With a lean, scalable QMS implemented from project inception – including controlled design reviews, documented requirements, systematic verification protocols, and integrated risk management – the same start-up could have maintained continuous audit readiness. Each design iteration would have been formally approved, each requirement traced through to testing, and each risk systematically assessed and mitigated. Market entry would have remained predictable, and the technical strength of the product would have been matched by regulatory robustness.