Nilesh Shah Frames AI Risks and Opportunities for India IT

Senior market commentators led by Nilesh Shah flagged AI as both a major growth opportunity and a structural risk for the Indian IT sector, sized at about $350 billion. Shah emphasized that it is still premature to declare a definitive outcome, noting no widespread client contract cancellations to date and describing the likely shift as a drawn-out transition rather than a cliff event. He also argued that market valuations should reflect slower revenue growth, suggesting a fair multiple nearer 15 times trailing earnings versus current 19-20 times.

The practical calculus for impact centers on which parts of IT work are automatable. Shah and company managements point out that a software developer typically spends 16-20% of time writing code; the remainder is client engagement, design, requirements, and problem-solving. If AI primarily automates code generation, that points to productivity uplift and margin expansion rather than immediate headcount elimination. Key commercial parameters mentioned are:

• •Revenue growth expectation for large IT firms at 5-8% in rupee terms
• •Suggested valuation multiple at ~15 times trailing earnings
• •Current consensus multiples near 19-20 times

India's IT exporters have adapted through multiple paradigm shifts, from Y2K to cloud and SaaS. That institutional memory matters: firms can re-skill, repackage services, and tilt to higher-value outcomes. However, AI introduces a different vector because it can compress labor costs, change delivery models, and reshape how IP and platforms are valued. A valuation reset of 10-15% is plausible if consensus growth proves optimistic, which would have downstream effects on hiring plans, M&A for capability gaps, and reallocation toward productized platforms and IP-rich services.

Monitor client contracting behaviour, margin trajectories, and how vendors reprice managed services versus outcome-based, product-first offerings. Watch hiring and reskilling signals from the top-10 vendors, and whether guidance cycles and analyst models move from headcount-driven to output- or outcome-driven metrics.