Claims management software · United Kingdom
The operating system for
accident management.
One claim. One record. Every workstream, document, conversation and pound accounted for in the same place.
M. Okonkwo
- Accident
- 04/07/2026
- Liability
- Non-fault
- TP insurer
- Admiral
Credit hire
42 days
£3,570.00
Storage
18 days
£450.00
Recovery
Complete
£285.00
Engineering
Total loss
PAV £8,950
Claim value
£4,305.00
Activity
- 14:22VD Authority signed by clientClient
- 11:05Engineer's report forwarded to solicitorSystem
- 09:41Valuation confirmed with clientR. Whitfield
- YesterdayStage — Engineering → Valuation confirmedSystem
No customer logos or certification badges appear on this site, because ClaimCore does not have them yet. Every figure above can be reproduced in front of you.
The problem
The claim is in six places at once.
The hire agreement is in a shared drive. The engineer’s report is in somebody’s inbox. The storage clock is running in a spreadsheet, and the only person who knows what the third-party insurer said last week is on annual leave.
None of that is a software problem until you try to answer a simple question: what is this claim actually worth, and what is holding it up? Then it is the only problem.
The lifecycle
FNOL to recovery, on one spine.
Every stage below is a real stage in the shipped pipeline — and every one of them is editable, because no two firms run the same process.
- FNOLCaptured and verified
- OnboardingDocuments signed
- Hire & storageClock running
- EngineeringReport received
- ValuationConfirmed with client
- Disclosed to TPInsurer notified
- Authority & fundsVD in
- Off-hireExposure closed
- Payment packSent to solicitor
- RecoveredMoney in
Stages, chase timings, checklist and document types are configuration, not code. Changing how your business works does not require us.
The claim record
Everything about the claim. One view.
Claimant, vehicle, third party, hire, storage, recovery, engineering, documents, signatures, correspondence, charges, invoices and the full activity trail — on one screen, in one scroll.
A handler picking up somebody else’s claim should not have to reconstruct it. Neither should a director asking why it is still open.
Why ClaimCore
Six specific things, not one vague one.
Your administrator changes it, not a consultant
Stages, rates, SLAs, document wording and automation rules are edited in a screen. There is a consultancy market around configuring the incumbent; there is not one around configuring this.
Credit hire evidence, captured at the time
GTA groups, effective-dated rate tables, comparables and impecuniosity recorded at the point of hire — and a check that names what is still missing while you can act on it.
Separation enforced by the database
Not by the application remembering to filter every query. Two independent layers, so the mistake that will eventually be made is caught below the software.
Migration included
At every tier, with a rehearsal that changes nothing so you see exactly what would happen first. The incumbent prices it on analysis, payable upfront, with the figure left blank.
Nothing metered
Unlimited claims, documents and email. Your bill does not rise because you had a busy month, which means you can forecast it.
A published price
From £499 a month including five users. You can tell whether we are in your range without taking a call first.
Chasing
Claims move without the chasing.
Milestones raise their own follow-ups on your SLA timings, and close themselves when the thing they were waiting for arrives.
- Chase solicitor for VD AuthorityOpen
- Chase engineer reportOpen
- Off-hire — payment sent to clientOpen
- Chase payment packOpen
Every task above was raised by a milestone, not by a person — and closed by the event it was waiting for.
What’s in it
Built around the claim. Built for the business.
ClaimCore is in active development. What is shipped is marked shipped, and what is not is marked too — so a demo shows you the product rather than a roadmap.
| Module | What it means for the business | Status |
|---|---|---|
| First notification of loss | Capture a claim from the public, an agent or an API — nothing reaches your records unverified. | Shipped |
| Claim record | Claimant, vehicle, third party, every workstream and the full history on one screen. | Shipped |
| Configurable pipeline | Your stages, your names, your order — changed in the admin screen, not by us. | Shipped |
| Credit hire & storage | Hire and storage periods, day rates and recovery charges feeding the claim's value. | Shipped |
| Engineering & total loss | Reports, pre-accident value, salvage and the total-loss decision, sent on to the solicitor. | Shipped |
| Documents | Typed, permissioned, tied to the claim, and served only to people entitled to see them. | Shipped |
| E-signature | Send, sign, seal. Every signature carries a certificate — signer, IP, timestamps, consent text and a SHA-256 of the sealed document. | Shipped |
| Solicitor correspondence | Inbound email filed against the right claim, matched on your reference or theirs. | Shipped |
| Claim finance | Charges derived from the workstreams, invoices, payment packs and commission — reproducible from stored rates and dates. | Shipped |
| Chase & SLA | Milestones raise their own follow-ups and close them when the wait ends. | Shipped |
| Finance ledger | Receipts allocated to the invoices they settle, part payments with real figures, aged debt and write-off with a reason. | Shipped |
| Fleet compliance | MOT, tax, insurance and servicing chased before they fall due, with utilisation measured two ways. | Shipped |
| Analytics | Where claims stall, what happened to each month's cohort, and every figure against the same period last time. | Shipped |
| Public API & webhooks | A versioned API scoped by keys you issue, and signed webhooks your systems can trust. | Shipped |
| Migration Centre | Bring your existing book across: map, validate, rehearse without changing anything, then commit. | Shipped |
| GTA-grade credit hire | Vehicle groups, rate tables on the annual cycle, extensions with reason codes, and need and impecuniosity captured at deployment rather than reconstructed later — plus a check that names the evidence still missing while there is time to get it. | Shipped |
| Liability | Decisions, apportionment, evidence and the third-party insurer's position, tracked properly — and the split flows through to the invoice. | Shipped |
| Repairs | Repairer, estimate, authorised and final cost, against the total-loss threshold. | Shipped |
| Workflow automation | Build the rules yourself: trigger, condition, action, delay — without waiting for a developer. | Shipped |
| Customer & partner portals | Claimants, referrers, engineers, repairers and solicitors self-serve, so your handlers stop fielding status calls. | Shipped |
| Guided vehicle inspections | Nine required views on a phone, walked in the order you go round the car. It refuses to submit while one is missing, and names which — so the photograph a defendant asks about eight months later was taken. | Shipped |
| ClaimCore AI | Reads a document and proposes claim field values, each shown beside the exact words it was read from — checked against the document before you see it. Nothing is written until somebody accepts it. | Shipped |
| Cited credit-hire assistant | Would cite a named authority with a link, or decline. Not built: it needs a corpus of UK authorities, and in a litigated domain a citation the product cannot verify is worse than no answer. | Planned |
Who it is for
A credit hire operator and a repair network have almost nothing in common.
Except that both are sold the same claims software. There is a page for each of these written about that business, not one page with the words changed.
Moving in
Your old system keeps running until you are satisfied.
The most common reason firms stay on software they dislike is not the software — it is the thought of moving four thousand live claims out of it while continuing to run a business.
Map your columns, validate every row, then rehearse the entire import without changing anything — as many times as you want — and see exactly what would be created before anything is. Included at every tier.
Trust
Claims data is the sensitive kind.
A motor claim carries a name, an address, a date of birth, bank details, medical detail and a signature. Held in UK and EU regions, permissioned server-side on every action, with an append-only activity trail and a tamper-evident audit record on every document a client signs.
What it costs
From £499 a month, published.
Including five users, with unlimited claims, migration included and a twelve-month term. Professional starts at £1,450 including fifteen. Most firms need Core and one or two of the six modules — and we would rather tell you which in the first conversation than sell you all six.
ClaimCore connects to Microsoft 365 for claim correspondence, to Entra ID for sign-on, and to your other systems through a versioned API. See the integrations — including a list of what does not exist yet.
See it against one of your real claims.
Bring a live file. Thirty minutes, no slides — we will walk it through the system end to end and show you exactly where it would sit.