How the CxO Shakeout Rewires IT Services Firms

The CxO power shakeout over agentic AI will force IT services and consulting companies to rebuild their sales, marketing, and delivery model around business executives — CFOs, COOs, CMOs — instead of the CIO and CTO organizations they have sold to for thirty years, and to staff those accounts with deep domain experts rather than technology professionals. That is the argument of this post, and I will make it bluntly: the firms that keep running the CIO playbook will watch their accounts get taken by firms that learned to sit in the CFO’s office and talk about cost per completed task.

Yesterday I published my analysis of the coming CxO power shakeout over agentic AI — the transfer of agent fleet ownership from technology leadership to the business executives whose P&L the agents touch. I wrote that post for the enterprise side of the table. This one is for my side. I spent more than twenty years inside the large IT services firms — and I can tell you the shakeout does not stop at the client’s org chart. It rewires the vendor’s entire operating model, because every one of those firms is built, top to bottom, around a buyer who is losing the budget.

The Account Model Just Lost Its Anchor

The entire commercial architecture of IT services — account leadership, client partner roles, relationship maps, the annual planning ritual — assumes one thing: the money flows through the CIO or CTO organization. Win the CIO relationship, and the account renews. That assumption held through ERP, through offshore, through cloud. It is now breaking. Futurum’s 1H 2026 survey of 838 organizations put primary AI purchasing authority with the CIO at just 13 percent, scattered the rest across CTOs, CEOs, CAIOs, CDOs, and CFOs, and titled its analysis accordingly: AI implementation is the new account control point. BCG’s AI Radar 2026 found 72 percent of CEOs calling themselves the main AI decision-maker. Bain found 83 percent of CFOs planning to raise AI budgets more than 15 percent over two years.

Read those numbers as a services executive and the conclusion is uncomfortable. Your account teams are camped outside an office that controls 13 percent of the decision. The other 87 percent is held by executives your firm has historically met twice a year, at steering committees, through the CIO’s introduction.

Sales and Marketing: From the CIO Conference Circuit to the CFO’s Reading List

What changes first is who you sell to, and therefore what you sell. A CFO who is about to directly manage a reconciliation agent fleet does not want a platform pitch. She wants to know what one completed close task costs, where the spend caps sit, who is accountable when an agent expands its own scope, and what the audit trail looks like. A COO taking ownership of claims agents wants cycle time, exception rates, and the autonomy ladder each agent sits on. These are domain conversations conducted in domain language — agentic AI is intent in, outcomes out, and the buyer now owns the intent and the outcome. The technology in the middle is your problem, not their interest.

So the seller has to change. A client partner who came up through application development cannot carry that meeting. The firms that win will put former bankers in front of banking CFOs, former claims executives in front of insurance COOs, former marketers in front of CMOs — people who ran the function before they sold to it. Marketing follows the same migration: less presence on the CIO conference circuit, more original research and benchmarks written for the business executive’s reading list. Cost per completed task by function. Autonomy readiness by industry. The kind of material a CFO forwards to her controller, not the kind a CIO files under vendor collateral.

Delivery: Domain Experts Lead, Technologists Move Into the Engine Room

Here is the part I suspect the industry will resist longest. For three decades, delivery leadership on large engagements has belonged to technology professionals — program managers who grew up in code, architecture, and integration. That made sense when the deliverable was a system. It stops making sense when the deliverable is a business outcome produced by an agent fleet that a CFO or COO personally manages. The stakeholder the engagement lead answers to every week is now a business executive, and a delivery lead who can hold a room on Kubernetes but not on credit policy cannot hold that relationship. I have seen this up close in my work in regulated loan origination: the hardest questions in an agent deployment — which exceptions escalate, where the autonomy boundary sits, what an acceptable error rate is on a decision that touches a borrower — are credit and operations questions. A technologist can implement the answer. Only a domain expert can supply it and defend it to the executive who owns the risk.

So the engagement structure inverts. Domain consultants — lending, claims, supply chain, marketing operations — lead the account, own the stakeholder relationship, and translate executive intent into agent specifications. Technology professionals move into the engine room: platform, agent identity, execution boundaries, observability. Still essential. No longer in front. This accelerates the pyramid-to-diamond shift I have been writing about for some time — the labor pyramid of a few partners atop thousands of junior technologists collapses when agents do the junior technical work, and what remains scarce, and billable, is seasoned domain judgment. Firms staffed 80 percent technologists and 20 percent domain experts will need something closer to the reverse at the client-facing layer. That is not a reskilling memo. That is a different hiring engine, a different career ladder, and a different pitch to campus and lateral talent.

The Trio: Where the Services Firm Actually Fits Now

None of this makes the CIO irrelevant, and services firms should not act as if it does. The client-side model that emerges from the shakeout is a trio, and the vendor’s durable position is the bridge in the middle of it:

The business CxO sets the intent, owns the outcome metric and the P&L, and directly manages the agent fleet touching their function — the reconciliation agents, the claims agents, the campaign agents.
The CIO/CTO organization provides the platform, the agent identity layer, the execution boundaries, and the governance controls every business-owned fleet runs on — working with the business CxO internally rather than above them.
The services firm becomes the bridge between the two: domain experts facing the business CxO, technology experts facing the CIO organization, and a shared governance language holding the trio together.

That bridge role is not a consolation prize. It may be the most defensible position a services firm has held in years, because the two client-side parties genuinely struggle to talk to each other. Across my library of 315 public enterprise agentic AI case studies, the deployments that reached production value almost always had a business-side owner — and the ones that stalled were technology-led programs hunting for a sponsor. The gap between those two outcomes is exactly the gap a translator gets paid to close.

Five Moves for Services Firms to Make Now

Re-map every strategic account around the business CxO. For each major client, name the CFO, COO, and CMO relationships you hold directly — not through the CIO’s introduction. Where the answer is none, that account is exposed.
Hire domain operators, not just more architects. Recruit executives who ran lending, claims, supply chain, or marketing before joining your firm, and put them in account leadership and delivery leadership — roles that carry the client relationship, not advisory sidecars.
Rebuild delivery around outcome ownership. Every agent engagement gets a domain lead accountable to the business CxO for the outcome metric and a technology lead accountable to the CIO organization for the controls. Two leads, one engagement, mirroring the client’s trio.
Market in the business buyer’s language. Publish cost-per-completed-task benchmarks, autonomy readiness assessments, and function-specific outcome data. A CFO who cites your research in a board deck is worth fifty CIO-event sponsorships.
Sell the governance bridge explicitly. Package the translator role — joint autonomy review boards, separation of duties between autonomy grants and spend controls, finance at the autonomy gate — as an offering with a name and a price, because that is the service the trio cannot function without.

The Question for Your Next Account Review

The offshore wave rewarded firms that industrialized delivery. The cloud wave rewarded firms that retooled fastest. This wave will reward the firms that change who they talk to and whom they send for meetings. So ask one question at your next account review: on our top ten accounts, how many CFO, COO, or CMO relationships do we own directly, and how many of our engagement leads could survive thirty minutes alone with that executive? If the honest answer is the CIO knows us and our delivery leads speak technology — the shakeout has already priced your firm, and it has not priced it kindly. The practitioner’s guide to running agentic AI programs on the intent-in, outcomes-out model is in my book Intent In, Outcomes Out.

Dr. Harish Kotadia, Ph.D., is an Enterprise AI Architect with 20+ years of IT consulting experience serving Fortune 100 clients, specializing in agentic AI systems for regulated enterprise environments, including loan origination.

Disclaimer: This blog post is based on survey findings and news items drawn from reputed media and analyst sources available in the public domain and cited above. It is intended for educational purposes, to help IT services and consulting leaders think through the organizational implications of enterprise agentic AI. Views and opinions expressed here are my own and do not represent those of any employer or client, past or present. The analysis presented is my independent interpretation of the published reports cited above and does not constitute legal, financial, or consulting advice of any kind.