$BlogRSDUrl$>
![]() |
| Cloud, Digital, SaaS, Enterprise 2.0, Enterprise Software, CIO, Social Media, Mobility, Trends, Markets, Thoughts, Technologies, Outsourcing |
ContactContact Me:sadagopan@gmail.com Linkedin Facebook Twitter Google Profile SearchResources
LabelsonlineArchives
|
Friday, June 19, 2026The Halo Is Changing: AI, Accenture, and the Reinvention of IT ServicesThere are moments in every industry when the numbers matter, but the narrative matters even more. Accenture’s recent market reaction feels like one of those moments. This is still a formidable company with global scale, trusted boardroom access, deep enterprise relationships, delivery discipline, and a long history of navigating technology transitions. It has not suddenly become weak, nor has it forgotten how to serve clients. The sharper point is that investors are now asking whether the old IT services value equation deserves the same valuation halo in an AI-native world. For decades, the global services industry carried a powerful halo. Scale was seen as strength. Headcount was seen as capability. Global delivery centers were seen as industrial muscle. Certifications, offshore leverage, utilization, partner tiers, and pyramid structures were interpreted as signs of maturity. Large transformation programs were seen as proof of customer intimacy. The ability to mobilize thousands of people across geographies became the defining proof that large services firms were indispensable to enterprise technology. That halo was not artificial. The industry earned it by helping enterprises move from mainframes to ERP, from ERP to cloud, from fragmented systems to digital platforms, and from manual operations to automated workflows. But AI is changing the lens through which the industry is being judged. That does not mean services companies are becoming irrelevant. In fact, the opposite may eventually prove true. As enterprises move from AI experimentation to AI at scale, services companies may become even more central because they sit at the intersection of technology, process, data, governance, compliance, change management, and execution. What is changing is not the relevance of services. What is changing is the measure of relevance. This is where Phil Rosenzweig’s idea of the Halo Effect becomes useful. When companies perform well, observers describe their leadership as visionary, their culture as disciplined, their people as energized, and their strategy as bold. When performance turns, the same organization is suddenly described as complacent, overexposed, bureaucratic, or strategically confused. The underlying company may not have changed in a day; the interpretation has. Performance contaminates judgment. During success, everything is covered in gold dust. During pressure, everything is seen through smoke. The services industry must avoid both extremes. The old halo said large services companies would always win because they had reach, relationships, talent, process maturity, and trusted delivery. The new reverse halo says they are vulnerable because AI will automate the work on which they depend. Both views are incomplete. IT services are not dead. Enterprises are not suddenly simple. Legacy estates remain complex. Data is still fragmented. Business processes are full of exceptions. Cyber risk is increasing. Regulatory scrutiny is rising. SaaS, cloud, data, and AI ecosystems are becoming more interconnected, not less. What is fading is not services; what is fading is the comfort of undifferentiated, labor-heavy, effort-priced services. The old IT services equation was built around effort: people multiplied by billing rates, utilization, and duration. The industry perfected this model. It industrialized talent sourcing, training, global delivery, quality processes, program management, and account mining. It became a remarkable execution engine for the enterprise world. For every major technology wave—cloud, SaaS, digital, cybersecurity, data, analytics—the answer usually involved more migration, more integration, more support, and therefore more services effort. AI is different because it does not simply create new work; it questions the unit of work itself. If a code migration that once required 200 people can be done by 40 people plus AI agents, who captures the saved value? If testing, documentation, support, configuration, process mapping, and knowledge management can be compressed dramatically, does the services firm protect the old effort model or lead the new productivity model? The right answer is clear: services firms must lead the productivity shift. Firms that help clients compress work, improve quality, reduce risk, and accelerate transformation will not lose relevance. They will move closer to the center of enterprise reinvention. One analogy may help. The traditional services model was like a large factory floor. When demand increased, you added more stations, more workers, more supervisors, more shifts, and more throughput. Scale mattered because throughput depended on coordinated human effort. The AI-native services model looks more like a power plant. The question is not how many people are standing on the floor; the question is how much energy the system generates, how efficiently it converts input into output, how reliably it runs, and how safely it operates under stress. Services companies cannot simply sprinkle AI tools across the old factory and call it reinvention. They have to redesign the machinery itself: pricing, delivery methods, workforce architecture, incentives, IP creation, governance, and client value measurement. This is why Vishal Sikka’s warning deserves attention. His argument that services-led and software companies may need radical reinvention, even potentially outside the glare of public markets, should not be read only as a call to go private. It is better understood as a call for strategic freedom. Public companies are often rewarded for quarterly stability: predictable margins, utilization, cash conversion, dividends, buybacks, and incremental growth. But AI reinvention may require bold moves that create short-term discomfort—cannibalizing legacy revenue, shrinking effort-heavy work, investing heavily in AI-native platforms, changing incentives, retraining at scale, acquiring capability rather than capacity, and accepting temporary margin pressure. The larger question is whether services companies can act with the independence and speed required to disrupt themselves before clients or competitors do it for them. The positive interpretation is that services companies are not starting from weakness. They have enormous advantages if they choose to use them differently. They understand enterprise complexity. They know how large companies actually operate. They understand messy legacy estates, regulatory constraints, process exceptions, security concerns, data fragmentation, and organizational resistance. They have relationships with CIOs, CFOs, CHROs, business heads, and transformation leaders. They know how to run programs across geographies, functions, and platforms. In an AI world, where the hardest work will be moving from pilot to production, these advantages can become even more valuable. The Netflix analogy is relevant here. Netflix did not survive because it loved DVDs. It survived because it was willing to attack the DVD model while that model was still profitable. It moved from mail-order DVDs to streaming, then from streaming distribution to original content, and then into global entertainment infrastructure. The hardest time to reinvent is not when the old model is dead; it is when the old model is still producing cash. That is where many services companies are today. The traditional model is not dead. It still produces revenue, employs millions, serves clients, and creates value. But the next model must be built before the old one visibly declines. The services industry also needs to avoid the classic mistake of judging performance only in absolute terms. A company can improve and still fall behind. Revenue can grow and still disappoint. Margins can remain healthy and still be repriced. Internal dashboards can show thousands of people trained on AI, hundreds of pilots launched, dozens of partnerships announced, and many internal productivity programs underway. But these are absolute measures. The real question is relative: are services companies moving faster than client expectations, faster than competitors, and faster than the rate at which AI is commoditizing traditional effort? This is where the measurement system must change. In the old model, the industry measured headcount, utilization, pyramid ratio, billability, certifications, bookings, revenue, margin, and delivery efficiency. Those metrics still matter, but they are no longer sufficient. The new measures must include AI-led productivity, cycle-time compression, defect reduction, autonomous resolution, reusable IP adoption, revenue from AI-native offerings, client outcomes achieved, work eliminated through automation, agent governance maturity, and value delivered per employee. The industry does not need to abandon discipline. It needs a new discipline. Another analogy helps here: the difference between a barometer and a thermostat. Many companies use AI metrics like a barometer. They report the weather: how many people were trained, how many pilots were launched, how many tools were deployed, how many partnerships were signed. That is useful, but it does not change the room. A thermostat changes the temperature. Services firms now need thermostat metrics: how much work was actually compressed, how much quality improved, how much speed increased, how much cost was avoided, how much revenue shifted to differentiated offerings, and how much measurable value was created for the client. The industry does not need more AI weather reports. It needs proof that the operating temperature has changed. The future value equation for services companies will not be people multiplied by rates. It will be intelligence multiplied by trust. The winning firms will combine domain depth, data capability, AI-native delivery, reusable IP, governance, ecosystem orchestration, and change leadership. In banking, life sciences, manufacturing, insurance, telecom, retail, healthcare, and the public sector, AI cannot be deployed safely with generic coding skills alone. It requires business context, regulatory understanding, process redesign, exception handling, auditability, security, human oversight, and measurable outcomes. AI without domain depth is like a brilliant intern: fast, impressive, and occasionally dangerous. Enterprises will still need guides, architects, integrators, and accountable transformation partners. The opportunity is for services firms to become those partners at much higher levels of value. This is why the next phase could put services companies at centerstage. The first phase of generative AI was model fascination. The second phase was pilot proliferation. The third phase will be enterprise adoption at scale. That third phase is where services companies matter most. Models alone do not transform enterprises. Copilots alone do not redesign operating models. Agents alone do not resolve data quality, security, compliance, integration, and change management. The real enterprise AI challenge is not creating impressive demos. It is making AI work reliably, safely, repeatedly, and measurably inside complex organizations. That is a services problem as much as a technology problem. The center of gravity will therefore move from “AI tools” to “AI operating models.” This is where services firms can lead. They can help clients redesign processes around agents, modernize data foundations, integrate AI into enterprise applications, build control towers for agent governance, establish human-in-the-loop models, measure productivity, manage risk, retrain workforces, and convert scattered pilots into scalable transformation programs. This is not lower-value work. It is higher-value work. But it must be priced, sold, staffed, and measured differently. There is also a human dimension to this transition. The IT services industry employs millions of people. Behind phrases like automation, productivity, compression, and AI leverage are careers, families, aspirations, and identities. Reinvention cannot simply be a financial exercise. Developers must become AI-augmented engineers. Testers must become quality architects. Business analysts must become process intelligence specialists. Project managers must become transformation orchestrators. Support teams must become automation supervisors. Domain experts must become agent trainers, model evaluators, and governance owners. The worst version of the future is AI as a blunt cost-cutting weapon. The best version is AI as a way to raise the quality, leverage, and dignity of work. The final lesson from the Halo Effect is humility. Markets overpraise during good times and overpunish during bad times. A single stock reaction does not define the destiny of a company or an industry. Accenture and other leading services firms have reinvented many times before, and it would be unwise to underestimate their ability to do so again. But it would be equally unwise to dismiss the signal. AI is forcing the services industry to justify its value in a world where intelligence is abundant, automation is accelerating, and clients are under pressure to do more with less. The old halo was built on scale. The new halo will be built on intelligent scale. The old model sold effort. The new model must sell outcomes. The old model celebrated utilization. The new model must celebrate work compression. The old model priced people. The new model must price value. The old model implemented systems. The new model must redesign work. The old model was powered by labor arbitrage. The new model will be powered by agentic leverage, domain depth, data readiness, governance, and trust. This is not the end of IT services. It may be the beginning of a more important chapter. Services companies can move to centerstage in the enterprise AI era because they are uniquely positioned to translate AI potential into enterprise reality. But to do so, they must change what they measure, what they reward, what they sell, how they deliver, and how they define value. The halo has not disappeared. It is changing. The companies that understand this will not merely survive the AI transition. They will define it. Labels: GenAI, Halo Effect, IT Services | |
| Sadagopan's Weblog on Emerging Technologies, Trends,Thoughts, Ideas & Cyberworld |