I'm Rachit Elhance,
I'm Rachit Elhance,
I'm Rachit Elhance,
PRODUCT DESIGNER.
PRODUCT BUILDER.
PRODUCT ARCHITECT.
PRODUCT DESIGNER.
PRODUCT BUILDER.
PRODUCT ARCHITECT.
PRODUCT DESIGNER.
PRODUCT BUILDER.
PRODUCT ARCHITECT.
SCROLL
SCROLL
Designer. Builder.
Lifelong learner.
Designer. Builder.
Lifelong learner.
Designer. Builder.
Lifelong learner.
Hi, I’m Rachit.
A product builder with a design-first mindset and an engineering background. I work best close to the product, where ideas are still messy and decisions actually matter.
Over the last 5+ years, I’ve worked across startups and freelance projects, taking ideas from zero to usable systems. Most recently, I co-founded a HealthTech startup in India, where I designed the product, built internal systems, worked directly with hospitals, and shipped while resources, direction, and certainty were constantly shifting.
I’m strongest at turning ambiguity into structure. Designing systems that can be built, shipped, and used in the real world.
I spend an unreasonable amount of time with music. Albums end to end, songs on repeat, and the occasional guitar nearby. It’s how I reset and think.
The vinyl player here isn’t a gimmick. It’s just how my brain prefers to work ♪ ♫
Hi, I’m Rachit.
A product builder with a design-first mindset and an engineering background. I work best close to the product, where ideas are still messy and decisions actually matter.
Over the last 5+ years, I’ve worked across startups and freelance projects, taking ideas from zero to usable systems. Most recently, I co-founded a HealthTech startup in India, where I designed the product, built internal systems, worked directly with hospitals, and shipped while resources, direction, and certainty were constantly shifting.
I’m strongest at turning ambiguity into structure. Designing systems that can be built, shipped, and used in the real world.
I spend an unreasonable amount of time with music. Albums end to end, songs on repeat, and the occasional guitar nearby. It’s how I reset and think.
The vinyl player here isn’t a gimmick. It’s just how my brain prefers to work ♪ ♫
Hi, I’m Rachit.
A product builder with a design-first mindset and an engineering background. I work best close to the product, where ideas are still messy and decisions actually matter.
Over the last 5+ years, I’ve worked across startups and freelance projects, taking ideas from zero to usable systems. Most recently, I co-founded a HealthTech startup in India, where I designed the product, built internal systems, worked directly with hospitals, and shipped while resources, direction, and certainty were constantly shifting.
I’m strongest at turning ambiguity into structure. Designing systems that can be built, shipped, and used in the real world.
I spend an unreasonable amount of time with music. Albums end to end, songs on repeat, and the occasional guitar nearby. It’s how I reset and think.
The vinyl player here isn’t a gimmick. It’s just how my brain prefers to work ♪ ♫
What I Can Help With
What I Can Help With
Everything I can help with
Everything I can help with
Everything I can help with
Design & Interaction
UI/UX
Interaction design
Design Systems
Protopie
Micro-interactions
Design & Interaction
UI/UX
Interaction design
Design Systems
Protopie
Micro-interactions
Design & Interaction
UI/UX
Interaction design
Design Systems
Protopie
Micro-interactions
Build & No-Code
Framer
Wordpress
Shopify
No-Code Tools
Basic Frontend
Build & No-Code
Framer
Wordpress
Shopify
No-Code Tools
Basic Frontend
Build & No-Code
Framer
Wordpress
Shopify
No-Code Tools
Basic Frontend
Product & Systems
Product Architecture
Flows
Internal Tools
System Cleanups
Edge Cases
Product & Systems
Product Architecture
Flows
Internal Tools
System Cleanups
Edge Cases
Product & Systems
Product Architecture
Flows
Internal Tools
System Cleanups
Visual & Motion
Rive
Spline
Visual Prototypes
Micro-Interaction
Visual & Motion
Rive
Spline
Visual Prototypes
Micro-Interaction
Visual & Motion
Rive
Spline
Visual Prototypes
Micro Interactions
Visual & Motion
Rive
Spline
Visual Prototypes
Micro Interactions
Visual & Motion
Rive
Spline
Visual Prototypes
Micro Interactions
Operations & Ownership
Roadmapping
Stakeholder Coordination
Process Setup
Notion
Agile Workflow
Operations & Ownership
Roadmapping
Stakeholder Coordination
Notion
Agile Workflow
Operations & Ownership
Roadmapping
Stakeholder Coordination
Notion
Agile Workflow
Early-stage products
Early-stage products
Zero-to-one work, unclear requirements, fast iteration, and decisions that actually matter.
Zero-to-one work, unclear requirements, fast iteration, and decisions that actually matter.
Messy systems
Early-stage products
Untangling flows, edge cases, and half-built features into something usable and coherent.
Zero-to-one work, unclear requirements, fast iteration, and decisions that actually matter.
Messy systems
Untangling flows, edge cases, and half-built features into something usable and coherent.
Messy systems
Untangling flows, edge cases, and half-built features into something usable and coherent.
Scaling foundations
Scaling foundations
Design systems, internal tools, and product structure that won’t collapse as teams grow.
Design systems, internal tools, and product structure that won’t collapse as teams grow.
Scaling foundations
Design systems, internal tools, and product structure that won’t collapse as teams grow.
Experience
Experience
Roles where I built, shipped, and owned outcomes.
Roles where I built, shipped, and owned outcomes.
Roles where I built, shipped, and owned outcomes.
Mesdo
Director & Co-Founder
2024-2025
Mesdo
Director & Co-Founder
2024-2025
Mesdo
Director & Co-Founder
2024-2025
Stealth Startup
Product Designer
2023-2024
Stealth Startup
Product Designer
2023-2024
Stealth Startup
Product Designer
2023-2024
Devsnest
Product Designer
2022-2023
Devsnest
Product Designer
2022-2023
Devsnest
Product Designer
2022-2023
Bridge Athletic
UI/UX Designer
2022
Bridge Athletic
UI/UX Designer
2022
Bridge Athletic
UI/UX Designer
2022
iCeipts Techology
UI/UX Designer
2021
iCeipts Techology
UI/UX Designer
2021
iCeipts Techology
UI/UX Designer
2021
Freelance Experience
Freelance Experience
Projects where I helped teams ship, iterate, and simplify.
Projects where I helped teams ship, iterate, and simplify.
Projects where I helped teams ship, iterate, and simplify.
Nexdoc Ai
Product Designer
Nexdoc Ai
Product Designer
Nexdoc Ai
Product Designer
Korai Health
Framer Designer
Korai Health
Framer Designer
Korai Health
Framer Designer
Glitch.House
Creative Designer
Glitch.House
Creative Designer
Glitch.House
Creative Designer
DeliveRx
Product Designer
DeliveRx
Product Designer
DeliveRx
Product Designer
Censie Capital
Wordpress Developer
Censie Capital
Wordpress Developer
Censie Capital
Wordpress Developer
TradeFlo
Product Designer
TradeFlo
Product Designer
TradeFlo
Product Designer
001.
How do you usually approach a new product or problem?
I start by trying to understand what’s actually unclear. That usually means mapping the problem space before jumping into solutions: who the user is, what decision they’re stuck at, and what assumptions we’re making without realizing it. I rely a lot on simple artifacts early, flow diagrams, rough journeys, constraint lists, because they expose gaps faster than polished screens. I’m less interested in finding the “best” idea early and more interested in removing the wrong ones quickly.
002.
What kind of work do you enjoy most?
I enjoy work where the structure isn’t there yet. Early products, evolving systems, or teams that have grown faster than their process. That’s usually where small decisions have outsized impact. I like being in the phase where you’re deciding what not to build, what to simplify, and what needs to exist before anything else can work properly.
003.
Do you lean more toward design or execution?
Execution. Design is how I reason through problems, but execution is how I test whether that reasoning holds up. I’m comfortable starting with rough assumptions, shipping something imperfect, and then tightening it based on feedback and usage. Over time, I’ve found that momentum and learning matter more than correctness on the first pass.
004.
How has working on Mesdo shaped your perspective?
Mesdo taught me what breaks when theory meets reality. When you’re working with limited time, limited money, and real users, you quickly learn that clarity beats cleverness. I became more disciplined about prioritization, more direct in communication, and more careful about where complexity is allowed to exist. That experience made me calmer and more deliberate as a builder.
005.
How do you prefer to work with teams?
I work best with teams that value clear ownership and honest communication. I’m comfortable working async, documenting decisions, and making progress without constant check-ins. I tend to take responsibility for the shape of the work rather than just my slice of it, which usually helps teams move faster with less coordination overhead.
001.
How do you usually approach a new product or problem?
I start by trying to understand what’s actually unclear. That usually means mapping the problem space before jumping into solutions: who the user is, what decision they’re stuck at, and what assumptions we’re making without realizing it. I rely a lot on simple artifacts early, flow diagrams, rough journeys, constraint lists, because they expose gaps faster than polished screens. I’m less interested in finding the “best” idea early and more interested in removing the wrong ones quickly.
002.
What kind of work do you enjoy most?
I enjoy work where the structure isn’t there yet. Early products, evolving systems, or teams that have grown faster than their process. That’s usually where small decisions have outsized impact. I like being in the phase where you’re deciding what not to build, what to simplify, and what needs to exist before anything else can work properly.
003.
Do you lean more toward design or execution?
Execution. Design is how I reason through problems, but execution is how I test whether that reasoning holds up. I’m comfortable starting with rough assumptions, shipping something imperfect, and then tightening it based on feedback and usage. Over time, I’ve found that momentum and learning matter more than correctness on the first pass.
004.
How has working on Mesdo shaped your perspective?
Mesdo taught me what breaks when theory meets reality. When you’re working with limited time, limited money, and real users, you quickly learn that clarity beats cleverness. I became more disciplined about prioritization, more direct in communication, and more careful about where complexity is allowed to exist. That experience made me calmer and more deliberate as a builder.
005.
How do you prefer to work with teams?
I work best with teams that value clear ownership and honest communication. I’m comfortable working async, documenting decisions, and making progress without constant check-ins. I tend to take responsibility for the shape of the work rather than just my slice of it, which usually helps teams move faster with less coordination overhead.
001.
How do you usually approach a new product or problem?
I start by trying to understand what’s actually unclear. That usually means mapping the problem space before jumping into solutions: who the user is, what decision they’re stuck at, and what assumptions we’re making without realizing it. I rely a lot on simple artifacts early, flow diagrams, rough journeys, constraint lists, because they expose gaps faster than polished screens. I’m less interested in finding the “best” idea early and more interested in removing the wrong ones quickly.
002.
What kind of work do you enjoy most?
I enjoy work where the structure isn’t there yet. Early products, evolving systems, or teams that have grown faster than their process. That’s usually where small decisions have outsized impact. I like being in the phase where you’re deciding what not to build, what to simplify, and what needs to exist before anything else can work properly.
003.
Do you lean more toward design or execution?
Execution. Design is how I reason through problems, but execution is how I test whether that reasoning holds up. I’m comfortable starting with rough assumptions, shipping something imperfect, and then tightening it based on feedback and usage. Over time, I’ve found that momentum and learning matter more than correctness on the first pass.
004.
How has working on Mesdo shaped your perspective?
Mesdo taught me what breaks when theory meets reality. When you’re working with limited time, limited money, and real users, you quickly learn that clarity beats cleverness. I became more disciplined about prioritization, more direct in communication, and more careful about where complexity is allowed to exist. That experience made me calmer and more deliberate as a builder.
005.
How do you prefer to work with teams?
I work best with teams that value clear ownership and honest communication. I’m comfortable working async, documenting decisions, and making progress without constant check-ins. I tend to take responsibility for the shape of the work rather than just my slice of it, which usually helps teams move faster with less coordination overhead.