I build products that ship.
Some of them, I also code.
I'm Anuraag Burman, a product leader based in Singapore with 10+ years of experience in product strategy, execution, and vision. Currently a Super IC at Delivery Hero / Foodpanda, where I've worked across growth, fintech, wallets, subscriptions, and incentives. I'm also deeply curious about AI. Not as a buzzword, but as a genuine shift in how we build and operate. So I've been learning, building, and experiencing that shift firsthand.
Most PMs talk about AI. I build with it. I've shipped a RAG-powered knowledge base on GCP that cut support costs by 12%. I've taken a stock intelligence app from "what if" to deployed MVP over a weekend using Claude Code. I know the difference between Sonnet and Haiku, and more importantly, I know when to use which one and why.
Delivery Hero / Foodpanda
- Subscription economics: Engineered 1-click enrollment and strategic free trial entry points that swung conversion from 8% to 38% and meaningfully lifted resubscription rates and LTV.
- Wallet strategy: Architected the shift to internal fintech wallet. Order share went from 3% to 27%, $30M GMV in 2 months, 6.99x ROI on cashback spend. Then connected Wallet to Subscriptions to build a loyalty flywheel.
- Partner integrations: Brought Spotify, TADA (SG), LineGo (TW), and Bolt (MY) into the Pro subscription. Turned it from "you save on delivery" to "this is your lifestyle membership." Built a reusable V1/V2 integration playbook.
- Incentives at scale: Owned the EUR 300M+ incentives domain. Built Offers Zone and Audience Targeting used across Quick Commerce, Shops, and Pandago. Drove EUR 60M in cost savings.
- AI knowledge base: Built a GenAI-powered semantic search tool using GCP Vertex AI for the Turkey subscriptions launch, giving internal teams and CX instant access to product details. Now extended to all markets. Reduced support costs by 12% through faster time-to-resolution.
- Payment reliability: Overhauled routing infrastructure to hit 99.8% payment success rate. In fintech, that number is everything.
How I got here
Things I built because I wanted to
What I learned: Writing a thorough PRD before touching any code is what makes AI-assisted development fast. The skill isn't coding. It's specification, architecture decisions, and understanding cost tradeoffs between models like Sonnet and Haiku. That clarity is the same skill that makes cross-functional programmes work at scale.
What I learned: The product decision that mattered most wasn't the AI model. It was designing the information architecture so the right answers surfaced for the right queries. That's a product problem, not an engineering one. The tool now serves all markets and drove a 12% reduction in support costs through faster resolution times.
What I learned: Composition is a design skill, not just a technical one. Choosing which components to use, how they relate to each other, and where to break from the library's defaults requires the same product judgment as deciding what goes on a roadmap and what doesn't.
What I learned: AI app builders are excellent for validation and terrible for iteration. The v1 comes fast, but the moment you need to deviate from what the tool assumed, you're fighting it. That taught me to evaluate AI tools the same way I evaluate any product: by their constraints, not their demos.
Where strategy meets building
Say hello.
I'm always happy to connect with people thinking about product strategy, AI-native development, or building at the intersection of product and engineering. If something here resonated, I'd welcome a conversation.