A named surface
We pick the screen that is costing support time and finish that before starting another.
Selected projects
Browse outcomes from dashboards, design systems, and launch sites, then invite a conversation about your roadmap.

On an engagement
We pick the screen that is costing support time and finish that before starting another.
Decisions are written down so a new engineer is not reconstructing them from git.
Each piece of work has an end, not an open retainer that drifts.
Projects
A dense day view that still works on a reception laptop with a small screen.
Colour, type, and spacing moved out of one-off CSS and into a shared package.
Empty states, form errors, and a homepage that survived the first traffic spike.
Beyond this website
Explore projects, process, and ideas on the channels where this work lives.
Background
I work with product teams on web applications where clarity matters more than novelty. My recent work spans design systems, API-backed dashboards, and performance-minded marketing sites.
How I help
Replace a tired product screen without pausing the rest of the release.
Open conversationMove an existing app onto tokens your team can extend after I leave.
Open conversationThe week before a public launch: states, empty views, and the bugs users hit first.
Open conversationA short written trail so the next engineer is not guessing why a component exists.
Open conversation“Ananya took the billing screen from a sketch to something support stopped apologising for.”
Mehul K. · Product lead
Work with me
Mon–Fri · replies within one business day
Remote-first · based in Hyderabad, available across India