JPMorgan and Goldman Sachs Are Deploying LLMs Across Operations
JPMorgan Chase’s LLM Suite — a large language model-powered productivity platform deployed to more than 60,000 employees across the bank’s technology, research, and operations divisions — generated measurable productivity outcomes that JPMorgan’s technology leadership disclosed in Q1 2026: software engineers using the LLM Suite’s coding capabilities reported a 35 percent reduction in time spent on routine documentation and code review tasks; research analysts reported completing first drafts of market research summaries in half the time of the prior manual process. JPMorgan’s AI strategy disclosures confirm the company’s position as the most aggressively AI-invested major bank by headcount and tooling deployment, with CEO Jamie Dimon describing AI as potentially the most transformative technology the bank has encountered in its operating history. Goldman Sachs and Morgan Stanley have followed on comparable timelines, at lower disclosed scales, producing a picture of the three largest US investment banks simultaneously and independently concluding that LLM deployment at the employee level is operationally necessary rather than optionally innovative. Morgan Stanley’s technology disclosures describe an AI @ Morgan Stanley assistant product reaching 98% weekly use among financial advisor teams, while the Federal Reserve’s SR 11-7 model risk guidance still anchors how bank examiners review AI-assisted decisioning across the three firms.
The speed of adoption in financial services is striking relative to most enterprise categories, given that financial services firms operate under more stringent regulatory oversight of technology risk than almost any other industry. The Office of the Comptroller of the Currency, the SEC, and FINRA all issue guidance on AI use in federally regulated financial activities; model risk management frameworks at major banks require validation, documentation, and ongoing monitoring of every model used in a regulated activity. The fact that the three largest investment banks have deployed LLMs to tens of thousands of employees reflects a deliberate scoping decision: the use cases that have been deployed at scale are productivity tools operating outside the regulated decision chain — research drafting, document summarisation, code generation, internal knowledge retrieval — rather than the loan approval, investment advice, or trading decision functions where regulatory explainability requirements would currently prohibit black-box AI deployment.
How JPMorgan’s LLM Suite Reaches 60,000 Employees
JPMorgan’s LLM Suite deployment covers a range of internal use cases that share a common property: the AI output is reviewed and validated by a human employee before it reaches a client, a regulator, or a recorded decision. Document analysis (processing contracts, regulatory filings, and legal documents to surface relevant provisions), email drafting, meeting summarisation, code generation for internal applications, and financial model documentation are the primary categories. The Suite integrates with JPMorgan’s internal data systems, allowing queries against proprietary research, deal history, and client documentation that would not be accessible through an external general-purpose LLM without exposing data outside JPMorgan’s security perimeter.
The proprietary data integration is the feature that distinguishes an enterprise LLM deployment from a consumer ChatGPT use case. JPMorgan’s decades of transaction data, credit performance history, market research, and client relationship data represent a training and retrieval corpus that no external model can access. When a JPMorgan analyst asks the LLM Suite to summarise comparable transactions in a specific sector, it draws from internal deal memos and research reports that are genuinely differentiated from the public internet. Enterprise AI deployment at scale across professional services has consistently shown that proprietary data integration — retrieval-augmented generation against internal knowledge bases — is the primary driver of differentiated value over general-purpose model access.
Goldman Sachs and Morgan Stanley’s Parallel Deployments
Goldman Sachs’ GS AI Platform provides coding assistance to Goldman’s software engineers — a deployment that the bank’s CTO described as having meaningfully accelerated the bank’s internal technology development velocity — alongside research summarisation tools for its equities and fixed income research divisions. Goldman has been more restrained than JPMorgan in disclosing specific productivity metrics, but has confirmed that its AI deployment covers the majority of its technology organisation and is expanding to trading operations support functions including pre-trade analysis documentation and post-trade reporting assistance.
Morgan Stanley’s AI deployment is the most clearly scoped of the three. AI at Morgan Stanley was built in partnership with OpenAI and deployed to the bank’s 16,000 financial advisors as an AI assistant for client communications: the system retrieves relevant research, product information, and client history to help advisors prepare for client meetings and draft client communications. The use case is precisely within the productive middle ground where AI creates value without triggering fiduciary liability — the advisor remains the decision-maker and client-facing professional; the AI reduces preparation time and information retrieval burden. Morgan Stanley has disclosed that advisor adoption has reached above 90 percent within the financial advisor population, which is the adoption rate that defines a successful enterprise AI rollout rather than a tool that employees route around. OpenAI’s enterprise revenue growth reflects deployments like Morgan Stanley’s — high-adoption, high-ACV, professional-services relationships that anchor the company’s ARR expansion.
The Regulatory Guardrails Defining AI’s Scope in Finance
The OCC’s AI risk management framework for national banks requires that AI models used in regulated activities — credit decisions, anti-money-laundering screening, fraud detection — meet explainability, auditability, and bias-testing standards that current large language models do not satisfy for final decisions. A loan approval cannot be made by an LLM that cannot explain its reasoning in terms that satisfy the Equal Credit Opportunity Act’s adverse action notice requirements; a trading decision cannot be made by a model whose internal workings cannot be audited in the event of a regulatory inquiry. These requirements define the scope within which banks can operate LLMs: the productivity and research applications being deployed at scale today are outside this regulated decision chain; the credit, trading, and fiduciary advice functions remain in it.
The practical consequence is that the AI transformation underway in financial services is, for now, an internal efficiency story rather than a client-facing product story. The productivity gains accrue to the bank’s employees and margins before they appear in client outcomes. As explainability techniques improve — and as regulatory guidance evolves in response to the industry’s practical AI deployment experience — the scope of what AI can do inside the regulated decision chain will expand. The banks that have built the internal tooling infrastructure, employee familiarity, and data integration foundations through the current productivity-tools phase will be positioned to extend AI into regulated functions faster than competitors who waited for regulatory clarity before beginning deployment.
What 35 Percent Productivity Gains Look Like Inside the Work
JPMorgan’s disclosure that software engineers using the LLM Suite reported a 35 percent reduction in time spent on routine documentation and code review is useful as a headline number. It is less useful as a description of what actually changed in how those engineers spend their days. The 35 percent is not distributed evenly across the work: it is concentrated in the specific moments where the engineer would previously have written a first draft — a commit message, a code comment block, an internal design document, a test case description — that required no novel thinking but that required enough sustained attention to pull them out of the flow work they were doing. The AI reduction in those moments is not “35 percent of all engineering work is now faster.” It is “the ceiling on context switching has been raised for a specific category of interruption.”
Julie Zhuo’s product management framework consistently returns to the user in the task: not the user as a category or a demographic, but the specific person with a specific goal at a specific moment who is about to decide whether to use the tool or route around it. The LLM Suite’s 60,000-employee adoption rate is a deployment success, but the question that determines whether deployment becomes durable value is whether the tool is present at the moments that matter to the individual engineer or analyst using it. An AI research tool that produces a usable first draft for 85 percent of standard document types is a meaningful upgrade for the analyst who was spending 40 percent of their day on first-draft production. It is a marginal upgrade for the senior analyst whose value is entirely in the judgment applied after the first draft exists — and that analyst may adopt the tool nominally while finding it does not materially change how they experience the work.
The distinction between adoption rate and value-density is why the most rigorous enterprise AI deployments track task completion time against specific workflow steps rather than overall productivity aggregates. JPMorgan’s 35 percent figure almost certainly obscures a distribution: some engineers experience a 60 percent reduction in documentation time because their role involves continuous documentation; some experience 10 percent because their documentation burden was already low. The product team building for durable retention needs to know which of those groups is driving cancellation risk — not the average. Enterprise AI deployments that hold at scale over three and five year windows will be the ones that identified the specific tasks where the marginal user experienced genuine relief, then built the product around those moments rather than around the headline efficiency number that landed in the quarterly earnings call. The 35 percent is where the story starts; the distribution underneath it is where the product decisions live.
