Sachin Barnwal

I cut through the noise to design products that serve the people using them and the business paying for them.

(01) Approach

I take unclear requirements and turn them into products people actually use.

Users and the business sometimes want different things. I stay on the problem until one design works for both.

01 / 02Product Redesign · FintechFinvasia · In development

One overloaded landing screen, split in two: Home for the user’s own money and what they can do next, Market for what the market is doing.

02 / 02AI Product · EnterpriseDigiMantra · Cloudwick

A review layer for generative AI extraction, built for people who don't know what a prompt is.

Generated cover. Screens to come.

The index has all nine projects, drafts included

A requirement becomes a walkable prototype in a day, and the team agrees on the product before I draw a screen.

Stage 01 · Gaps
Catch the gaps before a design tool opens
I run the requirement through Rovo first. It flags the missing flows and unstated edge cases I used to find in design reviews.
Stage 02 · Structure
Structure the screens before designing them
An AI pass breaks the requirement into screens: what each holds and how it connects to the next. I don't make structural and visual decisions in the same sitting.
Stage 03 · Prototype
A working prototype, same day
Figma Make turns the structure into something clickable. Product, engineering and business walk the same flow in one meeting, before I open Figma.
Stage 04 · Copy
Copy that sounds like the brand
UX copy comes from an AI project loaded with the brand guidelines and product docs. I check it. I don't rewrite it.
Stage 05 · System
Hand the design system to Codex
The system lives as structured variables. Codex drafts new screens from it, and I review and adjust instead of starting from a blank canvas.
Stage 06 · Research
Run research alongside
AI pulls research and stress-tests my assumptions, and generates variations so I choose between options instead of defending my first idea.