Chapter 10 · The Atlas

Vendor Cohort Distribution.

Five categories. No end-to-end integrator.

The workstream catalogued every vendor referenced across the thirty-three phases of research. The total reached two hundred sixty-three named operators, distributed across five structurally distinct categories. The distribution is not the headline finding. The structural observation underneath the distribution is: no single category plays the end-to-end integrator role. The market is functionally segmented. The integrator engagement is the structural gap.

Vendor Cohort · Five Categories Across Thirty-Three Research Phases
Hyperscaler · cloud and compute
12
Model provider · frontier LLM and foundation models
18
Strategy consultancy · advisory and transformation
14
Systems integrator · implementation and operate
24
Specialist AI firm · vertical and use-case-specific
195

Vendor counts are approximate and aggregated across the thirty-three research phases. A single vendor can appear in more than one phase; counts reflect distinct-vendor inclusions in vendor landscapes.

The five categories and what each does not do

The hyperscaler category — Microsoft Azure, Amazon Web Services, Google Cloud, Oracle Cloud Infrastructure, Alibaba Cloud, and the regional clouds — provides compute, storage, security, and increasingly the foundation-model layer. The category does not own the function-vertical design problem. The hyperscaler arrives with a platform and a set of horizontal services; the design of the AI surface inside the operating function is downstream of the platform.

The model-provider category — OpenAI, Anthropic, Google DeepMind, Mistral, Cohere, Meta AI, AI21, and the analogous frontier-model cohort — provides the underlying generative AI capability. The category does not own the data architecture, the function-vertical integration, or the change-management discipline. The model is a primitive. The deployment is a separate problem.

The strategy-consultancy category — McKinsey, BCG, Bain, Deloitte Consulting, PwC Strategy&, EY-Parthenon, Accenture Strategy, Roland Berger, Kearney — provides the strategy layer. The category does not own the implementation surface in the depth required for production deployment. The strategic recommendation is a starting point; the operating-function integration is downstream.

The systems-integrator category — Accenture, Tata Consultancy Services, Infosys, Wipro, Cognizant, Capgemini, IBM Consulting, NTT Data, HCL, LTIMindtree — provides the implementation surface. The category does not own the strategy layer, the vendor-neutral procurement filter, or the engagement-architecture discipline required to absorb the cautionary cohort. The integrator depth on a specific industry surface is also frequently shallower than the specialist depth in the same surface.

The specialist-AI category is the largest category by count. One hundred ninety-five named operators across thirty-three phases. The category contains the deepest production references in nearly every use case. The category does not own the cross-function integration. A specialist runs deep on one surface and shallow on the surrounding architecture; the integrator engagement is what connects the specialist depth into the operating function.

The structural observation

No single vendor category plays the end-to-end integrator role with the nine-function shape that crosses strategy, infrastructure, AI management, technology selection, function-vertical design and implementation, training, performance measurement, realignment, and business-as-usual operation. The market is functionally segmented along the five categories. An end-to-end integrator must work across all five categories with vendor neutrality as a structural property. The integrator's competitive case is not depth on any one of the five categories. It is the engagement architecture that absorbs the five categories into a single function-vertical deployment.

The implication for the senior executive reader is procurement-architecture-specific. The default procurement model — select a strategy consultancy for the strategic layer, a hyperscaler for the platform, a systems integrator for the build, and a specialist for the use case — produces a four-vendor stack with no single accountable end-to-end owner. The cautionary cohort in Section Eight is concentrated in operators that ran this default model. The integrator engagement is the alternative procurement architecture.