FOR CROs
The same validated method, every client, in one click.
A CRO runs a dozen sponsors’ qPCR methods at once, each to its own spec. Validate a client’s method once, then run it the same way for every one of their samples, everything except the cycler, so when a sponsor asks how a number was produced you reopen it, not redo it.
When a sponsor questions a number
You have to show how you got it, or the account walks.
You reconstruct a questioned number, get a different one, and the sponsor doubts every result you sent.
Across a dozen contracts, one client’s genes or criteria hit another’s samples, and a wrong-spec number ships.
The Excel, R, Prism and geNorm relay, plus manual report assembly, runs per client and drifts.
Re-selecting samples, assays, mix and protocol by hand every run, across a dozen concurrent client projects.
One method every run, so you can always show how you got it.
Each client’s method is pinned to that client’s own runs, so one sponsor’s spec never lands on another’s samples.
Validate a client-ready method once, geNorm-scored reference genes you choose, saved as a preset.
One click starts every client run from the preset, the mix and protocol frozen to the exact reaction.
The same method every run, so re-running the analysis gives the number you delivered, not a different one.
When a sponsor asks how you got it, the exact analysis reopens with its data and methods, a lookup, not a re-run.
Sponsor confidentiality
One sponsor’s data never touches another’s, even when they compete.
Each client or project works in its own workspace, and workspace membership is the only way into a project’s experiments, samples, assays and results. That holds inside your own CRO account, and it holds for the account owner: no membership, no read across projects.
So you can serve competing sponsors on one account and still run one validated method for every one of them. The only things shared across the account are the billing pool and the system catalogs of instrument types and standard protocols. Never a client’s work.
Data is encrypted in transit and at rest and hosted in the EU. When a sponsor’s CDA or your own security review wants the detail, we will walk them through exactly how the isolation works.
The D-DEAR method
Validate once, run every client in one click.
One continuous workflow, from the sponsor’s spec through the report, so every client run reproduces the method you validated.
That’s D-DEAR: Define, Design, Execute, Analyze, Report. Everything except the cycler.
A new sponsor arrives with its own SOP, reference genes and acceptance criteria and says run our assay, our way. You encode that spec once so every run for that client is measured against it.
Because the spec lives with the method, months later you can see which version of it produced any deliverable, instead of reconstructing the intent from a lab notebook.
Author what a good run for this client starts from: validated assays with their acceptance criteria, a reference-gene panel scored with geNorm where you choose which genes to keep, and the mix and protocol, saved as a preset. The CRO authors the preset from the sponsor’s spec.
Each client gets its own preset carrying its own parameters, so run-to-run difference is the biology, not which analyst set the run up, and one sponsor’s method never bleeds into another’s.
Because the design is recorded, the reference-gene choices, controls and acceptance criteria stay visible into every analysis and every deliverable, instead of living in one scientist’s spreadsheet.
Instead of re-selecting samples, assays, mix and protocol by hand for every client run, you start from the client’s preset and land in Design fully populated. The imported Cq is never overwritten.
The mix and cycling protocol are frozen at instantiation, so a run started today reproduces the reaction you validated, even if you later revise the client’s method for a new version.
Clarida guides and records here, it does not pipette or drive the cycler: everything except the cycler.
Bring raw amplification curves and Clarida can call Cq itself, with more than one established method to choose from, or start from the Cq values the instrument produced. Your imported Cq is never overwritten, whichever cycler the client’s job ran on.
From there: reference-gene stability scored with geNorm so you keep a stable panel for that client’s sample type, efficiency-corrected quantification (relative NRQ or standard-curve absolute), per-metric QC that surfaces outliers instead of dropping them, and inter-run calibration across plates.
So the deliverable is the same whether scientist A or B ran it, this batch or last month’s: the difference between two runs is the biology, not which analyst ran which spreadsheet.
When a sponsor challenges a number, the exact analysis reopens: the method, the settings and the data behind every value, as it was for that run’s version of the method, already on the record.
The report comes straight out of the recorded analysis instead of hand-assembled from a spreadsheet, so there is one less place for a per-client slip to creep in.
The record carries its own data inside it, so it still works months later: it opens and re-analyses without Clarida, a database, or the software that made it. A number you cannot reconstruct costs the account, so this is the tie-breaker that keeps it.
Why switch
One recorded method, instead of a relay run once per client.
Right now every client run is set up from scratch, and the analysis is a relay, times every client. One scientist re-selects the layout, reference genes and controls, exports to Excel, runs a delta-delta-Cq calculation in an R or Python script, sends reference genes through a separate geNorm or GenEx detour, builds the figure in GraphPad Prism, and assembles the report by hand. Every handoff is a place for method to slip in, and it slips in differently per client and per run.
Clarida does not replace your cycler or your client’s LIMS. It is the one recorded method around the run: validate it once, start every client run from the preset in one click, apply the same efficiency correction, geNorm-scored reference-gene normalization, QC and inter-run calibration every run, and reopen the exact analysis when a sponsor asks. One consistent method in place of a relay that drifts, so every deliverable reproduces what you validated.
Today, times every client
Exported, reformatted, and pasted between apps that never talk.
With Clarida
- Definethe sponsor’s spec
- Designvalidate the method once
- Executeone click per client run
- Analyzesame method, every run
- Reportreopen on challenge
One record, from the question you framed to the figure you publish.
Every client run, the same method
One validated preset per client, started in one click, so the deliverable is the same whichever scientist ran it and whichever cycler the job used.
Reopen instead of re-run
When a sponsor challenges a number, the exact analysis reopens with its data and methods, so you reconstruct how it was produced instead of redoing it and risking a different answer.
Each client walled off from the rest
Each project is isolated by workspace membership, so one sponsor’s data never touches another’s, even inside your own CRO account.
From the source
Trust the analysis, because they wrote it.
Clarida comes from the team behind geNorm, qbase+ and the MIQE guidelines the field reports to. The methods you rely on stay in the hands that defined them, now maintained and moved to the cloud.
28,000+
citations of the geNorm and qBase methods
Since 2007
building qPCR analysis software
MIQE
the reporting standard, co-authored by the team
For the lab that runs it at volume
One validated method, run for every client at volume.
Author once, run at volume
Your team validates a client’s method once and every run for that client starts from it in one click, so a fixed team serves more concurrent projects and the setup tax stops eating billable time.
Reopen the analysis, do not re-run it
When a sponsor challenges a result, the exact analysis reopens with its data and methods on the record. A number you cannot reconstruct costs the account, not one report.
Every client walled off from the rest
Each project is isolated by workspace membership, so you can serve competing sponsors on one account with no sponsor’s data ever touching another’s. The confidence a CDA needs.
The report comes out of the analysis
The client-ready report is produced straight from the recorded analysis instead of hand-assembled from a spreadsheet, so the biggest per-client rework leak closes.
The method outlives the people
The validated method lives in the preset and the workspace, not a departing analyst’s laptop, so a new hire runs it from day one and the client’s work does not walk out the door.
Ready to run every client off one method?
One account, each client isolated in its own workspace, credits that scale with your project volume. Book a call and we will shape the deployment and the pricing around the sponsors you run.
Talk volumeQuestions, answered
No. Each client or project works in its own workspace, and access is gated by workspace membership, nothing else. One project never sees another’s experiments or results, even inside the same CRO account, and even the account owner has no read across projects.
The same rule holds for competing sponsors you both serve: without membership there is no path to a project’s data. The only things shared across the account are the billing pool and the system catalogs of instrument types and standard protocols. Never a client’s work.
Data is encrypted in transit and at rest and hosted in the EU.
Yes, it is yours, and you can export it whenever you want. Nothing is locked to us.
Every report is self-contained: it carries its own data and methods, and it reopens and re-analyses without Clarida, a database, or the software that made it, so what you deliver stays usable on its own.
For a deployment of the right size, dedicated infrastructure, and running Clarida inside your own cloud tenancy, is on the table, arranged on request and shaped around your contracts.
The shared platform already isolates every project by membership and hosts data encrypted in the EU, so many CROs start there and move to a dedicated environment only if a sponsor’s review requires it. Bring those requirements to the call.
No, and we will not pretend otherwise. Clarida is a research-use analysis platform, built for research-use qPCR service work, not a validated GxP / GLP / 21 CFR Part 11 system.
The record it produces is defensible to scientific and client scrutiny, because it reopens with its data and methods. If a contract is genuinely regulated, that is a different lane, and we will say so plainly rather than overclaim.
Clarida is instrument-agnostic and reads qPCR and RT-qPCR data from the major platforms, whichever cyclers a given client’s job ran on. Start from the Cq values an instrument called, or bring the raw amplification curves and let Clarida call Cq itself, using single-threshold, SDM or LinRegPCR. Your imported Cq is never overwritten.
So Clarida is the one consistent analysis and report layer downstream of whatever instrument the job used, and it also reads qbase+ files, so legacy analyses come across rather than start from zero.
Reference-gene stability is scored with geNorm so you keep a stable panel for a given client, or use global-mean normalization. Quantification is efficiency-corrected, relative results come back as a geometric-mean fold-change with confidence intervals and Benjamini-Hochberg across genes, and absolute quantification runs off a standard curve. The tests are the ones qPCR papers use: t-tests, Wilcoxon, Mann-Whitney, one-way ANOVA and Pearson or Spearman.
This is method consistency, not a promise of the same answer: different inputs give different results, the method applied to them is the constant, and every step is recorded so you can reopen the exact analysis months later. Nothing is a black box.
The report comes straight out of the recorded analysis, with the numbers, methods and QC each client’s method produced, so you deliver from the analysis instead of re-keying it into a spreadsheet.
Matching a sponsor’s exact house format stays your call. Bring your reporting needs to the call and we will show you what comes out of the box.
A CRO runs as one account and one budget, with credits that scale as your project volume grows, and each client isolated in its own workspace.
The specifics are a short conversation shaped around how many clients you run, not a fixed tier you have to fit into. We can start with a guided pilot on one client so you see it on real work first.
Analysis today is qPCR and RT-qPCR, read from the major platforms. dPCR support is on the roadmap.
If you run dPCR alongside qPCR for a client, raise it on the call and we will be straight with you on timing.
Validate once. Run every client in one click.
Start with a guided pilot on one client, then a price shaped around your book.