Clinical research technology and CRO services

Why sponsors choose ValidTrials.

Your clinical study deserves more than disconnected software and fragmented service providers. ValidTrials combines clinical research infrastructure with professional study services, so a sponsor can move from scientific planning to controlled data, statistical analysis and research documentation with one accountable partner. A platform license and a CRO contract are not the same purchase.

What you can use

One workflow

Protocol, sites, data, analysis and the report can name the same study and the same version.

Technology and people

The software does not replace a statistician, a monitor or a regulatory professional. Those roles are engaged in a scope of work.

Devices, diagnostics and drugs

The same record can hold a kit, a specimen or a dose. The regulation that applies still depends on the product and the country.

Traceable evidence

Changes keep a person, a time and a reason. An analysis names its snapshot.

Three ways to engage

Technology only, CRO services only, or both. Responsibilities are written in the agreement, not assumed from a subscription.

Look before you commit

A demonstration uses synthetic data. You can watch a workflow that matches your design before a proposal.

Not a ranking

We do not publish scores against other vendors. You compare coordination, handoffs and accountability on your own requirements.

What we will not claim

No savings percentage, no automatic compliance, and no statement that the system is a validated production environment for every sponsor.

How the work moves

Name the study

Design, countries, sites and what you need us to do.

See the record

Synthetic participants, forms and a snapshot.

Separate the contracts

Software access and professional services are listed apart.

Decide

A proposal states deliverables, milestones and what remains yours.

Related

One research lifecycle

A sponsor should be able to follow one decision from the protocol sentence that created it to the number in the report. The chain below is the one we configure. A later stage cites the version it used. The software does not promote a draft to approved on its own.

Protocol version
Objectives, endpoints and the visit grid, signed before sites are trained on them.
Operations
Sites, milestones, training and monitoring notes sit on that same study.
eCRF
Each field points at an activity in the approved protocol. A change keeps a person, a time and a reason.
Queries
A question on the field. It does not silently replace the value.
Snapshot
A checksummed copy is what statistics is allowed to use.
Output and report
A figure and a sentence cite that snapshot and that run, not a spreadsheet refreshed later.

Who is accountable

Software does not replace scientific judgment. The roles below are contracted in the scope, or they stay with you. We do not staff a role the agreement does not name, and we do not publish a headcount.

Sponsor
Regulatory responsibility, oversight, and acceptance of deliverables. This stays with you.
CRO project manager
The plan, the issues and the record of what was delegated. A service, when scoped.
Clinical monitor
Visits or central review, written on the study. A person decides what a finding means.
Data manager
Forms, checks, queries and the freeze. A service, when scoped.
Biostatistician
The analysis plan and the methods that exist in the product. Not every textbook model.
Investigator
Conduct at the site. We do not become the investigator by hosting the forms.
Regulatory specialist
Package preparation and tracking. The authority still decides.
Platform administrator
Accounts, roles and configuration. Not a clinical decision.

Why device and AI studies are a different design

A device or an algorithm is part of the intervention. The protocol has to say what it is for, which version was used, what a clinically important error is, and what the reference standard was. Regulation (EU) 2017/745 and ISO 14155:2020 are the texts a device team reads. This website is not a certified reading of them, and a Class IIb label does not set the sample size.

Intended purpose

The claim the investigation is built to examine.

Performance endpoints

Safety and clinical performance, defined before the look.

Reference standard

Independent of the model when the study is about an algorithm.

Version

A later model is a new version, not a silent update of the enrolled one.

Device accountability

Receipt, use, return or destruction, on the same study as the form.

Errors and subgroups

Missed urgency and false reassurance, and whether the result is the same across the groups you named.

A second statistical look

Verification by a qualified person is a service. It is not an automatic certificate.

A synthetic trace, so you can see the chain

This is an invented device study. It is not a result and not a participant. Protocol version 2.0 defines a performance endpoint. The eCRF field “index result” is tied to that activity. Query 14 asks the site to confirm a unit. Snapshot SYN-LOCK-01 is the copy the analysis uses. The approved run produces one figure. The report sentence quotes that figure and names the snapshot. If any link in that chain is missing, the number is not ready to quote.

Three ways to buy

Technology only
You receive access to the modules in the license. Your team, or another CRO, keeps the operational duties. Onboarding is configuration, roles and a synthetic walkthrough. Contracting is a software agreement.
CRO services only
We take the professional deliverables in the statement of work. Software may be yours already. You still accept each deliverable. Pass-through costs, such as ethics fees, are listed rather than hidden.
Integrated
One proposal, two responsibility lists: what the platform records and what a person at CAREPOI does. Milestones, acceptance and exclusions are written before setup.

What a sponsor can inspect

Oversight is the role you are given, not a separate product. Today that means accounts on the study. There is not yet a distinct read-only sponsor role, so the permissions are agreed. A demonstration can show milestones, open queries, monitoring notes and document status on synthetic data. We do not publish a screenshot and call it your study.

Questions

Is the software included when we hire the CRO?

Only if the scope says so.

Are you certified to run our study?

No. Registration as a CRO is not a certificate that a particular study is compliant.

Can we buy the software and keep our own CRO?

Yes. That is the technology-only path.

Software on this page is what the product can record today. CRO work is a professional service under a separate scope. Neither is a certification, a regulator’s approval, or proof that a study is compliant because the software was used. A qualified person still signs consequential decisions.

See the workflow on your protocol.

The conversation is about your study design and what the software can and cannot do today.