Naman JainProduct Manager

Product Manager · Growth, Monetization & Analytics

Naman Jain

I turn broken customer journeys into measurable growth and scalable operating systems.

At AlloHealth, I increased repeat revenue contribution from 33% to 45%, lifted realized LTV, and shipped payout and automation products. Now focused on B2C fintech across lending, payments, trading, and wealth.

View production workDownload resume
Open to Product Manager roles in Bengaluru
Seller Affordability OS
Seller commerce overview dashboard
Borrower mobile payments and Splitstore screen
Independent fintech caseAffordable CommerceBorrower mobile · Seller web · Lending platform
Lifecycle growthMonetizationProduct analyticsFinancial systemsAI operations

Production work · AlloHealth

Products shipped. Business metrics moved.

Aggregate operating evidence from my Founder's Office and Repeat Business roles. No confidential customer data is shown.

01

Growth & lifecycle

Built repeat into a measurable business line

Owned the post-first-purchase journey across fulfilment, treatment support, follow-up booking, reschedules, no-shows, and repurchase with a blended human-and-AI team.

33% → 45% revenue mix₹6.5K → ₹7.5K realized LTV
02

Conversion

Rebuilt the doctor-to-purchase handoff

Added product guardrails and a doctor-agent workflow so patients understood their prescription and could move cleanly from consultation to purchase.

35% → 85% handoff~5,000 eligible patients / month
03

Fintech-adjacent platform

Shipped an automated doctor payout product

Designed tiered payout economics, calculation and approval workflows, statements, payslips, and payment initiation in four weeks with a lean build team.

₹25L monthly volume21.7% → 16.7% cost / revenue
04

AI & operations

Used journey data to remove avoidable work

Audited WhatsApp journeys with AI-assisted workflows, fixed self-serve booking gaps, and deduplicated time-based calling tasks without losing customer context.

7,000 chats / month9,000 → 6,500 weekly tasks
Read the complete operating evidence

Selected work · 04

Business outcomes, product depth, and system thinking.

Production case studies and independent product concepts show how I work from customer problem to measurable, reliable operating model.

Independent portfolio concept6-month launch plan

Affordable Commerce inside super.money

A controlled commerce vertical that helps eligible UPI users shop by cash flow, complete a transparent credit checkout, and gives sellers the tools to fund and operate affordability.

The strategic questionHow could a UPI app build a repeatable, contribution-positive commerce business around what users can responsibly afford?
  • Affordability-first discovery
  • Repayment-aware bag and checkout
  • Merchant Affordability OS
Read case studyOpen prototype
End-to-end product walkthrough
Affordable Commerce prototype overview
2 live prototypes3 product bets8 system diagrams
Production impactFunnel · UX · operations

The 60-second Handshake

A doctor-side exit intervention that kept first-time online follow-up patients on the call long enough for a care agent to join, explain fulfilment, and complete the handoff.

The product questionHow might we protect the highest-leverage handoff in a new online repeat-consultation journey?
  • Handshake rate: ~55% → ~90%
  • Successful handshake: ~65% same-day conversion
  • No handshake: ~35% same-day conversion
Read case studyTry prototype
Doctor call · Rx handoff
+35 pp handshakeInteractive mockProduction result
Live product testResearch · strategy · prototype

Wispr Notetaker + Screen Context

Today, Wispr turns meeting audio into notes. I designed an optional layer that also saves the exact screen behind comments such as “change this banner,” so the final task is clear without a manual follow-up.

The product questionHow can Wispr connect what was said to the exact thing being shown on screen?
  • Today: transcript, summary, decisions, and action items
  • Missing: which screen or component “this” refers to
  • Proposal: link the comment to a screenshot, pointer, and owner
Read case studyOpen prototype
Evidence → product model → interactive prototype
Wispr product concept explaining what Notetaker does today, the missing visual context, and the proposed Screen Context add-on
1 live test2 Wispr surfaces3 execution outputs
Production-informed · public-safeMulti-journey systems study

Healthcare Journey Systems

How customer journeys become reliable production systems through explicit API contracts, workflow states, event-driven handoffs, schema decisions, observability, and failure recovery.

The systems questionHow do complex customer journeys become explicit, measurable, and recoverable production workflows?
  • API and integration contracts
  • State, entity, and schema modelling
  • Events, queues, and failure recovery
  • Observability and business metrics
Read systems case studyView business outcomes
Sanitized system context
Healthcare journey systems architecture overview
ArchitectureAPI designSchema designReliability

Production evidence

Measured outcomes from my current operating work.

At AlloHealth, I own customer journeys and business metrics across checkout, fulfilment, lifecycle communication, repeat, payout economics, and operational efficiency.

33% → 45%

repeat revenue contribution

End-to-end post-purchase journey ownership

₹6.5K → ₹7.5K

realized customer LTV

Latest quarter versus the prior two-quarter baseline

35% → 85%

doctor-agent handoff

Across roughly 5,000 eligible patients per month

21.7% → 16.7%

doctor payout cost / revenue

Tiered payouts across 60+ doctors and ₹25L monthly volume

How I work

From ambiguity to an operating product.

I use customer research, data, design, and systems thinking as one product discipline.

01

Frame the decision

Define the customer, business constraint, non-goals, baseline, and one falsifiable outcome before adding features.

02

Design the whole system

Connect UX, operations, economics, risk, data, APIs, and failure states so the journey can survive production.

03

Ship with evidence

Instrument the funnel, use controlled experiments, protect guardrails, and scale only when cohort economics hold.

SystemsAPIs, services, schemas, failure recovery
TrustConsent, disclosure, risk, compliance
GrowthFunnels, cohorts, A/B tests, unit economics
CraftResearch, journeys, prototypes, storytelling

Writing

Thinking in public, while the thinking is still alive.

Notes on product systems, fintech, markets, and making decisions when certainty is unavailable.

View all writing

About

I care about the moment a customer promise meets reality.

I joined AlloHealth's Founder's Office in June 2024, first working on P&L, supply-chain economics, doctor payouts, and fundraising diligence. Since March 2025, I have led Repeat Business across the full post-purchase customer journey, leading 2 analysts, 2 engineering interns, 2 customer experience managers, and specialised AI agents.

Before that, I worked on research and AI-assisted product concepts at Cactus Communications. I hold a B.E. in Electronics and Telecommunication from RV College of Engineering. I also managed a ₹10L pledged-capital trading account to approximately ₹16L over two years in college, building hands-on interest in equities, derivatives, bonds, REITs, and market risk.

LinkedInGitHubTableauEmail