USE CASE CORNER
3 WAYS TO MEASURE AI RETURNS
Banking’s newest obsession is how to measure ROI on AI.
Calculating returns has been anything but uniform so far: Some cite a usage rate for an AI tool, others the promise of efficiency. Banks have their own time horizons for calculating financial gains and their own formulas for how much of a vendor contract should count towards AI spend. Whether annual returns should encompass every use case in production or just the ones launched that year differs from bank to bank.
Yet as banks get serious about deploying AI at scale (see: “Death of the Use Case,” The Brief, May 15), they need to show they can measure ROI consistently – it’s the only way they can prove their massive spend has been worth it and to compare themselves against their peers.
This week, we highlight use cases that illustrate three ways banks are measuring returns that could become kind of standard – with revenue uplift, cost avoidance or savings and time savings.
#1 CODE TIME SAVER
Use Case: DevGen.AI
Line of Business: IT security
Vendor: OpenAI
ROI Type: Time savings
Bank: Morgan Stanley
Why it’s interesting: Outdated programming languages like COBOL and Perl don’t mesh with modern AI models, and rewriting the code to make them AI-ready was eating up developer hours at Morgan Stanley. The bank built a tool to speed that infrastructure modernization up which, in turn, cuts down the time it takes to produce new AI tools.
How it works: The bank’s tool was built on top of OpenAI's models and works in a few ways: For smaller code sections, it can fully translate one coding language into another, and for bigger chunks of code, the tool will say plainly what that code does to make it simpler for developers to understand and rewrite it in an updated language.
ROI: Since it launched the tool in January, the bank says it’s saved 280,000 developer hours and reviewed 9 million lines of code.
#2 FEEDBACK SAVINGS LOOP
Use Case: Truist Client Pulse
Line of Business: Retail banking
Vendor: n/a
ROI Type: Cost avoidance
Bank: Truist
Why it’s interesting: Banks interact with customers in more ways than ever, and Truist built an AI tool to let it know how customers are feeling about their products to make them better.
How it works: The bank built an enterprise data lake – a centralized way to store data – that could pull in customer feedback from call centers, surveys, app reviews and customer complaints. A core team of 10 (with 80 other employees helping part time) then built a tool that analyzes each customer interaction and feeds it into a dashboard that lets bankers see customer sentiment in real time and filter by geography or for specific products. It took between 12 and 18 months to take the idea to production, the bank says.
ROI: Truist expects to save $35 million from reduced complaints and said that building the tool in-house saved $10 million compared to what it would have cost to get a third-party vendor.
#3 EFFICIENTLY USEFUL ADVICE
Use Case: Advisor Assist
Line of Business: Wealth management
Vendor: n/a
ROI Type: Revenue uplift
Bank: RBC
Why it’s interesting: The bank’s wealth managers are using AI to summarize meetings and research investments, freeing wealth advisors up to spend more time with existing clients and onboard more.
How it works: The bank’s AI team, Borealis, built a tool that scans emails, the bank’s CRM system and past notes to make recommendations to advisors about the best way to approach a meeting and frame new investment opportunities for a client. It also summarizes meetings as they happen so the bank’s advisors can quickly take action off the back of the calls.
By the numbers: Around a third of the AI-generated insights have resulted in clients bringing more money into the bank. Over time, the tool is “expected to make 80% of our staff as effective as the top 10%,” RBC’s CEO Dave McKay told investors.
Want to know more about the specific ways banks are rolling out AI? Check out our Use Case Tracker – the inventory of all the AI use cases announced by the world’s largest banks available to members.
|
|