Pricing
Ways to work with us, from first look to full deployment
Pilot access is deliberately light so you can see the platform before committing. Deployment is sized to the service, site or region that will run it. Figures are given in writing, against your scope.
Pilot access
Three ways in, depending how far you want to go
Each step is separable. You can stop after Discovery, or run a pilot without any intention of a wider deployment.
Discovery
Clinical leaders and digital teams working out whether this is worth pursuing
No charge, no commitment
We will tell you plainly if Clinvela is not the right fit for your problem.
- A guided walkthrough of the platform as it is being built, using synthetic data
- A workflow mapping session with your team to trace one clinical pathway end to end
- An initial read on the systems, access and governance decisions a pilot would need
- A written summary of what a pilot could and could not cover for you
- No live clinical data, and no production access, at this stage
Guided pilot
One service or team ready to work a real pathway with our team alongside
Contributory — quoted for your scope
The figure reflects the work our team commits to and is agreed in writing before anything starts.
- One service or team, with a number of named users agreed with you
- The capabilities in the initial release scope, listed on the Platform page
- Success measures agreed and recorded before the pilot begins
- Onboarding, configuration and access assessed with your IT and digital teams
- A working session each week for the duration of the pilot, with a named contact
- A written outcome report at the end, against the measures agreed at the start
Design partner
Organisations that want to shape the platform and evidence the results
Structured and agreed together
We take on a small number of design partners so that the input stays real rather than nominal.
- Everything in a guided pilot, across several services or a whole department
- Direct input into release priorities, with a standing place on our review agenda
- A measurement plan agreed with your team, including baseline data where you hold it
- Joint reviews at agreed checkpoints, with findings recorded in writing
- A say in what is published about the work, on your terms and only with your permission
Full deployment
Sized to the service, site or region that runs it
Deployment tiers describe the scope we take on and the arrangements that come with it. Capability availability is set by the initial release scope, not by the tier.
Single service
One service or team, on one site, running the pathway in day-to-day use
Quoted per organisation
Sized on named users and the connections the service needs.
- Named-user access for the service, with organisation-specific roles and administration
- The capabilities in the initial release scope, including the Clinvela Ledger
- Source connections agreed in the assessment, with exceptions surfaced rather than hidden
- Onboarding, administrator handover and training for the team
- Support with a named contact and a defined route for incidents
Service group
Several services, or a whole hospital site, coordinating across teams
Quoted per organisation
Adds cross-service visibility and the governance reporting managers need.
- Everything in a single service deployment, across multiple services or a full site
- Operational visibility of outstanding, ageing and handover work across teams
- Multiple source connections, each assessed and validated with your IT team
- Administrator controls for membership, roles and governed configuration at scale
- A named service manager and priority handling of reported issues
Regional & multi-site
Health regions, groups and programmes spanning several organisations
Quoted per programme
Every deployment of this kind is scoped individually; there is no standard price to quote.
- Everything in a service group deployment, across several sites or organisations
- A regional or in-country hosting option where your data protection assessment requires it
- Cross-site coordination arrangements, each one explicitly agreed by the participants
- Governance reporting for programme and board-level review
- Availability, incident response and change windows defined in the agreement
What shapes a quote
Five things we need to know before we can price it
Send these with your enquiry and the written quote comes back faster.
- 1
Named users
How many people need their own accountable identity in the system — not a shared login.
- 2
Services and sites
One team, a whole department, a site, or several organisations working together.
- 3
Source connections
Which lab, radiology, record or scheduling systems we connect to, and how they are exposed.
- 4
Hosting option
Managed cloud, regional or in-country hosting, or an organisation-controlled environment.
- 5
Support and availability
The response times, change windows and reporting your governance bodies expect.
What every engagement includes
Not tiered, not an upsell, and not contingent on the size of the order.
Due diligence, not a sales deck
Security, data protection and clinical safety questions are answered in writing, and deployment requirements are assessed with your teams rather than assumed.
Agreements in place before data moves
Data protection terms are signed before any personal data is processed, with a Business Associate Agreement available for covered-entity deployments.
The Ledger, always
Verifiable histories and evidence exports are part of the initial release scope, at every tier — not an upsell.
Deployment options and how the platform fits an existing estate are set out on the Integrations & Compliance page.
Questions
Asked often, answered plainly
Why is there no price list on the page?
Clinvela is in development and every organisation differs — in systems, governance and how much of the pathway they want to coordinate. A published figure today would be a guess dressed up as a quote. Tell us your scope and we will come back with a written one.
Is patient data needed to start?
No. Discovery runs on synthetic data, and a pilot can begin that way too. Live clinical data is only introduced after the data protection and security assessment is complete and both sides have signed the relevant terms.
What happens when a pilot ends?
You get a written outcome report against the measures agreed at the start, and the decision to proceed, extend or stop is yours. Nothing converts automatically into a paid deployment.
Can we start with one team and widen later?
Yes. The deployment tiers are ordered that way on purpose, so a service that proves the model can extend to a site or a region without starting the assessment again from scratch.
Is anything here a committed delivery date?
No. The capabilities listed on the Platform page are labelled as initial release scope or planned expansion, and no integration described on this site is yet live. What we commit to in writing is the assessment and the pilot itself.
Early access
Get a written quote for your scope
Tell us the service, the teams and the systems involved. We will come back with a figure in writing, or tell you if Clinvela is not yet the right answer for you.