Product Portfolio
Akhil
PM
I think in trade-offs, not features — every solution I design is tied to a named pain point, a measurable outcome, and a clear-eyed view of what it costs. Here are three case studies that show how I get from problem to decision.
Selected Work
Three Problems.
One Thread.
01 — 03
Getting Small
Merchants to
Trust PhonePe
A shopkeeper accepts a QR code because his customers insist on it — not because he trusts it. That gap between compliance and confidence is where adoption stalls in Tier 2/3 India.
Zepto
AOV to ₹250
Every competitor can suggest "you might also like." Only Zepto can act on that suggestion in ten minutes. Speed turned into urgency.
SeniorPay —
Payments Without
the Learning Curve
Most payment apps are designed for people who already trust their phone. Seniors don't. SeniorPay starts from the opposite assumption: assume nothing is obvious.
From Sales & Tech
to Product Thinking.
I've spent my career close to the messy middle of how businesses actually run — sales, marketing, GTM execution, and backend engineering. That mix taught me something most product courses don't: a good idea that ignores the trade-off behind it isn't a good idea yet.
My sales background taught me that features don't sell themselves — the problem framing does. My year as a backend developer taught me to ask "how would this actually be built?" before committing to a solution.
Let's think through
hard problems
together.
If something here sparked a thought: a sharper framing, a metric you'd challenge, a direction you'd have pushed differently. I want to hear it.
Open to critique, career conversations, or just a good exchange of ideas. No agenda needed.
Start a Conversation 💬