
GrayQuest
Fintech · Education payments
Fee payments parents finish in one sitting
A monthly fee-financing flow for parents who abandon the moment a form feels like a loan application.
- 2M+parents reachable
- −41%drop-off at KYC
Swati Priya
I design high-stakes fintech, insurtech and edtech journeys that feel simple, trustworthy and easy to complete, across products available to 2M+ parents.
4+
Years designing high-stakes products
2M+
Parents reachable through shipped work
3
Regulated sectors: fin, insur, edtech
0
Flows shipped without a usability pass
Selected work
Three journeys where the hard part was not the interface — it was making a regulated, high-stakes decision feel answerable.

A monthly fee-financing flow for parents who abandon the moment a form feels like a loan application.
2M+
parents reachable
−41%
drop-off at KYC
3 steps
down from 7

Turning a dense diagnostic engine into one clear next action per student, per day.
+27%
session completion
1 action
per visit, by default
9 modules
unified in one system

A claims experience designed for stress: fewer decisions, visible status, no dead ends.
−35%
support tickets
2×
faster first submit
100%
claims with live status
Behind the screens
Process, not decoration. These are the habits and references that show up in every project I take on.
How I work
Every project starts as a sentence per step. If a step cannot be written plainly, the screen will not save it.
Research
Short, awkward, unmoderated calls with real users — parents, students, claimants — before any high-fidelity work.
Craft
The happy path is the easy 20%. I design the failure states in the same pass, not in a follow-up ticket.
Collaboration
Tokens, states and edge cases reviewed together, so handoff is a conversation instead of a document.
On my shelf

Tim Brown
Where I learned to stop defending a solution and start reframing the problem.

Don Norman
Affordances and error-tolerant design still settle half my product arguments.

About
I'm Swati Priya, a Senior Product Designer with 4+ years in fintech, insurtech and edtech. My work usually starts where a product is technically correct but humanly confusing — a loan form, a claim, a diagnostic report — and ends with a journey people can finish without calling support.
I like the unglamorous parts: eligibility rules, error copy, document uploads, status updates. That's where trust is either earned or quietly lost, and it's where I spend most of my time with engineers, risk teams and support.
Currently open to senior product design roles where clarity is a business requirement, not a nice-to-have.
Product design
Research
Domains
Tools