Lead Product Manager & Builder
A decade of 0→1 execution across gaming, e-commerce, and consumer tech. Leveraging AI and local LLMs to accelerate product delivery — from rapid prototyping to PRD drafting. The bridge between engineering, design, and business.
Incubated At
A mix of founder-led and operator chapters across gaming, commerce, and consumer tech, all centered on identifying the right problem, scoping the right solution, and shipping with measurable outcomes.
Quick Commerce of Fantasy Cricket
Led a cross-functional team of 8 (engineering, design, QA) through the full 0→1 lifecycle of India's only fantasy cricket app without team formation. Defined product strategy, aligned stakeholders across engineering and business, and drove GTM. Scaled to 500K+ downloads and grew contest revenue through structural innovations in gameplay format.
Lead Product Manager · Client: Swatch UK
Leading product strategy and cross-functional delivery for Swatch UK's digital gifting platform. Coordinating across Swatch's global team, engineering, and third-party vendors (Adyen, Easy2Play POS). Driving SFCC integration, payment architecture, and checkout optimisation targeting 4% gifting revenue uplift.
SME Product Delivery Studio
Owned end-to-end product lifecycles for SME clients across agritech, fintech, and e-commerce. Led discovery, authored PRDs, and managed cross-functional delivery with engineering teams of 3-5 per client. Consistently reduced MVP time-to-market through rigorous scope control and stakeholder alignment.
One Stop Solution — 33 Apps in One
Bootstrapped a consumer utility app from idea to 10K users with zero marketing spend. Identified a real user pain point, scoped the MVP, shipped in 3 months, and validated product-market fit before seeking capital. First proof of 0→1 execution ability.
The traditional fantasy cricket market had a structural flaw: Time-to-Value (TTV) was 4–8 hours. You selected a full team of 11, waited an entire innings, and only then discovered your result. For 400M+ casual Indian cricket fans, this was simply too much of a commitment.
"The Spell format — predicting 4 consecutive overs rather than an entire innings — cut TTV from hours to under 30 minutes. This structural change, not a marketing campaign, drove the initial viral acquisition."
Defer KYC to withdrawal
Lifted install-to-registration from 45% (industry avg.) to 60% by moving identity verification to the withdrawal step.
Second-screen real-time engagement
Live over-by-over prediction sync that sustained a 25–30% DAU/MAU ratio (~30K/~110K).
GST absorption without user impact
Restructured backend financial routing to absorb 28% GST — maintained 20% net commission with zero change to user-facing fees.
High-concurrency architecture scoping
Defined requirements for a leaderboard serving 3M users with zero latency during peak IPL traffic.
LTV:CAC optimisation & retention loops
Gamified retention loops and organic referral programs that sustained 25–30% DAU/MAU ratio.
Post-free gameplay, engagement fell off a cliff. The root cause was not poor product design — it was contest cancellations. Rooms were not filling to minimum participation thresholds, so contests were voided before they ran. Users who experienced a cancellation rarely returned.
The data told a starker story: bots were winning at only 9.85% vs humans at 36.59% — a 3.7× gap. Bots were too predictable, too static. Skilled users were gaming them systematically.
"The problem was not that bots were losing — it was that they were losing the same way every time. Predictable loss patterns killed the competitive tension that made contests worth entering."
Layer 1 — Historical Probability Engine
Weighted randomisation across probability ranges with 10–15% deviations into valid but less probable outcomes.
Layer 2 — Live Match Adaptation
Pre-spell recalibration using live score, run rates, and median cluster of real user predictions.
Layer 3 — Mid-Spell Reconfirmation Window
Bots re-evaluate when actual runs deviate beyond ±30% from expectation, with proportional adjustments.
New users on fantasy platforms face an immediate trust-commitment barrier. Asking for a wallet deposit before the user has experienced any product value is one of the fastest conversion killers in the category. T-Coins were designed to remove this entirely — giving users a risk-free path through real gameplay before any financial commitment was requested.
Join Spell Rooms
Every participant earns T-Coins — guaranteed. Powers 100% win assurance marketing.
Add Money
Wallet top-ups trigger T-Coin rewards — admin-configurable rate for promotions.
Arcade Games
Luck-based mini-games for additional T-Coin earnings between live matches.
The Core Design Principle
"T-Coin exclusive rooms deliver an identical gameplay experience to paid rooms — same mechanics, same competition, same leaderboard tension — without touching the user's wallet. By the time we requested a deposit, users had already won multiple times."
Swatch was leaving revenue on the table from two high-intent segments: last-minute personal gifters who needed instant delivery, and corporate buyers who needed digital assets at scale with no logistics overhead. Physical gift cards required shipping lead time. Without a digital option, these customers were going to competitors.
Phase 1 Scope (Shipped)
Consciously Deferred
Deferral was deliberate. Validate demand and purchase behaviour with a clean, minimal integration before adding complexity that could obscure the signal.
In 2017, the majority of India's smartphone users were on 1–2GB RAM entry-level Android devices. The explosion of super-apps — Uber, Ola, Zomato, Amazon, Flipkart, Paytm and more — made it technically impossible to keep all services installed simultaneously.
The insight was architectural: these apps didn't need to be native installations — they needed to be accessible. A single lightweight host application serving 33 services via integrated webviews could eliminate the RAM constraint entirely, with one install replacing thirty-three.
"First principles: what does the user actually need? Not the apps — the services. The app is just the delivery mechanism. Remove the delivery overhead and you've solved the problem."
SME clients in emerging markets typically arrive with a business problem, not a product brief. Led hypothesis-driven discovery, translated ambiguous objectives into modular engineering specs, and managed cross-functional teams of 3-5 across multiple concurrent client lifecycles — delivering working software within tight budget and timeline constraints.
Agritech
Supply chain and market access tools for farmers. Offline-first architecture for intermittent connectivity. Radically simplified UX for low digital literacy.
Fintech
Lending and payments infrastructure for underserved SME segments. Regulatory compliance, full audit trails, UPI ecosystem integration.
E-Commerce
Catalogue management, order tracking, vendor management systems for regional operators competing against national platforms.
Helpen Shopping Hub — B2B E-Commerce (O2O)
Directed the 0→1 product strategy for a B2B e-commerce platform. Scaled a lean digital MVP into an Online-to-Offline (O2O) ecosystem, integrating digital demand generation with distributed physical operations across 4 retail nodes.
What This Period Built
"Managing multiple concurrent product lifecycles for clients with fundamentally different domain constraints — where you can't copy solutions between them — is where systems-thinking and prioritisation discipline get sharpened fast."
Product Execution
Technical & AI Scoping
Analytics & UX
Navigating Ambiguity
Product management at its best is applied logic under uncertainty. I start with first principles, build hypotheses from data, and hold conviction loosely enough to update it. The job is not to be right — it is to be directionally correct, fast.
Technical Grounding
An early foundation as a software developer means I do not need a translator between myself and the engineering team. I scope API integrations, understand database schemas, and can identify when technical feasibility is being underestimated — or overestimated.
Constraint as Strategy
The most consistently bad product decision is trying to build too much. I treat constraints — budget, timeline, team size — as inputs to scope, not obstacles to it. Every MVP I've shipped has been defined by what we deliberately did not build.
Beyond the PM: The Writing Discipline
Published author of "99 Days and 6 Seconds... A Countdown to Forever" — a completed novel that demanded the same discipline as shipping a product: sustained structured thinking, rigorous editing, and knowing what to leave out. Currently writing a second book.
AI in My Product Workflow
I use AI tools daily as a product manager — not as a developer, but as an accelerator for PM execution:
Rapid prototyping — using Replit and Claude to build functional prototypes for stakeholder demos before writing a single engineering spec
PRD drafting & refinement — using ChatPRD and LLMs to generate structured PRDs, edge-case matrices, and acceptance criteria at 3x speed
Data analysis — using AI to synthesise user research, parse analytics, and surface insights from large datasets
Shipped an AI product — directed the development of Tricket's real-time AI prediction engine, defining the requirements and working hands-on with the engineering team to scope and deliver it
Currently Reading / Using
Senior PM or Lead PM roles. Consumer tech, gaming, e-commerce, or anything with a complex problem at its centre. Based in Kolkata. Open to remote and relocation.
Also see: tricket.in — the live product I built from zero. | Swatch Gift Cards — the gifting experience I built for Swatch UK.
Incubated at IIM Calcutta & IIT Patna · Currently exploring: AI-native product workflows & LLM-powered delivery tools.