Dhrumil KherdePRODUCT DESIGNER

About

I learned to draw parts before I drew screens.

Mechanical engineering first, design after. The habit came with me: work out what a thing is for, then work out what breaks it. Five years in, I build what I design as well, in Framer or React, which is how the second question gets answered.

Dhrumil Kherde
Open to work
What I look for[and how I got here]

I take on the products that are hard to make clear.

Clinical tools, dense SaaS, anything with too many states and two audiences who need opposite things from the same screen. I would rather do one of those properly than five easy ones.

  1. 2022

    Healthplix. First real design system, and the lesson that a system is a way of not having the same argument twice.

    Handoff time down 20%
  2. 2022 – 23

    Draftsy. A fantasy sports app built around a live draft nobody could be allowed to lose to.

    Engagement up 20%
  3. 2023 – 25

    Duggup, as founding product designer. Web and mobile, built from nothing.

    2,000+ users in week one
  4. 2025 – 26

    N1 Care. A clinical platform serving a clinician mid-shift and a patient at home from the same data. Sole designer on a team of 23.

    Report workflow 75% faster
  5. Now

    Looking for the next one that is genuinely hard to make clear.

Every role, in order

CLINICIANPATIENT

Fig. 01Two audiences, one screen[31 states]

The clinician reads one part of it and the patient reads another. The solid block is the state they both need, and they need opposite things from it.

What I do[05 disciplines]

The parts of the job I actually own.

Five parts of one job. The fifth is the one worth asking about: the work ends at a deployed URL rather than a Figma file.

  • 01ResearchFind the real friction
  • 02Systems80+ components in one system
  • 03InterfaceClinical tools, consumer apps
  • 04MotionBehaviour, not decoration
  • 05ShippingDesigned it, then built it
How I work[four decisions]

Four things I do on every project.

Each one links to the project where it earned its place. Open any of them and the decision is there, with the screens it produced.

  • 01

    Find the real friction

    Practitioners at Expand Health did not need more data on screen. They needed a triage layer that said “look here first.” Four scores gave them one.

    See it in Expand Health
  • 02

    Build the system, not the screen

    N1 Care runs on an 80+ component system with two visual languages: one for clinicians at work, one for the reports patients hold in their hands. Screens fall out of systems.

    See it in N1 Care
  • 03

    Make the work real early

    A static mockup can’t answer “what should this do?” I build working prototypes in HTML and Figma so engineers, founders, and investors react to behaviour instead of promises.

    The prototype that raised eyebrows
  • 04

    Keep going after v1

    The N1 health report went through eight design experiments and a 28-parameter quality checklist before it earned its final form. First versions are for learning, not framing.

    Eight experiments, one report
ALL SIGNALS4 SCORES
01Everything, then four scores
[six doors]
Before you ask[05 answers]

The questions people ask after the call.

Say hello

Fifteen minutes is usually enough.

Enough to work out whether this is a fit. If it isn’t, I will say so and point you at someone better suited.

See the work first
Status
Open to work
Based
India · works remote, worldwide
Best for
Health tech · SaaS · AI products
Reply
Within a day, usually the same one