Works

Curated platforms and systems (2022 — 2026)

Curated platforms and systems (2022 — 2026)

Pizza Hut Malaysia

Omnichannel

B2C Commerce

QSR

Pizza Hut Malaysia

Omnichannel

B2C Commerce

QSR

Pizza Hut Malaysia

Omnichannel

B2C Commerce

QSR

Fynd Commerce

Agentic AI

Enterprise SaaS

B2X Commerce

Fynd Commerce

Agentic AI

Enterprise SaaS

B2X Commerce

Fynd Commerce

Agentic AI

Enterprise SaaS

B2X Commerce

SwapEasy

B2B2C Platform

Re-commerce

Enterprise SaaS

SwapEasy

B2B2C Platform

Re-commerce

Enterprise SaaS

SwapEasy

B2B2C Platform

Re-commerce

Enterprise SaaS

JioMart Digital B2B

B2B eCommerce

Retail Ops

Storefront

JioMart Digital B2B

B2B eCommerce

Retail Ops

Storefront

JioMart Digital B2B

B2B eCommerce

Retail Ops

Storefront

Reliance Ecosystem

Ecosystem Design

B2C Scale

Multi-Product

Reliance Ecosystem

Ecosystem Design

B2C Scale

Multi-Product

Reliance Ecosystem

Ecosystem Design

B2C Scale

Multi-Product

How I Work

I own the architecture, team owns the craft

I assign full module DRI to each designer — but every architectural decision, every structural call, every stakeholder meeting is mine. At Fynd, this meant 5 designers each owned individual modules end-to-end — but no one shipped an architectural change without my review. We moved fast at module level without ever fragmenting the platform logic.

I fix process before I fix the design

At Fynd, PMs consistently shipped vague PRDs that left designers without context — and edge cases fell through. Instead of managing it case by case, I built a structured alignment loop: a quick review gate at each stage where the PM, their manager, and the designer confirm requirements together before work progresses. The PRD gets produced properly end to end. Designers stop guessing. Edge cases stop disappearing.

I ship constraints, not workarounds

On Pizza Hut Malaysia, engineering pushed back on good-to-have UI changes with two weeks left before launch. Instead of cutting scope or arguing timeline, I had the designers ship the remaining changes themselves using Cursor. The constraint became the solution. That's the pattern — I don't work around limitations, I find the path that makes them irrelevant.

I prototype before I design

Before a single Figma frame is finalised, I build a working prototype for client approval using AI tools to assemble end-to-end flows fast. This freezes exactly what gets built, locks edge cases early, and kills assumption-driven scope creep. On Pizza Hut Malaysia, this meant we shipped all end-to-end flows — across app, web, and kiosk — with every edge case covered, in under 3 months. Prototype-first isn't a preference — it's how I eliminate the revision cycles that kill timelines.

I start with why, not how

Most scope creep isn't a PM problem — it's a missing blueprint problem. When the product architecture isn't locked before design starts, every new stakeholder opinion reopens decisions you thought were closed. I don't open Figma until the blueprint is airtight — research, audit, competitor analysis, solution architecture, and user flows are all locked first. By the time pixels happen, the hard decisions are already made and documented.

Let's Connect

Let's talk strategy

How I Work

I own the architecture, team owns the craft

I assign full module DRI to each designer — but every architectural decision, every structural call, every stakeholder meeting is mine. At Fynd, this meant 5 designers each owned individual modules end-to-end — but no one shipped an architectural change without my review. We moved fast at module level without ever fragmenting the platform logic.

I fix process before I fix the design

At Fynd, PMs consistently shipped vague PRDs that left designers without context — and edge cases fell through. Instead of managing it case by case, I built a structured alignment loop: a quick review gate at each stage where the PM, their manager, and the designer confirm requirements together before work progresses. The PRD gets produced properly end to end. Designers stop guessing. Edge cases stop disappearing.

I ship constraints, not workarounds

On Pizza Hut Malaysia, engineering pushed back on good-to-have UI changes with two weeks left before launch. Instead of cutting scope or arguing timeline, I had the designers ship the remaining changes themselves using Cursor. The constraint became the solution. That's the pattern — I don't work around limitations, I find the path that makes them irrelevant.

I prototype before I design

Before a single Figma frame is finalised, I build a working prototype for client approval using AI tools to assemble end-to-end flows fast. This freezes exactly what gets built, locks edge cases early, and kills assumption-driven scope creep. On Pizza Hut Malaysia, this meant we shipped all end-to-end flows — across app, web, and kiosk — with every edge case covered, in under 3 months. Prototype-first isn't a preference — it's how I eliminate the revision cycles that kill timelines.

I start with why, not how

Most scope creep isn't a PM problem — it's a missing blueprint problem. When the product architecture isn't locked before design starts, every new stakeholder opinion reopens decisions you thought were closed. I don't open Figma until the blueprint is airtight — research, audit, competitor analysis, solution architecture, and user flows are all locked first. By the time pixels happen, the hard decisions are already made and documented.

Let's Connect

Let's talk strategy

How I Work

I own the architecture, team owns the craft

I assign full module DRI to each designer — but every architectural decision, every structural call, every stakeholder meeting is mine. At Fynd, this meant 5 designers each owned individual modules end-to-end — but no one shipped an architectural change without my review. We moved fast at module level without ever fragmenting the platform logic.

I fix process before I fix the design

At Fynd, PMs consistently shipped vague PRDs that left designers without context — and edge cases fell through. Instead of managing it case by case, I built a structured alignment loop: a quick review gate at each stage where the PM, their manager, and the designer confirm requirements together before work progresses. The PRD gets produced properly end to end. Designers stop guessing. Edge cases stop disappearing.

I ship constraints, not workarounds

On Pizza Hut Malaysia, engineering pushed back on good-to-have UI changes with two weeks left before launch. Instead of cutting scope or arguing timeline, I had the designers ship the remaining changes themselves using Cursor. The constraint became the solution. That's the pattern — I don't work around limitations, I find the path that makes them irrelevant.

I prototype before I design

Before a single Figma frame is finalised, I build a working prototype for client approval using AI tools to assemble end-to-end flows fast. This freezes exactly what gets built, locks edge cases early, and kills assumption-driven scope creep. On Pizza Hut Malaysia, this meant we shipped all end-to-end flows — across app, web, and kiosk — with every edge case covered, in under 3 months. Prototype-first isn't a preference — it's how I eliminate the revision cycles that kill timelines.

I start with why, not how

Most scope creep isn't a PM problem — it's a missing blueprint problem. When the product architecture isn't locked before design starts, every new stakeholder opinion reopens decisions you thought were closed. I don't open Figma until the blueprint is airtight — research, audit, competitor analysis, solution architecture, and user flows are all locked first. By the time pixels happen, the hard decisions are already made and documented.

Let's Connect

Let's talk strategy