510(k) Submission Failure: The $4 Million Lesson One Diagnostic Team Didn’t See Coming

‍Lessons from a small diagnostic company on where Buy vs DIY decisions go wrong

For small diagnostic companies, the 510(k) pathway definitely looks demanding but manageable, especially when the requirements appear defined and the process looks structured. With the right team in place, it can feel like future problems can be worked through with discipline and time. It’s only later, after a 510(k) submission failure, when teams begin to understand that those future problems needed to be tackled with rigor and immediacy.

One team we spoke with started from that position and they were blunt during the interview. As a small team with a strong scientific foundation, they had some experience in quality assurance, but limited to no experience in regulatory framework and clinical studies. They understood the process would be difficult and expensive, but they believed a diagnostic assay clearance was achievable.

The team expected the effort to take around two years and cost roughly $1–1.5 million. In the end, it ran closer to three years and cost approximately $4 million. It never reached submission.

‍

Where it started to break

The initial approach combined internal execution with targeted outsourcing. Manufacturing was handled externally, and a CRO was brought in early to support regulatory documentation and clinical work. At the same time, the team chose to keep analytical studies in-house, largely to manage costs and because they had the most knowledge about the assay.

While that division of responsibility appears reasonable, it actually introduced gaps that became more visible as the program progressed. And what the team did not understand was that while they were scientifically competent, they had underestimated both the magnitude and complexity of the analytical studies.

As the work advanced, the first signs of strain appeared in clinical assessment. The number of clinical samples required was growing higher than anticipated, driving both cost and timeline expansion. When one of the clinical sites finished but more samples needed to be run, the team had to replace it with a more expensive site, adding further pressure.

“We thought our internal team could handle more of the work.

We were right for QA and wrong for analytical.”

Where cost control created risk

Although the team engaged a CRO early, they limited how that expertise was used. The CRO was responsible for regulatory guidance and clinical execution, while analytical work remained internal and clinical site selections leaned toward lower-cost options.

In both areas, the risks were known but were weighed against cost.

The CRO raised concerns about the internal analytical capability and one of the clinical sites, but the team chose to proceed with the original plan in order to maintain budget control. Those decisions would later haunt them, contributing to rework and delays that far exceeded the savings.

Analytical work had to be repeated after it was determined not to meet required standards, and clinical variability increased. A single poor run at one site led to an additional round of clinical testing, adding approximately $500,000 and extending the timeline by six months.

“The CRO warned us about both our internal analytics team and processes.

Rework and delays are far more costly than doing it right earlier.”

Technical issues and organizational pressure

There were legitimate technical challenges in the program. Issues due to interference began to appear that had not been seen in development. The advanced assay design had higher variability when compared to simpler comparator assays. Limits of detection were more difficult to achieve consistently than expected.

At the same time, organizational factors amplified the impact of those challenges. New hires slowed decision-making and reduced alignment. The company was also managing growth, supporting other development programs, and pursuing funding, so attention was divided and priorities shifted.

The team continued the study which they likely should have stopped, largely due to investor pressure and the difficulty of pausing progress midstream.

“We overestimated our internal capabilities and those of a clinical site.”

The integration problem

Looking back, the issue was not just a single failure point but rather how the development was performed, and the response to new work as changes were made. This resulted in effort misalignment where decisions in one area created downstream consequences in another. Some of these dependencies were understood at the time, but others only became clear after rework was required.

In a process like 510(k), that lack of integration compounds quickly. Quality systems, clinical validation, analytical performance, and regulatory strategy need to move together, and if one area falls out of sync, the entire program absorbs the impact. The gate reviews are there for a reason: they keep efforts moving in parallel.

“Having clinical, regulatory, and quality working together is essential.

The program only progresses if all of these are coordinated.”

What could have prevented the 510(k) submission failure?

In hindsight, the team was clear about what they would do differently. They would spend more time in development to ensure the assay was robust under conditions aligned with FDA expectations. They would also not have overestimated their internal capabilities. Strong research and development skills do not transfer automatically to regulatory product development if you don’t have the experience.

They know now. Had they brought in external expertise earlier, it would have had broader authority across the program.

“DIY or Buy?

Buy. No question about it.”

That decision is not only about adding capacity, but about bringing in experience and ensuring that clinical, regulatory, and analytical work are integrated from the beginning.

The cost of that support can feel high early on, but the cost of delays, rework, and late-stage failure can be much higher.

“A 510(k) that fails late costs far more than an expensive 510(k).”

For small teams, this tradeoff is easy to underestimate because the process appears linear when viewed from the outside. In practice, success depends on how well the underlying work is aligned before submission.

For companies navigating that decision, working with an experienced CRO such as Arete Biosciences can help establish a clear assessment of readiness and risk before significant time and capital are committed.

‍

Our perspective

In early-stage IVD companies, it is not uncommon for clinical validation programs to be managed without dedicated clinical or regulatory leadership. Founding teams are often highly technical and focused on product development, with clinical and regulatory responsibilities layered onto existing roles as the program progresses.

However, as programs move into clinical validation and toward submission, the absence of a dedicated clinical and regulatory perspective can begin shaping decisions.

In our view, many of the challenges that emerged for this team were not driven by a lack of effort or capability, but by the absence of continuous clinical and regulatory input as the study evolved. Decisions around workflow, study design assumptions, and operational feasibility were made in good faith, but without the benefit of integrated oversight across those domains.

As a CRO, our role is to provide that perspective and to identify areas where adjustments can maintain alignment between study execution and the eventual submission strategy. This can include workflow, study design, and how emerging data should be interpreted as the program progresses.

In organizations where clinical and regulatory expertise is not embedded within the core team, external support becomes less about additional bandwidth and more about providing a structured, integrated view across the program. A team that brings together clinical, regulatory, operational, and data perspectives can help identify risks earlier, connect decisions across functions, and ensure that the study remains aligned with its intended submission path.

For early-stage companies, this is not about replacing internal strengths. It is about recognizing when a program has reached a level of complexity where additional perspective and structure can materially influence the outcome.

In the end, the submission itself is not the hardest part. Getting the data, systems, and execution aligned before you get there is.

‍

Thinking about a 510(k)? Let's chat.

‍