Commissioning custom elisa assay development without buying a protocol you cannot defend: why assay development begins with the decision the result has to support rather than with a pair of antibodies, what custom assays and custom assay development should deliver as a package, where elisa assay development runs aground on matrix interference rather than on sensitivity, how the reagent pair, the standard and the matrix together set the floor, and what validation evidence has to accompany an assay before anyone downstream is entitled to rely on a number it produces

Scoping the development

1. State the decision and the required precision. What will change depending on the number, and how small a difference must be detectable for that decision to be made? Those two answers set the required range and precision, and they often reveal that a simpler or a more sensitive format is needed than was assumed.
2. Define the matrix before the reagents. Serum, plasma, lysate, culture supernatant and process intermediate each interfere differently, and an assay developed in buffer will meet none of those challenges. Supply real samples, including the difficult ones, at the start of development rather than at the end.
3. Screen reagent pairs rather than choosing one. Capture and detection reagents that each work alone frequently fail together because they compete for the same epitope. Pair screening is a real experiment with a real cost, and a development plan without it is gambling on a first choice.
4. Fix the standard and its traceability early. The number the assay produces is relative to its standard. Recombinant material, a pooled natural sample and an international reference each give different absolute values. Choose one, document its source and lot, and plan how it will be replaced when it runs out.
5. Establish the validation package the use requires. Accuracy, precision within and between runs, selectivity, dilutional linearity, stability under the intended storage and handling, and a stated range. Regulated uses add more. Agreeing the package before development starts prevents an assay that works but cannot be signed off.
6. Plan the transfer while the developer is still available. A written method, a reagent list with lots, the standard curve model and acceptance criteria, plus a demonstration in the receiving laboratory's hands. Transfers arranged after the project closes tend not to happen.

The reagent pair is the assay

Format, plate chemistry and detection technology are largely interchangeable. What is not interchangeable is the pair of binders and where they sit on the target, because that determines sensitivity, specificity and whether the assay detects the form of the analyte you care about rather than a fragment or a complexed version of it.

Ask a development partner how many pairs they will screen and what they will do if none works. The answer to the second question separates a development project from an assembly job.

What the standard commits you to

Every result is a comparison to the standard, so the standard defines the units. Changing standard material later shifts every historical value, which makes trend data across the change uninterpretable unless a bridging study is run.

Choose material with a supply route, record the lot, and plan the bridge before the first lot is exhausted. This is one of the most predictable sources of pain in long running assays and one of the easiest to avoid.

Knowing when to buy a kit instead

If a validated commercial assay exists for the analyte in your matrix with adequate range and precision, buying it is almost always cheaper and faster than developing one, and it comes with a supply chain and a manufacturer's validation.

Custom development earns its cost when no kit covers the analyte, when the matrix defeats the available kits, when the required range is outside what is sold, or when the assay must be owned and transferable rather than dependent on one supplier's catalogue.

Common questions

Why does an assay that works in buffer fail in serum?

Matrix components bind reagents, alter the background and shift the curve. It is the single most common failure mode, and it is why real samples belong in development from the first screening rather than in a validation at the end.

What should a development package contain at handover?

The written method, the reagent identities and lots, the standard and its provenance, the curve fitting model, the acceptance criteria, and the raw data behind every validation claim. A report summarising results without the underlying data is not transferable.

Is a multiplex format worth the added complexity?

When several analytes genuinely inform one decision and sample volume is limited, yes. When one analyte matters, multiplexing adds cross reactivity and calibration problems for no benefit and makes troubleshooting considerably harder.

How long does a custom development take?

Longer than most plans, because reagent pair screening and matrix work are iterative. Compressed schedules usually compress validation, which is precisely the part that determines whether the assay can be used for anything important.

Browse by service class

• Compare Gene synthesis on advertised prices