Designing
products
people love.
4 years shipping B2B and B2C products people keep coming back to. I do the research, the systems, the pixels — and the code. One less person in the chain.
01 / Work
Selected Work
End-to-end product design across B2B and B2C SaaS — from research to shipped product.
MyHormonz
Hormone health platform — 3 surfaces designed from scratch in 45 days. The core challenge was making clinical data feel approachable to people who aren't doctors.
Kamelion
Teen wellbeing app, sole designer. I designed how the product logic actually works — when to show what, how personality tests feed into content, what gets unlocked when. It's live on both stores.
Quantive Results
Adobe needed to see OKRs they didn't own. The platform had no concept for that. I designed one — from discovery to handoff in 7 days — that separated visibility from accountability.
Quantive Signals
Analysts were screenshotting charts and pasting them into Slack to discuss anomalies. I brought the conversation back into the tool — in-chart annotations anchored to the actual data.
02 / About
Design is the easy part. Getting it shipped right is the job.
I'm Suryansh. I've spent 4 years building products across B2B and B2C — OKR platforms, health apps, analytics tools, a teen wellbeing app. Enough variety to know that the design problems are usually the same, but the context is everything.
At some point I got tired of handing off Figma files and watching things come back wrong. So I learned to build. Now I use Claude Code to take my designs into actual code — which means fewer translation errors and a much shorter distance between what I designed and what users see.
I ask a lot of questions before opening Figma. Who is this actually for? What are they trying to do? What's the thing nobody's said out loud yet? Five minutes of that usually saves a week of revision.
Skills
Looking for a full-time role where design has a real seat at the table. Also open to freelance if the project is interesting enough.
03 / Expertise
What I actually do.
Not just wireframes — research, systems, and sometimes the code itself.
Product & UX Design
From the first rough user flow to the final polished screen. I start with research because designing without it is just guessing. I talk to real users more than most designers would say is necessary.
Design Systems
The unglamorous work that makes everything else faster. I build design systems that engineers actually use — mostly by making components match how code works, not how a mood board looks.
AI-Assisted Development
I use Claude Code to turn my own designs into working front-end code — this portfolio is built with it. It's not magic, you still need to know what you're doing. But it cuts the handoff in half.
UX Strategy & Leadership
Running crits, helping junior designers develop taste, and saying the thing nobody else wants to say — like when a feature doesn't actually solve the problem. Leadership in design is mostly about creating space for the team to do good work.
04 / Process
How I work.
Roughly in this order. Sometimes I skip ahead. Sometimes I go back.
Discover
Lots of questions before I open Figma. What are people actually trying to do? What does success look like? Who has context I don't?
Define
What's actually the problem — not the symptom they described, but the real thing underneath it.
Design
Flows first, then UI. I don't go high-fidelity until the structure is right, or I end up redoing it.
Build
With Claude Code I take my own designs into working front-end. Fewer translation errors. I stop hiding behind "that's an engineering thing."
Iterate
Ship, watch what happens, fix the things that were wrong. Most of what I learn, I learn here.
Discover
Lots of questions before I open Figma. What are people actually trying to do? What does success look like? Who has context I don't?
Define
What's actually the problem — not the symptom they described, but the real thing underneath it.
Design
Flows first, then UI. I don't go high-fidelity until the structure is right, or I end up redoing it.
Build
With Claude Code I take my own designs into working front-end. Fewer translation errors. I stop hiding behind "that's an engineering thing."
Iterate
Ship, watch what happens, fix the things that were wrong. Most of what I learn, I learn here.
Most design problems turn out to be communication problems. Someone didn't ask the right question early enough, so now we're redesigning the wrong thing beautifully.
— My approach to product design
05 / Who I help
Who I work best with.
Startups
Pre-seed to Series A
You've got the idea and maybe some funding. Now you need something real to put in front of users. I help you get there without spending three months designing something that misses the point.
- Zero-to-one product design
- Fast iteration cycles
- Lean design systems
Product Teams
Scale-ups & growth stage
You have a product and a roadmap but not enough design bandwidth. I slot in, pick up context fast, and ship — whether that's IC work on a feature or helping the team get better at what they do.
- IC or lead capacity
- Design system scaling
- Cross-functional collaboration
Founders & Builders
Solo or small teams
You need something working, not a 40-page deck of mockups. I design it and build it — which is faster than coordinating between two people who've never talked to each other.
- Design + development
- AI-assisted workflow
- Direct, async collaboration
Common project types
06 / Contact06 / Contact
Got something
to build?
I'm looking for a full-time role where design has a real seat at the table. Also open to freelance work if the project is interesting enough.