I’m Rama Gudur, a product manager with experience delivering regulated, high-impact fintech products across global markets. My work spans embedded finance, lending, and payments — with a focus on building systems that scale, and products that get used.
I bring structure to ambiguity, push for clarity in decision-making, and work comfortably at the intersection of compliance, engineering, and commercial execution. I prioritise velocity without chaos, and care deeply about designing products that hold up in real-world environments — not just slides.
This page contains a sample product portfolio centred around Tap-on-Phone, a mobile-first contactless payment solution I helped bring to market. It includes a full set of product artefacts designed to reflect how I approach strategy, execution, and cross-functional leadership.
Included:
- Case Study — A narrative overview of the problem, solution, and outcome
- PRD (Product Requirements Document) — Detailed requirements and trade-offs
- One-Pager — Strategic framing of the product and its value
- User & Partner Research Summary — Insights that shaped the MVP
- Personas — Representative users grounded in real interviews
- Success Metrics Dashboard — Targets across UX, ops, infra, and GTM
- Roadmap Snapshot — Visual plan from discovery to GA
- Go-to-Market Checklist — What we needed to launch confidently
- Retrospective — What worked, what didn’t, and what I’d do differently
- Visuals — Sample wireframes and flows from the merchant UX
This portfolio is designed to demonstrate structured thinking, outcome focus, and the ability to navigate complex technical and regulatory environments while delivering a scalable product.
Case Study: Launching Tap-on-Phone – Mobile Payments Without a PoS device
Context
I led the global rollout of Tap-on-Phone, a mobile-first solution enabling merchants to accept contactless card payments directly on Android phones—no terminals, no cables, no waiting for hardware. The goal was to reduce payment friction for small and micro-merchants across multiple regions, especially where hardware cost or delivery logistics hindered adoption.
The vision: make any compliant Android phone a payment device—secure, certified, and scalable.
My Role
As Product Manager for Tap-on-Phone, I was responsible for:
- Defining the global product roadmap
- Coordinating cross-functional agile squads across compliance, engineering, design, and commercial teams
- Leading regional adaptations and internationalization strategy (UK, Europe, LAC, NAM)
- Overseeing end-to-end product development for value-added services (e.g., fraud tools, donations, loyalty)
I also drove KPI definition, market analysis, GTM readiness, and authored core documentation including PRDs, roadmaps, and security artifacts.
Problem Discovery
Through merchant feedback and PSP partner interviews in the UK and globally, we identified several consistent pain points:
- Small businesses (like mobile hairdressers or delivery couriers) lacked access to affordable, secure, and quick-to-set-up card payment options.
- Traditional hardware was expensive, cumbersome to deploy, and often arrived too late for high-churn SMBs.
- Merchants wanted simplicity: "If I have my phone, I should be able to get paid."
We also recognized growing demand for compliance-aligned solutions post-COVID, where touchless payments were expected by default.
Approach
We prioritised three dimensions early on:
- Compliance-first MVP: We launched with PCI CPoC certification, focusing initially on contactless-only transactions without PIN. This allowed us to move quickly and reduce audit overheads.
- SDK-first distribution: Rather than launching a branded app, we enabled PSPs and banks to integrate the tech via SDKs, accelerating distribution and leveraging trusted merchant relationships.
- Global readiness: We embedded multi-market localization and legal review from the start - including support for Dynamic Currency Conversion, fraud prevention APIs, and multi-language onboarding flows.
Key Trade-offs
- Deferred iOS support: Due to Apple's NFC restrictions, we focused exclusively on Android to maintain velocity and compliance alignment.
- MPoC (PIN entry) moved to Phase 2: We launched without PIN to reduce certification complexity and validated the need for it through market feedback post-MVP.
Outcome & Impact
Tap-on-Phone launched across five global regions in under 12 months.
Results included:
- 62% of merchants completed their first transaction within 48 hours of onboarding
- Transaction success rate exceeded 96% across supported Android devices
- Expanded payment acceptance to previously cash-only sectors (e.g., mobile vendors, on-demand services)
- Enabled partners to white-label the solution, increasing reach without duplicating go-to-market effort
- Supported value-added services: Donations, Carbon Calculator (ESG), Loyalty, and DCC - creating new revenue streams for PSPs
Internally, we streamlined cross-functional delivery by establishing clear documentation practices (PRDs, compliance logs, API flows), which improved velocity and stakeholder alignment.
What I Learned
This product deepened my appreciation for two things:
- The hidden complexity of payments: Beneath the simplicity of "just tapping a phone" lies a web of compliance, trust, security, and edge-case handling. Getting that right across devices and geographies takes real rigor.
- The power of strategic trade-offs: By narrowing scope early (e.g., no PIN, Android only), we delivered a globally viable MVP faster—and used post-launch insights to prioritize what mattered most to merchants.
Product Requirements Document (PRD): Tap-on-Phone
Author: Rama Gudur
Date: October 2024
Status: Final – Sample PRD
Version: 1.1
Approver: N/A – Portfolio Sample
Preamble
This sample PRD outlines my structured approach to tackling a technically complex challenge: enabling small merchants to accept contactless card payments directly on their mobile phones. It demonstrates how I think through product design, trade-offs, user validation, and outcome-focused delivery — all framed through a UK-first lens, with consideration for scaling across diverse markets.
1. Overview
1.1 Objective
Enable small merchants to accept contactless card payments—including PIN entry where required—directly on Android phones via NFC, without external hardware.
1.2 Background
In the UK and many global markets, smaller businesses face high barriers to accepting card payments—primarily the cost of terminals and lengthy onboarding. Tap on Phone offers a secure, cost-effective alternative for mobile-first merchants. It is designed to meet PCI's CPoC (Contactless Payments on COTS) and MPoC (Mobile Payments on COTS) compliance standards.
2. Goals and Non-Goals
2.1 Goals
- Accept contactless payments (Visa, Mastercard, Amex) on Android devices
- Achieve PCI CPoC compliance and prepare for MPoC certification
- Support PIN entry for high-value transactions (MPoC, Phase 2)
- Provide an onboarding flow under five minutes with no hardware dependency
- Launch initially in the UK, with Poland and India as expansion markets
2.2 Non-Goals
- iOS support (currently unfeasible due to Apple's NFC restrictions)
- External card readers or physical point-of-sale devices
- Custom enterprise integrations in the MVP phase
Trade-Offs
- Android-only: Due to Apple's NFC limitations, we're focusing on Android, which aligns with regulatory feasibility and merchant availability.
- Phase 2 for MPoC: Deferring secure PIN functionality to a second phase enables faster MVP delivery while reducing compliance overhead.
- SDK-first approach: Integrating via SDK with PSPs enables rapid scaling through existing merchant relationships, rather than launching a standalone branded app initially.
3. Users & Insights
3.1 Target Users
- Joe, an independent window cleaner in Manchester taking £15–£50 per job
- Amira, a mobile hairdresser in Birmingham offering on-site appointments
- Tomasz, a courier in Warsaw collecting payment on delivery
- Sundar, a market trader in Chennai selling produce with average ticket sizes of ₹200–₹800
3.2 Research Insights
- Conducted interviews with six sole traders and micro-merchants via PSP partners (e.g. Stripe Atlas, Razorpay)
- Common themes: "I don't want another machine", "Cards are more reliable than QR wallets"
- Onboarding delays due to waiting for physical terminals were a key blocker
- PIN functionality seen as useful only for higher-value transactions, not everyday usage
4. Requirements
4.1 Functional Requirements
- NFC-enabled tap-to-pay on Android 8.0+
- In-app transaction status: success, failure, pending
- Exportable transaction history with filtering and search
- Digital receipts via SMS, email, or QR code
- PIN entry interface compliant with MPoC standards (Phase 2)
4.2 Non-Functional Requirements
- Transaction processing time under two seconds in normal conditions
- Offline queuing and retry logic for intermittent network environments
- Accessibility compliance: WCAG 2.1 AA
- Multi-language support: English, Polish, Hindi (UK launch in English)
4.3 Compliance & Security
- Full PCI CPoC compliance for MVP, with MPoC targeted for Phase 2
- Secure PIN entry using Trusted Execution Environment (TEE)
- End-to-end encryption between device and acquiring partner
- Device integrity monitored through app attestation and runtime checks
5. Success Metrics
These metrics demonstrate performance across four domains: User Experience, Operational Readiness, Infrastructure Reliability, and Go-to-Market Fit. The goal is to ensure the product isn't just functional—it's scalable, reliable, and trusted in the real world.
User Experience
1. Merchant Activation Rate ≥ 60% within 48 hours
- Indicates ease of onboarding and immediate value
- Tracked from install → setup → first transaction
2. Net Promoter Score ≥ 45
- Reflects merchant satisfaction and likelihood to recommend
- Collected via in-app survey after 5+ transactions or 7 active days
Operational Readiness
1. Transaction Success Rate ≥ 95%
- Ensures reliability across various devices and network conditions
- Monitored via backend logs and PSP dashboards
2. Refund Completion Rate ≥ 98%
- Measures operational trust and edge-case handling
- Tracked via PSP reporting and merchant app logs
Infrastructure Reliability
1. System Uptime ≥ 99.9% (excl. planned maintenance)
- Critical for day-to-day reliability
- Monitored using synthetic testing and health checks
2. Mean Time to Recovery (MTTR) < 1 hour for Sev-1 incidents
- Ensures rapid incident response and resolution
- Logged through engineering runbooks and post-incident analysis
Go-to-Market Fit
1. Regional Availability ≥ 99% in live markets (UK, India, Poland)
- Validates full operational readiness in each territory
- Based on device support, onboarding funnel, and PSP stability
2. Device Coverage ≥ 90% of Android handsets used by UK sole traders
- Ensures the product supports most real-world phones
- Tracked via anonymised app telemetry and Google Play device catalogue
Metric Philosophy
These aren't vanity KPIs. Each one validates a known risk—technical, regulatory, or user-facing. Together, they tell a complete story: this product doesn't just work, it scales, and earns the trust of merchants in real-world scenarios.
6. Dependencies
- Android NFC SDK (API Level 21+)
- Device compliance with TEE for MPoC
- Integration with payment processors (e.g. Stripe, Adyen)
- Engagement with a PCI-certified testing lab
7. Timeline
Milestone | Target Date |
Discovery Complete | 15/11/2024 |
MVP Build (CPoC) Complete | 01/03/2025 |
Beta Launch (Android only) | 01/04/2025 |
Phase 2 – MPoC Build Start | 01/06/2025 |
General Availability (GA) Launch | 01/08/2025 |
8. Open Questions
- Will secure PIN (MPoC) be a commercial differentiator or simply required to win larger merchants?
- Should we lead with a branded merchant app or distribute via white-labelled SDK partnerships?
- Are there any legal or regulatory constraints in India or Poland that differ significantly from UK requirements?
Product One-Pager: Tap-on-Phone
Product: Tap-on-Phone
Type: Contactless Payment Acceptance (Android, NFC)
Markets: UK (lead), Europe, India, LAC, NAM
Status: MVP launched across 5 markets | Phase 2 in development
Objective
To enable micro and small businesses to accept contactless card payments directly on Android NFC-enabled smartphones - without external card readers - through a fully certified, software-based solution distributed via PSPs and acquiring partners.
Definition of Success
- Merchants complete their first transaction within 48 hours of onboarding.
- The product maintains a ≥95% transaction success rate across supported Android devices.
- PCI CPoC certification is secured for MVP; MPoC (PIN entry) certification follows in Phase 2.
- SDK integration achieves widespread adoption across three initial markets.
- Cost-to-serve is lower than hardware-based card acceptance.
Strategic Rationale
Traditional hardware-based point-of-sale solutions are cost-prohibitive and logistically complex for small and mobile businesses. Tap-on-Phone leverages existing Android infrastructure to eliminate merchant onboarding friction and lower barriers to digital payment acceptance. Mastercard's global partner network uniquely positions us to scale this compliant, software-based alternative to traditional terminals.
Scope (Version 1.0 – MVP)
Included:
- Contactless card acceptance via NFC on Android 8.0+ devices
- Real-time transaction confirmation, digital receipts, and refund capability
- Localised onboarding and support in UK, Poland, and India
- PSP/distributor SDK with customizable merchant UI
- PCI CPoC certification and security monitoring
Excluded (Out of Scope):
- iOS support (NFC restrictions prevent implementation)
- Secure PIN entry (MPoC) - planned for Phase 2
- Custom white-labeled merchant apps or direct-to-merchant distribution
Competitive Landscape
Hardware-based providers like Square and SumUp dominate the market, while software-only contactless solutions see limited adoption due to regulatory and implementation challenges. Few solutions offer PCI CPoC certification or scalable SDK distribution through acquiring partners. Tap-on-Phone fills this gap with a secure, globally scalable, partner-led model, differentiated by Mastercard's compliance expertise, brand strength, and market reach.
Timing Considerations
- Q3 2025: General Availability launch aligns with partner onboarding cycles and year-end merchant adoption surge
- Regulatory Windows: Certification timing aligns with PCI CPoC/MPoC and UK FCA compliance priorities
- Seasonal Opportunity: Positioned ahead of high-volume retail periods and Q4 promotional cycles in target markets
Strategic Impact
- Expands digital payment access to underserved merchant segments
- Reduces onboarding friction and hardware dependency
- Enhances Mastercard's partner ecosystem through SDK enablement
- Supports broader strategic priorities in embedded finance, ESG (via donations/loyalty APIs), and terminal-less payment infrastructure
User Research/Persona
Product: Tap-on-Phone
Purpose: Inform the design and scope of a mobile-first, hardware-free payment acceptance solution targeting micro and small merchants.
Research Objectives
- Identify adoption barriers related to traditional POS hardware
- Validate core user needs for MVP functionality
- Assess partner readiness for SDK-based distribution
- De-risk compliance and certification assumptions across markets
Target Personas
Ravi — Street Vendor (Bangalore, India)
- Profile: Daily transaction size ₹50–₹500
- Device: Entry-level Android handset
- Pain Point: Reliability issues with UPI; card machines are unaffordable
- Key Quote: “Cards are better than wallets, but I can’t afford a machine.”
- Product Impact: Drove decision to focus on software-only model and compatibility with low-spec Android devices
Sarah — Mobile Beautician (London, UK)
- Profile: On-the-go service provider, £30–£120 per appointment
- Device: Mid-range Android (Samsung A series)
- Pain Point: Informal card acceptance workflow; reliance on bank transfers
- Key Quote: “Clients prefer card, but I end up sending my bank details.”
- Product Impact: Prioritised sub-5-minute onboarding and digital receipt delivery
Kamil — Delivery Driver (Warsaw, Poland)
- Profile: Accepts payments on delivery
- Device: Shared Android device issued by employer
- Pain Point: Limited time per transaction; complex UX reduces efficiency
- Key Quote: “We’re in a rush — I need to tap and go.”
- Product Impact: Informed design of a minimal UI with clear success confirmation and retry handling
Partner Interviews
Conducted qualitative interviews with three key acquiring and PSP partners:
Partner | Region | Key Insights |
Stripe | UK | SDK model preferred to preserve control of onboarding and risk management |
Razorpay | India | Emphasised Android fragmentation risk and the need for broad device support |
Regional Acquirer | EMEA | PCI CPoC compliance required for deployment to regulated merchant base |
Summary of Insights & Product Decisions
Theme | Key Insight | Product Decision |
Hardware resistance | Merchants reluctant to purchase or manage terminals | Software-only approach, no external hardware |
Fast onboarding | Long activation windows caused drop-off | Onboarding flow designed for < 5 minutes |
PIN entry | Not a requirement for low-ticket transactions | MPoC support deferred to Phase 2 |
Receipt expectations | Receipts critical for trust in informal contexts | Email/SMS/QR receipt delivery included in MVP |
Distribution preferences | PSPs preferred SDK over standalone solution | Adopted SDK-first GTM model |
Regulatory dependencies | Certification prerequisites varied by partner/region | PCI CPoC prioritised for initial rollout |
Areas for Further Validation
- PIN entry experience in higher-value use cases (MPoC rollout)
- Local language support for onboarding flows
- Custom branding and white-label SDK needs across PSPs
- UX trust indicators (branding, animation, payment confirmation clarity)
Conclusion:
Research insights played a foundational role in defining Tap-on-Phone’s MVP scope, UX priorities, and go-to-market model. Each product decision was anchored in direct user needs and commercial partner constraints, ensuring that the solution was not only technically feasible, but strategically viable and ready to scale.
Sample Roadmap
Quarter | Phase | Milestone | Description | Owner/Lead |
Q4 2024 | Discovery | Market + Merchant Research Complete | Interviews across UK, India, and Poland to validate scope and demand | Product, Research |
ㅤ | ㅤ | Product Requirements Defined | PRD finalised; trade-offs aligned (e.g. no iOS, MPoC phased) | Product |
ㅤ | ㅤ | Certification Path Chosen (CPoC) | Compliance strategy locked in for MVP | Product, Compliance |
Q1 2025 | MVP Build | NFC Tap-to-Pay Feature Complete | Functional on Android 8.0+ with receipt and refund flow | Engineering |
ㅤ | ㅤ | SDK Integration with First 2 PSPs | Integration handoff + test suite with Stripe and Razorpay | Product, PSP Lead |
ㅤ | ㅤ | Internal QA + Pre-Certification Audit | Internal test pass and security checklists completed | QA, Compliance |
Q2 2025 | Beta Launch | MVP Beta Live in 3 Markets (UK, India, Poland) | Initial rollout to limited merchants via PSPs | Product, Ops |
ㅤ | ㅤ | KPIs Monitored & Reported | Activation rate, transaction success, refund flow | Product, Data |
ㅤ | ㅤ | Feedback Loop and Sprint Adjustments | UX and device compatibility tweaks post-launch | Design, Eng |
Q3 2025 | Phase 2 – MPoC | MPoC Development Kickoff | Begin PIN entry flow + secure TEE integration | Engineering, Security |
ㅤ | ㅤ | Value-Added Features Scoped | Loyalty, Carbon Calculator hooks planned | Product |
ㅤ | ㅤ | Partner Expansion (2 new acquirers) | EU and LAC partnerships under negotiation | Commercial |
Q4 2025 | General Availability | GA Launch with MPoC | PIN-enabled, certified GA version live | Product, Compliance |
ㅤ | ㅤ | SDK Live with 5+ Partners | Scaled distribution via acquiring partners | Product, GTM |
ㅤ | ㅤ | Postmortem + 2026 OKRs Set | Retrospective, learning log, strategic reset | Product, Strategy |
UX Walkthrough
Success Metric Dashboard: Northstar for Tap-on-Phone
Category | Metric | Target | Why It Matters | How It's Tracked |
User Experience | Merchant Activation Rate (within 48h) | ≥ 60% | Validates ease of onboarding and perceived value | Install → Setup → First Txn funnel |
ㅤ | Net Promoter Score (after 7 days / 5 txns) | ≥ 45 | Captures product satisfaction and likelihood to recommend | In-app NPS survey |
Operational Readiness | Transaction Success Rate | ≥ 95% | Confirms transaction reliability across devices and conditions | PSP logs + backend telemetry |
ㅤ | Refund Completion Rate | ≥ 98% | Ensures trust in edge-case handling and smooth merchant workflows | PSP reporting + refund logs |
Infrastructure | System Uptime (excl. planned maintenance) | ≥ 99.9% | Mission-critical for payment reliability | Synthetic monitoring + uptime dashboards |
ㅤ | Mean Time to Recovery (MTTR, Sev-1) | < 1 hour | Proves mature incident handling and engineering responsiveness | Incident runbooks + postmortem logs |
Go-to-Market Fit | Regional Availability (UK, India, Poland) | ≥ 99% | Validates legal, PSP, and technical readiness per region | Onboarding success + QA test coverage |
ㅤ | Device Coverage (UK Android SMB handsets) | ≥ 90% | Confirms real-world reach and compatibility across target merchant base | Google Play catalogue + anonymised telemetry |
Go-To-Market Checklist: Tap-on-Phone MVP
Objective: Ensure readiness across compliance, distribution, support, and technical operations before MVP launch in UK, India, and Europe.
Category | Checklist Item | ✅ |
Product Readiness | MVP features tested and stable (tap-to-pay, receipts, refund flow) | ✅ |
ㅤ | Android compatibility matrix validated across target devices | ✅ |
ㅤ | Performance benchmarks met (txn success rate ≥ 95%) | ✅ |
Compliance | PCI CPoC audit passed and certification received | ✅ |
ㅤ | Legal reviews completed for UK, India, and Poland | ✅ |
ㅤ | App attestation and secure build pipeline in place | ✅ |
Distribution | SDK packaged and handed off to initial PSP partners | ✅ |
ㅤ | Partner-specific implementation guides created | ✅ |
ㅤ | Developer support channel live (Slack/email/portal) | ✅ |
Support & Ops | Merchant support flows defined (refunds, transaction failures, receipt issues) | ✅ |
ㅤ | Support team briefed and trained on product + edge cases | ✅ |
ㅤ | Escalation process in place for live incidents | ✅ |
Monitoring & Data | Real-time monitoring dashboards configured (uptime, transaction failures) | ✅ |
ㅤ | KPIs + success metrics defined and tracking enabled | ✅ |
Retrospective: Tap-on-Phone MVP
What Went Well
- Defined the product scope tightly around user needs and compliance feasibility (e.g. CPoC first, MPoC deferred), which kept the build lean and audit-ready.
- The SDK-first distribution strategy proved effective, allowing partners to integrate quickly and scale merchant onboarding without building direct acquisition infrastructure.
- Onboarding flow met activation targets — a sub–5-minute setup resulted in over 60% of merchants completing a transaction within 48 hours.
- Early and consistent alignment between product, compliance, engineering, and PSP partners helped reduce last-minute misalignment and delivery risk.
What Didn’t Go Well
- Device fragmentation, especially in India, created more QA complexity than anticipated — test coverage across Android variants was slower and more manual than ideal.
- Receipt delivery (SMS vs email) introduced user confusion due to inconsistent confirmation UI and partner delivery timing.
- Partner implementation timelines slipped where technical responsibilities weren’t clearly assigned or tracked across onboarding.
What I’d Do Differently
- Begin QA automation and device compatibility validation in parallel with engineering sprints — not after MVP stabilisation.
- Involve merchant support and training earlier, so GTM isn't just external-facing but supported end-to-end.
- Design for edge cases (e.g. NFC timeout, offline flows) in the MVP phase to prevent first-launch friction.
- Establish clearer integration SLAs and ownership models with PSP partners to manage GTM accountability and technical handoffs.
Additional Work Snapshots
Beyond Tap-on-Phone, I’ve also led work in adjacent areas of fintech — including digital banking and internal operations tooling. These projects demonstrate breadth across regulated environments, partner integration, and customer-facing UX.
Case Snapshot: Digital Bank
Role: Product Manager (MVP Lead)
Regions: United Kingdom, Europe, India
Timeline: 2021–2022
Status: MVP launched and deployed across three partner institutions
Objective
To build a comprehensive, privacy-compliant digital banking platform from scratch — encompassing onboarding, KYC, account infrastructure, and operations tooling — with emphasis on regulatory compliance and partner scalability.
Responsibilities
- Defined and prioritized MVP scope across core domains: user onboarding, identity verification, account provisioning, and transaction flows
- Led backlog management, sprint planning, and delivery across engineering, compliance, and commercial teams
- Created onboarding flows incorporating regional KYC/AML requirements, including tiered verification, document uploads, and PEP/sanctions screening
- Integrated third-party providers for identity, FX, and payments through secure APIs
- Built internal tools for audit trails, escalation handling, and role-based access control
- Managed localization and partner readiness across three markets, enabling white-label customization and regulatory compliance
Outcomes
- Launched compliant MVP within five months, serving as foundation for deployment across three financial institutions
- Boosted activation rates 18% through streamlined onboarding and simplified user flows
- Enhanced operational efficiency with internal dashboards, reducing manual escalations and improving traceability
- Built scalable platform foundations and governance frameworks to support regulated market expansion
Strategic Themes
- Privacy-first architecture aligned with GDPR and regional compliance frameworks
- Core banking infrastructure: users, accounts, permissions, audit trails
- End-to-end product leadership in a regulated, partner-led environment
- Agile delivery across multi-market launches with direct integration ownership
Metrics Dashboard Insights
Note: All data anonymised. Metrics shown reflect MVP-to-launch period across UK, Europe, and India.
Metric | Target | Actual | Why It Mattered |
Onboarding Activation Rate | ≥ 65% | 70.2% | Validated effectiveness of KYC flow and document upload UX |
Verification Completion (first attempt) | ≥ 85% | 87.5% | Ensured ID+address verification success without manual fallback |
Support Escalation Rate (per 1,000 users) | < 2.0 | 1.4 | Demonstrated tooling reduced friction in Tier 1 issue handling |
Uptime (platform core services) | ≥ 99.9% | 99.96% | Confirmed readiness for partner bank production usage |
Time to Open Account (median) | < 5 minutes | 3 min 47 sec | Showed speed from app entry to account creation |
Region-specific KYC Fail Rate (India) | < 10% | 8.1% | Validated localisation strategy in regulated, high-friction market |
UX flows
Product Philosophy
I approach product management with a focus on structural clarity, strategic alignment, and operational resilience. My goal is to build products that don't just launch — they scale, hold up under pressure, and earn trust in real-world environments.
I prioritize:
- Clear scope and decisive action grounded in business and regulatory context
- A strong delivery culture: well-structured roadmaps, robust metrics, and seamless handoffs
- Cross-functional collaboration — especially at the intersection of compliance, risk, and engineering
I believe a good product manager reduces friction, illuminates trade-offs, and builds momentum by keeping teams aligned and purposeful. Whether shipping SDKs, internal tools, or user-facing platforms, I bring focus and confidence to complex environments.