Making difficult products feel obvious.

I design the systems, interfaces, and prototypes behind products that are genuinely hard to use, and quietly make them easier.

An isometric stack of five plates. The highlighted plate corresponds to the selected capability: Research.

Track record[measured]
5+
years designing digital products
10
modules for N1 Care, concept to production
80+
components in one clinical design system
75%
faster clinician report workflow
~50%
dev time saved with reusable React layouts
2,000+
Duggup users in week one
7+
production Framer sites live right now
45
chart types in one biomarker library
Selected work[03 / 05]

Products where the mess was the problem.

Proof[on the record]

Claims you can go and check.

One quote, and a ledger of the engagements behind it. Nothing here is anonymous.

Outstanding job. In just one week, it felt as though we had been working together for over a month.

Jasper MiddendorpCTO, N1 Healthcare
N1 HealthcareLong-term contract, Aug 2025 – Feb 2026
Clinical intelligence platform, 10 modules
Contract and client review, public on Upwork
Expand HealthDirect engagement
Practitioner dashboard and triage layer
Appreciation certificate on file
Healthcare job marketplaceTeam engagement, under NDA
Two-sided marketplace, mobile app and recruiter portal
Screens available on request
DuggupFull-time
Founding design, web and mobile, v1.0 in five months
2,000+ users in week one
How I work[no process theatre]

How the work actually happens.

  • 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 did what forty charts could not.

    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-point checklist before it earned its final form. First versions are for learning, not framing.

    Eight experiments, one report
40 SIGNALS4 SCORES
01Forty charts, four scores
Skills and tools[datasheet]

What I reach for, and what I lean on.

Highlighted entries are the ones I would defend in an interview, not just the ones I have opened.

01Design
  • Product design
  • Design systems
  • Interaction design
  • Prototyping
  • User research
  • Information architecture
02Build
  • HTML / CSS
  • React
  • Framer
  • Directing AI coding agents
  • Shipping to production
03Tools
  • Figma
  • Figma Make
  • Claude Code
  • Cursor
  • Notion
  • TickTick
04Domains
  • Health tech
  • Clinical tools
  • SaaS
  • AI products

Core strength

Live on the internet[05 live]

Sites you can poke at right now.

Click any one to open it live, in a window, without leaving the page.

The lab[side quests]

The serious work is serious.
The side quests are not.

Built to see if it could work. Every one is live, and every one taught me something the client work couldn’t.

All experiments, including the month I shipped 19 sites in 19 days

Before you ask[07 answers]

The questions people ask after the call.

Answered here instead, so you can decide before spending half an hour finding out.

Say hello

Have a complicated thing to make clearer?

Tell me what is not working. If I am the wrong person for it I will say so, and usually point you at the right one.

dhrumil.kherde@gmail.com
Status
Open to work
Based
India · works remote, worldwide
Best for
Health tech · SaaS · AI products
Reply
Within a day, usually the same one