LangChain Financial Services Japan

MUFG Bank

Enterprise Knowledge Search · Sales Automation

MUFG Bank’s FX and derivative sales teams spent too much time reading annual reports, market data, and financial disclosures by hand before they could create tailored presentations and recommendations for corporate clients.

100-200 pages
10x increase in the number of corporate clients receiving tailored financial recommendations
hundreds of sales professionals
reduced from several hours to just 3-5 minutes

Reported impact

Business outcome

MUFG shortened research and presentation prep from hours to minutes, made sophisticated client intelligence available to far more salespeople, and increased the number of corporate clients receiving tailored recommendations.

  • Productivity Improvement
  • Revenue Growth
  • Scalability

Solution

MUFG’s AI/ML team built a production RAG application that digests corporate data and turns it into sales-ready presentation material. In the research phase, the team used the Python version of LangChain with Streamlit to stand up chat and retrieval quickly, while the Retriever interface allowed different vector databases and search engines to be swapped and compared at low implementation cost. The system extracts key facts from long annual reports, market data, and disclosures, then uses fine-tuned prompting, retrieval, and few-shot guidance to surface the most relevant sections and generate structured recommendations. In production, MUFG moved to the TypeScript version of LangChain on Next.js, where Runnable Lambda dynamically changes content filters and indexes inside a custom RAG chain. That architecture turns research-heavy sales prep into a reusable knowledge workflow rather than a specialist-only manual process.

Data flow

Annual reports, market data, and disclosures are ingested into retrieval back ends chosen through the Retriever interface, LangChain extracts and summarizes the most relevant sections, few-shot prompting turns those insights into presentations and recommendations, and the production Next.js app serves the outputs to corporate sales teams.

Solution architecture

6 components · 2 layers
  1. Serving
    • Streamlit Delivered the interactive prototype interface for early sales-team experiments.
    • Next.js Hosts the sustainable and secure production application.
  2. Orchestration
    • Python version of LangChain Powered the early chat and RAG prototypes used for experimentation and feedback.
    • Retriever interface Lets MUFG swap retrieval back ends while validating search accuracy and cost.
    • TypeScript version of LangChain Runs the production implementation of the custom RAG workflow.
    • Runnable Lambda Changes content filters and target indexes dynamically inside the custom RAG chain.

Architecture clues

  • MUFG migrated from Python LangChain to the TypeScript version for production while keeping a similar interface.
  • Runnable Lambda changes content filters and indexes on demand within the RAG chain.
  • The Retriever interface made it cheap to compare vector databases and search engines.

Evidence from the source

10k reports, to market data, to financial disclosures
10x increase in the number of corporate clients receiving tailored financial recommendations
Runnable Lambda allowed them to dynamically change the content filter and target index
reduced from several hours to just 3-5 minutes
the Retriever interface, they were able to switch between several specific vector databases and search engines
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. LangChain

    MUFG Bank customer story

    First-party
    https://blog.langchain.dev/customers-mufgbank/
    Source type
    Vendor-published customer story
    Published
    Feb 27, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Feb 27, 2025 · LangChain · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.

Related

Similar use cases

See all like this