---
title: The Founder's Emotional Journey Through MDR Certification
description: Five stages most MedTech founders move through on the MDR path: denial, shock, anger, bargaining, acceptance — and what to do at each one.
authors: Tibor Zechmeister, Felix Lenhard
category: MedTech Startup Strategy & PMF
primary_keyword: founder emotional journey MDR
canonical_url: https://zechmeister-solutions.com/en/blog/founders-emotional-journey-mdr
source: zechmeister-solutions.com
license: All rights reserved. Content may be cited with attribution and a link to the canonical URL.
---

# The Founder's Emotional Journey Through MDR Certification

*By Tibor Zechmeister (EU MDR Expert, Notified Body Lead Auditor) and Felix Lenhard.*

> **Most MedTech founders move through five predictable emotional stages on the MDR path: denial, shock at the scope, anger at the pace, bargaining for shortcuts, and finally acceptance and disciplined execution. Recognising which stage you are in is not self-indulgence — it is a diagnostic that tells you whether your next decision is going to move the certification forward or burn another month.**

**By Tibor Zechmeister and Felix Lenhard.**

## TL;DR
- MDR Articles 5, 10, and 52 define the factual landscape — placing on the market, manufacturer obligations, and conformity assessment procedures — and this landscape is the emotional trigger for most founders.
- Stage 1 is denial: "our product is probably not a medical device." The fix is an honest intended-purpose decision and classification check.
- Stage 2 is shock: realising the full scope of QMS, tech file, clinical evaluation, and post-market surveillance. The fix is scoping, not panic.
- Stage 3 is anger: frustration with the slow pace and notified body queues. The fix is parallelisation and a realistic plan.
- Stage 4 is bargaining: hunting for shortcuts and exceptions. The fix is honest reframing — efficiency is not the same thing as evasion.
- Stage 5 is acceptance: disciplined execution on a prioritised backlog. This is where certification actually ships.
- Escalate to expert help when stages are repeating rather than progressing, or when a bad decision is about to become irreversible.

## Why this matters

Very little written about MDR acknowledges that certification is, for the people living it, a deeply emotional process. The regulatory literature treats founders as rational actors maximising compliance per euro. The actual experience is closer to a prolonged stress test: months of work without visible progress, a notified body that does not return calls, investors asking when CE mark arrives, and a growing suspicion that the startup's cash runway might not reach the finish line.

Ignoring this emotional dimension is not neutral. It leads to concrete bad decisions: rushing intended purpose to dodge a class upgrade, hiring the wrong person at the wrong time, outsourcing work the team should own, or — most expensive of all — freezing and doing nothing for weeks while the calendar burns. Recognising the stage you are in lets you diagnose the decision in front of you before you make it.

The five stages are not a rigid model. Founders loop back. Sometimes you are in two stages about two different parts of the project. But the pattern is common enough across 50+ certifications (Tibor) and 44 coached startups (Felix) to be worth naming.

## What MDR actually says

The emotional pressure points map directly to specific MDR articles. Understanding the factual trigger makes it easier to separate the feeling from the regulatory reality.

**MDR Article 5 — placing on the market.** A device may only be placed on the Union market or put into service if it complies with the regulation when duly supplied and properly installed, maintained, and used. This is the provision that forces the question: do you have a device, and is it compliant? This is where denial stage lives — founders who hope their product might not trigger Article 5 at all.

**MDR Article 10 — general obligations of manufacturers.** This single article enumerates the manufacturer's obligations: a risk management system, a quality management system compliant in substance with EN ISO 13485:2016+A11:2021, technical documentation under Annex II and III, clinical evaluation under Article 61 and Annex XIV, registration obligations, post-market surveillance, vigilance, and more. Reading Article 10 in one sitting is the usual trigger for stage two. It is a long article.

**MDR Article 52 — conformity assessment procedures.** This article, together with Annexes IX, X, and XI, defines which conformity assessment route applies to which device class and therefore whether a notified body is in the critical path. The timeline for conformity assessment, combined with notified body queues, is the trigger for stage three anger.

None of this is new, and none of it is secret. What surprises founders is the cumulative scope — the reading of Article 10 alongside Annex II is the moment when a two-person startup realises that the regulatory workstream is the size of the product workstream.

## A worked example

A SaMD startup — two founders, six months into development, Class IIa under Rule 11 — arrived at Tibor's office, in Felix's coaching program, with a product demo and a question: "how fast can we get CE marked?"

Stage 1 (denial) had already passed. They knew they had a medical device.

Stage 2 (shock) hit in the first 90 minutes. When the full scope was sketched on a whiteboard — QMS, tech file structure, clinical evaluation with literature search, software lifecycle under EN 62304:2006+A1:2015, usability under EN 62366-1:2015+A1:2020, cybersecurity under EN IEC 81001-5-1:2022, post-market surveillance plan, PRRC, notified body application — one founder went silent and the other said "so this is a two-year thing." That was the shock. It was the correct response.

Stage 3 (anger) showed up three weeks later in an email: "we applied to three notified bodies and nobody has even sent us a contract." The notified body capacity issue is real. The anger was directed at the wrong target — at NBs for being slow, rather than at the plan for not having budgeted realistic NB queue time.

Stage 4 (bargaining) appeared in month three. The founders started asking whether they could reclassify as Class I by narrowing the intended purpose, whether they could release a "non-medical" wellness version first, whether they could ship to a non-EU jurisdiction to buy time. Some of these were legitimate strategic questions. Others were shortcuts dressed up as strategy. The difference mattered.

Stage 5 (acceptance) arrived around month four. The founders stopped fighting the shape of the work. They hired a fractional RA person, adopted a lean eQMS, started the CER in parallel with software development, and set a realistic 18-month target. The pace did not change. The frustration did.

This sequence — roughly four months from first contact to acceptance — is close to average in our experience. Some founders get there in weeks; a few never do and either burn out or pivot away from MedTech entirely.

## The Subtract to Ship playbook

For each stage, there is a concrete move that helps.

**Stage 1 — Denial. "Maybe we're not a medical device."**
What it looks like: the founder frames the product as wellness, lifestyle, or "decision support only" to avoid the regulatory trigger. Sometimes this is right. Often it is wishful.
What to do: sit down with MDR Article 2(1) definition, Article 2(12) intended purpose, Annex VIII classification rules, and the Borderline Manual v4. Write a one-page intended-purpose statement and a draft classification justification. If you are a medical device, accept it in one week and move on. If you are genuinely a wellness product, document why with the same rigour — because you will be asked.

**Stage 2 — Shock. "This is enormous."**
What it looks like: paralysis after reading Article 10 and Annex II. The scope feels unbounded.
What to do: do not make strategic decisions this week. Scope the work into a flat list using the MDR requirement-to-source map: QMS, risk management, tech file, clinical evaluation, PMS, vigilance, labelling, UDI, Eudamed, PRRC. For each, mark current state (nothing, partial, complete) and estimated effort. This gives you a backlog, not a feeling. The shock is proportional to the ambiguity; the backlog removes the ambiguity.

**Stage 3 — Anger. "Why is this so slow?"**
What it looks like: frustration at notified body response times, at the pace of document review, at standards updates, at everything.
What to do: the correct target is your plan, not the system. NB queues are real and known; you should have budgeted for them. Parallelise: run QMS build, tech file assembly, clinical evaluation, and NB selection simultaneously rather than in sequence. Submit early to the NB for preliminary review even if not everything is final. Stop waiting.

**Stage 4 — Bargaining. "Can we find a way around this?"**
What it looks like: searching for classification downgrades, exemptions, scope reductions, or jurisdictions that feel easier. Some of this is legitimate strategy. Some is avoidance.
What to do: use the test "does this narrow my intended purpose in a way I genuinely believe serves patients and users?" If yes, proceed — a tight beachhead intended purpose is often the right move. If the honest answer is "no, we're just trying to dodge effort", stop and go back to stage five. Bargaining against the regulation rarely shortens the timeline; it usually extends it when the gap is discovered in audit.

**Stage 5 — Acceptance. "We know what to do. Let's execute."**
What it looks like: the backlog is visible, the team knows its next two weeks of work, the NB is contracted, the clinical strategy is in place, and the conversation shifts from "how can we avoid this" to "how do we ship this well."
What to do: protect this state. This is where certifications actually close. Run weekly backlog reviews, monthly deep reviews with any external expert you work with, and a ruthless prioritisation rule: the next task is the one that unblocks the most other tasks.

**When to escalate to expert help.** The honest signal is not panic — most founders feel panic and don't need a consultant, just a plan. The signal is repetition: you are looping through stages 2-4 for the third time on the same decision and not making progress. Or: a decision is about to become irreversible (submitting to the wrong NB, locking in a wrong classification in an investor pitch, signing a CMO contract that breaks your tech file structure). Those are the moments where an outside voice that has seen this 50+ times is worth far more than it costs.

## Reality Check

1. Which of the five stages are you in right now, honestly, today?
2. Is the same stage recurring for the second or third time, or are you progressing?
3. If you are in denial: have you written a one-page intended-purpose statement and classification justification you could defend in front of a notified body?
4. If you are in shock: do you have a flat backlog of MDR workstreams with current state and estimated effort per item?
5. If you are in anger: what is your actual, budgeted notified body queue assumption in weeks?
6. If you are in bargaining: is the strategic move you are considering narrowing your intended purpose for real reasons, or is it avoidance dressed as strategy?
7. If you are in acceptance: what single decision would most delay your next milestone if you got it wrong, and have you stress-tested it with someone outside your team?
8. Who on your team has explicit permission to say "we are stuck" out loud?

## Frequently Asked Questions

**Is this "emotional journey" real or just a narrative device?**
It is real. Across 50+ certifications and 44 coached startups, the pattern repeats. Naming it helps founders make better decisions under pressure.

**How long does each stage typically last?**
Highly variable. First-time founders often spend weeks in shock and months in bargaining. Second-time founders move through the early stages in days and spend most of their time in acceptance and execution.

**Can I skip the early stages if I already know MDR?**
Yes, partially. Founders who have shipped a medical device before usually skip stage 1 entirely and compress stages 2-4 into a few days of scoping. But even experienced founders re-encounter bargaining on specific decisions.

**When exactly should I bring in a regulatory consultant?**
Two signals: you are looping in stages 2-4 without progress on the same decision, or you are about to make an irreversible decision (NB choice, classification, intended purpose lock) without having stress-tested it with someone who has seen it before.

**Does acceptance mean giving up on speed?**
No. Acceptance is where real speed begins. The time wasted in denial, anger, and bargaining is what makes certifications slow. A founder in genuine acceptance with a clean backlog typically moves twice as fast as one still arguing with the regulation.

**Is burnout normal in this process?**
It is common but not inevitable. The founders who burn out are usually the ones who stay in anger or bargaining too long. Acceptance, counterintuitively, is the most sustainable emotional state.

## Related reading
- [The MedTech startup paradox](/blog/medtech-startup-paradox) — why the pressure feels harder in MedTech than in other startup domains.
- [When to bring in a regulatory consultant](/blog/when-to-bring-in-regulatory-consultant) — the decision framework for escalation.
- [No-bullshit MedTech startup timelines](/blog/no-bullshit-medtech-startup-timelines) — realistic numbers that help move past the anger stage.
- [Subtract to Ship applied to MedTech](/blog/subtract-to-ship-applied-medtech) — the execution discipline that lives in stage five.
- [10 reasons MedTech startups fail](/blog/medtech-startup-failure-modes-10-reasons) — several of the failure modes map directly to unresolved stages in this journey.

## Sources
1. Regulation (EU) 2017/745 on medical devices, consolidated text. Article 5 (placing on the market), Article 10 (general obligations of manufacturers), Article 52 (conformity assessment procedures).
2. EN ISO 13485:2016+A11:2021, Medical devices — Quality management systems — Requirements for regulatory purposes, referenced by MDR Article 10(9).
3. Author practice across 50+ notified body audits (Tibor Zechmeister) and 44 coached MedTech startups (Felix Lenhard).

---

*This post is part of the [MedTech Startup Strategy & PMF](https://zechmeister-solutions.com/en/blog/category/startup-strategy) cluster in the [Subtract to Ship: MDR Blog](https://zechmeister-solutions.com/en/blog). For EU MDR certification consulting, see [zechmeister-solutions.com](https://zechmeister-solutions.com).*