Now booking Instant Payments Readiness Workshops for Q1 2027 · Learn more → | Hiring for a technology leadership role?
Finov8XTrusted Senior Consultant for Banks & Fintechs

Case studies

Programs Ahmed led in employed roles at banks and lenders before founding Finov8X. Institutions are described by type and region to protect confidential details; results are stated with how they were measured.

Commercial bank · South Asia

Joining a national ISO 20022 instant payments rail without touching core uptime

10M+ transactions a year
99.9% uptime
Both phases delivered on schedule

Context

A commercial bank had to connect to a new national real-time payments scheme in two phases, on a core banking platform built for batch processing.

Problem & constraints

Real-time, 24x7 posting, alias resolution and in-flow fraud and sanctions screening had to be added without degrading availability for existing channels. Scheme certification deadlines set by the regulator; a batch-oriented core; operations teams staffed for business hours.

Ahmed's role

Ahmed led the program end to end as Senior Technical Program Manager (employed role, before founding Finov8X).

Approach

  • Split delivery into two scheme phases with separate certification gates.
  • Integrated pacs.008 and camt.053 message flows with alias and directory services.
  • Placed real-time fraud and sanctions screening in the payment flow rather than after posting.
  • Designed a nights-and-weekends operations model before go-live, not after.

Delivery, governance & risk controls

  • Phase-level go/no-go gates tied to scheme certification evidence.
  • Joint vendor and bank RAID log with named owners.
  • Hypercare with incident SLAs after each phase.

How results were measured: Annual transaction volume and availability as reported in production operations; schedule against the regulator's phase deadlines.

Lesson: Real-time rails are an operations change as much as a technology change: the 24x7 support model and screening placement decide whether go-live is calm.

Regulated digital lender · Saudi Arabia

Lifting on-time delivery from 62% to 89% across a digital lending portfolio

On-time delivery 62% → 89%
~30% throughput gain after the ART launch
~20% OPEX reduction while holding velocity

Context

A $100M+ digital lending portfolio of 80+ initiatives across retail, SME and BNPL, delivered by 10+ cross-functional squads.

Problem & constraints

Delivery predictability was low, dependencies were tracked in many places, and executives lacked a single view of risk and decisions needed. Regulated environment; parallel product launches; shared platform teams and vendors.

Ahmed's role

Ahmed was Senior Technical Program Manager and Delivery Manager for the portfolio (employed role, before founding Finov8X).

Approach

  • Rebuilt governance around a single-source-of-truth RAID log and dependency map.
  • Moved waterfall delivery into a SAFe Agile Release Train with PI Planning.
  • Introduced SQL / Power BI executive dashboards and AI-assisted reporting for steering committees.

Delivery, governance & risk controls

  • Monthly business reviews and steering committee chaired with explicit decision logs.
  • Release planning, change management and go/no-go ownership to protect uptime.
  • Budget, forecast and vendor cost governance.

How results were measured: On-time delivery measured as initiatives delivered by committed date across the portfolio; throughput as delivered features per PI.

Lesson: Predictability improves fastest when dependencies and decisions are visible in one place and executives are asked for decisions, not status.

Commercial bank · South Asia

Core banking migration and integration across three bank mergers

3 merger cutovers
Zero-downtime cutovers
99% uptime maintained

Context

Three successive bank mergers required consolidating core banking, digital channels, ATM controllers, CRM and payment systems onto one Temenos T24 core.

Problem & constraints

Each merger required customer, account and product data migration and full channel integration while branches and digital channels stayed live. Fixed legal merger dates; customer-facing channels could not go dark; multiple vendors.

Ahmed's role

Ahmed led the migration and integration program as Senior Technical Program Manager (employed role, before founding Finov8X).

Approach

  • Gap analysis and target architecture per merger.
  • Repeated mock conversions with reconciliation sign-off before each cutover.
  • SIT, regression and UAT across core, channels and payment ecosystems.

Delivery, governance & risk controls

  • Cutover runbooks with rollback criteria and named decision owners.
  • Hypercare with daily reconciliation after each cutover.

How results were measured: Availability of customer-facing channels during and after cutover weekends; reconciliation sign-off of migrated balances.

Lesson: Mock conversions are where zero-downtime cutovers are actually won; the cutover weekend should be a rehearsal you have already passed.