The FDA Pre-Submission Meeting You're Skipping Will Cost You Eighteen Months

Most technical founders treat the FDA pre-submission (Q-Sub) process as optional paperwork. Something to do later, once the science is tighter or the prototype is more polished. That instinct is exactly backwards, and it costs companies real time.

Photo by Etatics Inc. on Pexels.

Here's the math: a Q-Sub request takes roughly 90 days to get a formal written response. That feels slow. But a regulatory submission built on wrong assumptions about your device classification, your predicate, or your required clinical data can eat 18 months before FDA tells you what they actually need. You don't save 90 days by skipping a Q-Sub. You borrow 18 months at a very high interest rate.

What a Pre-Submission Actually Does

A Q-Sub is a formal written request to FDA asking specific questions before you file your 510(k), De Novo, or PMA. You can ask about device classification, the adequacy of your proposed testing protocol, whether a particular predicate is appropriate, or what clinical evidence FDA would expect for your indication.

FDA responds in writing. That response is not legally binding, but it is extremely useful in practice. Reviewers generally honor prior feedback provided the device and the questions haven't changed substantially.

The written record also matters during due diligence. Acquirers and lead investors in Series A medtech rounds want to see Q-Sub correspondence. It signals that your regulatory path has been stress-tested by the agency, not just by your consultant.

Where Founders Go Wrong

Three failure modes show up repeatedly.

First, founders ask vague questions. "Does FDA think our device is safe?" is not a Q-Sub question. FDA will not answer it, and a non-answer wastes your 90-day window. Good Q-Sub questions are specific and binary where possible: "Is [specific predicate 510(k) number] an appropriate predicate for our device given the differences described in Section 3?" That question has an answer.

Second, founders send Q-Subs too late. By the time you've run your bench testing, finalized your predicate analysis, and drafted your submission, you've already committed to a path. If FDA disagrees with your predicate choice at that stage, you're rebuilding from the middle of the house. Send your first Q-Sub before you design your verification and validation studies. That's the decision that's hardest to reverse.

Third, founders treat the Q-Sub response as a green light rather than a data point. FDA saying your proposed testing protocol is "generally adequate" does not mean your submission will sail through review. It means they have no objection to that specific aspect at that specific time. Don't paper over remaining uncertainties with a favorable Q-Sub response and call the path clear.

graph TD
    A[Device Concept Locked] --> B(Draft Q-Sub Questions)
    B --> C{Questions Specific Enough?}
    C -->|No| B
    C -->|Yes| D[Submit Q-Sub to FDA]
    D --> E[FDA Written Response ~90 days]
    E --> F(Design V&V Studies Based on Feedback)
    F --> G[Build Submission]

The Study Design Trap

Verification and validation studies are expensive and slow to repeat. A single animal study can run six figures. A usability study with the right patient population takes months to recruit. If you design those studies without knowing FDA's expectations for your device type, you're gambling.

Some device categories have recognized consensus standards. Others don't. Some indications require clinical data from a randomized controlled trial; others accept retrospective registry data. Your regulatory consultant may have strong opinions. Those opinions are worth something. They are not worth as much as a written response from the actual reviewer pool at FDA.

Send the Q-Sub before you commit the study budget. This is the single most leveraged use of the process.

One More Thing on Consultants

A good regulatory consultant will help you write a sharp Q-Sub. A mediocre one will either tell you that you don't need one (to avoid the 90-day wait that delays their next deliverable) or draft generic questions that produce generic responses.

Ask any consultant you're evaluating to show you Q-Sub questions they've written for a prior client. Read them. If the questions are vague or hypothetical, that tells you something about how they'll serve you when it counts.

The FDA is not your adversary here. They've built a formal mechanism for founders to get clarity before making expensive commitments. Using it isn't a sign that your path is uncertain. Ignoring it usually is.