Interactive analysis of where agentic AI can drive operating-efficiency and expense-productivity gains across Citi's wholesale businesses, with financial estimates grounded in Citi's disclosed FY2025 figures and external benchmarks.

Wholesale Banking · Operations Technology

Turning Citi's proven AI momentum into measurable operating-efficiency gains.

An opportunity map for agentic AI across Services, Markets and Banking — grounded in Citi's disclosed FY2025 financials and real industry benchmarks.

$1.5–3.0B
est. capacity + expense potential at maturity — gross
~3–5%
of the $55.1B expense base · one lever inside the ~$2–2.5B program, not additive to it
8
prioritized opportunities · 2026–2028
▼ Scroll to explore
The mandate

Drive AI strategy, operating efficiency, and expense productivity.

Citi delivered record FY2025 revenue and positive operating leverage across all five businesses — while committing to keep bending the cost curve. The wholesale franchise, with its scale and process intensity, is where AI compounds fastest.

$0B
FY2025 total operating expense
0%
FY2025 efficiency ratio
target ≈ 60% in 2026
$0B
run-rate savings still to capture (≈$2–2.5B)
0%
2026 RoTCE target (10–11%)
The wholesale franchise

Three businesses, one operations spine.

Services — the engine

Treasury & Trade Solutions (cross-border / international payments, USD clearing) + Securities Services. FY2025 revenue $21.3B · opex $10.8B · cross-border value $416B.

Markets

Fixed Income + Equities (incl. Prime). High-volume, low-latency. FY2025 revenue $22.0B · opex $14.1B.

Banking

Investment Banking (M&A, ECM, DCM) + Corporate Banking. FY2025 revenue $8.2B · opex $4.5B.

Shared spine: onboarding/KYC, reference & client data, trade & payment processing, reconciliations, settlement, controls, and regulatory reporting — where most addressable expense (and AI opportunity) concentrates.

The opportunity map

Eight opportunities, ranked by impact & feasibility.

Each estimate is built bottom-up from a disclosed segment cost pool × an addressable share × a conservative AI savings rate — and anchored to a documented "quantum-leap" benchmark. Click any card to expand.

Live ROI model

Pressure-test every assumption.

Pick an opportunity and adjust the addressable cost pool and AI savings rate. The financial impact and the portfolio total recompute live. Defaults reflect the conservative ranges in the analysis.

$0.2B$6B
0%40%
This opportunity → / yr run-rate
Portfolio potential — capacity + expense (all 8, at maturity)
Rows overlap (KYC & controls span segments) — read as a landscape, not a sum. Figures are gross potential; they reach P&L only through redeploy-or-release decisions. AI is one lever inside Citi's ~$2–2.5B program.
See it in action

Agentic AI on a live wholesale case.

From copilot to autonomous multi-step agent — grounded in Citi data and bank-grade governance. Pick a scenario and run the agent.

Before · manual
After · agentic
Basis

Ready
Prioritization

Impact vs. feasibility.

Bubble size = estimated annual run-rate impact. Hover any bubble for detail. Sequencing weighs ROI certainty, cost-pool size, and data/regulatory dependencies.

Sequencing

A 2026–2028 delivery roadmap.

A discussion starter

One way to frame the first 90 days.

The inside view — which you and the team have — decides the real sequence. This is an outside-in frame to react against: rough order of magnitude throughout, and much of it likely already in flight.

Weeks 1–4
Listen & baseline
Baseline the spineSTP by flow · exception volumes & aging · cost per payment / trade / KYC file
Capacity auditWhat deployed AI (code review, Stylus) has freed — and where it went
Governance runwayWhat Model Risk & Compliance need to see before agentic automation ships
Weeks 5–8
One or two lighthouse wins
Scale the SDLC leverHighest certainty — already proven inside Citi
Payment-exception triage — human-approvedCross-border flow · visible in-year
Ship inside a quarterSmall enough to deliver, visible enough to anchor the mandate
Weeks 9–12
Lock the scaling frame
One-page scorecardRun-rate vs. $2–2.5B target · STP · cost per exception · hours redeployed · adoption · MRM cycle time
Self-funding logicEarly savings finance the next wave
Into the 2027 planGovernance pattern pre-agreed with Model Risk
Week-one questions — likely already in flight
1. Where does STP break most, by flow and business — and what does each break cost?
2. What is the exception aging profile in payments and post-trade, and the cost per case?
3. How much capacity has deployed AI actually created — and where was it redeployed?
4. Which client- and reference-data gaps block the next wave of use cases?
5. What evidence will Model Risk & Compliance expect before autonomous steps run in regulated flows?

Illustrative by design — the real sequence, numbers, and scorecard belong to the team. The intent: show where hands-on outside help could contribute from week one.

Pressure-test, continued

The questions this analysis should be asked.

A serious review will — and should — attack this brief. These are the challenges it expects, answered plainly; several are conceded outright, and each concession maps to something the weeks 1–4 baseline settles with internal data. Click any card.

Fair — gross vs. net

"The headline potential exceeds Citi's entire $2–2.5B savings program — overreach?"

A fair challenge — and the reason the headline is stated as gross capacity-plus-expense potential rather than savings. The committed program is a net figure over a defined window; the estimate here sits before overlaps between rows, investment cost, and redeploy-or-release decisions. The honest claim: AI is one lever capable of carrying a large share of the committed number — not a new number on top of it.

+ answer
Conceded — designed in

"The 100,000 hours a week is capacity, not P&L — you're conflating the two."

Conceded — and the distinction is the whole game. Capacity becomes P&L only through explicit decisions: released positions, avoided backfills, reduced vendor and BPO spend, or redeployment into revenue work (which surfaces as operating leverage rather than expense). The proposed scorecard carries 'hours redeployed vs. released' as a first-class metric for exactly this reason.

+ answer
By design · ROM

"Citi doesn't disclose operations cost by process — where do the pools come from?"

Triangulated from disclosed segment expense, industry cost-structure studies, and peer analogs — rough order of magnitude by design. The sliders exist so every pool can be replaced by internal data the team already holds. Any single number should be expected to move materially; ranking and direction are the robust part.

+ answer
True — read as landscape

"The eight rows double-count — KYC, screening, and controls overlap."

They do. The portfolio view is presented as a landscape, not a sum — gross, overlapping potential rather than an additive total. A bottom-up build on internal data nets the overlaps in weeks — which is the weeks 1–4 baseline exercise.

+ answer
True — used as bounds

"The benchmarks are survivor stories — Klarna walked back its agent claims; HSBC's result is classic ML, not agentic."

All true. Benchmarks are used as bounds on what has been achieved somewhere, not forecasts for Citi — the modeled savings rates sit deliberately below them. The failures are design inputs too: Klarna's over-automation of judgment work is precisely why human-in-the-loop tiers gate every regulated or judgment-dense step here.

+ answer
Agreed — sequenced for it

"Consent orders on data and controls are open — autonomous agents in sanctions flows is reading the room badly."

Agreed — and the sequencing says so. The first wave is SDLC plus agent-assisted investigation that drafts repairs and rationales for human sign-off; no autonomous action in regulated flows. Autonomy earns its way in through low-risk, reversible steps, against an evidence bar Model Risk and Compliance define. The reference-data work the orders require is the same foundation these use cases need — complementary programs, not competing ones.

+ answer
Deliberately out of scope

"There's no cost-to-achieve and no J-curve — what does this cost?"

Cost depends on build-vs-buy, platform reuse, and restructuring choices only internal planning can make. Directionally, programs of this shape run net-negative for 12–24 months before crossover, and the self-funding logic in the 90-day frame — early lighthouse savings financing the next wave — is how the curve stays shallow. A credible investment case is a weeks 9–12 output, not a pre-meeting guess.

+ answer
Different model

"Cross-LOB KYC consolidation has a graveyard — the external utilities failed."

They failed on liability, jurisdiction, and data ownership. What's proposed is internal consolidation — one client record, one policy engine, a shared service inside the bank's own perimeter — which is exactly the design those failures argue for.

+ answer
The basis

Every estimate has a documented quantum leap behind it.