Matter cockpit
Parties, forum, stage, documents, deadlines and the next hearing in one operating view.
CaseOps for law firms
The operating system for litigation-heavy law firms.
CaseOps turns scattered files, research tabs, draft folders, hearing notes and billing workflows into one matter-native system of work.
Built for Indian legal workflowsLive at caseops.ai
One workspace for matters, research, drafting, hearing preparation, contracts, outside counsel and billing, with control surfaces that legal teams can trust.
System
Matter-native
Output
Cited legal work
Control
Audit + review
Drafting studio
Grounded first drafts with inline citations, assumptions and missing-fact placeholders.
Hearing pack
Chronology, last order, bench brief and oral points assembled from the matter record.
Billing and recovery
Time, invoice approval and payment links tied back to the same matter economics.
The problem
Most firms do not have a legal stack. They have fragments.
The issue is not a lack of tools. It is that the tools do not share the same operational truth.
Matters live in one place, the actual work in five others.
Case files, research notes, orders, draft versions, calendars and billing systems drift apart the moment a matter becomes active.
Partners review without a clean operational spine.
The draft sits in one tool, authorities in another, and the hearing note in a chat thread. Review quality depends on who remembers what.
Institutional memory disappears between matters.
The firm's strongest arguments, prior positions and practical playbooks are rarely structured enough to be reused on demand.
Revenue systems do not reflect the legal workflow.
Time, invoices and collections usually sit outside the matter, so real profitability and team discipline arrive late.
What firms pay for
Context switching
Associates rebuild the state of the matter every time they change workflows.
Review friction
Partners review a draft without the whole chain of facts, authorities and hearing context.
Deadline risk
Orders, listings and team ownership fall through gaps between systems.
Late commercial visibility
Revenue tracking arrives after legal work, instead of guiding it in real time.
The operating spine
Everything hangs off the matter.
CaseOps uses the matter as the unit of legal work, so documents, drafts, hearings, teams and billing stay attached to one live record.
Parties
Claimants, respondents, counsel and role context.
Documents
Orders, pleadings, annexures and evidence with indexing state.
Hearings
Listings, chronology, last order and hearing packs.
Billing
Time entries, invoices, collections and payment state.
Matter cockpit
The same record powers every workflow.
Parties, forum, stage and next hearing in one cockpit
Documents, drafts and hearing packs tied to the same record
Team scoping, ethical walls and audit at matter level
Research, recommendations and billing anchored to live facts
Research + drafting
Draft faster without giving up accountability.
The goal is not to produce unverifiable text faster. The goal is to produce reviewable legal work anchored to sources and the matter record.
How the drafting loop works
1
Start from the matter record, not a blank document.
2
Retrieve statutes, judgments and internal precedents against the issue.
3
Generate a first draft with inline citations, assumptions and missing facts.
4
Route it through reviewer sign-off before it becomes operational output.
Authorities attached
Substantive output is grounded in statutes, judgments and internal precedents, not free-floating model guesses.
Reviewer-first design
Assumptions, missing facts and citation trails are visible so senior lawyers can judge output quickly and defensibly.
Bench-aware appeal drafting — shipped
When the matter has an upcoming listing, the appeal-memorandum draft pulls authorities authored by that bench (court-scoped via the resolver) and prefers ones aligned with the matter's practice area. It is citation selection with visible source context, not an outcome forecast.
Statute model + verbatim quoting — shipped
7 central acts catalogued (BNSS / BNS / BSA / CrPC / IPC / Constitution / NI Act, 91 sections). Attach sections to a matter as cited / opposing / context; the prompt receives bare text and quotes verbatim.
Refusal over fabrication
Weak evidence and absent facts should produce a refusal or a placeholder, not a polished hallucination.
Hearing readiness
Turn hearing preparation into a repeatable system.
The team should not rebuild chronology, last order context and oral points by hand on the morning of a listing.
Chronology assembled from the matter timeline
Last effective order surfaced without manual digging
Proceeding-sheet directions converted into review-required tasks and deadlines
Affidavit question bank, mock hearing, and transcript-first coach feeding oral prep
Source-backed bench context and calibrated historical patterns shown with limitations
What the team walks into court with
Litigation intelligence brief
Current posture, proceeding directions, affidavit prep, source-backed bench context and review-required items.
Chronology
A defensible timeline assembled from filings, orders and matter activity.
Oral points
The key propositions and supporting authorities, assembled into a usable hearing pack.
Platform breadth
Run more of the practice in the same system.
CaseOps is designed to keep adjacent legal workflows attached to the matter graph instead of forcing the firm back into disconnected tools.
Contracts and playbooks
Upload, compare against playbooks, surface deviations, and move obligations back into the matter graph.
Research and knowledge reuse
Search the public corpus and tenant-private annotations without leaving the operating workflow.
Litigation Intelligence
Review proceeding signals, affidavit gaps, mock-hearing feedback, source-backed bench context, calibrated patterns, and graph links from one matter queue.
Outside counsel coordination + portal — shipped
Manage counsel briefs, budgets and spend on the same matter portfolio. Briefed counsel get a magic-link login at /portal/oc — assigned matters, work-product upload, invoice submission, time entries — gated by MatterPortalGrant with audit on every action.
Client portal + KYC — shipped
Each client gets their own /portal view of the matter with Comms, Hearings and KYC tabs. Magic-link auth on a separate cookie scope; matter-grant scoping; full audit trail on KYC + reply state.
Team visibility
Partners, associates and legal ops work from the same matter truth instead of status being rebuilt in meetings.
Institutional memory
Strong prior arguments, preferred clauses and review patterns become reusable assets, not tribal knowledge.
Firm-wide operating discipline
The product is designed to run across litigation, advisory, contract and portfolio workflows without changing systems.
Commercial discipline
Work and revenue live together.
Legal teams should not finish the work and only then discover whether the matter was properly captured, billed and collected.
Billing path
Time -> invoice -> payment link -> recovery
Capture
Time + expense
Dispatch
Invoice workflow
Settlement
Pine Labs link
Timekeeping inside the matter
Capture effort where work actually happens, instead of asking the team to reconstruct it later.
Invoice approval and dispatch
Billing states are visible, traceable and auditable from the same record used for legal work.
Collections visibility
Payment state, partial recovery and write-off posture are visible without leaving the platform.
Trust and control
Control is built in, not bolted on.
For law firms, product quality is not only speed. It is whether the system preserves boundaries, ownership and reviewer accountability.
Tenant isolation at query and storage layer
Matter-level ethical walls that override broad role access
Audit on sensitive actions, exports and AI runs
Scoped, source-backed review workflows for legal output
Signed access patterns for private documents and attachments
Configurable workspace contact, ownership and oversight
Review-required legal AI
Scoped access
The system acts inside tenant and matter boundaries, not with broad, invisible privilege.
Acceptances are explicit
Recommendations and draft approvals are tracked actions with ownership, not silent automation.
Legal outputs stay accountable
The workflow is designed so a firm can justify what was used, what was reviewed and who accepted it.
The AI angle
AI as associate leverage, not as an autopilot.
AI is a feature of the system, not the product. Legal knowledge stays in retrieval and source systems — statutes, judgments, your own precedents — not baked into model weights. Every substantive output is grounded in a named source; uncertainty renders as a refusal or a placeholder, not a polished hallucination.
Drafting Studio
Produces a first draft from the matter record with inline citations to named judgments. Refuses to cite what it cannot ground.
Grounded research
voyage-4-large embeddings + HNSW + cross-encoder reranker return results with source links and cosine-strength.
Explainable recommendations
Forum, authorities and next-best-action come with rationale, assumptions, missing facts, and a confidence label.
Refusal over fabrication
Missing facts render as [____] placeholders. Out-of-corpus queries return an explicit no-result.
The partner's payoff
A junior who used to spend 3 hours on a first draft plus 2 hours chasing citations gets a grounded draft in 10 minutes. The partner's review becomes the actual legal work — not clerical assembly. Citation discipline stays stricter than before, because the reviewer-findings block catches BNS vs BNSS, uncited claims and fact gaps before the draft leaves chambers.
Agentic scope: today, four narrow agents — cause-list watcher, corpus ingest, structured extraction, document retry. Coming in Sprint I: Grantex trust plane + Temporal-durable filing-deadline, obligation, and intake-triage agents. Substantive legal judgment is always a human step. Outbound actions (filings, payments, client communications) default to human approval.
Contact
If the goal is to run the whole firm on one system, start here.
Founder-led conversations for law firm pilots, strategic walkthroughs and deployment planning.
Direct contact
mishra.sanjeev@gmail.comWrite directly for a live walkthrough of the platform, law-firm pilot discussions or a founder-level conversation about how the operating model fits your practice.
For litigation-heavy firms
A stronger operating system for firms where matters, hearings and drafting drive the workload.
For growth-stage partnerships
Get operational visibility without turning legal work into generic workflow software.
For teams that need control
Review, audit and access boundaries remain visible even as the product becomes more capable.