Methodology Demonstration — LTIMindtree AI/Cloud Spend FY 2024-25

By Ravi Patel — Founder, BatchWise. Published 22 May 2026. Methodology demonstration on public data; refreshes when LTIMindtree publishes FY 2025-26 results.

Headline financial markers (FY 2024-25, publicly disclosed)

Marker	FY 2024-25 value	Source
Total revenue	₹38,008 crore / ~$4.49 billion (+7.0% YoY INR; +5% constant currency)	Q4 FY25 press release
EBIT margin	14.5%	Q4 FY25 press release
Order inflow FY25	$6 billion (+6% YoY)	Q4 FY25 press release
Client base	700+ digital transformation clients	Integrated Annual Report 2024-25
Hyperscaler Strategic Partnership Agreements	All three: AWS, GCP, Microsoft Azure	FY25 press releases + AR 2024-25
Google partnership — Agentic AI cloud transformation	Announced FY25	FY25 press release
Microsoft specialisations	10 (added/retained, including AI app development + analytics on Azure)	FY25 press release
Post-merger context	Third post-merger reporting year (LTI + Mindtree merger Nov 2022)	Public M&A history
Listings	BSE/NSE only (not US-listed)	Public
AI revenue disclosure	Not disclosed separately	Management commentary FY25

Methodology application — LTIMindtree-specific angles

Post-merger integration residue (Domains 1 + 2)

LTI + Mindtree pre-merger had largely overlapping hyperscaler partnerships, foundation model strategy, and ML tooling. Three post-merger years later, the consolidation should be largely complete but pockets of vendor + contract overlap typically persist — particularly in: (a) duplicate hyperscaler reserved-capacity commitments that pre-date the merger and were structured around individual entity volumes, (b) ML platform tooling (one of LTI vs Mindtree teams adopted the other\'s tooling but pockets retained legacy), (c) AI vendor SOWs signed by individual BUs in either pre-merger entity that didn\'t get rolled into the post-merger MSA. A methodology engagement at LTIMindtree would specifically surface integration-residual overlap — different from greenfield vendor consolidation analysis at pure-standalone peers.

L&T group cross-entity cost allocation (Domain 6)

LTIMindtree is a subsidiary of Larsen & Toubro Limited. Cross-entity AI cost allocation between LTIMindtree and L&T parent / sister entities (L&T Technology Services in engineering services; L&T itself for AI in infrastructure / construction operations) is a transfer pricing matter under Section 92 IT Act. Shared AI / cloud spend at the L&T group level allocated to LTIMindtree must satisfy arm\'s-length under OECD TP Guidelines Chapter VII. The methodology applies — public data does not enable quantification, but the framework is what an LTIMindtree CFO needs.

Hyperscaler SPA depth (Domains 2 + 3)

LTIMindtree\'s Strategic Partnership Agreements with all three hyperscalers (AWS, GCP, Azure) create both opportunity and complexity. Opportunity: portfolio negotiation leverage at scale; flexibility to route workloads to the lowest-cost-per-workload hyperscaler. Complexity: managing commitments and reserved-capacity discounts across three providers; risk of allocating spend in ways that fail to maximise any individual provider\'s tier-volume discount. A real engagement would quantify the trade-off between portfolio flexibility (multi-cloud) and concentration leverage (single-vendor commitments).

AI Spend & Tax overlay

• GST RCM on foreign AI/cloud spend — standard 18% IGST under Section 5(3) IGST Act; reconciliation against GSTR-3B Table 3.1(d) for past 24 months
• Section 195 TDS post EL 2.0 abolition (1 August 2024) — dual-regime reconciliation for FY 2024-25
• Cross-entity transfer pricing within L&T group — particularly relevant given the parent + sister-entity structure
• Post-merger transfer pricing — LTIMindtree itself has subsidiary structure across geographies; intra-group AI cost allocation persists from pre-merger periods and needs documentation review

What a peer CFO would draw from this

1. Post-merger spend rationalisation has a long tail. Three years post-merger and integration-residual vendor overlap typically persists. If your entity is mid-integration or recently emerged from an M&A, scope the AI spend rationalisation specifically as part of integration synergy capture rather than as a standalone exercise.
2. Subsidiary of a conglomerate parent creates structural TP complexity. Cross-entity cost allocation within a group is Big-4-managed at large scale, but the principles apply at any scale. If your entity is part of a larger group, scope cost allocation upstream into the engagement.
3. Multi-hyperscaler strategy is deliberate at LTIMindtree scale but accidental at smaller scale. The portfolio-vs-concentration trade-off at $4-5B revenue is different from at $0.5B revenue. Methodology framework applies; conclusions differ.

How a real engagement differs

Same as the Infosys, TCS, HCLTech demonstrations — the methodology demonstration on public data shows framework + direction; a real engagement would surface integration-residual vendor overlap, L&T group cross-entity allocation quantification, multi-hyperscaler portfolio optimisation arithmetic, and quantified RCM + TDS recovery roadmaps. Internal data access required.

For peer CFOs evaluating BatchWise AI

• AI Systems Review methodology
• AI Spend & Tax Optimisation methodology
• Schedule a discovery call

Sources

• LTIMindtree — Integrated Annual Report 2024-25
• LTIMindtree FY25 Q4 Press Release
• LTIMindtree quarterly earnings call transcripts FY 2024-25
• LTIMindtree + Google Cloud Strategic Partnership announcement (FY25)