<h2>Key Takeaways</h2>
<ul>
<li>Barclays, HSBC and Standard Chartered, three of the UK&#8217;s largest banking groups, have all built AI-driven fraud and financial-crime detection systems, but the quality and independence of what each has actually disclosed about those systems varies enormously, and a UK C-suite comparing them should notice the gap in evidence as much as the technology itself.</li>
<li>HSBC&#8217;s is the best-documented of the three. A dated, on-the-record press release from Google Cloud, quoting HSBC&#8217;s own Group Head of Financial Crime Risk and Compliance, states that its AML AI system detects 2 to 4 times more true positive risk than HSBC&#8217;s previous approach, while cutting alert volumes by more than 60% and reducing processing time for billions of transactions from several weeks to a few days. HSBC also won Celent&#8217;s Model Risk Manager of the Year award in 2023 after deploying it, a genuine third-party validation rather than a vendor&#8217;s own claim.</li>
<li>Barclays&#8217; account, published as a named customer story by database vendor Aerospike, is about infrastructure performance rather than AI accuracy specifically: its fraud platform now handles more than 10 million transactions a day, four times its previous throughput, at under 100 milliseconds latency for 99.99% of requests, an 80% latency reduction, while the underlying fraud dataset grew from 3 terabytes to more than 30 terabytes in three years without a system redesign. Those are real, named-executive-attributed figures about the data layer that makes Barclays&#8217; fraud models workable at scale, not a disclosed accuracy or false-positive figure for the models themselves.</li>
<li>Standard Chartered was the earliest mover of the three, becoming the first global bank to deploy AI vendor Silent Eight&#8217;s platform in its sanctions compliance operations in July 2018, confirmed in Standard Chartered&#8217;s own press release. But that release contains no performance figures at all. The widely cited claim that Silent Eight&#8217;s platform cuts manual investigation time by up to 70% is the vendor&#8217;s own general marketing figure, not one Standard Chartered has itself confirmed applies to its deployment, and it&#8217;s worth reading with that distinction in mind. Standard Chartered&#8217;s venture arm, SC Ventures, also invested in Silent Eight&#8217;s 2019 funding round, making the bank both a customer and a financial backer of its own AI supplier.</li>
<li>None of this means Standard Chartered&#8217;s or Barclays&#8217; systems work less well than HSBC&#8217;s, only that HSBC has published independently verifiable outcomes and the other two, so far, largely haven&#8217;t. For a UK C-suite benchmarking its own fraud AI investment, the more useful comparison isn&#8217;t which bank&#8217;s number sounds most impressive. It&#8217;s which bank&#8217;s claims are actually checkable, and HSBC is currently the only one of the three that clears that bar.</li>
</ul>
<p>Ask three UK banking groups how their AI fraud detection performs, and you&#8217;ll get three very different kinds of answer:</p>
<p>One with a dated press release, a named executive and an independent industry award behind it.</p>
<p>One told through a database vendor&#8217;s customer story, rich with named-executive infrastructure numbers but silent on the fraud model&#8217;s actual accuracy, and one confirmed only in outline, its most-quoted performance figure belonging to the vendor rather than the bank.</p>
<p>All three are real deployments. Only one of them is genuinely easy to independently verify.</p>
<h2>HSBC: the best-documented of the three</h2>
<p>HSBC&#8217;s system, built on Google Cloud&#8217;s AML AI product and internally named Dynamic Risk Assessment, is the most thoroughly disclosed of the three banks&#8217; AI financial-crime systems.</p>
<p>According to a <a href="https://www.googlecloudpresscorner.com/2023-06-21-Google-Cloud-Launches-AI-Powered-Anti-Money-Laundering-Product-for-Financial-Institutions?ref=lucinity.ghost.io" target="_blank" rel="nofollow noopener">press release Google Cloud published</a> on 21 June 2023, the system detects 2 to 4 times more true positive risk than HSBC&#8217;s prior transaction-monitoring approach, while cutting overall alert volumes, the flagged transactions that then require a human analyst&#8217;s time, by more than 60%.</p>
<p>HSBC monitors around 4 billion transactions a year across its customer base, and Google Cloud&#8217;s release says the system cut the batch processing time needed to analyse billions of transactions across millions of accounts from several weeks down to a few days. &#8220;Google&#8217;s models are already demonstrating the tremendous potential of machine learning to transform anti-financial crime efforts in the industry at large,&#8221; said Jennifer Calvery, HSBC&#8217;s Group Head of Financial Crime Risk and Compliance, in the release.</p>
<p>HSBC went on to receive <a href="https://www.celent.com/en/awards" target="_blank" rel="nofollow noopener">Celent&#8217;s Model Risk Manager</a> of the Year award in 2023 after adopting the system as its primary transaction-monitoring approach in key markets, an independent industry recognition that sits alongside, rather than merely repeating, the bank&#8217;s own figures.</p>
<h2>Barclays: real numbers, but about the data layer, not the model</h2>
<p>Barclays&#8217; publicly available account of its fraud AI comes from a different kind of source: a named customer case study published by Aerospike, the real-time database vendor whose technology underpins Barclays&#8217; fraud platform.</p>
<p>Dheeraj Mudgil, Barclays&#8217; VP Enterprise Fraud Architect, is quoted directly: the platform gave Barclays &#8220;quick access to large datasets with one hop to the data from the client and the predictability we needed for our fraud platform.&#8221; The figures in that case study are concrete and specific: Barclays&#8217; fraud platform now processes more than 10 million transactions a day, four times the throughput of its previous system, at under 100 milliseconds&#8217; latency for 99.99% of transactions, an 80% reduction in latency compared with the prior architecture.</p>
<p>The underlying fraud dataset grew from 3 terabytes to more than 30 terabytes over three years without requiring a redesign of the system&#8217;s architecture or caching layer. Aerospike&#8217;s case study says the resulting consolidation reduced stand-in processing and improved fraud outcomes by lowering both false positives and false negatives, though it gives no specific percentage for either.</p>
<p>What&#8217;s worth being precise about is what this case study actually is: a real-time data infrastructure story, told by the database company that supplies that infrastructure, about the plumbing that lets Barclays&#8217; fraud detection models run fast enough and on enough data to be useful at scale. It says nothing, in the material available, about how accurate Barclays&#8217; actual fraud-detection models are, what algorithms they use, or how their outputs compare with the system they replaced. That&#8217;s a materially different, narrower kind of evidence than HSBC&#8217;s, even though both are, in their own ways, genuine and specific.</p>
<h2>Standard Chartered: first to deploy, least to disclose</h2>
<p>Standard Chartered has the longest track record of the three. On 9 July 2018, the bank announced it had become the first global financial institution to deploy AI vendor Silent Eight&#8217;s platform, which applies machine learning and natural language processing to sanctions and watchlist name-screening, matching customer names against watchlists using fuzzy logic and learning from the historical decisions of Standard Chartered&#8217;s own analysts. &#8220;I am very pleased with this investment which is contributing significantly to the Bank&#8217;s innovation agenda,&#8221; said Markus Schulz, Standard Chartered&#8217;s Global Head of FCC Controls, in the announcement, adding that the tool was meant to &#8220;empower our teams to make more effective and efficient decisions, complementing the core monitoring and screening platforms that we have already established.&#8221; Standard Chartered&#8217;s own press release contains no performance figures at all, no time saving, no accuracy improvement, no volume figure.</p>
<p>The number most often attached to this story, that Silent Eight&#8217;s platform cuts manual investigation time by up to 70%, comes from Silent Eight&#8217;s own marketing material, not from a Standard Chartered disclosure confirming that figure applies to its specific deployment. That distinction matters and is worth stating plainly rather than letting the two blur together, the way most retellings of this story do. There&#8217;s also a governance detail worth a UK C-suite&#8217;s attention: Standard Chartered&#8217;s corporate venture arm, SC Ventures, participated in Silent Eight&#8217;s $6.2 million Series A funding round in November 2019, more than a year after the original deployment. That makes Standard Chartered simultaneously a customer of and a financial stakeholder in the company supplying part of its financial-crime AI, a relationship that isn&#8217;t inherently improper, corporate venture arms invest in vendors they use fairly often, but is exactly the kind of detail a board should want surfaced and understood, not left implicit.</p>
<h2>What a UK C-suite should actually take from this</h2>
<p>All three of these are genuine, multi-year AI deployments at major UK banking groups, and none of the gaps described here are evidence that Barclays&#8217; or Standard Chartered&#8217;s systems perform worse than HSBC&#8217;s. What differs, starkly, is the quality of publicly available evidence behind each one. HSBC&#8217;s account comes with a dated release, a named senior compliance executive, specific before-and-after figures, and an independent industry award. Barclays&#8217; comes with real, named-executive-attributed numbers, but about data infrastructure throughput rather than fraud-model accuracy, published by the vendor supplying that infrastructure. Standard Chartered&#8217;s comes with a confirmed deployment date and a named executive&#8217;s general endorsement, but its most-cited performance figure belongs to the vendor&#8217;s marketing, not the bank&#8217;s own disclosure. For a board benchmarking its own AI fraud investment against any of the three, the useful exercise isn&#8217;t ranking whose numbers sound biggest. It&#8217;s asking, of your own programme, whether the evidence you&#8217;d eventually publish about it would meet the HSBC standard, an independently checkable, dated, specifically-attributed outcome, or whether it would look more like the other two: real, but resting on someone else&#8217;s word.</p>


Fraud Detection AI at Barclays, HSBC and Standard Chartered: Only One of Them Has Actually Proven It Works

<h2>Key Takeaways</h2>
<ul>
<li>Six UK universities&#8217; published infrastructure case studies, at <a rel="nofollow" href="https://www.networksjournal.com/content/university-of-leicester-backup-storage-consolidation">Leicester</a>, <a rel="nofollow" href="https://www.networksjournal.com/content/royal-holloway-university-hpe-dhci-refresh">Royal Holloway</a>, <a rel="nofollow" href="https://www.networksjournal.com/content/birmingham-city-university-work-area-recovery-centre">Birmingham City</a> and <a rel="nofollow" href="https://www.networksjournal.com/content/cranfield-university-nutanix-hci-original-deployment">Cranfield</a>, share a pattern: none of them modernised proactively. Every one of the four was forced into the decision by something external, a departing member of staff, a lease running out, a building earmarked for redevelopment, or a seasonal capacity crunch, and the modernisation followed as a consequence, not a strategic choice made in isolation.</li>
<li>At the University of Leicester, that trigger was fear rather than a specific failure. Systems Specialist Mark Penny described a backup architecture where losing a single media server could have knocked out backup and restore access &#8220;for potentially weeks,&#8221; a risk that never actually materialised but drove the university to replace ten individual media servers with <a rel="nofollow" href="https://www.networksjournal.com/content/university-of-leicester-backup-storage-consolidation">a shared Cloudian object storage platform</a>, cutting rack space in half.</li>
<li>A second Leicester project shows the same institution hitting the identical pattern twice. The university&#8217;s <a rel="nofollow" href="https://www.networksjournal.com/content/university-of-leicester-high-availability-storage-failover">load balancers</a> had been &#8220;built years earlier on open-source software by technicians who had since left the university,&#8221; Penny said, leaving a system nobody still on staff fully understood. The replacement wasn&#8217;t a strategic upgrade; it was a response to institutional memory walking out the door.</li>
<li>Royal Holloway and Cranfield were both driven by harder deadlines. Royal Holloway&#8217;s legacy hardware carried &#8220;various legacy dependencies&#8221; that made routine support difficult while raising energy costs, and it moved to <a rel="nofollow" href="https://www.networksjournal.com/content/royal-holloway-university-hpe-dhci-refresh">HPE dHCI under a consumption-based GreenLake model</a>, cutting its data centre footprint 75% and energy use more than 72%. Cranfield&#8217;s original decision came from hardware, licence and support contracts approaching renewal at the same time one of its two data centre buildings was scheduled for redevelopment, forcing the question rather than inviting it.</li>
<li>For a UK C-suite, the useful pattern across these four case studies isn&#8217;t which vendor or platform they chose, Cloudian, HPE, Nutanix, all appear once. It&#8217;s that each institution&#8217;s own account describes the trigger as external and largely outside its control, and that the resulting projects still delivered large, measured gains, 50% space savings, 75% footprint reduction, 80% less time spent on infrastructure management, once forced. The lesson isn&#8217;t to wait for a crisis. It&#8217;s that a board reviewing its own infrastructure roadmap should ask which of its systems are quietly waiting on the same kind of external trigger, a departing engineer, an expiring lease, a contract renewal, rather than assuming it will choose the moment itself.</li>
</ul>
<p>Read individually, these are six unremarkable-sounding infrastructure stories: a university replaces some servers, another moves to the cloud, a third builds a backup site. Read together, four of them, at Leicester, Royal Holloway, Cranfield and Birmingham City, tell an identical story about why the decision actually got made, and it&#8217;s rarely the reason the resulting case study headline suggests. The other two, Oxford and Kingston, are useful precisely because they don&#8217;t fit the pattern, and the difference is worth naming.</p>
<h2>Leicester, twice: what happens when the person who built it leaves</h2>
<p>The <a rel="nofollow" href="https://www.networksjournal.com/content/university-of-leicester-backup-storage-consolidation">University of Leicester&#8217;s</a> first infrastructure overhaul wasn&#8217;t triggered by a failure. It was triggered by the university recognising how bad a plausible failure would be. Under its previous architecture, ten media servers each individually maintained backup and index data on SAN-based hardware; losing any one of them could have meant weeks without backup or restore access for the devices it served. &#8220;We wouldn&#8217;t be able to continue backing up data, access backups or conduct restores until we replaced the hardware and spun up the system again, a process which could have taken weeks. Fortunately, we never faced this situation, but we knew we had to make a change,&#8221; said Mark Penny, the university&#8217;s Systems Specialist. Leicester replaced the setup with Cloudian HyperStore object storage across 12 HPE Apollo servers, cutting the rack space needed for 2.5 petabytes of usable storage from 48U to 24U, a 50% saving, chosen over an open-source alternative and a more expensive commercial rival partly because Penny could install and test it himself on a laptop in 15 minutes.</p>
<p>The university&#8217;s <a rel="nofollow" href="https://www.networksjournal.com/content/university-of-leicester-high-availability-storage-failover">second, related project</a> shows the same forcing pattern playing out again, almost immediately after the first. Having replaced the storage layer, Leicester still needed load balancers reliable enough to keep it running, and its existing ones were &#8220;home-grown, built years earlier on open-source software by technicians who had since left the university,&#8221; in this publication&#8217;s own account, leaving a system nobody currently on staff could confidently maintain. Penny ran a proof of concept with Cloudian&#8217;s HyperBalance appliances and didn&#8217;t look further: &#8220;We were impressed by how easy it was to set up the load balancer solution and get going&#8230; We didn&#8217;t look at anything else.&#8221; The result now balances traffic across 15 HPE Apollo servers, handling 3.3 gigabytes of storage per second at peak without measurable performance loss. Two separate Leicester projects, two separate forcing events, neither one a proactive strategic decision made on the university&#8217;s own timetable.</p>
<h2>Royal Holloway and Cranfield: deadlines set by leases and buildings, not by IT strategy</h2>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/royal-holloway-university-hpe-dhci-refresh">Royal Holloway University of London&#8217;s</a> legacy infrastructure had accumulated &#8220;generations of hardware with various legacy dependencies,&#8221; making day-to-day management harder than it needed to be while a large data centre footprint drove rising energy costs, in the university&#8217;s own description of the problem. Working with Wavenet and HPE, Royal Holloway replaced it with a virtual infrastructure platform under HPE&#8217;s consumption-based GreenLake model, cutting its data centre footprint by 75%, its VMware socket count by 85%, and its energy use by more than 72%. &#8220;A modern, world-class university needs server infrastructure future-proofed for the cloud age,&#8221; said Zoë Faiz, the university&#8217;s Assistant IT Director.</p>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/cranfield-university-nutanix-hci-original-deployment">Cranfield University&#8217;s</a> original decision had an even more concrete deadline attached. Its intensive IT needs had been running on two ageing data centres built on traditional three-tier server architecture, with hardware, software licences and support contracts approaching renewal at the same time one of the two buildings was scheduled for redevelopment. &#8220;We took this opportunity to look at the whole infrastructure stack and all the overheads the servers brought from a management point of view,&#8221; said Edward Poll, Cranfield&#8217;s Head of IT Infrastructure. Working with CDW, the university moved to a Nutanix hyperconverged platform, chosen specifically for its flexibility to incorporate VMware and adapt to future financial and technical change. Cranfield&#8217;s relationship with that same setup continued into a <a rel="nofollow" href="https://www.networksjournal.com/content/cranfield-university-nutanix-hci-refresh-2024">2024 technology refresh</a>, this time on a rolling four-year cycle the university maintains deliberately rather than reactively, completed in four weeks with no user downtime and sustaining the 80% reduction in infrastructure management time the original deployment had already delivered.</p>
<h2>Birmingham City University: the trigger was a calendar, not a crisis</h2>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/birmingham-city-university-work-area-recovery-centre">Birmingham City University&#8217;s</a> version of this pattern is the clearest example that the forcing event doesn&#8217;t have to be a technology failure at all. BCU&#8217;s largest annual opportunity to fill course places is its clearing period, a predictable, recurring calendar event that nonetheless required robust infrastructure to handle a surge in student applications without downtime. The university had previously used a seasonal hot-standby facility from Wavenet, staffed for 200 contact centre workers during clearing, and chose to convert it into a permanent, year-round work area recovery centre securing around half a petabyte of data across 400 virtual machines. &#8220;Having Wavenet as our partner means everything,&#8221; said Matt Peers, BCU&#8217;s Senior Project Manager. &#8220;The inclusion of work area recovery is essential for continuous and trusted connections during clearing.&#8221; The initial engagement led to a five-year contract, and the trigger, in this case, was entirely predictable and recurring rather than an emergency, which is itself a useful variant of the same underlying pattern: a known, calendared pressure point forcing a decision that a general sense of &#8220;we should modernise&#8221; never quite had.</p>
<h2>Oxford and Kingston: the same broad category, and neither one fits</h2>
<p>Two other university Microsoft 365 case studies this publication has covered, at <a rel="nofollow" href="https://www.networksjournal.com/content/university-of-oxford-microsoft-365-governance-architecture">the University of Oxford</a> and <a rel="nofollow" href="https://www.networksjournal.com/content/kingston-university-microsoft-365-data-migration">Kingston University</a>, sit under the same general &#8220;university IT overhaul&#8221; umbrella as the four above, and deliberately don&#8217;t share the forcing-event pattern. Oxford&#8217;s Microsoft 365 governance project was driven by an organisational reality, a decentralised federation of 39 colleges needing local autonomy within a coherent central structure, not a departing engineer or an expiring lease. Kingston&#8217;s data migration was driven by data volume and disruption risk, a genuinely large, ongoing logistics problem rather than a single triggering event. Neither university&#8217;s own account describes a forced hand the way Leicester&#8217;s, Royal Holloway&#8217;s, Cranfield&#8217;s or Birmingham City&#8217;s do. That&#8217;s a useful negative case: not every university IT project in this publication&#8217;s archive was reactive, which makes the four that were stand out more clearly as a real pattern rather than something true of university IT projects generally.</p>
<h2>What a UK C-suite should actually take from reading these six together</h2>
<p>The pattern worth taking from this isn&#8217;t that reactive infrastructure decisions turn out badly, all four forced projects here delivered large, specifically measured improvements once undertaken. It&#8217;s that four separate UK universities&#8217; own published accounts each independently describe the same structure: a real, often quantifiable improvement that only happened because something external forced the timing, a person leaving, a lease or contract expiring, a building being redeveloped, a calendared seasonal peak. None of the four case studies describe an infrastructure team identifying the opportunity on its own initiative ahead of that trigger. For a UK board reviewing its own technology estate, the practical question these six case studies together suggest isn&#8217;t whether to modernise, it&#8217;s which systems are currently being kept running only because nothing has yet forced the decision, the equivalent of Leicester&#8217;s departed technicians&#8217; home-grown load balancer, quietly working until the person who understood it was no longer there to ask.</p>


The Common Thread in University IT Projects

<h2>Key Takeaways</h2>
<ul>
<li>Klarna&#8217;s AI customer service story is really two announcements eighteen months apart, and a UK C-suite should read both, not just the first one that went viral. In February 2024, Klarna said its OpenAI-built assistant handled 2.3 million conversations in its first month, doing the equivalent work of 700 full-time agents, cutting resolution time from 11 minutes to under 2, and was projected to add $40 million to 2024 profit.</li>
<li>By May 2025, chief executive Sebastian Siemiatkowski told Bloomberg the strategy had gone too far. &#8220;We focused too much on efficiency and cost,&#8221; he said. &#8220;The result was lower quality, and that&#8217;s not sustainable.&#8221; Klarna started recruiting human customer service agents again, on flexible, remote, gig-style contracts.</li>
<li>The headcount numbers are genuinely mixed, and worth reading precisely rather than as a clean before-and-after. Klarna&#8217;s workforce fell from roughly 5,000 to almost 3,000 employees, about 40%, but Siemiatkowski himself credited much of that to ordinary staff attrition, which he put at 15 to 20% a year, not to the AI system directly replacing people.</li>
<li>The AI didn&#8217;t get switched off. As of the May 2025 reversal, it was still handling two-thirds of all customer inquiries, response times were 82% faster than before the AI launched, and repeat contact rates were still down 25%. What changed was where the company drew the line between what AI should handle and what a person should.</li>
<li>Klarna reversed its AI-first messaging five months before pricing a $1.37 billion IPO on the New York Stock Exchange in September 2025 at a $15.11 billion valuation, itself a steep comedown from the more than $45 billion the company was valued at in 2021. For a UK C-suite, the lesson isn&#8217;t that Klarna&#8217;s AI failed. It&#8217;s that a cost-driven AI rollout and a customer-quality AI rollout are different projects with different failure modes, and Klarna ran the first one before realising it needed the second.</li>
</ul>
<p>Klarna&#8217;s AI customer service assistant is the most cited AI case study in enterprise circles for a reason: it is one of the few with a genuinely public, multi-year arc, a triumphant launch, a candid reversal, and enough concrete numbers at each stage to actually compare. Most AI case studies a UK C-suite reads are either brand-new and unproven or old enough that no one is still checking the follow-up. Klarna&#8217;s is neither. It has been checked, restated and partly walked back by its own chief executive, on the record, twice.</p>
<h2>What Klarna actually announced in February 2024</h2>
<p>Klarna&#8217;s AI assistant, built in partnership with OpenAI, went live globally in Klarna&#8217;s app in February 2024. In a press release dated 27 February 2024, Klarna said the assistant had handled 2.3 million conversations in its first month, two-thirds of Klarna&#8217;s total customer service chat volume, work the company said was equivalent to that of 700 full-time human agents.</p>
<p>Average resolution time fell from 11 minutes to under 2, and repeat customer inquiries, people re-contacting support because their issue hadn&#8217;t actually been resolved, dropped 25%.</p>
<p>Klarna said the assistant was on par with human agents on customer satisfaction scores, available around the clock in 23 markets, and could communicate in more than 35 languages. The company estimated the assistant would drive a $40 million improvement to 2024 profit. &#8220;This AI breakthrough in customer interaction means superior experiences for our customers at better prices,&#8221; said Sebastian Siemiatkowski, Klarna&#8217;s co-founder and chief executive, in the announcement.</p>
<p>OpenAI&#8217;s own chief operating officer, Brad Lightcap, called Klarna &#8220;at the very forefront among our partners in AI adoption and practical application.&#8221;</p>
<h2>The hiring freeze nobody outside the company saw happen in real time</h2>
<p>What followed the launch wasn&#8217;t publicised with the same fanfare. In a Bloomberg Television interview reported in December 2024, Siemiatkowski said Klarna had effectively stopped hiring around a year earlier as the AI system took on more of the workload, with headcount falling 22%, to roughly 3,500 employees, over that period, driven mostly by natural attrition rather than layoffs.</p>
<p>That framing matters: Klarna didn&#8217;t announce mass redundancies tied to the AI launch. It quietly stopped backfilling roles as people left, and let the AI system absorb the resulting gap in customer service capacity.</p>
<h2>May 2025: the reversal, in Siemiatkowski&#8217;s own words</h2>
<p>By May 2025, in another Bloomberg interview reported by trade publication CX Dive and others, Siemiatkowski said the strategy had gone further than it should have. &#8220;We focused too much on efficiency and cost,&#8221; he said. &#8220;The result was lower quality, and that&#8217;s not sustainable.&#8221; He was specific about what he thought the company had got wrong: not that AI itself was the mistake, but that Klarna had let cost-cutting outrun the customer experience it owed people who needed genuinely human help. &#8220;I just think it&#8217;s so critical that you are clear to your customer that there will always be a human if you want,&#8221; he told Bloomberg, adding, &#8220;Really investing in the quality of the human support is the way of the future for us.&#8221; Klarna began recruiting customer service staff again, piloting what CX Dive described as an &#8220;Uber-type&#8221; flexible, remote, gig-style arrangement aimed at &#8220;highly educated students, professionals and entrepreneurs&#8221;, with one stated goal being to bring in-house some of the customer service work Klarna had previously outsourced to third-party contractors, rather than simply re-hiring for the original 700 roles the AI had absorbed.</p>
<p>Separately, in a CNBC interview around the same time, Siemiatkowski gave the fuller headcount picture: Klarna&#8217;s total workforce had fallen from about 5,000 to almost 3,000 employees, a roughly 40% reduction.</p>
<p>But he was careful not to credit all of that to the AI system directly. &#8220;Natural attrition in a company like ours is 15-20% per year, so we shrink naturally 15-20% by people just leaving,&#8221; he said, framing the AI&#8217;s role as enabling the company to not backfill those departures rather than actively cutting jobs itself.</p>
<p>That distinction, between AI-enabled attrition and AI-driven layoffs, is one most retellings of the Klarna story flatten, and it&#8217;s a materially different claim about what the technology actually did.</p>
<h2>The AI didn&#8217;t get switched off. The target changed.</h2>
<p>The detail most useful to a UK C-suite is what didn&#8217;t change in May 2025: the AI assistant was still handling roughly two-thirds of all customer inquiries even after Siemiatkowski&#8217;s public reversal, CX Dive reported, with response times still 82% faster than before the assistant launched and repeat contact rates still down 25%. Klarna didn&#8217;t retreat from AI-handled customer service as a category.</p>
<p>It retreated from treating &#8220;AI handles it&#8221; as sufficient for every kind of interaction, and rebuilt a deliberate lane for cases, complex disputes, financial hardship, anything where getting it wrong costs a customer real money or trust, that get routed to a person instead of resolved end-to-end by the assistant.</p>
<p>The rollout&#8217;s actual failure mode wasn&#8217;t that the AI performed badly against the metrics Klarna originally chose to measure. It was that those metrics, speed and average satisfaction, didn&#8217;t capture whether harder, lower-volume, higher-stakes cases were being handled well.</p>
<h2>The timing a UK C-suite shouldn&#8217;t miss</h2>
<p>Context that rarely makes it into the Klarna story: the May 2025 reversal came five months before Klarna priced its US initial public offering. Klarna listed on the New York Stock Exchange under the ticker KLAR in September 2025, pricing shares at $40 and raising $1.37 billion at a $15.11 billion valuation, a real recovery from the roughly $6.7 billion trough Klarna&#8217;s valuation fell to in 2022, but still a steep comedown from the more than $45 billion it commanded at its 2021 peak.</p>
<p>A company preparing to go public in 2025, after a valuation collapse, had every commercial incentive to tell an aggressive cost-efficiency story through 2024, and then to be seen correcting course on customer quality before investors started asking pointed questions about churn and brand damage.</p>
<p>None of that makes Siemiatkowski&#8217;s admission untrue. It&#8217;s a reasonable, evidence-based reading of why the timing looked the way it did.</p>
<h2>What a UK C-suite should actually take from this</h2>
<p>Klarna&#8217;s AI assistant did what Klarna said it did in February 2024: handled millions of routine conversations faster and, on the metrics Klarna chose to track, at least as well as the humans it replaced.</p>
<p>That part of the story holds up. What failed wasn&#8217;t the AI&#8217;s competence at the task it was measured against; it was the decision to let a cost and efficiency target stand in for a customer-quality target, and to let that substitution run for the better part of a year, through a hiring freeze and a real headcount reduction, before correcting it in public.</p>
<p>For a board weighing its own AI-driven customer service plans, the specific, transferable lesson isn&#8217;t &#8220;AI customer service doesn&#8217;t work,&#8221; which the two-thirds figure that survived the reversal directly contradicts.</p>
<p>It&#8217;s that the metrics chosen to declare an AI rollout a success will determine what gets missed, and that a board should decide, before launch, which failure it would rather catch early: a bad quarter of efficiency numbers, or a public reversal after a year of customers quietly getting worse service than they were promised.</p>


Klarna Cut 700 Jobs’ Worth of Work With AI. Its CEO Now Says That Was the Mistake

<h2>Key Takeaways</h2>
<ul>
<li>Twelve AI deployments published on this site reduce to three real categories: internal knowledge retrieval, customer- or citizen-facing communication, and narrower plain-language interfaces over an existing system.</li>
<li>The largest, most specific results came from the narrowest, most rules-based tasks, such as Amey&#8217;s bid-writing time falling from four days to 30 minutes.</li>
<li>Four of the twelve, moinAI, contexxt.ai, Yepic.AI and Policy-Insider.AI, all run on OVHcloud infrastructure specifically for GDPR and European data-sovereignty reasons.</li>
<li>Jaguar Land Rover&#8217;s case study describes a roadmap and a secured business case rather than a finished, measured deployment, unlike the other eleven.</li>
<li>Across the set, the size and specificity of a reported result tracks how narrow and well-bounded the automated task was, not how ambitious the AI project sounded.</li>
</ul>
<h2>TLDR</h2>
<ul>
<li>Twelve AI deployments published on this site, spanning automotive engineering, water utilities, infrastructure services, legal tech, aged care, local government, customer chat, enterprise knowledge search, generative video and public-affairs monitoring, describe a narrower range of actual mechanisms than the industry variety suggests. Most are built to solve one of two problems: finding information that already existed but was too slow to locate, or communicating with a customer or citizen faster than a human team could manage alone.</li>
<li>The clearest, most repeatedly measured successes cluster around document-heavy, rules-based tasks. Amey&#8217;s bid-writing platform cut drafting time from four days to 30 minutes; an unnamed Dynamiq legal client cut contract review from 1.5 hours to 45 minutes; Anglian Water cut manual governance effort by up to 6,000 hours a year. In each case, the AI was retrieving and structuring information a human already had the standing to evaluate, not making a new judgement call.</li>
<li>A distinct European vendor cluster runs through four of the twelve deployments, moinAI, contexxt.ai, Yepic.AI and Policy-Insider.AI, all built on OVHcloud infrastructure specifically because of GDPR and data-sovereignty requirements their customers demanded. None of the four cite performance or cost as the primary reason for that infrastructure choice; all four cite European hosting as close to non-negotiable.</li>
<li>Not every case study reports a completed, measured result. Jaguar Land Rover&#8217;s engagement describes a roadmap and a secured business case, not a deployed tool with a time saving attached, a genuinely different, earlier stage of the same underlying problem the other eleven case studies describe as finished.</li>
<li>For a UK C-suite, the practical value of reading these twelve together isn&#8217;t a list of AI success stories to imitate individually. It&#8217;s the pattern underneath them: the deployments with the clearest, most defensible results all automated a narrow, well-bounded, previously manual task, and the ones with the vaguest results were the ones asked to do more than that.</li>
</ul>
<p>Twelve AI case studies published on this site look, on the surface, like twelve unrelated stories about twelve unrelated organisations. Read together, in their own words, they describe a much smaller number of actual problems being solved, and a genuinely useful pattern in which of those problems produced results specific enough to trust.</p>
<h2>Twelve deployments, and what each one was actually built to do</h2>
<p>At <a rel="nofollow" href="https://www.networksjournal.com/content/jaguar-land-rover-ai-investment-roadmap-engineering">Jaguar Land Rover</a>, the problem was strategic rather than operational: building a business case for a new, data-driven engineering operating model and prioritising which AI use cases were worth pursuing across a 16,000-strong engineering workforce. Aiimi applied its AI Strategy Framework to build a roadmap measured against impact, feasibility, affordability and enterprise alignment, and separately extended Enterprise Search over JLR&#8217;s product engineering documentation. &#8220;They helped us show where data and AI could make a real difference to engineering, aligning that to business value and shaping an AI roadmap that builds momentum quickly,&#8221; said Dave Hird, JLR&#8217;s Head of Data Driven Engineering &#038; AI.</p>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/anglian-water-asset-document-governance-automation">Anglian Water</a> solved a related but more advanced version of the same problem. Asset and site documentation was scattered across physical &#8220;blue boxes,&#8221; shared drives and specialist applications; manual audits consumed up to 17,000 hours per cycle, and inspectors repeatedly flagged document control issues because field teams couldn&#8217;t reliably find current information on site. Aiimi&#8217;s Virtual Blue Box automatically classifies and tags documents across all 7,000 of the utility&#8217;s sites, running continuous compliance checks. &#8220;By harnessing the capabilities of Machine Learning and Natural Language Processing, it addresses critical challenges faced by technicians in having access to the most relevant and latest information when they&#8217;re on-site and need it most,&#8221; said Stuart Rawdon, Anglian Water&#8217;s Enterprise Content Governance Manager.</p>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/amey-generative-ai-knowledge-platform-bid-writing">Amey</a> had &#8220;decades of asset management expertise&#8221; locked inside individual silos rather than something anyone could quickly search, according to this publication&#8217;s own account. FOIL built Gennie, a generative AI knowledge platform integrated into Amey&#8217;s Microsoft ecosystem. &#8220;We have this vast, deep experience of how we manage assets for our clients. What if you could bring together all of that knowledge and make it searchable and instantaneous?&#8221; said Rob Curley, Amey&#8217;s Project Director.</p>
<p>An unnamed client of <a rel="nofollow" href="https://www.networksjournal.com/content/dynamiq-ai-legal-agent-contract-review">Dynamiq</a> faced the same shape of problem inside a legal department: reviewing thousands of contracts and regulatory documents on tight timelines while relying on costly outside counsel to fill the gaps. Dynamiq built an AI legal agent on the IBM watsonx platform. &#8220;IBM watsonx.data provides a very robust platform for integrating and embedding proprietary client data for AI agents,&#8221; said Vitalii Duk, Dynamiq&#8217;s founder and chief executive.</p>
<p>At <a rel="nofollow" href="https://www.networksjournal.com/content/regis-aged-care-generative-ai-clinical-handover">Regis Aged Care</a>, Australia&#8217;s largest residential aged care provider, clinicians spent two to three hours per shift reviewing more than 200 pages of clinical notes during handovers. Cognizant built a generative AI assistant on Microsoft Copilot Studio, benchmarked against senior clinician standards throughout development. &#8220;Be ambitious about the question you want answered. Don&#8217;t limit yourself in terms of what you think is possible,&#8221; said Imtiaz Bhayat, Regis Aged Care&#8217;s Chief Information Officer.</p>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/ferndown-town-council-decisions-ai-meetings">Ferndown Town Council</a> moved the same underlying idea into local government: a Clerk previously managing agenda preparation and action tracking entirely by hand adopted GovMeetings, a platform powered by Decisions AI. &#8220;Decisions AI has completely reshaped how we run our meetings. It&#8217;s efficient, professional, and intuitive,&#8221; said Liz Bishopp, the council&#8217;s Clerk.</p>
<p>The remaining six deployments move away from internal knowledge retrieval into customer- and citizen-facing communication, and generative content. <a rel="nofollow" href="https://www.networksjournal.com/content/moinai-secures-german-health-insurer-chats-with-eu-based-managed-databases">moinAI</a>, a Hamburg-founded chatbot company serving more than 100 German customers including major insurers, processes several million customer interactions a year. &#8220;Our customers, particularly in the German health sector and SMEs, require the strictest data protection and security standards, and prefer a provider based in Germany or Europe,&#8221; said Florian Nommensen, moinAI&#8217;s Managing Director and CTO.</p>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/contexxt-ai-generative-ai-knowledge-platform">contexxt.ai</a>, a DeepTech startup founded within an academic setting in 2023, built its Sesame platform on a zero-knowledge architecture so that neither it nor its cloud provider can access customer data being processed. &#8220;Research shows we spend up to two hours a day searching for information. Sesame gives that time back,&#8221; said founder and chief executive Torsten Katthöfer.</p>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/yepic-ai-generates-1-million-videos-on-high-end-gpu-cloud-instances">Yepic.AI</a> builds generative AI video and voice translation technology. &#8220;Twenty-five million Americans don&#8217;t speak English, and in the UK nearly 1 million people can&#8217;t speak English well enough to access healthcare without an interpreter,&#8221; said Aaron Jones, the company&#8217;s CEO, framing the tool as an access problem rather than a productivity one.</p>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/policy-insider-ai-processes-5000-daily-policy-documents-on-gdpr-compliant-public-cloud">Policy-Insider.AI</a> processes around 5,000 new political documents a day across more than 40 institutions and 8,000 daily social media posts from over 4,000 policymakers, replacing manual monitoring of public policy across languages and borders. &#8220;The availability of powerful CPU and latest GPU architectures&#8230; is crucial to our platform effectively handling AI workloads,&#8221; said Agata Chudzinska, the company&#8217;s co-founder and Head of AI.</p>
<p><a rel="nofollow" href="https://www.networksjournal.com/content/velotix-ai-assistant-development-time-compliance">Velotix</a> embedded a conversational assistant into its data access platform so users could manage compliance policy in plain language rather than through specialist tooling. &#8220;With AI supporting natural language queries, we give users the freedom to stay focused on their work, while intelligent policy enforcement runs silently in the background,&#8221; said Yoram Segal, the company&#8217;s Chief Technology Officer and Chief AI Officer.</p>
<p>And at <a rel="nofollow" href="https://www.networksjournal.com/content/akzonobel-corporate-event-app-guest-communication">AkzoNobel</a>, the problem was smaller in scale but familiar in shape: fragmented guest communication at corporate events, information scattered across emails and PDFs. QuantumXL built an AI-powered guest app. &#8220;They really listened to the brief and delivered above and beyond,&#8221; said Tina Waller, AkzoNobel&#8217;s Events Manager.</p>
<h2>Comparisons of the projects</h2>
<p>Laid side by side, these twelve deployments split cleanly into three categories rather than twelve unique stories. Six, Jaguar Land Rover, Anglian Water, Amey, Dynamiq&#8217;s client, Regis Aged Care and Ferndown Town Council, are internal knowledge-retrieval tools: AI built to find, summarise or structure information a human employee already had standing to use, just not quickly. Four, moinAI, contexxt.ai, Yepic.AI and Policy-Insider.AI, are customer- or public-facing communication and content tools, chat, translation, video and document monitoring, aimed outward rather than at internal process. Velotix and AkzoNobel sit closer to the first group in mechanism, plain-language interfaces over an existing system, but serve narrower, more specific functions, data compliance and event logistics respectively, than the broader knowledge-retrieval cluster.</p>
<p>A distinct vendor pattern runs through the outward-facing cluster specifically: moinAI, contexxt.ai, Yepic.AI and Policy-Insider.AI are all built on OVHcloud infrastructure, and all four cite the same reason, GDPR compliance and European data sovereignty, rather than raw performance or cost, as the deciding factor. contexxt.ai&#8217;s Torsten Katthöfer put it most directly: &#8220;We were looking for a partner that thinks and acts with an European mindset.&#8221; That&#8217;s a genuinely different kind of infrastructure decision than the internal-tooling cluster made: Dynamiq&#8217;s client and Velotix both chose IBM&#8217;s watsonx platform specifically for enterprise integration and on-premises deployment flexibility for regulated finance and healthcare clients, while Aiimi&#8217;s two clients, Jaguar Land Rover and Anglian Water, and FOIL&#8217;s client, Amey, chose their vendors for domain-specific knowledge architecture rather than infrastructure sovereignty at all.</p>
<p>The clearest outlier among the twelve is Jaguar Land Rover, and it&#8217;s worth reading as a genuine methodological control rather than a weaker result. Every other case study in this set reports a completed deployment with a measured outcome attached. JLR&#8217;s reports a secured business case, leadership buy-in and use cases &#8220;moving into active development,&#8221; a roadmap-stage engagement rather than a finished one. That&#8217;s not a flaw in the case study; it&#8217;s evidence the other eleven organisations had already passed the stage JLR was still working through when this publication&#8217;s account of its project was written.</p>
<h2>Successes</h2>
<p>Where these case studies report a measured result, the results are large and specific rather than vague. Amey&#8217;s bid drafting time fell from four days to 30 minutes, a 95% reduction, with 80% of tender content now generated through the platform and, in the organisation&#8217;s own account, 100% of previously siloed institutional knowledge retained rather than lost to staff turnover. Dynamiq&#8217;s client cut contract review time from 1.5 hours to 45 minutes, cut the time to answer business queries from two days to 60 minutes, and cut clause identification from 20 minutes to two. Anglian Water&#8217;s Virtual Blue Box cuts manual governance effort by up to 6,000 hours a year, delivered zero minor risks in a subsequent BSI audit, reduced Environment Agency and EPA visit actions by 40%, and is estimated to avoid up to £450,000 in annual costs. Regis Aged Care cut clinical handover review from two to three hours down to under one, with zero hallucinations recorded during trials and nearly 60% of users engaging with the assistant daily or several times a week. Ferndown Town Council cut meeting preparation time by 40%.</p>
<p>Velotix&#8217;s result is the most dramatic in relative terms: a conversational assistant that would otherwise have taken six months or more to build launched in one month, an 80%-plus reduction in development time, with an expected 60 to 70% cut in compliance costs and up to 95% fewer manual tasks. Yepic.AI&#8217;s growth figures are the clearest commercial validation in the set: Yepic Studio generated 1 million videos, and the company&#8217;s monthly revenue grew from $2,000 to $50,000 within five months. AkzoNobel&#8217;s app achieved adoption rates above 95%, and Policy-Insider.AI now handles roughly 100,000 queries a day at peak, scaling with major political events rather than breaking under them. Across all eleven completed deployments in this set, not one reports a negative or null result; where a case study is candid about a gap, as Amey&#8217;s and Dynamiq&#8217;s client&#8217;s accounts are about the absence of any downside mentioned at all, that absence is itself worth reading cautiously rather than as proof nothing went wrong.</p>
<h2>Things to learn</h2>
<p>The first lesson from reading these twelve together is that the size of the result tracks the narrowness of the problem, not the ambition of the AI. The deployments with the largest, most specific, most confidently reported numbers, Amey, Dynamiq&#8217;s client, Anglian Water, Velotix, all automated a single, well-bounded task with a clear existing correct answer: a bid response format, a contract clause, a compliance policy, an audit record. The deployments with output that&#8217;s harder to verify independently, generative video, chatbot conversation quality, event-app satisfaction, report adoption and growth figures rather than accuracy or time-saved figures, because there often isn&#8217;t a single correct answer to measure against.</p>
<p>The second lesson is that infrastructure choices in this set were rarely about the AI model itself. Four companies chose the same cloud provider for the same non-technical reason, GDPR and data sovereignty, and two chose IBM&#8217;s watsonx platform for enterprise integration and on-premises flexibility rather than model quality. A board evaluating a vendor for a similar deployment should expect the infrastructure conversation to be dominated by compliance and integration requirements specific to its own regulatory environment, not a comparison of model benchmarks.</p>
<p>The third lesson is the one Jaguar Land Rover&#8217;s case study makes visible by not fitting the pattern of the other eleven: a roadmap-and-business-case stage is a legitimate, necessary part of an AI programme, not a sign of a stalled one, and a board should expect its own early-stage AI initiatives to look like JLR&#8217;s account rather than Amey&#8217;s or Velotix&#8217;s finished numbers. Reading a roadmap-stage case study against a completed-deployment one as though they represent the same level of achievement is exactly the kind of imprecise comparison that makes AI case studies less useful than they should be, and precisely the comparison a UK C-suite should avoid making when it reviews its own AI programme&#8217;s progress against outside examples.</p>


Twelve AI Deployments Compared: What Networks Journal’s Own Case Study Archive Actually Shows

<h2>Key Takeaways</h2>
<ul>
<li>Lockheed Martin, KPMG and Nationwide Building Society, a defence contractor, a professional services firm and a UK financial mutual, all sequenced their <a rel="nofollow" href="https://www.networksjournal.com/ai">AI</a> programmes the same way: consolidate and govern the underlying data first, then build AI on top of it. That pattern held across three organisations with almost nothing else in common, which is itself worth taking seriously.</li>
<li>Lockheed Martin&#8217;s own published pilot numbers are worth reading precisely rather than as an unqualified success: an early generative AI question-answering system improved from 45.45% response accuracy to 56.8% with prompt engineering and to 66.0% after further query optimisation. Against general, inexact industry benchmarks for enterprise retrieval-augmented Q&#038;A systems, which commonly range from roughly 60% to the mid-80s depending on task and tuning, though no single authoritative figure exists, 66% sits at the lower-to-middle end, a credible, improving, honestly reported result rather than a standout one.</li>
<li>KPMG&#8217;s case study contains no quantified outcome at all, but the underlying confidentiality stakes are real and specific, not generic: professional codes including the ICAEW Code of Ethics impose a standing duty of client confidentiality that survives the end of an engagement, and ICAEW&#8217;s own technical guidance requires firms to actively manage conflicts of interest, precisely the risk an AI system with poorly controlled access across many clients&#8217; data could create if access controls aren&#8217;t built first.</li>
<li>Two of the three, Lockheed Martin and Nationwide Building Society, built their governance layer with <a rel="nofollow" href="https://www.ibm.com/solutions/artificial-intelligence">IBM</a>, whose watsonx.governance platform was independently named a Leader in 2025&#8217;s Gartner Magic Quadrant, Forrester Wave and IDC MarketScape for AI governance platforms, a genuine, analyst-confirmed market position distinct from the consumer-facing model providers, <a rel="nofollow" href="https://openai.com/solutions/">OpenAI</a>, Anthropic, Google, that dominate headlines but don&#8217;t compete in this specific governance-platform category.</li>
<li>Context worth holding onto throughout: MIT&#8217;s NANDA research group reported in August 2025 that 95% of enterprise generative AI pilots deliver no measurable return on investment, and only 5% reach production. Judged against that backdrop, all three organisations here, imperfect, still-in-progress results included, are already ahead of where most enterprise AI efforts currently stall.</li>
</ul>
<p>Three organisations with almost nothing in common, a defence and aerospace contractor, a Big Four professional services firm, and a UK building society, arrived at the identical sequencing decision for their AI programmes: govern and consolidate the data first, then build on top of it. That&#8217;s a genuinely useful pattern for a UK C-suite to notice, and it&#8217;s worth reading each of the three cases precisely, including where the published numbers are modest rather than triumphant, rather than treating every AI case study as either a success story or a cautionary tale.</p>
<h2>Lockheed Martin: real numbers, honestly modest</h2>
<p>Lockheed Martin, the global aerospace and defence company, had valuable data locked away across 46 disparate systems spanning multiple data lakes, data management, analytics and business intelligence tools, making it difficult to put that data to consistent use across the enterprise. &#8220;Data is the foundational element by which we pull everything together across the enterprise,&#8221; said Stephan Gerali, Chief Architect and Senior Fellow at Lockheed Martin. Working with IBM, Lockheed Martin replaced those 46 systems with a single, connected and accessible data environment built on IBM watsonx.data, along with watsonx.data integration and intelligence tools. With a unified, scalable data foundation in place, the company built out a broader AI ecosystem, culminating in the Lockheed Martin AI Factory, a secure environment where 10,000 engineers build, iterate on and deploy AI solutions at scale, accelerated by IBM Granite open AI models. Agentic frameworks and virtual agents developed inside the AI Factory, powered by watsonx.governance and watsonx Orchestrate, now help manage complex workflows including handling HR-related inquiries through natural language. &#8220;We&#8217;re getting closer each day to a data-driven culture where folks can take the data they have and immediately make use of it,&#8221; Gerali said.</p>
<p>The specific figure worth reading carefully: in an early generative AI question-answering pilot, response accuracy rose from 45.45% to 56.8% with prompt engineering, and to 66.0% after query optimisation. That&#8217;s a real, transparently reported improvement, and it&#8217;s worth being honest about where 66% actually sits. Enterprise retrieval-augmented Q&#038;A systems commonly report accuracy figures ranging from roughly 60% up into the mid-80s depending on the task and how heavily the system has been tuned; there&#8217;s no single authoritative industry-wide benchmark, figures vary hugely by domain and evaluation method, but against that general spread, 66% reads as a credible, still-improving result at the lower-to-middle end, not a standout one. That&#8217;s not a criticism of Lockheed Martin&#8217;s disclosure, if anything the opposite: publishing an honest, incrementally improving figure rather than a rounded-up success number is precisely the kind of transparency a defence contractor&#8217;s own governance context would predict. The US Department of Defense adopted five formal AI Ethical Principles in February 2020, Responsible, Equitable, Traceable, Reliable and Governable, developed by the Defense Innovation Board, followed by a 2021 implementation plan and specific AI ethics guidance for contractors from the Defense Innovation Unit. That framework applies across a defence contractor&#8217;s AI use generally, not only to weapons systems, which is a plausible, if not explicitly stated, part of why Lockheed Martin&#8217;s own account of this pilot reads as a careful progress report rather than a marketing claim.</p>
<h2>KPMG: no number at all, and a genuinely specific reason the governance mattered first</h2>
<p>KPMG, one of the Big Four professional services firms, needed better mechanisms for securing sensitive information across a complex data estate while maintaining regulatory compliance and data governance standards, and wanted its consultants to be able to access valuable insights safely rather than being blocked by fragmented controls. Following a successful pilot, KPMG signed a three-year engagement with Aiimi to deploy its AI-powered Workplace AI platform, helping the firm classify, refine and govern its data landscape. The platform lets teams identify, secure and intelligently classify data while respecting retention rules, access controls and client obligations. &#8220;To have trust in AI outputs you must first have trust in your underlying data. The Aiimi platform gives us that trust,&#8221; said Chris Allen, Chief Data Officer at KPMG UK. The three-year engagement gives KPMG a structured foundation for governing its data estate as it scales its data and AI ambitions across the firm.</p>
<p>Unlike Lockheed Martin, KPMG&#8217;s case study contains no quantified outcome whatsoever, no accuracy figure, no time saving, no cost reduction. That&#8217;s worth naming plainly rather than filling in with assumption. What&#8217;s genuinely worth understanding, though, is why the governance-first sequencing wasn&#8217;t optional for a firm like KPMG in a way that goes beyond generic caution. Professional codes governing accountancy and professional services firms, including the ICAEW Code of Ethics, impose a standing duty of client confidentiality that survives the end of a specific engagement, and ICAEW&#8217;s own technical guidance specifically requires firms to identify and actively manage conflicts of interest. For a firm serving competing clients simultaneously, an AI system with poorly controlled access isn&#8217;t a hypothetical risk, it&#8217;s precisely the mechanism through which one client&#8217;s confidential information could inadvertently inform work product delivered to a competitor. That&#8217;s a real, citable, professional-standards basis for KPMG&#8217;s approach, not just sound general practice, and it&#8217;s a more specific reason to build access controls before scaling AI than the case study itself spells out.</p>
<h2>Nationwide: the third data point in the same pattern</h2>
<p>Nationwide Building Society took the same sequencing approach at a third kind of institution again, a UK financial mutual rather than a defence contractor or a professional services firm, building an AI Centre of Expertise with IBM Consulting and Microsoft Azure OpenAI Service before scaling deployment, a case study this publication has examined in detail elsewhere, including the real, separately-reported improvement in customer letter response times that emerged after the original case study&#8217;s governance-first framing, alongside Nationwide&#8217;s own acknowledgement, reported separately, that broader return on investment across its wider AI rollout remains difficult to quantify. The relevant point for this comparison is narrower: Nationwide is the third organisation in this set to build the governance layer before the measured result, reinforcing rather than complicating the pattern visible at Lockheed Martin and KPMG.</p>
<h2>The vendor pattern worth naming plainly</h2>
<p>Two of these three organisations, Lockheed Martin and Nationwide Building Society, built their governance layer specifically with IBM, either directly through watsonx.governance or via IBM Consulting. That&#8217;s not incidental: IBM&#8217;s watsonx.governance platform was independently named a Leader in Gartner&#8217;s first AI Governance Platforms Magic Quadrant, The Forrester Wave for AI Governance Solutions, and the IDC MarketScape for Unified AI Governance Platforms, all in 2025, a genuine, three-firm analyst consensus specifically in the enterprise AI governance category, distinct from the consumer-facing model providers, OpenAI, Anthropic, Google, that dominate general AI coverage but don&#8217;t compete in this particular governance-platform space at all. KPMG&#8217;s approach with Aiimi sits outside that specific IBM pattern, a reminder that &#8220;governance-first&#8221; is a genuine cross-industry principle, not proof that every large enterprise is converging on identical vendor infrastructure to get there.</p>
<h2>What a UK C-suite should actually take from all three</h2>
<p>The most useful context for reading any of these three case studies is one none of them state directly: MIT&#8217;s NANDA research group reported in August 2025 that 95% of enterprise generative AI pilots deliver no measurable return on investment, and only 5% ever reach production. Against that backdrop, Lockheed Martin&#8217;s honestly modest 66% accuracy figure, KPMG&#8217;s unquantified but professionally well-justified governance build, and Nationwide&#8217;s governance-first sequencing followed by a real, if partial, measured result, are not underwhelming stories. They&#8217;re evidence of three organisations that got further than the overwhelming majority of enterprises currently attempting the same thing, precisely because each one treated the unglamorous data and governance work as the actual project, rather than a delay before the real one began. For a board weighing its own AI investment, the specific lesson isn&#8217;t which vendor to pick or which sector to imitate. It&#8217;s that the sequencing itself, data and governance before scale, appears to be the genuine differentiator, and that a case study reporting a modest, improving number is, on the evidence here, a better sign than one reporting no number and claiming full success.</p>
