An operational layer for Defendant Litigation.

AI that knows the operational state of every case — how close it is to breaching an insurer SLA, where the disbursements actually sit, what each inbound email needs in reply.

Backed by — an MoJ-supported programme

Who we're built for

Defendant-side insurance litigation teams.

  • motor
  • EL / PL
  • credit hire defence
  • counter-fraud
  • disease
  • recoveries

Whether you're a 10-fee-earner specialist firm or a 60-strong insurance department inside a larger practice, the operational shape of defendant litigation work is the same. That's who the product is built for.

It's a reconciliation problem dressed up as inbound email.

Fee earners at insurance litigation law firms don't just do legal work. They sit at the centre of a multi-party coordination problem — claimant solicitors chasing status, the court funds office asking about disbursement payments, counsel clerks asking when their fee will land.

The fee earner doesn't control any of that money or any of those timelines, but they're the person everyone calls.

INBOUND CHOKEPOINT SOURCE OF TRUTH Claimant solicitor "where's our cheque?" Court funds office "disbursement query" Counsel's clerk "fee outstanding" Fee earner ×1 query Insurer "we paid"
Multi-party squeeze

A layer that knows the operational state of every case.

Decrey runs as a layer that knows the operational state of every case — who's owed what, what's been paid, what's been reconciled, what's been chased and when. When an inbound chaser arrives, the system already knows the answer.

Built into that layer: per-insurer reporting formats, panel SLAs and the clocks that run against them, CPR deadline cascades, disbursement state across paid-out, awaiting-recovery, recovered, and billed. Not generic templates — the actual operational rules each insurer runs to.

Case state case lifecycle · disbursement ledger · deadlines Per-insurer rules SLAs · reporting templates · panel guidelines Procedural regime FRC · OIC · multi-track · CPR deadline cascade Drafts & reports human-reviewed surface always reviewed before they leave the firm inbox
Operational layer

Nothing leaves the firm without a fee earner's approval click.

Nothing Decrey generates leaves the firm without a fee earner's approval click. No auto-send, no auto-submit, ever. Drafts come into a review queue, get reviewed, get edited, get approved. Decrey's job is to do the operational work; the fee earner's job is to decide whether the output is right.

This isn't a configurable setting. It's structural. SRA supervision rules, professional indemnity insurance, and UK GDPR accountability all require explicit human sign-off on anything that goes out — and we'd build it this way regardless.

STEP 1 STEP 2 STEP 3 STEP 4 Inbound email arrives Decrey drafts queued Fee earner approves approved edits captured Out audited logged
Approval flow

On the firm's side of the insurer-panel relationship.

Decrey integrates with your case management system — Proclaim, VisualFiles, others — rather than replacing it. Existing workflows stay; Decrey handles the operational layer that previously absorbed fee earner hours.

No data leaves the firm without going through documented sub-processors. UK GDPR-aware infrastructure. Audit logging on every action the system takes. The compliance posture is on the security page.

FIRM SYSTEMS O Outlook email X Excel panel reports P Proclaim CMS V VisualFiles CMS INSURER PANELS A Aviva Insurer SLAs A AXA Insurer SLAs + others DECREY Decrey Operational Intelligence FEE EARNER Reviews & approves
System landscape

Pilot conversations officially open for 2026.

The product is in active build. Synthetic data only until pilot DPAs and sub-processor reviews are committed. If you're a partner, head of department, or operations lead at a defendant insurance firm, get in touch.