Fintech

$250 Million Saved: Why Bank AI Success Depends on Coordination, Not Code

Technical Program Manager Aditya Agarwal on the coordination challenge that determines whether digital transformation succeeds or stalls

Written By : Arundhati Kumar

Artificial intelligence has officially become banking's top concern. According to CSI's 2026 Banking Priorities survey, 27% of community bank and credit union leaders listed AI as their primary challenge for this year, surpassing cybersecurity for the first time. Leaders increasingly view AI through a dual lens: a powerful driver of efficiency and automation, yet simultaneously a catalyst for fraud, operational risk, and organisational complexity.

Aditya Agarwal has spent over seven years managing complex Citibank programs, watching well-funded technology projects collapse not from bad code, but from organizational friction. Working through Tata Consultancy Services from 2018 to 2025, he joined Citibank directly in October 2025 as Digital Tech Program Lead Analyst for Call Center and Operations, coordinating chatbot delivery streams processing 12 million customer interactions monthly. A council member of the Association of Information Technology Experts (AITEX), Agarwal's experience challenges conventional wisdom about why bank transformation efforts struggle – success depends less on choosing the right AI models and more on orchestrating the dozens of teams that must work in concert.

Banking automation presents unique challenges: unlike consumer tech companies, which can iterate rapidly, financial institutions must balance innovation speed with ironclad data security, regulatory oversight, and zero tolerance for errors. A chatbot that incorrectly processes a payment or exposes customer data triggers regulatory investigations, potential fines, and reputational damage that can last for years. Technical Program Managers occupy the critical intersection between competing demands, translating business objectives into executable technology roadmaps while embedding risk controls at every development stage.

When Six Teams Speak Different Languages

Programs Agarwal currently oversees at Citi demonstrate the scale of AI-driven transformation: conversational AI handles over 70% of customer service contacts in North America, resolving 85% of interactions without human escalation. Response times dropped to under ten seconds, while agent productivity increased approximately 30%. Yet behind these numbers lies a complex orchestration rarely discussed.

"TPMs are the bridge between product, engineering, and compliance," Agarwal explains. "In highly regulated environments like Citi, scaling an AI chatbot isn't just a coding exercise. It requires cross-functional orchestration between data scientists, developers, cybersecurity, legal, and risk teams."

Data scientists think in model accuracy percentages. Infrastructure engineers focus on latency and system reliability. Compliance officers work from regulatory frameworks. Coordinating these groups demands someone who understands enough of each domain to identify conflicts early.

Allowing customers to dispute transactions through chat is seemingly simple. Yet chatbots must authenticate identity, retrieve transaction history from multiple backend systems, validate dispute eligibility against card network rules, generate legally compliant documentation, route cases to appropriate queues, and provide status updates. All while maintaining audit trails satisfying regulatory oversight.

"My role involves mapping every dependency: which APIs need modification, what data governance approvals are required, how changes impact fraud detection systems, when compliance testing occurs, and how the feature integrates with existing customer service workflows," Agarwal notes. "Miscommunication at any point cascades into delays, rework, or production failures."

Under Agarwal's coordination, chatbot projects at Citi reduced call center traffic by 40% and created approximately $250 million in annual cost avoidance. Coordination determined success.

Federal Mandates Don't Negotiate Deadlines

Regulatory complexity adds layers absent from most technology projects. Consent Orders issued by the Office of the Comptroller of the Currency and Federal Reserve Board mandate specific outcomes with firm deadlines and ongoing monitoring. Banks must prove not just that problems are fixed, but that control frameworks prevent recurrence.

"Regulators require clear evidence of oversight, documented progress, and ongoing accountability," says Agarwal, who managed technical delivery for Citi Global Wealth's Consent Order remediation addressing Matter Requiring Attention 2020-15. "TPMs translate regulatory requirements into actionable technical workstreams – turning high-level mandates into testable system changes."

Six workstreams across technology, risk, finance, and operations required alignment while resolving blockers to meet regulatory milestones. Standardised governance dashboards provided executives and regulators with real-time visibility into remediation progress.

Compliance initiatives have a fixed scope determined by regulators. Missing deadlines means continued scrutiny, potential operational restrictions, and, in extreme cases, enforcement actions.

Multi-Partner Platforms Multiply Complexity

Digital payment platforms serving retail partners face coordination challenges that single-product teams never encounter. When Agarwal managed CitiPay delivery between 2021 and 2023, he coordinated a platform enabling customers approved for store-branded cards at partners like Macy's, Best Buy, and Home Depot to access accounts digitally immediately, without waiting for physical cards. Each partner operates different technology stacks and follows its own release schedule.

"Citi must provide standardised APIs and security protocols while allowing flexibility for partners to customize implementations," Agarwal explains. "Platform reliability becomes paramount. System outages affect partner revenue, damage relationships, and risk losing contracts."

Partner onboarding frameworks, vendor deliverables, and third-party testing require coordination for secure integrations. Technical cutover plans need negotiation with partners. Release sequencing minimises disruption during high-volume periods. Monitoring and incident response procedures Agarwal's team implemented reduced customer-impacting incidents by 20-30%, supporting higher transaction success rates and retention.

Time-to-market for new capabilities accelerated by 20-30%, enabling faster onboarding and earlier revenue realisation. Platform expansion into new segments became possible through compliant, scalable payment capabilities.

Legacy Systems Don't Retire Overnight

Account Details Activity pages used by millions of customers daily sit atop dozens of legacy backend systems built over decades of bank mergers. Between 2018 and 2020, Agarwal coordinated the migration of these pages to Next Generation Architecture – modernizing customer-facing features without disrupting core banking required careful sequencing.

Engineers build new APIs communicating with old mainframe systems. Caching layers improve performance without data inconsistencies. Changes deploy incrementally, so rollback remains possible. Agarwal coordinated reuse of shared APIs, data services, and UI components across products, reducing duplicate build effort by 20-30%.

"Establishing technical standards, facilitating architecture reviews, and ensuring teams didn't solve the same problems independently were essential," Agarwal notes. "Standardisation simplified testing and reduced support burden."

Improved self-service features contributed to a 15-25% reduction in call center inquiries, lowering servicing costs. Customers gained real-time visibility into transactions, clearer dispute workflows, and consistent experiences across channels. Migration to Next Generation Architecture eliminated data delays, strengthening Citi's perception as a digital-first institution.

Silos Kill Even Well-Funded Projects

Large technology organizations naturally develop silos. Engineering teams focus on building reliable systems. Product teams prioritize user experience. Compliance teams enforce regulatory requirements. Each group optimizes for its domain, sometimes at the expense of overall project success.

"Financial services face pressure to deliver digital experiences comparable to consumer tech while operating under stricter constraints," says Agarwal. "Banks can't move fast and break things. They must move fast, maintaining perfect data integrity, complete audit trails, zero security breaches, and full regulatory compliance."

Success demands facility with engineering practices, risk frameworks, and stakeholder management. As financial institutions accelerate AI adoption and digital transformation, demand grows for professionals who can bridge technical and business domains while navigating regulatory complexity.

Clarity Act Stablecoin Yield Debate Delayed as US Lawmakers Remain Divided on Crypto Policy

Crypto Prices Today: Bitcoin Drops to $74,499, XRP at $1.40 Amid US-Iran Conflict Jitters

Why Did Solana Post About XRP? Key Insights Explained

10 Best Crypto YouTube Channels & Influencers

XRP Price Can Hit $1000 by 2030, Says Analyst Drawing Direct Comparison With BTC Market Cap Logic