Synthetic demonstration data — not for clinical use. Screens and figures on this site are illustrative. VerityRT is not FDA-cleared and makes no claim of clinical validation.
Discovery hypotheses, published rather than hidden
These are not established market rates. They are the ranges we are testing, published because asking a department to sit through a discovery call to learn a number is a waste of their afternoon.
What these numbers actually are
Hypotheses to be validated through interviews and paid pilots. They will move. A clinic that finds them wrong in either direction is giving us useful information, and we would rather hear it early.
The ladder
Readiness assessment
$5,000 – $15,000
2 – 4 weeks
A workflow map, a pain-point inventory, a data and regulatory inventory, and an honest answer about whether this is worth doing at your site.
Current workflow mapped step by step with the people who do it
Planning-system, oncology-information and archive version inventory
Existing checklists, protocols and QA procedures catalogued
Data volume, quality and access pathway assessed
A written recommendation, including the recommendation not to proceed
Implementation and validation
$20,000 – $75,000+
3 – 6 months
Read-only integration on a non-clinical environment, protocol configuration, validation against your own historical cases, procedures and training.
Gateway deployment inside your network
Your protocols configured, versioned and owned by a named clinician
Validation against your historical cases with expert adjudication
Standard operating procedures and staff training
A site commissioning package you keep
Annual platform subscription
$18,000 – $60,000 per site, per year
Annual
Plan QA, evidence, documentation, analytics and model monitoring, with the support and update commitments that clinical software requires.
All copilot modules
Protocol versioning and change control
Model monitoring by stratum with drift alerts
Audit export
Regression package on every upgrade
Enterprise multi-site
Custom annual agreement
Annual
Central governance across sites, federated policy, integrations, service-level agreements and custom analytics.
Federated policy with local gateways
Cross-site analytics and benchmarking
Named support with agreed response times
Custom integration work
Regulated modules are priced separately, after they exist
Why separate
Automatic contouring, planning recommendation and delivery monitoring are regulated functions with their own intended use, clinical evidence, quality system and cybersecurity documentation. Bundling them into a subscription before they are authorised would misrepresent what a clinic is buying.
What that means today
Nothing on this page prices a regulated capability, because none is available. The copilot scope is advisory and read-only.
What a department should demand before paying anything
Measured review-time reduction
On your cases, not a vendor's.
Sensitivity and false negatives
Specifically for critical checks. A false negative on a critical check is the number that matters.
Alert burden
How many findings per case, how many were acted on, and how many were noise.
A commissioning package
Site-specific, so your physicists can verify behaviour rather than trust it.
Security and privacy documentation
Before the first connection to anything, not after.
A clear regulatory status
In writing, for the exact configuration you would deploy.