Device status & classification
Assessment of intended use, medical purpose, product code, device classification, submission route and the boundaries of the regulated device.
FDA Regulatory Consulting
We help SaMD, SiMD and AI-enabled device teams determine the right US pathway, resolve the important questions early and prepare a submission in which the claims, risks, software and evidence tell one consistent story.
Selected clients
Healthcare teams we have supported


















Scope and deliverables
We can lead the complete regulatory workstream or provide specialist software and AI support to an established regulatory team.
Assessment of intended use, medical purpose, product code, device classification, submission route and the boundaries of the regulated device.
Predicate landscape, substantial-equivalence analysis, De Novo considerations and a clear rationale for the recommended pathway.
Focused questions, background package, meeting preparation and support interpreting FDA feedback before expensive evidence is generated.
eSTAR assembly, device description, indications, labeling inputs, substantial equivalence or benefit-risk rationale, and evidence integration.
FDA software documentation, risk management, verification and validation, cybersecurity, AI/ML evidence and predetermined change-control strategy.
Structured response strategy, gap closure and clear technical answers during interactive review, Requests for Additional Information or hold situations.
Ways to work together
We lead strategy, coordinate evidence, draft the software-heavy submission sections and support communication through FDA review.
We work alongside your regulatory lead on software, cybersecurity, AI/ML, predicate or evidence questions that need deeper technical input.
A second-opinion review of the pathway, eSTAR package or software documentation before submission or a formal response.
How it works
Review intended use, claims, architecture, current evidence, predicates, risks and commercial priorities.
Choose the pathway and use a Pre-Sub when FDA input is needed before committing to the evidence plan.
Close documentation gaps and assemble a submission whose technical sections support the same regulatory argument.
Manage review questions, coordinate technical inputs and maintain a controlled response record through the decision.
Regulations, standards and guidance considered
Frequently asked questions
That depends on its intended use, users, outputs and the consequences of relying on those outputs. We assess the product against the device definition and relevant exclusions, then document the reasoning and likely classification rather than relying on a feature checklist.
A Pre-Sub is most valuable when FDA feedback could change an expensive decision: the predicate strategy, clinical study, performance endpoints, cybersecurity approach, AI/ML change protocol or the proposed regulatory pathway. It should contain focused questions and enough background for FDA to answer them.
A 510(k) generally demonstrates substantial equivalence to a legally marketed predicate. De Novo is available for certain novel low-to-moderate-risk devices without a suitable predicate and establishes a new classification regulation and special controls. The right route depends on the intended use, technology and predicate landscape.
Yes. We can work with your internal team or another lead consultant and own defined sections such as software documentation, cybersecurity, risk management, V&V, AI/ML evidence or technical responses. Roles, interfaces and review responsibility are agreed at the start.
FDA controls the regulatory decision, so no consultant can promise an unconditional outcome. We can commit to defined deliverables, review standards and timelines within our control after assessing the product, evidence and pathway.
Yes. We can support the technical and regulatory submission work for non-US manufacturers. Separate US Agent, establishment registration, device listing and importer requirements may apply depending on the commercial arrangement and stage of market entry.
Related expertise
Remediate or build the software and lifecycle evidence needed to support the regulatory strategy.
Prepare the cybersecurity architecture, risk and testing evidence for the submission.
Turn pathway uncertainty into a filed FDA Q-Submission package and evidence roadmap.
Start with the product you have