UI Design
I design interfaces around the action each screen exists to drive, then hand off organized Figma files, components, and specs your developers can build without guesswork. You approve a clickable prototype before anything gets coded.
Interfaces designed for client teams, dashboards to storefronts
Replies within 24 hours, usually the same day
Work delivered for, or alongside, teams at:
What it costs
The floor covers a focused surface: a marketing site, a dashboard, or a product flow. Bigger scopes get quoted after we define the screens, never mid-project.
Multi-screen apps and full design systems are quoted after scoping the screen count.
All prices include GST.
How this runs
We name the one action each screen exists to drive and who takes it. Design decisions later get judged against this, not against taste.
You leave with: a screen list with a job per screen.
Structure and flow come first in low fidelity, so we argue about layout while it’s cheap to change. Nothing gets polished before the skeleton is agreed.
You leave with: approved wireframes for every screen.
High-fidelity screens get built mobile-first from a component library, with a style guide holding it all together. You click through a prototype, not a slideshow.
You leave with: a clickable prototype to approve.
Developers get organized Figma files, specs, exportable assets, and notes on states and edge cases. I stay available during the build so drift gets caught early.
You leave with: files your team can ship without rework.
I check the mobile layout before the desktop one, every time. Most of your users are on a phone, and an interface designed on a 27-inch monitor and squeezed down is why so many sites feel broken.
I refuse to decorate. If an element doesn’t help the user toward the screen’s one action, it goes, no matter how good it looks in a portfolio shot.
And because I’ve built what I’ve designed for years, I don’t draw things that are miserable to code. What you approve in the prototype is what your developers can actually ship.
— Gaurav
Before you write in
Not answered here? Ask directly and you will hear back within 24 hours.
Projects start at ₹40,000, and the price includes GST. The floor covers a focused scope like a marketing site or a single product surface: flows, wireframes, high-fidelity screens, a component library, a prototype, and developer handoff. Larger screen counts raise the quote, agreed before work starts.
All three. The principles carry across; the patterns differ. Dashboards need dense data kept legible, apps need touch-first flows, and marketing sites need conversion focus. I design for the medium’s real constraints, not one template for everything.
Organized, labeled Figma files, a component library with states and variants, a style guide, exportable assets, and notes covering edge cases. I stay reachable during the build, because handoff is where most designs quietly fall apart.
Usually, when the current interface buries the action, but I won’t promise a number from a design file. Design removes friction; measurement proves it. If you want the proof loop, pair the project with conversion optimization after launch and let the data speak.
Yes, and it’s often the better call. I audit where users struggle and where screens drifted apart, keep what works, and rebuild the rest into one consistent system. A redesign grounded in real usability issues beats a cosmetic refresh every time.
About me
2,000+ articles published under my own byline, and 5,000+ more elsewhere.
Content clients hire the writer, not an agency content mill.
I was a teacher before I was a developer. I taught mathematics to competitive-exam students, which is why I explain hard things plainly instead of hiding behind jargon.
What I am actually good at is the join: technical SEO, fast front-ends, and content treated as one system instead of three vendors blaming each other.
Describe the product or site and the screens that worry you. I’ll reply with how I’d scope it, the price for that scope, and a start date.
Replies within 24 hours, usually the same day
