

When regulatory strategy starts after prototyping, things don’t just slow down—they break. And once they break, they are expensive to fix.
Medical device development is not linear. FDA expectations are woven into design, testing, and evidence generation. When those expectations are ignored early, downstream failures stack up fast.
What Actually Goes Wrong (and Why It Hurts)
1. Studies That FDA Will Not Accept
Late regulatory involvement often means studies are designed without FDA logic in mind. Common problems include:
Wrong test models
Missing controls
Non-relevant endpoints
Poor linkage to intended use
The result? Data that looks impressive internally but is regulatorily unusable.
Impact:
Repeating bench or animal studies can cost $250,000–$1M+
Adds 6–12 months to development timelines
FDA does not approve effort. They approve evidence.
2. Wrong Endpoints, Wrong Conclusions
If intended use and risk classification were not nailed down early, teams often measure the wrong things:
Performance endpoints that don’t support safety claims
Bench tests that don’t map to clinical risk
Human factors studies done on the wrong user population
When endpoints don’t align with FDA expectations, even “positive” results can be meaningless.
Impact:
Entire studies may need to be redesigned
Lost investor confidence when timelines slip
Delays to first-in-human or submission milestones
3. Data That Cannot Be Traced or Defended
FDA expects traceability:
Risks → design inputs → verification → validation
Evidence tied directly to hazard mitigation
When regulatory planning is late, documentation gaps appear:
No clear rationale for why tests were selected
Weak linkage between risks and evidence
Incomplete design history files
This turns FDA review into a prolonged back-and-forth instead of a clean submission.
Impact:
Multiple FDA information requests
Longer review cycles
Higher likelihood of refusal-to-accept (RTA)
4. Forced Regulatory Pathway Changes
This is the most painful failure.
Late discovery that:
Your device is higher risk than assumed
A 510(k) is not viable
De Novo or PMA is required instead
At this point, the problem is not regulatory—it’s strategic.
Impact:
12–24 months of additional development
Millions in unplanned spend
Potential need to redesign the device entirely
This is how promising startups quietly die.
The Cost of Starting Too Late (Reality Check)
Across the industry, late regulatory strategy commonly results in:
30–50% cost overruns
1–2 years of avoidable delays
Repeated testing with no added value
Lost first-mover advantage
And no—“we’ll fix it in regulatory later” has never saved a program.
Where Kandih Comes In
This is exactly what Kandih Group exists to prevent.
Kandih works upstream—before rework is needed—to:
Align development plans with U.S. Food and Drug Administration expectations from the start
Define the right regulatory pathway early
Ensure studies are designed with FDA-acceptable endpoints
Build evidence strategies that are defensible, traceable, and submission-ready
Eliminate redundant testing and wasted spend
Instead of cleaning up mistakes, we help you avoid making them.
Bottom Line
Late regulatory strategy doesn’t just slow you down.
It creates invalid data, forces redesigns, and drains capital.
The fastest path to market is not skipping regulatory strategy—it’s aligning with FDA logic early and building once.
That’s how Kandih keeps development efficient, credible, and fundable.
References
FDA – Design Controls for Medical Devices
https://www.fda.gov/regulatory-information/search-fda-guidance-documents/design-controls-medical-devices
FDA – Refuse to Accept Policy for 510(k)s
https://www.fda.gov/regulatory-information/search-fda-guidance-documents/refuse-accept-policy-510ks
FDA – Benefit-Risk Factors to Consider for Medical Devices
https://www.fda.gov/regulatory-information/search-fda-guidance-documents/factors-consider-when-making-benefit-risk-determinations-medical-device
FDA – ISO 14971: Risk Management for Medical Devices
https://www.fda.gov/medical-devices/standards-and-conformity-assessment-program/recognized-consensus-standards
