JPMorgan recovered 360,000 hours a year with more than 450 AI use cases. The five categories, the operating discipline and five clear moves for UK finance.
Link copied
A bank's CIO pauses mid-talk on stage and says: "We have 450 AI use cases, all of them in production." The room goes quiet.
That scene happened. The disclosure JPMorgan's leadership made in late 2025 changed how the finance sector reads artificial intelligence. Projects run one at a time gave way to 450 parallel use cases; 360,000 hours of manual workload were recovered per year. The most critical point: every one of these use cases runs inside day-to-day operations.
UK finance leaders mostly read this case through a scale objection. The objection has a fair side. Yet the methodology's first requirement is discipline, well before budget.
The bank's leadership set up a unit called JPMorgan AI Research in 2023 and connected it to an internal platform called LLM Suite the following year.
By the end of 2025, more than 450 use cases were running in production. The team grouped them into 5 main categories.
The first is document synthesis. Legal contracts, regulatory filings and client due diligence documents reach employees with an AI summary attached. This use alone produces 100,000 hours of annual savings.
The second is research assistance. Equity research analysts used to spend 4 to 6 hours on a company file; with LLM Suite the task takes 45 minutes. The annual gain is 60,000 hours.
The third is client interaction preparation. Before a meeting, an investment banker has the client's correspondence, reports and interactions from the past 6 months summarised. Annual gain: 50,000 hours.
The fourth is operational control. Automation layers stretching from money laundering screening to credit approval save 90,000 hours a year.
The fifth is developer productivity. The bank uses its own GitHub Copilot derivative; this line brings in 60,000 hours a year.
The total comes to 360,000 hours a year. Roughly the workload of 175 full-time employees.
This is JPMorgan's real break point. The classic banking approach works like this: a use case is found, an external consultant is called in, a proof of concept runs for 6 months, and the result either enters the budget or dies quietly.
JPMorgan's leadership reversed that flow and positioned AI as a permanent operating unit. The business unit that owns the use case applies; the AI team deploys it on the platform within 2 to 4 weeks. The proof-of-concept stage was removed from the flow; the go-to-production decision is made within 30 days.
Stanford's Enterprise AI Playbook (2026) names this approach an "operating cadence". The organisation manages AI as a continuous flow rather than a one-off project. McKinsey's finding from the same year supports it: the companies producing the highest AI ROI place the work on the COO line rather than the CIO line.
A pattern I keep seeing while advising organisations: the moment executives step out of the scale trap, the conversation changes. JPMorgan did not reach 450 use cases in a day either; the team started with 12. For UK banks, the road map is built as follows.
Create a use-case catalogue. Ask every business unit for a list of repetitive tasks that take more than 5 hours a week. Score them by category, volume, number of people affected and cost of error. By the end of day one you will have 60 to 80 use cases; then you pick the ones that hurt most.
Commit to a single platform. When LLM Suite was being built, JPMorgan's leadership took a firm decision and constructed one internal layer instead of 18 separate pilot tools. A UK bank should do the same on top of Azure OpenAI or Anthropic enterprise. Otherwise data governance fragments.
Define an authorisation matrix. Every use case carries a data level: public, internal, confidential and restricted. LLM access is defined against those levels. The JPMorgan team built this matrix ahead of the compliance process.
Give use-case ownership to the business unit. The lending team writes its own use case; the AI team deploys it on the platform within 14 days. Gartner's latest report is blunt: 40 per cent of autonomous AI initiatives set up without business-unit sponsorship will fail by 2027.
Link hour savings to categories. Abstract productivity talk gets you nowhere. The JPMorgan team measures hours per use case. A UK bank should measure hours separately in transaction approval, client reporting and compliance screening, and build the annual total from those lines.
The objection usually arrives through budget and points to JPMorgan's AI spend, cited at around the 1 billion dollar mark. The figure misleads. Cost per use case, on known numbers, sits in the 200,000 to 400,000 dollar range.
A mid-sized UK bank can open 25 to 30 use cases a year with 5 million dollars. The data already sits inside the bank; the model can be open source or hosted. The most expensive line is engineering capacity, and that grows with an in-house team.
JPMorgan also began the journey with 12 use cases. Today's 450 is the result of a discipline compounded over five years.
There is a cold data point here. According to the EY 2026 CEO Outlook report, 73 per cent of banking and finance CEOs mark AI as their most strategic investment line for the next 12 months.
Only 19 per cent of the same CEOs say the AI transformation team reports directly to them. The remaining 81 per cent still leave the work in a sub-layer of the technology organisation.
JPMorgan CEO Jamie Dimon holds a weekly meeting with the AI team in person. That is the structural difference. Unless UK banking leaders run the AI transformation themselves, they will never get close to JPMorgan's numbers.
JPMorgan removed 360,000 hours of manual workload a year with more than 450 AI use cases. The secret sat in positioning AI as a permanent operating unit rather than a one-off project.
The model stands on three legs working together: a single platform, business-unit ownership and a 30-day production decision cycle.
UK financial organisations can build the same discipline with 25 to 30 use cases in 12 months.
For the customer-facing parallel, read our Klarna case study on AI in customer service. If you plan to bring this shift to your board from the stage, our guide on how to choose an AI keynote speaker sets out the selection criteria, and our artificial intelligence speakers page shows who can tell this story in the room. To plan a session, contact us.
The publicly known technology budget runs at around 17 billion dollars a year; the whole of it does not go to AI. Pure AI investment sits at the 2 billion dollar mark. Average cost per use case is 200,000 to 400,000 dollars. For a UK bank, a starting set of 25 to 30 use cases is feasible with a budget of 5 to 10 million dollars.
LLM Suite is JPMorgan's internal platform and is closed to sale. It runs on Azure OpenAI and OpenAI enterprise infrastructure underneath. A UK bank can build a similar internal platform on Microsoft Azure or Anthropic enterprise in 4 to 6 months. The important part: the data governance layer, fine-tuning support and the audit trail must be designed together.
Measurement was done per use case. For each one, the formula "average time before AI multiplied by volume multiplied by annual repetitions" was applied, and the hours were totalled in reporting. The calculation is transparent; internal audit signs it off. A UK organisation should start with the same template.
JPMorgan's leadership placed the compliance team inside the AI team. A risk assessment is completed for each use case before deployment. Data classification is defined at 4 levels. Use cases falling into the EU AI Act's high-risk category were given an extra layer of human approval.
According to CNBC's reporting, more than 200,000 JPMorgan employees have access to LLM Suite. Because the platform is a single layer, every new use case opens to the same base; adoption moves quickly for that reason.
JPMorgan started with 12 use cases; that number is a sound reference. In the first step you build a catalogue of 60 to 80 items and select the ones with high volume and a bearable cost of error. A narrow start develops the platform and governance discipline without taking on major risk.
After Dinner Speakers
Contents
