AI for banking and financial services in Bangladesh

Regulatory and risk culture in Bangladesh banking is non-negotiable. Model output that touches customer outcomes, credit decisions, or KYC conclusions needs named human owners, logging, dual-control where committees expect it, and an exit path if a vendor locks the workflow. Copy-pasting a European AI governance checklist into a Dhaka operating model creates theatre; governance must map to your committee cycles, Bangla and English policy reality, and Bangladesh Bank guidance awareness without claiming regulator endorsement we cannot give.

Integration is the work. AI that cannot read from and write to systems of record becomes a parallel shadow stack. Core banking mixes, card and payment switches, and document stores often disagree on customer and merchant IDs. Data residency and vendor access rules limit how assessments begin — controlled samples first, production connectors later. Security questionnaires will ask where inference runs and who can access prompts containing PII; answers must be designed into the engagement, not improvised during procurement.

Talent is uneven: strong engineering pockets exist in Dhaka and Chittagong, but roles combining domain, integration, and change leadership are scarce. Hiring a full in-house AI team before use cases survive scrutiny is expensive. Branch and call-centre adoption fails when enablement is English-only or when supervisors never own exception queues. Peak periods — salary days, festival seasons, campaign launches — break naive automation without escalation design.

Procurement pressure from vendors who over-claim autonomous KYC or credit decisions creates false urgency. Shadow use of consumer chat tools on customer data is a governance incident waiting for internal audit. Multi-entity groups — banking, NBFI, payments adjacents under one brand — need AI programmes that respect entity boundaries rather than pretending one workflow fits all licences.

Arcloops will challenge vendor claims in selection engagements and sequence readiness → prioritised use cases → controlled pilot → production criteria you accept. We decline use cases that require guaranteed autonomous decisions on regulated outcomes we cannot responsibly deliver.

Campaign and festival-season volume spikes stress care and onboarding queues — automation must include escalation to named humans, not vanity deflection metrics. Agent banking and correspondent networks introduce partner document quality variance HQ-centric pilots ignore. Bangla/English policy and customer communication require enablement design, not English-only governance PDFs. Internal audit and Bangladesh Bank-adjacent committees will ask for logging, dual-control evidence, and exit paths — programmes that treat those as phase-two items stall before production.

Vendor access to production environments is often slower than pilot timelines assume — assessments should plan for anonymised samples and staged connectors. Mobile banking and agent channel growth multiply device and identity edge cases KYC workflows must respect. We refuse invented NPL or cost-save percentages for board packs.

Engagements typically open with AI readiness assessment, AI governance & risk, or a scoped merchant/KYC workflow review using real samples. Product maps include MerchantPro, Approvals, AI in Finance, and AI in Legal & Compliance when ownership is clear. Consulting covers strategy, policy, enablement, and vendor selection when independence matters more than a product push.

Delivery is from our Dhaka primary office with hybrid sessions at bank headquarters and major branches when scoped. Parent context: banking & financial services industry page and Bangladesh market page. Metrics are operational — exception ageing, document cycle time, straight-through on agreed samples — never invented ROI.