Assay Development Is Not a Line Item

In a CRO statement of work, “assay development” can look deceptively simple.

It may appear as one line in the quote:

Functional assay development.
Estimated timeline: 4–6 weeks.
Estimated cost: $X.

For a founder, that line can feel reassuring. The assay has been named. It has a budget. It has a timeline. It has a place in the SOW. The program feels like it is moving forward.

But assay development is often one of the most uncertain parts of an early discovery or preclinical program. It should not be treated as a black-box line item.

Before signing the SOW, founders should ask a simple question:

What exactly does “assay development” include?

One phrase, many possible meanings

“Assay development” does not mean the same thing in every quote.

In one SOW, it may include a thoughtful staged effort: benchmark testing, multiple pilot runs, several assay conditions, interim data review, and defined criteria for moving into test article screening.

In another SOW, it may mean a limited feasibility attempt under one or two starting conditions.

Both may appear under the same phrase.

That difference matters.

For many early discovery and preclinical programs, especially functional assays, the challenge is not just technical execution. The biology itself may be uncertain. The assay window may be weak. The positive control may not behave as expected. Primary cells may vary by donor. The cell line may express too little target. The timing may be wrong. The readout may detect activity, but not support ranking.

The CRO may be capable. The scientists may be experienced. But no team can guarantee that a new assay system will become decision-grade within a loosely defined scope.

That is why the line item needs texture.

Ask for itemization

Founders do not need to turn every SOW into a full protocol. At the precontract stage, some details will naturally remain flexible.

But the assay development scope should still be clear enough that both sides understand what is being attempted.

Ask the CRO to itemize the line.

For example:

How many pilot runs are included?

How many plates per run?

How many donors, cell lots, or cell lines will be tested?

How many assay conditions are covered?

Are benchmark molecules included?

Are positive and negative controls included?

Will the CRO test multiple time points?

Will dose-response curves be included, or only single-concentration testing?

Will different readouts be compared?

Will there be an interim data review before the next run?

What happens if the first pilot does not show a usable assay window?

What work would require a change order?

These are practical questions. They are not micromanagement.

You are not asking the CRO to promise that the assay will work. You are asking what development effort is actually covered by the quoted scope.

That distinction is important.

Define what “ready” means

Another important question is:

What does it mean for the assay to be ready for test article testing?

This should not be left vague.

For some assays, “ready” may mean the benchmark shows a clean dose response, the positive and negative controls separate well, and the assay window is strong enough to support molecule ranking.

For others, “ready” may mean the CRO has demonstrated a measurable signal, but the assay still has limitations.

Those are very different levels of readiness.

If the assay is intended to support final lead selection, the bar should be higher. A weak but detectable signal may be scientifically interesting, but not necessarily decision-grade. An assay may technically “work” and still be too variable, too narrow, or too poorly controlled to rank molecules with confidence.

Founders should ask before signing:

What is the expected assay window?

What control performance would be considered acceptable?

What level of variability is tolerable?

What would make the CRO recommend moving forward to TA testing?

What would make the CRO recommend further optimization?

What would make the CRO say this assay system is not suitable for the intended decision?

The goal is not to over-define every detail before the work begins. The goal is to agree on the decision logic.

Decide what happens if the assay window does not appear

This is where many timelines slip.

The SOW includes assay development. The CRO runs the pilot. The assay window is weak. The team tries another condition. Then another. Then a new control is discussed. Then another donor or cell line is needed. Then the founder receives a change order.

Sometimes this is unavoidable. Biology does not always cooperate.

But founders should not discover the boundary of the original scope only after the assay starts failing.

Before signing, ask:

If no usable assay window is observed after the included runs, what happens next?

Will the CRO provide a recommendation?

Will there be a data review meeting?

Will additional optimization require a change order?

Could an alternative assay format be proposed?

At what point should the team stop optimizing and reconsider the approach?

This matters because the risk is not only financial. The larger risk is often time.

A few extra pilot runs can consume weeks. A change order may need review and approval. Additional reagents may need to be sourced. A new benchmark may need to be generated. Meanwhile, lead selection waits.

In early programs, time lost to ambiguous assay development can be more damaging than the extra cost.

Make the black box visible

A CRO may have excellent scientists and still provide a quote where “assay development” is summarized too broadly. That is common. Quotes and SOWs are often written for contracting and operations, not as full scientific decision documents.

The founder’s job is to close that gap before signing.

Ask what is included.

Ask what is not included.

Ask what success means.

Ask what partial success means.

Ask what triggers a change order.

Ask when the team will stop, rethink, or redirect.

This does not make assay development rigid. It makes it transparent.

“Assay development” is not a magic phrase. It is a scoped scientific effort with assumptions, limits, and decision points.

Before you sign the SOW, make sure you know what is inside that line.