Operational drag
- Claims handling still absorbs 60 – 70% of insurer operating cost base.
- Fee earners spend 30 – 40% of billable hours on administrative handling rather than legal work.
Insurance defence litigation is still driven by fragmented processes, inconsistent handling, and delayed visibility.
Each of these is individually tolerable. Together they compound into a drag on profitability, reserving discipline, and panel performance that the industry can no longer absorb.
Four forces are compounding simultaneously. Firms that ignore them do not stay where they are — they move backwards relative to firms that operationalise first.
F.01
Claims directors are being asked to defend reserving decisions in near-real-time. Monthly MI cannot support that cadence.
F.02
Panel reviews are tightening from annual to quarterly. Consistency and evidence now matter as much as settlement outcome.
F.03
Combined ratios are under sustained pressure. Every £ of defence cost is being audited, benchmarked, and challenged.
F.04
NIHL, motor, EL, and professional negligence volumes are rising against flat or shrinking defence-side headcount.
Every category of software currently in defence firms does one job — and none of them is operational control. The gap is not a feature. It is a layer.
Case management systems
Record keeping
No operational intelligence. Passive data store.
Billing systems
Output only
Measures what happened. Does not control what is happening.
Reporting tools
Retrospective
Explains last month. Cannot shape this week.
Productivity AI
Drafting & summary
Helps individual fee earners. Does not orchestrate the matter.
None of them provide operational control. That is the gap.
This is not a new idea. Operational infrastructure for insurance defence has been conceptually possible for a decade. What changed is the enabling stack — across three dimensions, simultaneously, in the last 18 months.
Driver
AI can now structure workflows, not just generate text.
Large language models crossed the threshold from drafting aids to reliable classifiers of structured legal work. The capability that unlocks real operational software — consistent classification of events, confidence scoring, supervised approval chains — is now production-grade. It was not 18 months ago.
Driver
Claims, medical, and evidence data is now digitised.
The underlying records that a matter operates on — claimant GP records, employment histories, audiograms, insurer reserving data, panel SLAs — exist as structured or structurable data for the first time at scale. The infrastructure layer no longer has to build the data substrate. It can use it.
Driver
Portfolio-level intelligence is now a stated requirement.
Insurers are no longer asking whether standardised panel-firm intelligence is useful. They are writing it into panel agreements. Firms that cannot deliver it will not be renewed — and firms that can will be favoured. This is a procurement change, not a preference.
The infrastructure layer is now possible.
We define ourselves by the layer we occupy — not by the technology we use to occupy it.
What we are
What we are not
Positioning
GAAS LAW is the operational layer insurers use to understand, control, and audit legal execution across their panel.
Request Executive DemoDeterministic AI · Human approval required · Every action audited
The decision is not whether to adopt structured infrastructure. The decision is whether to be among the firms that adopt it first — or among the firms that adopt it after panel agreements force the issue.
Without structured infrastructure
→ Rising inefficiency
With structured infrastructure
→ Control · Consistency · Visibility
The difference between Path A and Path B, over three panel review cycles, is the shape of the firm.
Operational control is no longer a competitive advantage. It is becoming the baseline. The only remaining question is who crosses it first — and what that firm looks like on the other side.