Indian legaltech funding jumped sharply in 2025. Cumulative venture capital into the category crossed the $793 million mark across 86 funded companies, according to Tracxn data, with 2025 itself adding more than 700 percent year-on-year growth in deployed capital. Most of that money went to the same three categories: AI drafting, AI research, and contract intelligence.
This post is about the categories the capital has not yet found.
We are identifying three whitespace plays where the market is structurally open, the buyer is definable, and a founder with the right assets can build a category-defining company over the next thirty-six months. None of these are speculative. All three have ready buyers today.
Play 1: Structured court data APIs for the enterprise
The opportunity. Background verification firms, banks, non-banking finance companies, insurers, and corporate compliance teams all need litigation data on specific parties, and none of them have a clean way to get it at scale. The dominant workflow in 2026 is a human analyst manually searching eCourts, saving screenshots, and writing a narrative report. Cost per check ranges from ₹150 to ₹600, turnaround is measured in hours to days, and error rates are high because entity resolution is being done by eye.
The buyer is already spending. The Indian BGV market alone was estimated at over ₹1,500 crore in annual revenue in 2024, growing at roughly 12 to 15 percent per year. A structured court data API does not create a new budget line. It replaces an existing one, with better unit economics.
Why now. Three things converged in the last 24 months. Court data coverage at Layer 2 crossed the threshold where API-first products become viable (26.8 crore records and counting on eCourtsIndia). AI-assisted entity resolution is cheap enough to run at every query. And RBI’s tightened due-diligence expectations on lenders have raised the cost of getting a litigation check wrong.
What a winner looks like. A developer-first product with a clean REST API, 100 ms response times, entity-resolved results, and transparent coverage reporting. Pricing in the ₹2 to ₹10 per query band, with enterprise contracts in the ₹20 lakh to ₹1 crore range. Integration into BGV platforms, loan origination systems, and vendor onboarding flows.
Who could build it. Only operators already sitting on Layer 2 court data infrastructure. Starting from zero requires 18 to 24 months of data engineering before the first API call ships.
Play 2: Litigation intelligence for lenders
The opportunity. Banks and NBFCs write lakhs of loans a month. For each one, they check CIBIL, PAN, GST, and now, increasingly, litigation exposure. A pending suit, a pending recovery case, or a history as a respondent in financial-fraud litigation materially changes underwriting risk. Today this check is either skipped, done cursorily at origination, or outsourced to a vendor who returns a PDF three days later.
What the product looks like. A continuous monitoring service. At origination, pull a full litigation history on borrower and guarantors, normalised into a risk score. After disbursement, monitor the same entities for new case filings. Alert the lender when a new matter is filed within a defined window. Price per portfolio rather than per query.
Why now. RBI’s Digital Lending Directions and tightened early-warning signal frameworks make continuous monitoring a compliance-driven purchase, not a nice-to-have. The ecosystem has no clear market leader today. A well-executed vertical product targeting NBFCs and fintech lenders could reach 50+ customers within 18 months.
Adjacent use cases. The same data layer supports insurance underwriting (fraud history on claimants), corporate vendor risk (pending disputes on vendors), and M&A data-room assembly (target litigation summary in 24 hours instead of 4 weeks).
Play 3: Vernacular legal AI for the 80 percent
The opportunity. Roughly 1.6 million of India’s approximately 2 million enrolled advocates practise at district and subordinate courts. Most of them do not work in English. Their drafting, their client communication, and increasingly their orders are in Hindi, Tamil, Marathi, Bengali, Telugu, Kannada, Gujarati, Punjabi, Malayalam, and other scheduled languages. The entire English-first AI stack skips this market.
What the product looks like. An AI copilot that drafts, summarises, and cross-references in the advocate’s own language. Reads scanned Hindi orders. Produces Marathi written replies. Understands local practice conventions. Pricing needs to be designed for the district-court lawyer, not the senior counsel: a ₹200 to ₹500 per month price point, freemium up front, SMS-ready alerts.
Why now. Three forces. Open-weight Indic LLMs are good enough in 2026 to handle legal-domain tasks with reasonable fine-tuning. Phase III of the eCourts project is explicitly funding translation of judgments into Indian languages. And mobile data costs in Tier-2 and Tier-3 India make an always-on legal assistant viable for the first time.
What makes this hard. Data. A vernacular legal AI needs vernacular training data at scale, which is scarce. The moat is whoever ingests and cleans district-court orders in Indian languages first. This is a Layer 2 problem dressed as a Layer 4 product.
The common thread
All three plays share a structural feature. Each depends on a rich, structured, well-maintained court data layer underneath. An API product without reliable ingestion is vapourware. A litigation intelligence product without entity resolution misidentifies borrowers. A vernacular AI without trial-court orders in Indic languages has nothing to learn from.
The operator who builds the data layer well will find that the three plays above arrive on its doorstep, not because they chose to partner, but because the alternative is impractical.
What this means for eCourtsIndia
We are building the data layer that all three plays will depend on. Our API is already in use by teams exploring Play 1 and Play 2. Play 3 is the farthest horizon, and also the one we care most about, because it serves the 80 percent of Indian advocates that the current legaltech stack has ignored.
If you are a founder building in any of these three lanes, or a fund writing a cheque into one of them, we would like to hear what you are working on.
Explore eCourtsIndia data for your own whitespace play: ecourtsindia.com/search. API access: ecourtsindia.com.
Related reading
- Mapping India’s Court Data Stack: From NJDG to APIs to AI Agents
- Inside eCourts: How India Digitised 29,600 Courts
Sources
- Tracxn, 2025: Legaltech India Funding Summary.
- Grand View Research, 2024: India Legal AI Market Report.
- Ken Research, 2024: India BGV and RegTech Outlook.
- Reserve Bank of India: Digital Lending Directions, 2022 and subsequent circulars.
- Bar Council of India: Enrolment statistics.