FDA De Novo Fee Calculator: model your full program budget before you hire support

Most De Novo teams underestimate cost risk because they budget only the submission fee and a draft-writing line item. Real cost drivers are usually evidence generation, iteration after FDA feedback, and coordination overhead across labs, consultants, and internal functions. This calculator helps you convert pathway uncertainty into a working budget range you can defend to leadership.

How this calculator should be used

This is not a promise of FDA outcomes. It is a planning instrument for scenario analysis. You should run at least three scenarios: a lean base case, a likely case, and a stressed case where additional evidence or iterative clarifications are required. Teams that run only one number usually fail to reserve enough runway for first-cycle surprises.

The tool intentionally separates user fee, evidence spend, external support, and internal labor. Keeping these buckets separate gives you better control over contract structure and milestone release decisions. For example, if evidence spend is high but strategy uncertainty is low, you can prioritize fixed-scope laboratory contracts while keeping strategic consulting light. If strategy uncertainty is high, you may invest more in pre-submission planning and risk reduction before committing expensive studies.

Why budget modeling is a De Novo critical path item

In De Novo submissions, cost is tightly connected to evidence logic. If your intended use and labeling claims are broad, evidence requirements can expand quickly. If your risk controls are not mature, design updates can trigger repeat testing. If your study endpoints are weakly aligned to decision questions, you may have to generate additional analyses under time pressure. None of this is unusual, but it becomes expensive when budget assumptions are not explicit from the start.

Strong teams treat budget modeling as a governance artifact. The model is reviewed with regulatory, quality, engineering, clinical, and finance stakeholders every month. Each change in claims, indications, or architecture updates the budget model, not just the Gantt chart. This practice makes scope decisions concrete: leaders can see exactly what a claim expansion or protocol change costs before approving it.

Budget discipline also helps vendor management. When you know your evidence envelope and risk exposure, you can negotiate deliverables instead of buying generic support time. That usually improves both quality and timeline reliability.

Interpreting each line item

1) FDA user fee

Use the currently published FDA medical device user fee schedule for De Novo submissions and apply the right business-size category if eligible. Teams often miss this detail in early estimates and then need emergency approval when invoicing starts. Keep this value explicit in every board or executive update to avoid confusion between agency fees and service fees.

2) Non-clinical testing

This bucket can include bench testing, software verification and validation, cybersecurity assessments, biocompatibility, sterilization validation, electrical safety, EMC, packaging integrity, shelf life, and human factors activities depending on product profile. Treat this as the largest volatility source for many hardware and software-enabled products. Changes in architecture or claims frequently cascade into this bucket.

3) Clinical evidence

Not every De Novo submission requires a large prospective study, but many require at least some form of clinical evidence strategy, literature justification, real-world data handling, usability evidence, or post-market rationale. Build this line item with protocol, site, monitoring, statistics, and data-management assumptions visible. Hidden assumptions here create avoidable variance later.

4) Regulatory/writing support

This includes strategic advisory, submission assembly, quality review, deficiency response support, and cross-functional integration. Be cautious with contracts that appear inexpensive but exclude core authorship and review cycles. Cheaper proposals can become expensive when change orders are triggered by normal project iteration.

5) Internal labor

Internal cost is real even if not invoiced externally. Regulatory leads, quality engineers, clinical leads, software leads, and program managers spend significant effort on alignment, review, and response handling. If you do not budget internal time, your timeline often slips when competing priorities collide.

Scenario design: base, likely, stressed

Use a base case only for directional planning. Your likely case should include moderate iteration and one evidence adjustment. Your stressed case should include an expanded clarification cycle and incremental evidence scope. A practical rule is to increase contingency as uncertainty rises instead of forcing unrealistic precision too early. The point is decision quality, not perfect forecasting.

For governance meetings, keep one-page summaries for each scenario that show top assumptions, top risks, and trigger points for re-baselining. Trigger points could be protocol revision requests, architecture changes, labeling expansion, or external dependency delays. When trigger points are predefined, teams react faster and with less organizational friction.

How to use this model when comparing providers

Provider proposals should map directly to your budget model. Ask each vendor to show exactly which assumptions they are using for evidence scope, review cycles, and deficiency support. If a proposal omits those assumptions, you cannot compare offers fairly. Normalize proposals by mapping them to the same scenario assumptions, then compare value per deliverable rather than total quote alone.

If one vendor appears much cheaper, inspect exclusions first: is deficiency response billed separately, are technical sections outsourced, are review loops capped, and are PM hours counted? Price gaps often reflect scope gaps rather than efficiency differences.

To accelerate this process, pair this page with the directory workflow: Compare +50 FDA De Novo providers. Use the same scoring rubric for all finalists.

Common budget mistakes and fixes

• Mistake: treating user fee as the dominant cost. Fix: model evidence and iteration costs first, then add fee.
• Mistake: no contingency. Fix: include 10-25% based on uncertainty profile.
• Mistake: mixing capital and operating assumptions. Fix: separate one-time tooling from submission program spend.
• Mistake: ignoring internal labor opportunity cost. Fix: include burdened internal labor.
• Mistake: awarding vendor contract on lowest quote. Fix: award on risk-adjusted value and deliverable clarity.

Operating model recommendations by company stage

Early-stage teams usually benefit from concentrated strategic support early, then reduced external dependence once evidence pathways are clear. Mid-stage teams with a mature quality function often achieve better economics with selective specialist support and stronger internal authorship. Large organizations should prioritize governance consistency across functions and avoid fragmented vendor ownership that increases integration costs.

Regardless of stage, decision rights should be explicit. One accountable owner must control indications, claim language, and evidence alignment. Diffused ownership creates expensive reversals.

FAQ

Is this calculator a replacement for formal project finance?

No. It is a practical pre-finance tool to align regulatory and operational assumptions before detailed procurement and formal forecasting.

How often should we update the model?

At minimum monthly, and immediately after any major change in indication scope, testing strategy, study design, or architecture.

Should we include potential post-market obligations?

For submission budgeting, keep post-market activities separated but visible. Do not hide post-market work in submission assumptions.

What contingency level is reasonable?

Many teams start at 15% for likely-case planning and move to 20-25% in higher-uncertainty contexts. The correct level depends on device novelty and evidence volatility.

Decision framework for executive review

A useful executive package includes three scenario budgets, key assumptions, confidence score per assumption, and mitigation actions. Tie each major cost driver to a responsible owner and a review cadence. This turns the De Novo budget from a static spreadsheet into an active control mechanism.

When leaders ask for one number, provide the likely-case number plus a range with explicit uncertainty sources. This is more credible and prevents overconfidence. It also helps cross-functional teams align on where to spend effort to shrink uncertainty.

If your organization is comparing consulting partners now, run this calculator before calls and bring the outputs into each discussion. It immediately improves question quality and exposes whether a vendor can think in integrated program terms.

Citations

• FDA: Medical Device User Fee Amendments (MDUFA)
• FDA: De Novo Classification Request
• 21 CFR Part 860
• FDA: Q-Submission Program Guidance