Source reading · Antler India
A reading of 19 B2B AI opportunity areas that asks, for each one, which workflow it changes, who would use it, who would pay, and whether the case depends on conditions specific to India.
This synthesis is Bharat in Beta's editorial layer. It reads Antler India's What's NEXT in B2B AI (Gowri Shankar, published 31 July 2025) as an investor perspective, not evidence that customer demand has been validated.
Healthcare, financial services, legal and real estate each bundle several jobs with different users and buyers. The software is broadly portable across markets; the harder assumption is that the person who signs off on a diagnosis, claim, contract or valuation will trust the output. The source names none of these buyers.
Sales, HR, security, developer tools, strategy and enterprise transition are global categories with clear functional buyers. The source gives no India-specific reason for them. A new product has to show a measurable change in one function faster than incumbent software can add a similar feature.
Agents that act, voice systems that speak to customers and the underlying AI stack all depend on permissions, escalation and evidence of reliability. Voice is the one entry here that the source links to Bharat as well as global markets; language and call type become the practical starting constraint.
AI-first services and manufacturing replace a provider or a process rather than adding a tool. That can make the value easier to measure, but the company then takes on licences, liability, hardware, installation or on-site support that the source does not discuss.
The source’s domestic entries for banking, healthcare, retail and government rest on affordability and Indian public programmes. The software is often the same as elsewhere. What is specific to India is the buyer’s budget, procurement, data and, for government, the programmes named in the source.
How to read the notes
Each note first names the workflow, user and likely buyer where the source supports it. It then separates the software opportunity from the adoption assumptions it depends on, such as trust in outputs, procurement or data availability, and says whether the case is specific to India or broadly portable.
The source lists sub-areas rather than customers. Where it names no buyer or workflow, the note says so instead of filling the gap. Themes that also appear in other investors' lists stay separate entries; repetition across sources is not evidence of demand.
Explore the source set
Each entry keeps Antler India's source link, author and publication date, then adds a compact review with two points on why it may matter and what the source leaves open, two possible starting points and two questions. The analysis narrows an opportunity area; it does not turn it into proven demand.
Browse all 19 entries
Bharat in Beta