T. Rowe Price Is Putting Claude Inside Investment Research, Not Just Back-Office Work

T. Rowe Price is expanding its use of Claude across its investment organization, putting portfolio managers and analysts to work with Claude and Claude Cowork on synthesizing complex research rather than confining the tools to back-office automation — the more typical enterprise adoption sequence. The firm’s developers are separately building internal investment tools with Claude Code. Eric Veiel, T. Rowe Price’s President and Chief Investment Officer, says Claude lets investment professionals “cover more ground and go deeper on what matters.” The rollout sits under an AI leadership model the firm announced in August: dedicated AI leads embedded inside individual investment divisions, with a central group, T. Rowe Price Labs, governing responsible use firm-wide — every application owned by its business unit, with human judgment and accountability kept explicitly central to client outcomes.

The shape of that governance model — decentralized ownership paired with centralized review — echoes what other regulated organizations have needed to make agentic AI usable at scale. The Government of Alberta’s Ministry of Technology and Innovation used Claude Code to scan 466 million lines of code across 1,280 applications and 3,400 repositories in about 20 hours, work it estimated would otherwise take 6.5 years; roughly 50 agents ran a two-stage review that flagged issues by exact file and line so human engineers could verify every finding before anything shipped, including full test-and-fix rebuilds of decades-old systems.

Different industries, same design constraint: agentic AI moving into consequential, judgment-heavy work only scales once there’s a verifiable human checkpoint built into the workflow, not bolted on after. T. Rowe Price is applying that constraint to investment decisions instead of code; Alberta applied it to legacy government systems. Both are concrete evidence that “human-in-the-loop” is becoming a design pattern with real vendor tooling behind it, not a compliance footnote.