Enterprise
The questions that stall a large deal, answered before you ask them.
Multi-branch operations, security teams and procurement functions all have to say yes. This page is written for each of them.
For the operations director
Teams, branches and who sees what
What a person may do and how much of the book they may see are set independently. A handler with full capability on their own caseload and no access to the rest is a normal configuration rather than a compromise.
For multi-branch operations →One definition of every figure
Because there is one system. The consolidated report is a query rather than a monthly reconciliation, and every branch is counted the same way because the counting is not theirs to change.
Configuration without us
Stages, rates, SLAs, document wording and automation rules are edited by your own administrator. No consultant, no release, no change request — which is what determines whether a platform still fits your process in three years.
Acquisitions migrate
The Migration Centre is included, and a mapping profile built for one source system is reused for the next firm you buy that runs the same one.
How migration works →For IT and security
Isolation enforced by the database
Row Level Security on 72 tables, with the application connecting as a database role that owns nothing and cannot bypass a policy — so the policies apply to it. Two independent layers, so a mistake in the software is caught below it.
Single sign-on
Microsoft Entra ID, tenant-bound. Plus multi-factor authentication, a durable lockout held in the database rather than in process memory, and deactivation that takes effect on the next request rather than the next sign-in.
An audit trail with before and after
Every recorded change carries the old value, the new value, who made it and from where — viewable in the product rather than exported on request.
Restore for one customer
A single-tenant restore, so your data can be recovered without rolling back anybody else’s. It has been rehearsed rather than documented, and Enterprise customers get an annual rehearsal evidenced in writing.
Measured, not asserted
100,000 claims on a production build under Row Level Security, with nothing over eight tenths of a second. Reproducible in about four minutes, and we will run it in front of you.
What we do not hold
No ISO 27001, no Cyber Essentials, and no third-party penetration test. The controls above are real and tested; the certificates are not held. We would rather say so here than have you find out in week six.
For procurement
Service levels that carry credits
99.9% uptime with service credits, a two-hour P1 response and 24/7 cover for P1. Written into the contract rather than described on a page.
Data protection paperwork, ready
A data processing agreement, a published sub-processor register and a completed security questionnaire. Requestable directly from our security address without going through sales first.
UK and EU data residency
Application, database and document storage all in UK or EU regions, with custom retention and residency terms available at this tier.
A named person
A customer success manager who knows your configuration, plus quarterly review. Not a shared queue with a service level attached to it.
Said plainly
ClaimCore is a young product with no customers of the scale this page is written for. What it has instead is an architecture that was built for it, evidence that can be reproduced in front of you, and a willingness to tell you what it does not have.
If your procurement process requires an ISO 27001 certificate, ClaimCore does not meet it today. That is a conversation about sequencing, and it is one we would rather have in the first meeting.
Send the security questionnaire before the demo, if that is easier.
We would rather answer IT's questions early than discover them in week six.