Our price with nothing hidden behind it, the shape of the stack you’d be replacing counted from our own register, and a calculator that runs on your numbers instead of ours. Plus everything the arithmetic leaves out.
A business case needs two numbers: what the new thing costs, and what the old thing costs. We can give you the first exactly. We can’t give you the second, because it’s yours, and any supplier who hands you a figure for your own spending has made it up.
So this page does three things. It states our price with nothing hidden behind it. It shows, from our own register, the shape of the stack you’d be replacing. And it gives you a calculator that works on your numbers, with every step of the arithmetic visible, so you can put a size on the question before you ever talk to us.
Three lines. Two of them have a number, and the third doesn’t, so we say so instead of writing one in.
| What | Price | Why it’s that |
|---|---|---|
| The software | £1 per Commvita Flow Edition instance | Published, and it’s the whole licence. The Flow Edition carries the platform base: identity, access, audit, the data layer, flow and governance. The Population Platform adds the clinical record when you want it. |
| The hosting | Your own | It runs on your kit or your cloud tenancy, so this is a cost you already carry and already know. We never see the bill and never mark it up. |
| The support | Not published | Response times and a support model are contract matters and we haven’t settled them. We’d rather leave a blank here than print a number we can’t stand behind. |
That third row is the honest limit of this page. Until support is priced, no one can give you a complete total for the commvita side, including us. What the calculator below can do is show you the scale of what sits on the other side of the ledger, which is the part that decides whether the conversation is worth having.
The platform benchmarks itself against the products that do the same job, capability by capability, and the register ships inside the software. That register is also a map of what a health system buys today, so here’s what it shows.
To cover the 440 capabilities commvita audits itself against, the register names 454 separate suppliers and 1,023 separate products. That isn’t a list of everyone’s competitors. It’s a list of who you’d be buying from.
The supplier with the widest coverage in the register reaches 75 of the 440 capabilities, about one in six. Only eighteen suppliers reach ten or more. There’s no one you can buy all of this from.
Three hundred and twenty-three of those suppliers appear against exactly one capability. Each is a contract, a renewal, an assurance pack, an integration and somebody’s afternoon.
The licences are the part everyone counts. The part that doesn’t appear on any purchase order is what it takes to hold them together: the interfaces, the assurance packs, the renewal calendar, and the people whose week goes on moving data from one system into another. That last one is usually the largest number in the whole model, and it’s the one nobody has a line for.
Put your own figures in. The arithmetic is shown as it happens, so you can check every step and argue with any of it.
The boxes start with round example numbers so the page isn’t blank. They’re not a claim about your organisation. Replace them.
A word about the third box. We don’t count those people as a saving, and neither should your case. They’re the integration layer, and when the systems stop needing one, they go back to the job they were hired for. The value shows up as work done, not as posts removed, and a case built the other way tends to fall over at the first staff-side meeting.
The site carries a planning target of up to 80% off software and total cost of ownership. It’s worth saying plainly what kind of number that is.
It’s a model, not a measurement. It assumes a stack of point systems with their integrations, their infrastructure and their assurance overhead collapses into one platform priced at £1, hosted on kit you already pay for. Under those assumptions the licence line nearly disappears, the interface line mostly does, and the people line changes shape instead of vanishing. That’s where the number comes from, and it’s labelled as a planning target wherever it appears.
What it isn’t is a result anybody has banked. No deployment has run long enough to produce an audited before-and-after, and when one has, we’ll publish the measured figure next to this one and let you see the difference. Until then the calculator is more use to you than the target is, because it runs on facts you can check and we can’t.
Every number above is a run-rate. A business case has to carry the cost of getting there, and these are the lines the calculator doesn’t have.
You’ll pay for the old system and the new one at once, for as long as the migration takes. On a clinical system that’s usually measured in quarters. It’s the single biggest line the run-rate model misses.
Extracting, mapping and checking a record set is work, and some of it is yours because only you know what your local codes mean. The platform reports its own mapping rate and says review when the record isn’t clean enough.
A five-year deal signed last year is a cost until it isn’t. Sequencing a consolidation around renewal dates is usually what sets the timetable, not the technology.
People are slower on a new system before they’re faster on it. Budget for the dip, and for the training that shortens it.
Some of the gains on this site come from working differently, not from software. Shorter waits and fewer crisis admissions need a pathway change that the platform supports and doesn’t deliver on its own. Count those separately, or your case will claim credit it can’t evidence.
| Claim on this page | Where to test it |
|---|---|
| £1 per Flow Edition instance | Stated the same way on the editions page and the launch letter, with the same caveat about support. |
| 454 suppliers, 1,023 products, 75 as the widest single reach | The competitive register ships inside the platform and names every one. The competitive intelligence explainer sets out how it’s built and where commvita is behind. |
| What’s actually running today | The transparency explainer covers live, built and stub, and which pages read the platform and which show seeded data. |
| What leaving would involve | Migrating on, and leaving, and the escrow page for what happens if we’re not here. |