
BNPL Launch at Simpaisa: 0 → 100K Users in 8 Months
Launched Simpaisa's BNPL product from scratch, full underwriting, repayment flows, collections, regulator briefings, to 100K users in 8 months through iterative agile discovery.
What this is, in one paragraph.
Took BNPL from product concept to 100K active users in 8 months. Built the full stack, eligibility, underwriting, repayment, dunning, collections, regulatory posture, and the consumer UX, using rapid agile discovery cycles and a tight feedback loop with credit and risk.
“Launched Simpaisa's BNPL product from scratch, full underwriting, repayment flows, collections, regulator briefings, to 100K users in 8 months through iterative agile discovery.”
The job to be done.
BNPL was being launched across the region by Tabby and Tamara, but most local merchants needed a partner who already handled their acceptance. Simpaisa had the merchant base and rails; what was missing was a defensible BNPL product with a credit, risk and ops model that worked in Pakistan and could port to MENA.
What we shipped.
- Eligibility + underwriting engine (alt-data scoring + bureau where available)
- Repayment scheduling, dunning and collections workflows
- Merchant-facing BNPL integration (existing SDKs + new BNPL endpoints)
- Consumer onboarding KYC flow with friction-tier risk-based capture
- Regulator briefings + central-bank engagement on consumer-credit posture
- Analytics: cohort default tracking, ARPU per cohort, recovery funnel
Where I sat in the work.
CPO. Owned product strategy, regulatory engagement, partner stack (bureau, alt-data, collections), and the cross-functional discovery cadence with risk, credit ops and engineering.
What moved.
- Reached 100K active users in 8 months
- Discovery → first live merchant in 14 weeks
- Default rate held within target band through cohort-by-cohort tightening
- Created the product blueprint Simpaisa is using for MENA expansion
What we chose against.
- Launched with bureau data only where available, alt-data scoring elsewhere, slower onboarding in low-data segments, but no skipped underwriting
- Built dunning + collections in-house instead of outsourcing, higher ops cost early, much tighter feedback into the credit model
What I'd take into the next build.
- BNPL is a credit product first, a checkout product second. Treating it as the latter is how funds get burnt.
- Cohort discipline is the difference between scale and a blowup. Track every cohort to maturity; do not average them.
- Regulator engagement should start before discovery, not after, especially in markets with developing consumer-credit law.
Relevance to networks, PSPs and cross-border platforms.
Tabby, Tamara, BNPL-curious banks and BaaS providers in MENA all face the same question: how do you ship BNPL inside a regulated payments org, fast, without taking unmanaged credit risk? This is what that looks like in production.
Discussing payment infrastructure / product leadership roles?
Reference-available. Download the résumé or get in touch.
More case studies
A regulated, multi-rail payments platform processing $1B+ annual GTV and 25M+ monthly transactions across pay-in, payout, wallets (DCB/IBFT), card acquiring (MPGS/MDES), settlement, FX and cross-border corridors, PCI DSS and ISO/IEC 27001 certified.
Automated merchant onboarding pipeline, KYC/KYB, UBO discovery, sanctions and PEP screening, risk-tiered decisioning with full audit trail. Activation cut from weeks to hours; manual review load down 70%.
A multi-rail settlement and reconciliation engine, canonical double-entry ledger, three-way auto-reconciliation, exception management and corridor-aware payout windows. Closed the gap between treasury, finance and product at $1B+ GTV.