Walk into any Indian private equity fund, venture capital firm, or large M&A advisory and ask how they run legal due diligence. You will hear some version of this: a junior associate collects PDFs of case records from public portals, cross-references party names in Excel, and produces a memo two weeks later. The process is heroic, expensive, and error-prone. It is also completely unnecessary in 2026.
This post walks through the hidden cost of PDF-based due diligence, quantifies the time-to-close and quality impact, and explains why the shift to API-based diligence is the single highest-leverage change a deal team can make this year. We write this as operators who have watched the friction firsthand.
The typical PDF-based diligence
Consider a mid-market PE fund looking at an acquisition of an Indian manufacturing company with operations in five states and three group entities. The legal DD typically runs like this.
- Counsel asks the target for a litigation schedule. The target provides what it knows, which is not always everything.
- Counsel’s team independently searches eCourts portal for the target’s entity names and key individuals across relevant states.
- Each search returns a list of cases. Each case is downloaded as a PDF or screenshot.
- The associate copy-pastes party names, case numbers, and statuses into Excel.
- The team reads through orders to understand exposure, amounts claimed, and adverse rulings.
- Findings are consolidated into a DD memo, typically delivered in 10 to 14 days.
Every step in this workflow is a reasonable response to the tools that were available five years ago. Every step is wasteful in 2026.
The four costs
- Time-to-close. Legal DD is almost always on the critical path for deal closure. A 10 to 14 day legal diligence is a 10 to 14 day delay. For deals that need to close in 45 days, this is 20 to 30 percent of the window.
- Cost per matter. A mid-level associate spends 20 to 40 hours per target on search and triage. At blended rates of ₹10,000 to ₹20,000 per hour, the fully loaded cost runs into several lakhs per target.
- Completeness risk. Manual searches miss. Name variations, misspelled parties, related entities in other states, legacy group companies, and partner litigation can all slip through. Every deal has a story of a post-close surprise.
- Freshness. A litigation schedule produced three weeks before signing can be stale by the time the deal closes. New filings, adverse orders, or recovery proceedings that land in between are regularly missed.
The aggregate effect is that Indian legal DD is slower, more expensive, and less reliable than it needs to be. Sophisticated funds have known this for years. What has changed in 2026 is that alternative workflows actually exist.
What API-based diligence looks like
The target entity list, promoter names, related party list, and key management personnel go into an automated lookup against a national court data API. Within minutes, the output is a structured litigation profile covering every court, every state, every related party, with freshness measured in hours not weeks. The human lawyer’s job is then to read the orders and make judgments, not to chase the data.
| Dimension | PDF workflow | API workflow |
|---|---|---|
| Coverage scope | Whatever associate searches manually | National, all courts, all related parties, automatic |
| Time to first complete list | 2 to 5 days | Minutes |
| Freshness at closing | Up to 3 weeks stale | Hours stale, can re-run pre-signing |
| Cost per target | ₹2 to 5 lakh in associate time | A fraction, largely in senior review |
| Completeness risk | Moderate to high | Much lower with entity resolution |
| Audit trail | Screenshots and Excel | Structured log of every query and match |
Why the shift has not happened faster
Three reasons, all addressable.
- Habit. The PDF workflow has been the default for two decades. Senior partners learned diligence this way. Associates are trained on it. Change is slow in any professional services discipline.
- Procurement. Large law firms have procurement processes that lag behind available technology. Getting a court data API vendor through firm security and billing can take months.
- Trust. Partners want to see that the API source is authoritative, complete, and citeable. Without a track record, they default to the workflow that, whatever its flaws, they know.
These barriers fall in a predictable order. Habit falls when a specific associate on a specific deal wins time with API data. Procurement falls when the firm sees the associate hours saved. Trust falls when the data holds up over a full year of deals.
What this means for eCourtsIndia
We designed eCourtsIndia.com with deal teams in mind. Our REST API lets a DD workflow query across 37 states and union territories, 26.8 crore case records, and 29 lakh advocate profiles in a single call. The eCourts MCP extends the same capability to AI-assistant-driven DD workflows, where a senior lawyer can ask \”pull the full litigation profile of target entity X, its subsidiaries, and its promoter family\” and get a structured answer back.
Legal DD is one of the highest-stakes, most time-pressured workflows in Indian finance. It should be the first workflow to move off PDFs. The technology exists. The data exists. The only question left is whether the next deal your team closes is the last one that runs on screenshots.
If you run diligence at a fund, advisory, or law firm, you can see the API in action at eCourtsIndia.com/api-documentation. To discuss enterprise integration, reach out through the contact page.
Related reading
Sources
- Public PE and M&A practice guidance from Indian deal law firms (AZB, Trilegal, CAM, SAM, Khaitan)
- Practising Associates Reports on legal DD cost structures
- eCourtsIndia.com customer integration patterns, April 2026
Why Due Diligence Is Still Stuck in PDFs
Most Indian legal due diligence still runs on PDFs. Court orders downloaded, emailed, printed, annotated with yellow highlighter, scanned back, and attached to a data room. This workflow has not materially changed in twenty years. What has changed is that the source data is now digital and structured. The bottleneck is in the last mile from portal to report. Moving that last mile from PDF to API unlocks the next leap in due diligence speed and quality.
A typical M and A legal due diligence exercise for a mid sized Indian target takes 200 to 400 hours of associate time. A large fraction of that goes into downloading court data, reading orders, summarising them into a matrix, and checking for anything that affects valuation. With a proper API for court data, the download and summarisation steps collapse. Associates spend their time where they add the most value, on interpretation and risk assessment, rather than on data collection.
The Three Moves From PDF to API
Move one is structured search. Instead of downloading individual case PDFs and reading them sequentially, the team runs structured queries through a court data API that returns the same information in normalised form. Move two is automated summaries. Good order summaries generated by AI layers that understand legal structure accelerate the time from raw order to a partner usable note. Move three is integration with the DMS. Summaries and source links flow directly into the deal room, where the associate can annotate and partners can review.
These three moves compound. A firm that still does all three manually spends weeks on what a firm using an API driven flow does in days. Over a calendar year, the difference adds up to dozens of deals completed or a whole extra practice area staffed from the freed up hours. The firms that are quietly making this shift are the ones that clients will gravitate to for time sensitive deals. See our complementary piece on legal due diligence from PDFs to API for a fuller operational playbook.
Build or Buy
Large firms sometimes consider building their own crawl and analysis layer. This path is expensive and fragile. It distracts the firm from its core work and it binds an engineering team to maintenance of external systems that change without notice. The better path for almost every firm is to buy from a specialist. The specialist does nothing else and therefore is always ahead on coverage and reliability. The firm focuses on what it does best, which is advising clients.
For a firm that does choose to build internally, the discipline is to define a clear scope. For example, coverage of the three specific jurisdictions where the firm does most of its work, and a commitment to stop at that scope. The trouble is that scope always creeps once the team realises the rest of the portals also need coverage. This is how internal tools grow into full time infrastructure teams that were never budgeted. Buying from a trusted vendor avoids that drift.
Integration Patterns That Work
Three integration patterns keep coming up in successful implementations. First, nightly batch ingests of watched entities into the firm’s DMS. Second, on demand lookups during partner reviews so that fresh information is pulled at the moment of decision. Third, a periodic anomaly report that surfaces new matters filed against any watched party since the last check. The combination of these three keeps the firm in continuous awareness mode rather than episodic lookup mode.
Clients notice the difference. A deal partner who can answer a question about a new FIR filed against a counterparty this week, inside the meeting where the question comes up, builds credibility that no pitch deck can match. The shift from PDFs to API is not a back office efficiency. It is a client facing quality upgrade. That is the frame senior partners should use when they evaluate spend on this kind of infrastructure. Also see eCourtsIndia for a direct look at how such an integration feels in practice.