Regulatory success for startups isn't about documentation — it's about strategy. This guide covers how to build a lean, stage-appropriate regulatory plan that keeps you on track without burning your runway.
Start by confirming your device classification with documented rationale — this determines your conformity assessment route, documentation requirements, Notified Body involvement, and timeline. Choose your target market early and integrate regulatory milestones into your product roadmap from day one, not after development.
The most common regulatory mistake a medical device startup makes is not starting too late — it's starting without a strategy. Documentation without a clear classification, intended use, and target market is expensive to produce and frequently needs to be redone.
Regulatory strategy is the layer that sits above documentation. It answers the questions that determine everything else: which framework applies to your device, which market to enter first, what evidence you'll need, and how long that will realistically take.
Getting these questions wrong early on — or deferring them — is one of the most reliable ways to burn runway without making regulatory progress.
Classification is the single most consequential early decision in your regulatory journey. Your device class determines your conformity assessment route, your documentation requirements, your Notified Body involvement, and your timeline.
Under EU MDR (Regulation (EU) 2017/745), devices are classified as Class I, IIa, IIb, or III based on intended purpose, duration of contact, invasiveness, and other criteria. UK MDR follows a similar structure but with some differences — particularly for devices that would be Class I under EU MDR but may be reclassified under UK rules.
Borderline products — devices that sit at the boundary between a medical device and a general consumer product — are especially difficult to classify. Software as a Medical Device (SaMD) adds another layer of complexity, with specific rules under EU MDR Annex VIII and MDCG guidance that differ from hardware devices.
Do not assume your classification. Get it confirmed in writing, with documented rationale, before you build your regulatory plan around it.
EU MDR, UK MDR (UKCA), and FDA 510(k) are three distinct regulatory pathways. Each has different timelines, evidence requirements, and costs. Choosing which market to enter first — and in what order — is a strategic decision that affects your entire regulatory plan.
For many early-stage startups targeting EU and UK markets simultaneously, the practical answer is to align your regulatory strategy around EU MDR compliance first — then address UK-specific requirements in parallel where the overlap is highest.
One of the most important things a regulatory strategy must do is give you a realistic timeline — and then map that against your available runway.
For Class I devices with self-certification, EU MDR compliance is achievable in months with focused effort. For Class IIa devices requiring Notified Body certification, the current average timeline — from initial submission to certificate — is significantly longer. Plan accordingly.
Timeline realism is not pessimism. It's the foundation of a fundable, executable regulatory plan. Investors doing due diligence will ask about your regulatory timeline — make sure your answer is grounded in reality.
Practical approach: Build your regulatory milestones into your product roadmap from day one. Regulatory timelines are not separate from your product timeline — they are part of it.
A common mistake is to treat technical documentation as a single deliverable — something you produce all at once before submission. In practice, documentation builds over time as your product develops, and the most efficient approach is to build it progressively in parallel with development.
The core documents you'll need for EU MDR compliance include:
Starting with the Intended Use Statement and classification rationale is the most logical first step — these two documents anchor everything else in your technical file.
Define what your device does, who it's for, and how it will be used. Get your classification confirmed with documented rationale. This is the foundation of everything else.
Based on classification and market priorities, define which framework applies and in what order you will seek conformity assessment.
Map key milestones against your product development roadmap and available runway. Identify where Notified Body involvement is required and when to initiate contact.
Begin with risk management and intended use — these inform design decisions and should be live documents throughout development, not retrospective write-ups.
Identify appropriate Notified Bodies early, understand their application requirements, and plan for 13–18 month review timelines in your roadmap.
Classification errors discovered late can invalidate your entire conformity assessment approach. Confirm classification with documented rationale before building your strategy around it.
EU MDR, UKCA, and FDA have different timelines and evidence requirements. Trying to pursue all three simultaneously at an early stage usually leads to scattered effort and slower progress on all fronts.
Current Notified Body capacity constraints mean certification timelines are significantly longer than they were under MDD. Build realistic timelines into your plan from the start.
Design decisions made during development affect regulatory compliance. Involving regulatory input during development — not after — avoids costly redesigns and documentation rework.
Regvo works with medical device startups to define their regulatory starting point, confirm classification, and build a practical plan matched to their stage and runway. Book a free discovery call to get started.
Book a free discovery callClassification is the most consequential early decision. Your device class determines the conformity assessment route, documentation requirements, Notified Body involvement, and timeline. Never assume classification — confirm it with documented rationale before planning anything else.
For most early-stage startups, aligning around EU MDR compliance first is more practical, then addressing UK-specific requirements in parallel where overlap is highest. Pursuing EU, UK, and FDA simultaneously from day one typically scatters resource and delays everything.
Notified Body certification for a Class IIa device currently takes 13–18 months on average. This timeline should be built into your product roadmap and runway planning from the start — not treated as a separate administrative process.
You need: intended use statement, device description and specifications, risk management file (ISO 14971), clinical evaluation report, post-market surveillance plan, Declaration of Conformity, and — for Class IIa and above — a full technical documentation file reviewed by a Notified Body.
Assuming classification without confirming it, underestimating Notified Body timelines, or treating regulatory planning as a post-development activity. These decisions define the entire certification journey — getting them wrong early is expensive to fix.