Designer with an architect's head and an artist's hands. I think in systems and sketch in the margins. Seven years of untangling complex products taught me that creativity is not decoration; it is structure you can feel. Strong opinions, always with receipts.
From 340B healthcare platforms to defense drone swarms to enterprise SaaS, I build design systems that scale and interfaces people trust. Lately I keep exploring how AI and AR/VR can make software more human.
Projects & works · The proof
Flagship · Healthcare SaaS · 340B
Seven fragmented tools became one coherent product experience for the 340B Drug Pricing Program.
User satisfaction 5.6 → 8.8 / 10 · support tickets 65 → 39 per week
Read the case study →
Flagship · Defense · Ground Control
A zero-error control language for autonomous drone swarms, invented from scratch.
Task success 58% → 92% · mission flow build time 19 → 8 min
Read the case study →Learnings · Field notes
The receipt: The PharmaForce component library standardized on outline icons across fifty component types.
The tradeoff: Outline icons can cost recognition speed at small sizes. In a dense claims UI, the lighter visual weight kept tables scannable, and that was worth the trade. Solid variants stayed reserved for active states.
The receipt: The 340B claims tables kept their column density. Summary widgets went on top instead of stripping columns out.
The tradeoff: Density fights scannability. Cutting columns felt cleaner but tested worse: analysts distrusted "simplified" views. Progressive summarization beat subtraction.
The receipt: The Bulk Payor Upload wizard split one dreaded task into three steps: template, upload, review.
The tradeoff: More steps means more clicks. Even so, bulk upload time fell from 2 hours to 10 minutes. Steps cost clicks; they buy certainty.
The receipt: Swarm UX added confirm-with-delay to destructive drone commands, and the upload review screen itemized every invalid record.
The tradeoff: Friction on the happy path annoys; friction at the failure point reassures. Error clicks dropped 60% in testing after the pause was added.
The receipt: The PharmaForce export wizard got live progress toasts and a re-download history panel. Tickets asking where files went fell 70%.
The tradeoff: Ambient status can become noise. The toasts earn their place by appearing only while something is actually happening, then getting out of the way.
The receipt: The configuration wizard shipped with smart defaults for frequency, dates, and claim types. Users completed report setups with zero mis-configurations on first try.
The tradeoff: Defaults can hide power from experts. Every default stayed one tap from its full control, so speed never cost capability.
System thinking · The method
A one-off fix solves a screen. A system solves every screen that has not been designed yet.
At PharmaForce, seven tools each carried their own buttons, tables, and layouts, so users re-learned the product seven times. One shared library replaced all of it. QA rounds per feature fell from 5 to 1 or 2, and releases grew from 2 to 5 features a month.
Good design is a system pretending to be simple.
My go-to architecture
Results · Attached to their projects
Fields I have worked in
My journey · Opt-in story
Mechanical engineering at B.V. Raju Institute of Technology. Machines taught me tolerances and constraints; the sketchbook kept asking why the machine’s interface felt like an afterthought.
Constraints are not the enemy of creativity. They are its syllabus.
End-to-end client design at Psynik Solutions, spanning e-commerce, EdTech, hospitality, and fitness, then a PGP-D at IIT Bombay to turn instinct into discipline.
Breadth first, then depth. Every industry sharpened a different edge.
Ground control systems for robotics, drones, and agriculture at Brane Enterprises. Modular design systems built from scratch; operator training time cut by 35%.
Design for stress, not just use. In the field, calm interfaces save missions.
Senior UX at PharmaForce: an enterprise design system covering 95% of UI components across a compliance-heavy 340B healthcare platform, cutting development cycles by 60%.
Systems thinking beats screen thinking. One source of truth, seven products.
Contact · Say hello
Complex platform? Mission-critical tool? A design system that needs taming? I am one message away, and I text back fast.