Averon Legal Systems — CPR compliance SaaS for UK costs lawyers.
UK costs lawyers track Part 47 detailed assessment deadlines in spreadsheets. One missed deadline can invalidate a costs claim worth tens of thousands of pounds. We built the software that eliminates that risk.
← All case studiesSpreadsheets tracking legal deadlines worth hundreds of thousands.
Costs lawyers in England and Wales manage detailed assessment proceedings under CPR Part 47. The procedure involves multiple sequential deadlines — Precedent H budget filings, points of dispute responses, replies — each with strict statutory timescales.
Most costs law firms manage these deadlines in Excel. A missed Part 47 deadline can result in the court refusing to hear the assessment — costing the client the entire recoverable costs claim, which may be in the tens or hundreds of thousands of pounds.
There was no purpose-built software for this workflow. Existing legal practice management systems treat costs as an afterthought. The specific CPR Part 47 deadline calculation logic was not implemented anywhere.
A dedicated compliance engine. Multi-tenant. Client-facing.
Averon Legal Systems is a multi-tenant SaaS where each law firm has its own isolated workspace. The core product is a deadline calculation engine: the costs lawyer enters a trigger event — service of a bill, receipt of points of dispute — and the system automatically calculates every subsequent statutory deadline with the relevant CPR rule cited.
A separate client portal gives the instructing solicitor read-only access to their matters — eliminating the need for status-update emails. Stripe handles firm-level subscriptions. Row-Level Security at the database layer ensures complete data isolation between firms.
Why we made the choices we made.
Multi-tenant with Row-Level Security from day one
Averon Legal serves multiple law firms from a single database. Data isolation is not optional in legal SaaS — a costs lawyer from Firm A must never be able to see Firm B's client matters. We use Supabase's Row-Level Security at the database level, not application-level guards. This means even a bug in the application code cannot expose cross-firm data. The RLS policies were written and tested before a single UI component was built.
Deterministic deadline calculation engine
CPR Part 47 deadlines are not estimates — they are legally binding. A deadline calculation engine that returns different results on different inputs, or that relies on user interpretation of the rules, is a liability. We built a deterministic TypeScript function library for deadline calculation: given a trigger event and a date, it returns the exact statutory deadline with the relevant CPR rule referenced. This is unit-tested against known cases.
Separate client portal (not a role within the main app)
Costs lawyers' clients are typically litigation solicitors at other firms. Giving them a login to the costs lawyer's internal practice management system is a security and UX problem. A dedicated client portal — with its own URL, its own auth session, and its own view — gives clients exactly the information they need (matter status, deadlines, filed documents) without exposing the costs lawyer's full workflow. Isolated by the same RLS policies.
Firm-level Stripe billing (not per-user)
Costs law firms are small. A typical firm has one to five costs lawyers. Per-user SaaS pricing creates friction and administrative overhead for small teams. Firm-level billing — a single subscription per practice — simplifies procurement, reduces billing questions, and matches how legal firms think about software expenditure.
Six weeks from domain research to beta.
Building a regulated-industry SaaS?
We understand compliance requirements, data isolation, and the engineering disciplines that regulated markets demand. Book a scope session.