ServiceNow Commercial and Professional Services London, United Kingdom

KPMG UK

IT Operations Automation

KPMG UK needed to redesign internal IT support before renewing major managed-service contracts because routine incidents were interrupting consultants, support requests moved through multiple teams, and the firm lacked proof that a more automated model would pay off.

22 AI use cases delivered in 85 days
30% target ticket deflection
4X ROI from ServiceNow investment
85 working days from April 30 to September 1

Reported impact

Business outcome

KPMG UK achieved a 4x ROI on its ServiceNow investment, put 22 AI use cases into production in 85 working days, saved millions of pounds in renegotiated managed-service agreements, created a 24/7 multilingual support foundation, and established a live enterprise AI blueprint it now takes to clients.

  • Cost Reduction
  • Productivity Improvement
  • Speed to Market

Solution

KPMG UK treated its contract-renewal window as a chance to build an AI-first service model instead of just extending the old one. A ServiceNow IT Service Management value assessment identified where automation could reshape incident economics, after which an internal team with no previous AI experience completed an immersive sprint and launched 22 production AI use cases in 85 working days. Employees now start in Microsoft Teams, where ServiceNow AI Agents understand who they are, where they are based, and device health before resolving routine issues or routing work into the broader ITSM flow. ServiceNow Impact provided the prioritization framework, governance cadence, and architecture support that let the team scale quickly without chaos. With the old and new experiences running in parallel during rollout, KPMG gained a repeatable proof of value that not only changed vendor negotiations but also became a client-facing blueprint for enterprise AI adoption.

Data flow

Employees message a ServiceNow AI Agent in Microsoft Teams instead of navigating a portal or ticket form. Routine issues are resolved there, while more complex work flows into the redesigned IT Service Management model, and ServiceNow Impact guides the sequencing, governance, and scaling of the highest-return use cases.

Solution architecture

3 components · 3 layers
  1. Compute
    • AI Agents Resolve high-volume support requests and provide a conversational front door for employees in Teams.
  2. Orchestration
    • IT Service Management Provides the service model and value framework KPMG redesigned around AI automation.
  3. Governance
    • ServiceNow Impact Supplies prioritization, governance, and architectural support throughout the AI rollout.

Architecture clues

  • KPMG deliberately ran the old and new support models in parallel during rollout.
  • ServiceNow Impact established the governance cadence and architectural patterns for scale.
  • The new service experience starts in Microsoft Teams rather than the ServiceNow portal.

Evidence from the source

A ServiceNow IT Service Management value assessment provided the evidence, identifying how AI could transform incident management and reduce the volume of routine support requests.
In just 85 working days, from April 30 to September 1, KPMG had 22 AI use cases live in production.
Rather than navigating the ServiceNow portal, completing forms or waiting on hold, they chat directly with a ServiceNow AI Agent.
ServiceNow Impact was embedded throughout the journey, applying a use case prioritization framework to sequence the highest-return opportunities.
Those vendor negotiations reflected a fundamentally different demand profile, allowing KPMG to purchase managed services based on a much higher level of automation.
Transparency Evidence & methodology 100/100 reference value · 79% 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 value100/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 specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/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. ServiceNow

    KPMG UK customer story

    First-party
    https://www.servicenow.com/customers/kpmg-uk-ai.html
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Sitemap last modified Aug 28, 2026 · ServiceNow · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
  • Unverified extracted date Aug 28, 2026 · ServiceNow · Unknown Legacy extracted date without source-page confirmation.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.