Product-focused UX designer
Portfolio 2026
I turn complex workflows into products people can use and developers can build.
Close to three years of product design across fintech, e-commerce, ERP and marketplaces. Sole designer on multiple products, from requirement analysis with clients and stakeholders to developer handoff.
See the workTwo shipped client projects and two self-initiated ones. Each shows the business problem, the calls I made and what they cost.
All case studies on BehanceA micro-finance lender's staff, credit managers, partner banks and affiliates work the same loan application, from lead to sanction.
The call. One review screen in twelve states, shared by every desk, instead of a tailored screen per role. A file changes hands four times and nobody re-learns it.
Families in Hyderabad book a verified pujari, a bhajan band and the samagri in one place. Each provider runs their side from their own app.
The call. Pujaris, bands and stores sign up, get approved, take work and get paid in the same order. I designed that sequence once and changed only the steps where their work differs.
One place for the things people track: water, food, vitals and exercise, with reports worth handing to a doctor.
The call. No streaks. A missed week is when you most want the readings, so Tracto counts the days you did log, and that number only goes up.
A web app for Indian freelancers that brings tasks, client conversations, invoices and time into one calm dashboard.
The call. Design the money loop first. A client's approval in the project thread becomes an invoice, with GST or LUT wording picked from the client's country.
How I work
Understanding the business
Rinova earns on fees and insurance, pays affiliates for referrals and only earns when a loan is disbursed. Tracing one ₹2,30,000 loan showed me which of those numbers the admin needed in front of them.
Following one loan's money →Working through ambiguity
Before drawing Tracto I wrote four constraints, like no diagnosis and no data leaving the phone, so later decisions had something to fail against.
What Tracto will not do →Explaining decisions
For every project I keep a record of what I chose, what it cost and why, so a reviewer can argue with the reasoning behind each screen.
The calls that shaped Rinova →Working with engineering
Rinova's developers built alongside the design, so every stage got one owner, a fixed list of exits and a message for the customer before its screen was final.
What the developers built against →Using AI well
I use it for research prep, sample data and a second read of my own logic. The product calls come from the brief, the people using it and the team.
An example from Rinova →Making the team better
Named states, components with every variant and one status language across portals. At Starkin that cut design-to-dev rework by about 40%.
Experience →About
I studied mechanical engineering at PES University and moved into design through robotics. My first UX work was operator screens for autonomous warehouse robots at Ati Motors. The habit of thinking in systems stayed: I map the states and the people before I draw anything.
Since then I've been the only designer on six-plus products in fintech, e-commerce, ERP and marketplaces, owning the full cycle: requirements with clients and product managers, wireframes, high-fidelity UI, prototypes, usability testing and annotated developer handoff.
An operations role where I kept designing: mapped approval workflows with leadership and operations, redesigned the digital touchpoints and removed manual handoffs between approval stages.
Sole designer on client products in fintech and marketplaces, often several running at once. Specs built for implementation cut design-to-dev rework by about 40%.
Redesigned workflows across 5+ K-12 cloud ERP modules, from admissions to inventory, cutting average task time by about 30%.
Designed operator screens for autonomous mobile robots in warehouses, validated with operators, cutting task completion time by about 25%.
