Between 2019 and 2022, I was a Principal Product Manager at Grab, Southeast Asia's leading superapp. Grab processes billions of dollars in transactions annually across ride-hailing, food delivery, financial services, and more — serving hundreds of millions of users across Singapore, Indonesia, Vietnam, Thailand, Malaysia, and the Philippines.
I led two very different product domains: Growth, Engagement & Loyalty (GEL), which focused on consumer lifecycle and monetisation; and Driver Rentals, which was essentially a fintech product managing vehicle financing and payments for 30,000+ drivers. The combination taught me things about payments at scale that I carry into every product role since.
Lesson 1: Payments is not a feature — it's infrastructure
When most product managers think about payments, they think about a checkout flow. At Grab, I learned that payments is the circulatory system of a superapp. Every service — rides, food, groceries, financial services — depends on money moving reliably, instantly, and cheaply across borders and currencies.
On the Driver Rentals side, we managed a fleet of 30,000+ vehicles across multiple markets. Each driver had a unique financial relationship with Grab: rental contracts, insurance, fuel advances, incentive payouts, and penalty deductions — all flowing through a single billing platform. When I took over, invoices were ageing badly and operational costs were ballooning.
We rebuilt the billing platform into a unified, multi-tenant system. The result: $4.5M in operational cost savings and a 35% reduction in invoice ageing. The lesson was clear — payment infrastructure done right doesn't just process money; it reduces friction across the entire business.
Lesson 2: Growth is a system, not a campaign
On the GEL side, I owned the consumer growth and engagement portfolio across all of Grab's verticals. The temptation in a superapp is to treat growth as a series of campaigns — discounts, promotions, push notifications. We took a different approach.
We stopped running blanket promotions. Instead, we built a growth system that used machine learning to nudge users based on what they actually did on the app. If a user always ordered food on Tuesdays but never used ride-hailing, we target-nudged them exactly then. The compounding effect: a 2% increase in ARPU across the platform — which, at Grab's scale of millions of daily users, translates to enormous revenue impact.
One specific initiative I'm proud of: we redesigned the onboarding funnel using data-driven experimentation and iterative A/B testing. Within three quarters, onboarding success improved by 15 percentage points, reaching 94%. That single improvement had downstream effects on every metric — retention, frequency, lifetime value.
Lesson 3: Non-transactional engagement creates surprising monetisation
Here's something counterintuitive I learned at Grab: some of the most valuable product features don't involve a transaction at all.
We built a food reviews platform from scratch, integrating user-generated content into the food discovery journey. It wasn't obvious that reviews would move the revenue needle — but they did. The platform delivered a 1.4% revenue uplift and measurable retention improvement. Users who engaged with reviews ordered more frequently and tried more merchants.
We also built non-transactional engagement tools — content, gamification, discovery features — that didn't directly charge users but created surfaces for advertising and merchant promotion. These tools unlocked $2.5M in ad revenue and $1.4M via merchant discovery, improving lifetime value without increasing subsidies. It proved that engagement is monetisable even when it's not directly tied to a purchase.
Lesson 4: Multi-market fintech requires radical simplicity
Grab operates in six very different markets, each with its own payment rails, regulatory environment, currency, and user behaviour. Building payments infrastructure that works across Singapore (banked, card-heavy, real-time payments via PayNow) and Indonesia (underbanked, cash-heavy, diverse e-wallet landscape) requires radical simplicity in your platform layer.
The mistake I see many fintech teams make is building market-specific payment flows. What works better is building a thin, flexible abstraction layer that handles the complexity of local payment methods while presenting a consistent interface to the services consuming it. At Grab, this is what allowed us to launch financial products quickly across markets without re-engineering the payments stack each time.
Lesson 5: Driver economics is a fintech problem
Most people think of Grab drivers as gig workers. From a product perspective, each driver is a small business with complex financial needs: they need to finance a vehicle, manage cash flow, handle insurance, and optimise their earnings.
On the Rentals product, we were essentially running a financial services business embedded inside a ride-hailing platform. The billing platform managed rental contracts, insurance premiums, fuel advances, incentive calculations, and penalty deductions — all in real-time, all at scale.
The insight that changed our approach: driver financial health directly correlates with supply reliability. When drivers have predictable costs and transparent earnings, they drive more consistently. When billing is opaque or inconsistent, they churn. We redesigned the entire billing experience around transparency and predictability, and the retention impact was immediate.
What I carry forward
Three years at Grab taught me that fintech isn't just about moving money — it's about building trust at scale. Every payment is a promise, and at millions of daily transactions, even small failures compound into massive trust erosion.
Today at Intellect, I apply these same principles differently. When we're designing payment flows for enterprise mental health contracts, or building credit systems for B2B2C engagement, the muscle memory from Grab is invaluable. The context changes; the fundamentals of building reliable financial infrastructure at scale do not.
If you're a product leader moving into fintech, the biggest mindset shift is this: payments is not a feature team. It's the foundation everything else sits on. Treat it accordingly.