Most Indian law firms run on the same software stack: Microsoft Office, a network drive, a billing spreadsheet a partner's spouse maintains, and three WhatsApp groups named some variation of "Internal — final — final2." The product is good. The work is hard. The software is mostly invisible.
That stack worked when firms were five lawyers in one office. It buckles around twenty fee-earners spread across two cities. Files go missing. Conflicts get checked twice or not at all. Billing realisation drops because partners forget to log time, and nobody can tell who's profitable. The instinct to fix it with custom software is right. The execution is where most firms get burned.
This is the field guide we wish more managing partners had before the first vendor pitch.
The four things a law firm system must do
Strip away the marketing pages. A real law firm management system has to do four things, in this order:
- Tell you what's open. Every matter, every party, every key date, every status — visible to the right people, invisible to the wrong ones.
- Hold the documents. Versioned, searchable, auditable, on the right side of the bar council and the client's confidentiality expectations.
- Track time and money. Billable hours logged where the work happens, not in a separate app. Realisation visible to partners, not just the CFO.
- Show the partners what they care about. Originations, write-offs, AR aging, work-in-progress per partner. The numbers a managing committee actually argues about.
A system that does these four well will get used. A system that does eight things badly will sit in a tab nobody opens.
Where Indian firms have specific needs
You can pick up a US-built practice management product and force it to work in Mumbai. We've seen the duct tape. The places where Indian firms need actual local design:
- Conflicts logic that respects family groups. Indian corporate clients often share directors, beneficiaries, and ultimate owners across a dozen entities. Conflict checking on entity name alone misses half the real conflicts.
- Court-aware deadlines. High Court vacations, the Supreme Court's roster, bar holidays — these are not features in foreign systems. A custom build can codify the calendars your team actually works against.
- E-stamping and e-filing. State-specific e-stamp paper APIs, court e-filing portals (with their UI quirks), GST on legal services. Each is a small integration; together they're the work.
- Bilingual document handling. Hindi, regional languages, and English interleaved in case files. A vault designed only for English text breaks indexing on contracts that aren't.
- Partner allocation that matches your partnership deed. Originating partner, working partner, supervisory partner — each with a different cut. Off-the-shelf systems handle one model; you have your own.
The build vs buy question, honestly
We get asked this every month. The honest answer is uncomfortable:
- Buy if you're under ten fee-earners, you're a single practice area, and your processes match a packaged product's defaults closely enough that adopting it will not require changing how partners work.
- Build if you have specific conflict, allocation, or workflow rules nobody has packaged — and if you'll have ten or more fee-earners using it within twelve months, so the cost amortises.
- Hybrid is the under-discussed option: buy a billing or document core, custom-build the partner reporting and matter-management surface that sits on top. We do this often.
The trap is the middle: a small firm that buys a big enterprise product and tries to bend it. The product wins, the team gets demoralised, and three years in someone is hand-keying numbers from one spreadsheet to another.
If you're considering custom-built matter management or a document vault, the right first question isn't "what should we build" — it's "what's our partnership deed actually expecting the software to enforce?"
What goes wrong in legal-tech builds
Three failure modes that account for almost every law firm software project that quietly dies:
The Big Bang. Twelve months of build, no production use, a launch dinner, then six weeks of bugs. Partners try it once, hit something broken, and never come back. Solution: ship to one practice in six to ten weeks. Use it for real for a month. Then expand.
Software that treats partners as users. Partners are not users — they are the system's customers and reluctant editors. The associate who logs time daily is the user. Build for them first; partner dashboards come later, in a more polished form.
Skipping the boring numbers. Realisation, AR aging, write-offs — boring, critical. Most pretty matter-management systems have terrible billing reporting because the founders found billing dull. The managing committee will only fund version two if version one tells them whose practice is most profitable.
The cost of getting these wrong isn't just the money. It's the political cost of a failed software project inside a partnership, which makes the next attempt harder for years.
A six-to-ten-week shape
The shape we use, and recommend even for firms not working with us:
- Week 1–2: Discovery. One day on-site at the busiest practice. Sit with the senior associate logging time. Sit with the partner who runs originations. Talk to whoever maintains the existing billing spreadsheet — they know more about your firm's mechanics than the website you're reading right now.
- Week 3–6: Build the core. Matter management with custom conflict logic, the document vault, and time entry. One practice area only. Live deployment, real usage from week 5.
- Week 7–8: Billing engine. Partner allocation, write-offs, GST handling, partner-level reporting. This is the partner-pleasing layer.
- Week 9–10: Roll out + retainer. Second practice area, training, a clear scope for ongoing support.
Then a monthly retainer for what's next: e-filing integration, the second-office rollout, the partner-track-record dashboard somebody will inevitably ask for in month three. We talk about why a real software retainer matters elsewhere; for legal-tech specifically, it matters more than for any other vertical we work in.
What we do
Tanvora Labs builds custom software for law firms — matter management, document vaults, e-billing, partner reporting — out of our studio in Pune. We've shipped this work for Halverson Chambers in Mumbai. Six-week core build, fixed scope, fixed price. Code is yours from day one.
If you're at the stage of asking these questions seriously, book a thirty-minute discovery call. No pitch deck. We listen for the bottleneck and tell you whether building custom is the right move or whether one of the off-the-shelf products would actually fit. Sometimes it's the latter, and we say so.