I don't start with features. I start with why the problem exists — then work the mess until it becomes something a team can actually ship.
The stated problem is rarely the actual one. I dig until the "why" stops moving.
Business goal → user behaviour → product → technology → outcome. In that order, every time.
Messy requirements don't scare me. They're usually where the interesting work begins.
I look for where AI changes the workflow itself — not where to bolt on a chatbot.
Shipping isn't the finish line. Impact is. One metric, one named owner.
Most PMs pick a lane. I've shipped in all four — which means I've seen how a decision made in a dashboard lands on a shop floor.
PLM & planning systems for a 35+ store apparel retailer. Compliance SaaS across 3 product pods. Restaurant platforms with 800+ outlets.
Voice kiosks in 500+ locations. A civic app built with a state government. QR ordering that cut order time 40%.
Luxury-brand checkout flows with an agentic layer. Embedded analytics, rule engines, universal search — decision data where there was none.
Production execution on real factory floors — SMV drift cut to under 3%, returning ~600 supervisor hours a year.
Messes I walked into, questions I asked, and what came out the other side.
Shipped at work — click any card to open the full story.
Retail, apparel-manufacturing and media teams all asked for "an AI agent" — and each meant something completely different by it.
What does this team actually need the agent to do — and how will we know it works?
Lead the design and development of Gemini Enterprise (GE) agents: use-case discovery → agent design → build → evaluation → rollout to client teams.
GE agents taken from discovery to rollout across retail, apparel manufacturing & media.
An apparel manufacturer's SMV drift sat at 15–20% — planned production time versus reality — and nobody could see where it went. Supervisors firefought instead of supervising.
What if the floor could see drift the day it happens, not in next month's report?
Floor-level discovery → mapped where time actually leaked → designed production-execution features around the client's existing ERP and POS, not against them.
SMV drift 15–20% → under 3%. An estimated 520–600 supervisor hours returned every year.
A premium apparel retailer running made-to-measure, inventory, demand planning and allocation across 35+ stores — on processes held together manually by 10+ teams.
What's the one source of truth everything else should hang off?
Designed Ops Core — the planning and product-lifecycle layer around the existing ERP/POS estate. One design-code master across made-to-measure, inventory, demand and option-health planning, pre-production and allocation.
Rolled out across 35+ stores in and outside India, automating manual process for 10+ teams.
Lunch-hour queues, order errors, and a restaurant chain that needed throughput without hiring its way out of the problem.
What's the fastest a hungry human can get from "I want that" to "paid"?
Took a voice-enabled self-ordering kiosk from concept to rollout. Then went after food courts with QR ordering — several outlets, one cart.
Live in 500+ locations across India. QR ordering cut order time by 40%.
Three product pods shipping inconsistent experiences, compliance frameworks evolving under everyone's feet, and enterprise customers falling behind on training.
Why does the product get smarter every release while its users don't?
Standardised UX across pods, shipped a rule engine + universal search + embedded analytics, applied AI to the highest-volume audit workflows, and rebuilt training and enablement around the frameworks customers were actually audited on.
Training completion up 45%. Design inconsistencies down 40%. Audit-readiness up across enterprise accounts.
International restaurant chains running front-of-house, billing, analytics, CRM and back-of-house on one platform — with delivery work stalling somewhere nobody could name.
Where does work actually stop moving — not where do people say it does?
Used cohort analysis to find the real bottlenecks, reshaped the process around them, and owned a mobile inventory app end to end — UI/UX through launch.
Delivery bottlenecks cut 83%. Inventory app reaching 1,600+ users across 800+ outlets.
Civic complaints in Rajasthan disappearing into paperwork — citizens couldn't report safely, authorities couldn't prioritise what they couldn't see.
What if a complaint knew where it needed to go?
Co-founded Karyavahi with the Dept. of IT, Govt. of Rajasthan. Led a team of 4 building anonymous submission with sentiment analysis, auto-routed to the responsible authority.
Top 3 of 7,000 applications in the state. Pitched to entrepreneurship cells of Stanford, UC Berkeley & Northeastern.
Things I made on my own time — to learn, to test an idea, or because a real user needed it.
A gamified product-thinking game for engineers — branching scenarios, an animated PM character and a live leaderboard. Launched on Product Hunt.
A Gemini Enterprise chatbot for a concept sneaker store — Dialogflow CX subagents, Vertex AI Search data stores and full architecture docs.
Gym management web app for a Jaipur training centre — role-based views, slot logic, fee tracking, physio management, built for low-tech staff.
Problem framing, user journeys and end-to-end design for a pickup app that helps households refurbish, recycle or resell.
Rapid prototypes and point-of-view demos for enterprise retail and D2C clients — PLM, ops platforms, retail-intelligence dashboards.
Methods, tools and domains I use to turn the mess into a product.
What do you investigate first?
A roadmap is a sequence of bets. Strategy is knowing which bets you're refusing to make, and why. If your roadmap survives every new piece of information unchanged, it isn't a strategy — it's a queue.
Feature requests are symptoms. When a product is broken, adding features is how you bury the problem under new surface area. I'd rather delete three things than ship a fourth that compensates for them.
I was an engineer. The best technical ideas come from people who saw the raw problem — not a finished PRD. Handing engineers a solution to build wastes the smartest people in the building. I even built a game about this.
Adding a chatbot because everyone else did is decoration. The real question is whether AI can collapse an entire workflow — remove the step, not decorate it. If it can't, don't ship it.
Polish is persuasive — that's what makes it dangerous. I stress-test the decision underneath before falling for the Figma. Shipping isn't the outcome; the metric moving is.
Built "Think Like a PM" — a gamified branching-scenario game. Launched on Product Hunt.
"Willow" — a Gemini Enterprise concierge with Dialogflow CX subagents and Vertex AI Search.
Adding agentic layers to luxury retail checkout — where the store talks back.
One metric, one named owner per process. Making accountability a product feature.
Not AI added to workflows — workflows redesigned because AI exists.
Zero-to-one products: gym ops software, civic tech, whatever has a real user attached.
Got one of these brewing? Let's break it down together →
I'm a Senior Product & Outcome Manager at devX AI Labs who enjoys sitting in the uncomfortable space between:
business problems × user problems × technology
I like problems that don't come with a clean PRD. The ambiguous ones. The ones where everyone has a different opinion about what should be built — because that's usually where product thinking matters most.
I started as a software engineer, co-founded a civic-tech startup with a state government, and have since shipped products for factories, restaurants, retailers and compliance teams. Different rooms, same job: find the real problem, make it simple, make it matter.
That's the shape of it — the interesting part is what your specific mess reveals at each step. Send it to me and I'll break it down properly →