Not because the regulations are unclear, but because people tend to hear what they want to hear.

I one worked with a company with a Class II medical device that qualified for a 510(k) exemption. They completed device registration and listing, entered the market, and largely considered their regulatory work complete.

Then FDA showed up.

The inspection resulted in nine observations and eventually a Warning Letter.

The issue wasn’t the product itself. It was a fundamental misunderstanding of what “510(k)-exempt” actually means.

One of the most persistent myths in medtech is that exemption from premarket submission somehow translates into exemption from the rest of the regulatory framework.

It doesn’t.

A device may be exempt from a 510(k), but that doesn’t eliminate expectations around design controls, validation, complaint handling, documentation, or quality system oversight.

After receiving the initial observations, the company submitted a response and mitigation plan. FDA reviewed it and determined the response was insufficient, issuing an Untitled Letter.

At that point, the problem shifted from inspection findings to full-scale remediation.

The company attempted to recover by implementing a quality management system with the help of an engineer with no medtech, regulatory or quality experience.

So when FDA returned, the company received seven additional observations—not because a quality system didn’t exist, but because the system that had been implemented wasn’t being followed.

Creating procedures is one thing. Demonstrating that the organization actually operates according to them is something else entirely.

As the remediation effort expanded, the underlying gaps became increasingly clear:

• Required validation activities had never been completed.

• Biocompatibility testing was missing.

• Design documentation was incomplete.

• A design history file had to be created.

• Complaint handling processes required substantial revision.

• Seven CAPAs were opened to address the deficiencies systematically.

What’s interesting is that none of these issues involved a particularly complicated technology or regulatory pathway.

The challenge wasn’t complexity. It was confidence.

The company believed it had fewer regulatory obligations than it actually did.

And once that assumption takes hold, it influences everything that follows—what testing gets performed, what documentation gets created, and how resources are allocated.

The remediation ultimately required rebuilding the quality system, completing the missing validation activities, establishing a complete design history file, transferring the design into manufacturing, and documenting the actions taken for FDA review.

Only after those systems and records were fully implemented did FDA close the observations and Untitled Letter.

Here’s the key point to remember - FDA observations rarely begin where the actual problem began. They’re usually just the point where the misunderstanding finally becomes visible.

In this case, that misunderstanding started with a single word: Exempt.

Not exempt from a 510(k).

Exempt from a 510(k), while still fully accountable for building and maintaining a compliant quality system.

Those are two very different things.

And FDA has been making that distinction for a long time.

On the surface, everything looked aligned—compelling technology, strong narrative, clear path to market.

But a quick check of the FDA product code told a different story, because the device had been aligned to the wrong product code.

That may sound like a minor issue, but trust me - it isn’t.

The product code determines:

• The regulatory pathway

• The required testing

• The applicable standards

• The level of evidence needed

It is the starting point for everything that follows. Get it wrong, and the consequences don’t show up immediately. They show up later—during submission, during review, or worse, after significant capital has already been deployed.

In this case, the likely outcome was predictable:

• A rejected submission

• A required restart under the correct classification

• Duplicated testing

• Expanded timelines

• A regulatory budget that effectively doubles

That’s not a technical correction. That’s a complete reset.

The investor saw the issue and stepped away.

No remediation plan.
No CAPAs.
No recovery timeline.

Just a decision made early enough to avoid all of it.

What This Tells You

Most expensive regulatory problems aren’t caused by complex failures.

They start with foundational misalignment:

• Wrong product code

• Misinterpreted intended use

• Incomplete understanding of applicable standards

These are not edge cases. They’re common.

And they tend to survive longer than they should because everything built on top of them appears to be moving forward.

Until it isn’t.

Where Remediation Usually Begins

In most situations, this issue isn’t caught at the conference coffee break conversation stage.

It shows up later:

• During submission preparation

• In FDA review questions

• Or after a rejection

At that point, the work isn’t just corrective—it’s reconstructive.

Because by then, you’re not fixing a document. You’re unwinding a strategy.

The Quiet Lesson

Due diligence in medtech isn’t just about the technology.

It’s about whether the regulatory foundation holds.

Because if it doesn’t, everything built on top of it—testing, timelines, capital allocation—has to be reconsidered.

And by then, it’s rarely a small adjustment.

The Reality

Some remediation efforts cost millions.

Some cost years.

And some, if caught early enough, never have to happen at all.