Skip to content

Partners

How does your product perform in labs you never see?

How your kit, master mix or instrument holds up across labs. Each product raises its own questions, so a pilot sets out with you what the view would show.

On this page

What a field view would show you

You validated your product on a handful of units. Then it shipped to labs you cannot see into.

A field view would close that gap: a picture of how your product holds up in those labs. Each product raises its own questions, so the view is built with its maker in a pilot, starting from one of them.

What a pilot would look at:

  • Reproducibility across the field. How tightly your product would reproduce across labs and instruments, on one scale, beside the one-off study you ran.
  • Drift, while it is a signal. A batch or condition starting to read differently would show before it turns into complaints. Clarida does not record lot numbers today.
  • The slow drift a single run never shows. A no-template control returning earlier Cqs across months would be carryover contamination emerging, seen while it is still a warning.
  • What to build next. Where your product would fall short in practice: the weakest assay in a panel, the limit of detection labs reach, the instrument it would underperform on.

A lot reading a full Cq late would show across the field at once, not one support ticket at a time. A problem confined to one lot points to manufacturing rather than handling.

Validation answers one question, on one day, for one set of units. Your product keeps meeting new ones: a new lot, an instrument it has never run on, new hands at the bench. A field view would keep looking as those shift.

What it would look at, by product

Kits. The analysis your customers run from your kit's preset is what a view of your kit would draw on. For runs imported with their curves, Clarida calls Cq itself, with the baseline your kit's settings set, so each instrument's own Cq algorithm stops being a variable. What kit makers get.

Master mixes. A mix is one part of someone else's experiment, so a raw number on its own is confounded by the assay, the sample and the instrument. A view would compare across what it runs with: probe chemistries against SYBR Green, one instrument class next to another. What master mix makers get.

Instruments. Once your instrument leaves the building, you see it through service calls and returns. For runs imported with their raw curves, Clarida calls Cq the same way every time, so a real optical or thermal difference between units could show through the software. What instrument makers get.

A drift that tracks a model or a firmware revision would point back to the hardware, yours to fix. One that scatters across labs would suggest handling, the customer's to address.

Frequently asked questions

What would you see from your customers' runs?

Nothing, today: no maker receives statistics from labs' runs. What a field view would show, and on what terms, is set down in a pilot before the first statistic.

What can it tell you, and what can't it?

It would tell you how closely replicates agree within each experiment: precision inside one run, in many labs. It would not tell you how runs, labs or months compare, because each lab runs its own samples and assays. That needs one control, from you, run the same way everywhere, and a pilot can set one up.

It would not tell you about accuracy, how close a result sits to the true quantity, because the samples labs run are uncontrolled and unknown. Any "how much" question needs a known standard or control, which field data on its own does not carry.

Can you see how your product compares to other manufacturers'?

No. A pilot looks at your own product only.

Is this a validated IVD analysis pipeline?

No. Clarida is for research use. A field view would not be a validated IVD pipeline, and not part of any product's regulatory clearance.

Does this work with your product?

Clarida reads run files from CFX, LightCycler 480, QuantStudio, Rotor-Gene or RDML, with their amplification curves, and a Cq table from any instrument. SYBR Green and probe chemistries come in, singleplex and multiplex. Clarida does not analyze dPCR. If your product writes a format Clarida does not read yet, bring a file to the call.

How would a pilot set it up?

It is a build we take on together, not a self-serve dashboard and not a trial you sign up for and set aside. A pilot starts from the question you care about most, and works out which statistics would answer it and how many runs a first view needs.

What can you publish from a pilot?

Nothing yet: there is no field data on your product. What a pilot produces, and what you may publish, is agreed before it starts.

Updated

Pick the first question you want the field to answer.

Bring it with you, and the pilot is scoped around it. A founder answers within a working day, and the scope and terms are agreed before a pilot starts.

More for partners

All partner pages
  • Kit makers

    Your customers pick your kit and import their run. The analysis starts from your targets, controls, call cutoffs and settings.

  • Master mix makers

    Your mix becomes a preset with its cycling protocol and analysis settings, and each experiment on it starts from them, on the lab’s own instrument.

  • Instrument makers

    If Clarida reads your cycler’s run files, it calls Cq from the curves and takes the run to normalized, QC-checked results.