About.
I'm Nayan. I'm building Decrey.
I'm building Decrey to take the repetitive operational work off the people doing panel litigation. The reporting, the chasing, the reconciliation, the per-insurer admin that fills the gaps between actual legal work. The work that's currently absorbing fee earner hours without producing anything a partner would call legal output.
Why this problem
UK defendant insurance litigation is a market where the operational work — chasing, reporting, reconciling, formatting to per-insurer templates — has scaled out of proportion to the legal work. Fee earners on insurer panels spend a substantial share of their week on tasks that produce no chargeable legal output and that no fee earner wants to do.
There's been real AI progress in adjacent areas — large-firm general-purpose tools, in-house insurer products, claimant-side platforms. But the specific operational reality of being a defendant firm on an insurer panel hasn't had a purpose-built product behind it. Most of what exists is either generic AI inside a case management system, or insurer-side tooling that doesn't sit on the firm's side of the relationship.
That's the gap Decrey is built into.
Why this approach
Defendant insurance litigation runs on a long list of small, firm-specific, insurer-specific operational details. Which template a particular insurer wants payment requests in. Which portal needs a six-digit code. Which SLA clock starts when. How the panel grading dashboard treats a missed deadline versus a late one.
These details aren't incidental — they're the work.
A general-purpose AI tool can't see most of this. It can draft a competent letter, but it doesn't know which of your insurer's three letter templates to use, what the right matter reference format is, or which workflow gets escalated to a senior fee earner versus closed at intake. Those details have to be built into the product.
Decrey is built narrow on purpose. The depth comes from being designed for one type of firm doing one type of work, with the per-insurer rules, panel reporting formats, procedural specifics of FRC/OIC/multi-track work, and operational coordination patterns built into the product rather than left for the firm to configure.
Get in touch
If you're working in defendant insurance litigation and the description above sounds familiar, I'd like to hear from you. Whether you're curious about the product, want to share what your team's day-to-day actually looks like, or are interested in a pilot conversation later in 2026 — reach out.
Nayan