The founder's consulting-prep problem
The founder is not ready to decide classification, 510(k), De Novo, Premarket Approval (PMA), exemption, or predicate strategy alone. The real problem is intake readiness: can the founder show the consultant what the product is, what public clues were checked, what similar devices were found, and which decisions still need professional judgment?
When that preparation is missing, the conversation starts with scattered search terms and vague product assumptions. When it is prepared, the consultant can spend more time on judgment, risk, pathway options, and next evidence needs.
What should be clear before the first paid call
| Preparation area | Question to answer | What TrueMedDevice organizes |
|---|---|---|
| Product definition | What is the device, who uses it, where is it used, and what problem does it address? | A concise product-definition worksheet with intended-use assumptions and claim boundaries. |
| Public FDA clues | Which product codes, device classes, exemptions, 510(k)s, De Novo records, or PMA signals might be relevant? | A source ledger that separates clues from conclusions. |
| Similar devices | Which public records look close enough for a reviewer to inspect, and which are only broad comparators? | A similar-device shortlist with why each record might or might not matter. |
| Consultant questions | What must the qualified reviewer decide before the team spends more money? | An open-question list for pathway, evidence, testing, labeling, and claim-boundary review. |
What becomes easier after the packet
- The consultant intake starts with a source-linked product story instead of a blank search.
- The founder can ask sharper questions about 510(k), De Novo, PMA, exemption, or non-device boundaries.
- Investor and manufacturer conversations avoid turning public clues into unsupported pathway claims.
- Paid consultant time can focus on judgment, assumptions, evidence gaps, and next steps.
- The team gets a clearer go / pause / research-more decision before committing to a broad engagement.
When two consultants give different answers
A founder may ask the same pathway question to two consultants and hear different answers. The goal is not to decide which consultant is right from a public article. The goal is to compare the reasoning: what product definition each consultant assumed, which intended use they relied on, which FDA sources or similar devices they cited, what evidence gaps they named, and which next step they recommended.
A pathway-prep packet gives the founder a comparison frame. If one consultant assumes a different user, claim, technology, accessory, software function, or use setting, the advice may diverge for a real reason. If two answers use the same assumptions but cite different sources or skip different gaps, the founder has a focused follow-up question instead of a vague conflict.
How the packet is organized
| Packet component | What it captures |
|---|---|
| Product definition worksheet | Intended use, user, patient population, technology, environment, accessories, software, and claims. |
| FDA source ledger | Product Classification, 510(k), De Novo, PMA, exemption, and guidance links where relevant. |
| Comparator shortlist | Candidate public records and why each might or might not matter. |
| Pathway clue matrix | Possible product code, regulation clue, similar-device pattern, and source limitation. |
| Reviewer question list | Decisions that still require qualified regulatory, legal, quality, or clinical review. |
Pathway clue matrix
- Possible product code and generic category.
- Regulation citation and device class clue.
- Similar devices and public submission record pattern.
- Exemption, De Novo, 510(k), or Premarket Approval watch-out.
- Why the clue may not apply to the startup's product.
What needs qualified review
- Final classification and product-code applicability.
- Whether exemption, 510(k), De Novo, Premarket Approval, or another path should be discussed.
- Predicate suitability, testing strategy, clinical evidence, labeling, and claim boundaries.
- Quality-system, legal, reimbursement, distribution, import, and commercial launch implications.
What TrueMedDevice can prepare
TrueMedDevice prepares the pathway-prep evidence packet: public source ledger, product-code clues, similar-device shortlist, pathway clue matrix, source limitations, and open questions for the consultant or RA/QA reviewer.
Source ledger
What it can tell you
FDA's public overview of device classification and regulatory control categories.
What it cannot decide
Your product's final classification, product code, exemption, or submission pathway.
What it can tell you
How FDA describes product codes and generic device categories in the classification database.
What it cannot decide
Which product code applies to your device or whether a code is sufficient for launch planning.
What it can tell you
Public context about Class I and Class II device exemptions.
What it cannot decide
Whether your specific device, claims, or changes qualify for an exemption.
What it can tell you
FDA's public overview of the De Novo classification request pathway.
What it cannot decide
Whether De Novo is appropriate for your product or evidence strategy.
What it can tell you
Current FDA context for electronic medical device premarket submissions through the CDRH Portal.
What it cannot decide
Whether a submission is complete, sufficient, or strategically appropriate.
Frequently asked questions
Is a pathway assessment the same as a regulatory strategy?
No. This is a source-backed preparation packet for qualified strategy review. It helps a reviewer see the evidence and assumptions faster.
Can public databases prove my device is exempt?
No. They can surface exemption clues and related records, but a qualified reviewer must decide whether any exemption applies to your specific product and claims.
What is the best next step after the packet?
Use it to brief a qualified regulatory reviewer or consultant with source links, product assumptions, comparator clues, and explicit open questions.
Need a pathway-prep packet before buying full consulting?
Start with public-source evidence, product definition, product-code clues, similar-device records, and open reviewer questions before committing to a broad engagement.
Reader feedback
Useful pages should feed the next topic choices. Leave a signal or a short comment.