Every law firm we have worked with in India has the same drawer. Sometimes it is a literal drawer, sometimes a senior partner's inbox, sometimes a Google Sheet maintained by a long-suffering practice manager. In it lives the firm's CRM — a list of prospects, referrers, fee quotes mid-conversation, engagement letters waiting to be signed, and clients whose last matter closed two years ago and who really ought to be called.
Eventually someone buys a CRM. Often Salesforce, sometimes Zoho, occasionally HubSpot. Six months later the CRM is empty except for the first three weeks of data, and the drawer is back.
This is a field guide for managing partners and business development leads at Indian law firms about why that keeps happening, what a real law firm CRM has to do, and where the boundary sits between buying a packaged product and building something that actually fits.
Why generic CRMs fail at law firms
A generic CRM is a sales pipeline tool. It models the world as: lead arrives, gets qualified, moves through stages, closes as a deal, drops out the bottom. That model is honest for SaaS sales, real estate, and most B2B selling. It is dishonest for law.
A law firm's intake looks nothing like a pipeline. A senior partner gets a call from a former classmate who has a friend with a tax problem. The partner judges in thirty seconds whether the firm wants the matter, runs a mental conflicts check against the parties involved, calls a junior partner in the tax practice, sets up a meeting, talks fees in a way that is both deliberately vague and precisely understood, sends an engagement letter, opens the matter. None of that fits a stage-and-percentage pipeline.
Worse, the same client will generate ten more matters over the next eight years across five practice areas, and the firm needs to remember every one of those matters, every fee conversation, and every interaction in between. Salesforce can model this. The cost is six months of consulting, a custom object schema, and a workflow nobody trusts. We have seen it tried in firms of every size in Mumbai, Delhi, and Bengaluru. The pattern is consistent — the CRM becomes a graveyard, and the real intake data lives in the partners' heads and on WhatsApp.
CRM is not practice management. They are two different products.
The most common buying mistake we see at Indian firms is conflating CRM with practice management. They are different products for different stages of the client journey.
- Practice management — products like Provakil, MyKase, LegalDesk, Counsel Crest, and global tools like Clio Manage — runs the matter after it opens. Court calendaring, deadline tracking, time entries, disbursements, billing, document storage. Good ones are excellent at this, and we generally recommend buying rather than building. We covered this in more detail in our field guide to custom software for Indian law firms.
- CRM runs everything before the matter opens, plus the relationship over time across every matter. Lead capture, referral tracking, conflicts check, fee quote, engagement letter, origination credit, book of business, and the long arc of staying in touch with a client between active matters.
Most Indian firms have decent practice management and a spreadsheet pretending to be CRM. The leverage of a real CRM is rarely in winning more new logos — it is in not dropping the ten matters per year that a small inattention loses.
What a real law firm CRM actually does
Strip the marketing pages and a usable law firm CRM does six jobs. In this order:
- Prospect and referral capture with origination credit. Every new prospect has a source — usually a referring lawyer, a former client, a counsel relationship, a panel listing, or rarely, an inbound enquiry. The CRM must capture the source as a structured record, not free text. This is the data that drives partner profit-sharing later.
- Conflicts check at the moment of intake. The moment a new party is added — opposing counsel, opposing party, affiliated entities — the CRM must run a check against every party in every matter the firm has ever taken, including closed ones. Doing this manually scales until about thirty fee-earners and then quietly breaks.
- Fee-quote and engagement letter as first-class records. Most firms email a fee proposal, get verbal acceptance, and send an engagement letter as an attachment. None of this is structured. A real CRM captures the proposal as a record, links the engagement letter version, and connects both to the matter the moment it opens.
- Per-client relationship view across every matter. Not chronological. Not by practice area. By client. Show every matter the firm has ever opened for that client, every fee earned, every partner who has worked with them, every interaction logged. This is the screen partners actually use, more than any pipeline view.
- Partner cockpit — book of business, pipeline, referrals owed. Each partner needs a personal view: clients they have brought in or work with, active matters they originate or work, referrals they have sent and received, and pipeline conversations in motion. This screen, more than any other, is what changes behaviour.
- Referral and BD network ledger. The Indian legal market runs heavily on referrals from peer law firms, panel relationships, and international referral networks. A CRM that doesn't track who has sent the firm work, what was returned, and what is owed back, is missing the single most important relationship in the firm's growth engine.
A CRM that does these six well will get used. A CRM that does fifteen things badly will be the system everyone routes around with email and WhatsApp.
Where Indian firms diverge from the global CRM playbook
Most legal CRM software was built for US firms, and it shows:
- Referrals over inbound. US consumer firms run on Google Ads, intake chatbots, and standardised qualification flows. Indian corporate, litigation, and IP firms run on partner relationships and referral networks. A CRM optimised for inbound qualification leaves seventy percent of the firm's actual intake invisible.
- Origination credit lives in the CRM, not in the partner's head. Global firms have decades of formalised origination-credit policies. Indian firms typically don't, and the absence becomes visible the year a senior partner exits. A CRM is the cleanest place to formalise this without making it a political conversation every quarter.
- The partner cockpit, not the pipeline view, is the home screen. US-style legal CRMs default to a Kanban pipeline. For Indian firms the pipeline view is barely used after week three. The partner cockpit — clients, matters, referrals — is what survives.
- Bilingual and bicultural records. Indian client communications happen across English, Hindi, regional languages, formal email, and WhatsApp. The CRM must capture all of them or it will quietly miss the actual relationship history.
- DPDP-aware contact records. Personal data of clients and prospects is now governed by the DPDP Act. Consent, purpose, and deletion must be auditable. A spreadsheet CRM cannot satisfy this; a generic CRM with no India configuration will struggle.
Build, buy, or hybrid
The honest read:
- Buy a packaged legal CRM like Clio Grow or Lawmatics if you are a consumer-facing firm — family, immigration, personal injury, accident claims — running on inbound marketing and standardised intake. These products are excellent at that shape of work and we would not build over them.
- Buy a generic CRM like Zoho or Salesforce and accept it will become a partial directory and contact log, not a true CRM. This is a reasonable choice for firms under ten fee-earners where the partner can hold the rest in their head.
- Build a thin custom CRM layer if you are a 15- to 80-fee-earner corporate, litigation, IP, or full-service firm in India whose intake is mostly relationship-driven, where origination credit matters financially, and where conflicts checks and fee-quote tracking have already started to slip.
- Hybrid is what most of our clients land on. Keep a packaged practice management tool as the matter system of record. Build a focused CRM layer on top with the six jobs above. The custom layer is small — usually 10 to 14 weeks of work — and is the single highest-leverage piece of software a mid-sized Indian firm can commission.
The hybrid is the wedge. Boutique studios beat both packaged sales and enterprise consultancies here because the work is too small for a SaaS vendor to build for you and too specific for a horizontal CRM consultant to get right.
Worked example — what a thin custom CRM looks like
Recent shape of build we have done for a 38-fee-earner corporate and disputes firm in Pune, three offices, on Provakil for practice management.
Scope: a custom CRM layer that captures prospects from email and partner calendars passively, runs conflicts at intake against the full Provakil matter history via API, stores fee proposals and engagement letters as structured records, links each to its opened matter, maintains a per-client relationship view, gives each partner a cockpit, and tracks the firm's referral network. WhatsApp Business API as a side channel for client intake and engagement-letter signature reminders. DPDP-compliant audit log on every contact record.
Out of scope: court calendaring, time tracking, billing, document storage. All of that stays in Provakil.
Shape: 12-week build, fixed scope, fixed price at INR 16 to 22L, plus INR 50 to 70k per month retainer afterward for evolution and support. Engagement model close to what we describe in why fixed scope, fixed price beats time and materials. Post-launch support shaped like our take on honest software retainers.
The leverage isn't visible on day one. It shows up at month three, when the firm's first quarter-end origination-credit conversation runs from a single screen instead of three reconciled spreadsheets, and at month nine, when a senior partner exits and the firm's book of business doesn't walk out with them.
The three rollout traps
We have seen these break CRM projects more often than any technology problem.
Trap one: asking partners to type things in. Senior partners will not log a referral phone call into a form. Build the CRM to capture from calendar, email, WhatsApp, and the engagement letter automatically, and let the partner correct it. If a partner has to type, they will not.
Trap two: launching with the pipeline view as the home screen. Pipeline is the least useful view at an Indian corporate firm. The partner cockpit and the per-client relationship view are what change behaviour. Make those the home.
Trap three: skipping the engagement letter integration. The engagement letter is the moment a relationship becomes a matter. If the CRM does not capture this transition as a first-class event — with the letter version, the date, the fee structure, the partners involved, the conflicts cleared — the data layer is broken and nothing downstream will be reliable.
Where the leverage sits
A CRM at a law firm is not a sales tool. It is the firm's institutional memory of every relationship — past, present, and prospective. The firms that get this right treat the CRM as the system that survives any individual partner's departure, any year's profit-sharing argument, and any client's request for "everything you have ever done for us." The firms that get it wrong treat it as a pipeline, fill in three weeks of data, and go back to the drawer.
The good news is that the right CRM for an Indian firm is small. It does six jobs well, sits on top of a packaged practice management tool, and ships in a quarter.
If you are evaluating whether to bend a generic CRM into a legal shape or build a thin layer of your own, book a discovery call and we will walk through it against your specific firm shape. Related reading: our broader field guide to custom software for Indian law firms, the matter management build-vs-buy framework, and our law firm document vault field guide. For a sense of what these builds look like in practice, see the Halverson Chambers case study.