Product Manager · Mumbai
I turn messy business processes into software people use. Requirement, prototype, approval, spec, launch: I carry the product the whole way.
Scroll. This is one product's story.
From WhatsApp, Excel, email, phone to one clear requirement
A perishable-goods business bought through WhatsApp, Excel, email and phone. Quotes were typed in by hand, and buyers chased directors for approvals. A purchase request took about seven days to become an order.
My first job: sit with them and turn that noise into one clear requirement.
From requirement to clickable prototype
A prototype that looks and works like the finished product: vendors quote in their own portal, every quote is compared with the market price, and approvals go to the right person by order value.
From prototype to client approval
The client clicks through the real flows with realistic data in demos. We change it until they approve it, so they sign off on something they have already used.
From approved prototype to spec
Every rule, screen and approval, written from the approved prototype so developers never have to guess. Each test is tied to the rule it proves.
From spec to working software
I answer the developers' questions, check their work against the prototype, run the testing, and review every change before it merges.
From about 7 days to 3 days
Beforeabout 7 days
Live3 days
First live buying cycle, October 2026: 190 products, 22 purchase orders, 18 vendors. Request to order took 3 days.
Pull back
Each line is a product, drawn as far as it went through the four gates. Eleven prototyped, eight built, four live. Point at a dot to see it; click to open it.
Prototype and spec Built Live
Four lines that reached the end
Your turn
The same screen from the story, working, with sample data. You are the finance approver. Approve it, or send it back with a reason.
| Vendor (sample) | Rate / kg | vs market ₹21.00 |
|---|---|---|
| Green Valley Traders · awarded | ₹20.60 | 1.9% below |
| Sunrise Agro | ₹21.40 | 1.9% above |
| Kisan Fresh Co. | ₹22.80 | 8.6% above |
800 kg (300 kg tomato, 500 kg onion) · ₹16,480 · lowest quote awarded, so no reason is needed.
Approval chain · by order value
History
Posted on the wall
If the written spec and the prototype the client approved disagree, I fix the spec, not the prototype.
Every field has its rule, its format and the exact error message the user will see.
Anything outside the requirement is an open question for the client, not a feature I slip in.
Tested on the real screen, not "it should work". No sign-off with a caveat attached.
With the cost of each and my recommendation, so a decision takes minutes, not a meeting.
What is wrong or missing comes before what is fine. Agreement has to be earned.
Where the thread starts
Seven years fixing what broke for customers taught me to care about what happens after launch, not just before it.
Education software, banking hardware for customers in the UK, US and Europe, then a payments product. I learned where software breaks for real people.
Ran sprints and releases for product, QA and DevOps teams, and set up Jira automation that cut manual follow-up by about 30%.
My role ended in a company layoff.
The only product owner on two business platforms, plus nine client products. Eleven lines, four of them live.
B.Sc. Information Technology, S.M. Shetty College of Management Studies, Mumbai · Certified Scrum Master
Built for my own work, with AI
About 40 skills and 10 automatic checks. Closing a module went from about 50 manual steps to one command.
Reads every company code repository and emails leadership a PDF each morning. It refuses to send if any data is missing.
Starts a new product with 18 automatic checks, shared screen components and a page-speed limit.
Notes by typing, photo or voice in English and Hindi, turned into a list of who is waiting on whom.
↑↓ move · Enter go · Esc close