I build practice systems for law firms and chambers: matter management, conflict checks, hearing calendars, time and billing, client trust accounting and document trails — the operational spine for firms that have outgrown the clerk’s diary.
Where does a firm actually leak?
Not in the lawyering. In the fragments around it. Hearing dates live in three diaries that mostly agree. Files live in almirahs and email threads, findable by one person who has never taken a holiday without their phone. Billable time gets reconstructed at month-end — and memory bills modestly, which is a polite way of saying the firm donates hours to clients every single cycle. Client advances sit in the office account because moving them felt like paperwork. And conflict checks happen by asking around.
Each of those is survivable. The combination has three failure modes that are not: a missed limitation date, a conflict discovered mid-matter, and the retirement of the clerk who was the actual system. Any one of them costs more than a decade of software, which is the honest economic case for this page.
What does the system cover?
- Matter core. Parties, court, stage, next dates, responsible counsel, fee arrangement — every matter’s truth in one place, with practice-area templates so litigation and transactional work each behave like themselves.
- Conflict checks at intake. Party search across all history, run before the engagement letter and logged with a timestamp.
- The calendar that drives the week. Hearing dates with team views and escalating reminders; limitation dates tracked separately and loudly, because that is the one category where software should be actively annoying. The “kal kya hai?” scramble retires.
- Time and billing. Capture as work happens rather than reconstruction afterwards, billed by matter, retainer, hourly or fixed, with GST or UAE VAT invoicing generated clean.
- Trust and advance accounting. Client money separated by construction — the same ledger discipline I bring to money systems — with statements per client and an audit trail that answers questions instead of prompting them.
- Document register. Filings, orders, opinions and correspondence attached to the matter, searchable, access-controlled. The almirah becomes an index.
What does the firm feel in the first quarter?
Month one: the cause-list panic dies. Every lawyer opens the day knowing their dates, and for the first time the firm has a single next-dates view across all matters. Month two: billing catches up with work — time captured as it happens surfaces the hours month-end memory was quietly forgiving, and realisation per matter becomes a number partners discuss rather than a feeling they avoid. Month three: receivables ageing starts driving the Friday follow-up list, trust statements go out without an accounts scramble, and the first conflict caught at intake pays for the year.
Nothing here asks anyone to practise differently. It asks the operational floor beneath good lawyers to stop leaking, so that the work is what clients experience.
The deployable version of this — configured per firm, deployed in weeks, India, UAE and UK — is the Law Firm CRM.
Related reading
/products/law-firm-crm — the productised build · /services/fintech — the trust-accounting discipline · /industries/real-estate — the sibling document-heavy trade · /work/erp-migration — how records move without loss
The one-question test
Ask the office: how many matters have a next date this week? If the answer requires a meeting rather than a glance — /contact. Seedhi baat, and bring the diary.
Questions I actually get
Does it handle both litigation and non-litigation practice?
Yes — stages configure per practice area. Litigation matters track courts, hearing dates and limitation periods; advisory, due-diligence and transactional matters track deliverables, review rounds and closing conditions. Mixed firms run both with one conflict-check surface across everything, which is the point.
Can it read court cause lists automatically?
Where public feeds exist, dates cross-check against them and flag disagreements. The clerk's diary habit stays as the backup rather than being replaced by faith in a feed — trust, but verify. The system's job is to make sure two independent sources agree, not to become a single new point of failure.
Our senior partners will not change how they work.
They should not have to. They keep dictating; juniors and the clerk capture into the system. Adoption is designed around the hierarchy rather than against it — the partners get dashboards that need no typing, and the firm's knowledge stops leaving the building at 6 PM inside one person's head.
How are client advances kept separate from office money?
Structurally, using the same double-entry discipline as my fintech work — client funds sit in their own accounts with their own statements, and the system makes commingling difficult rather than merely discouraged. When the audit comes, the trail is a query rather than a week of reconstruction.
What does a conflict check actually cover?
Party-name search across every matter the firm has held, past and present, run at intake and logged with a timestamp. The log matters as much as the search: when a conflict surfaces two years later, being able to show what was checked and when is the difference between a procedural note and a professional problem.
Is a three-lawyer chamber too small for this?
No, and small chambers are among the best fits — the missed limitation date costs the same whether you are three lawyers or thirty, and the diary is a single point of failure at any size. Deployment at chamber scale takes days, and pricing scales down honestly.