EY Commercial and Professional Services global

EY

EY needed to respond to rapid generative AI disruption across its own business, but scattered proofs of concept, skill gaps, decentralized operations and fast-changing regulatory expectations made it difficult to turn experimentation into a coordinated, trustworthy enterprise transformation.

US$1.4 billion investment in an extensive transformation program

Reported impact

Business outcome

EY moved from fragmented experimentation toward a governed enterprise AI operating model that let teams test internal deployments, close skills gaps, centralize technology decisions and scale LLM-enabled work more confidently across the firm.

  • Productivity Improvement
  • Risk Reduction
  • Scalability
  • Speed to Market

Solution

EY treated itself as "Client Zero" and reorganized its own transformation around enterprise AI. The program built on strategic acquisitions and a prior shift to cloud and consolidated data systems, then mapped AI use cases directly to business goals and the firm-wide value chain so investment would not be wasted on isolated pilots. EY centralized AI technology consumption, data and systems integration, and developer tooling to create a common foundation for large language model adoption across business functions. Advanced tools and platforms accelerated the AI development lifecycle, while the EY responsible AI framework, firm-wide AI definitions and updated risk processes provided governance for ethical use, information security and data privacy. In parallel, targeted upskilling and change management helped employees integrate LLM-enabled workflows into day-to-day work at global scale.

Data flow

EY mapped priority AI use cases to business goals, routed data and systems into a centralized cloud-based foundation, and used advanced tooling to integrate LLM capabilities into employee workflows. Governance definitions, responsible AI controls and updated risk processes then governed how those AI-enabled workflows were developed, deployed and scaled across the organization.

Solution architecture

5 components · 4 layers
  1. Compute
    • large language models (LLMs) Provide the core generative AI capability that EY sought to integrate into daily workflows across the firm.
  2. Storage
    • cloud and consolidated data systems Supply the centralized data and systems base that let EY scale AI adoption across business functions.
  3. Orchestration
    • advanced tools and platforms Accelerate the AI development lifecycle so teams can move from proofs of concept to repeatable delivery.
    • AI infrastructure Supports firm-wide technology consumption and integration as AI moves into core operations.
  4. Governance
    • EY responsible AI framework Defines governance, ethical guardrails and risk controls for enterprise AI deployment.

Architecture clues

  • AI use cases were mapped to business goals and the full EY value chain before scaling.
  • Developers used advanced tools and platforms to accelerate the AI development lifecycle.
  • Firm-wide AI definitions and the EY responsible AI framework were used to align governance, risk and deployment.
  • The transformation built on a prior shift to cloud and consolidated data systems.

Evidence from the source

"By acting as our own 'Client Zero' and testing AI deployments internally, EY is determining answers to these questions now."
"Developers were empowered with advanced tools and platforms to accelerate the AI development lifecycle."
"EY responded to the AI disruption swiftly and accordingly, allocating an initial US$1.4 billion investment in an extensive transformation program with humans at the center."
"The transformation team recognized the need to bridge skill and knowledge gaps, particularly in integrating large language models (LLMs) into daily workflows."
Transparency Evidence & methodology 71/100 reference value · 83% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value71/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence83%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency10/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. EY

    Case study: How EY transformed itself with AI | EY - Global

    First-party
    https://www.ey.com/en_gl/insights/ai/case-study-how-ey-transformed-with-ai
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Industry
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • Business outcome
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Jan 15, 2025 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source