Ankit Gajera — home

Services

UI/UX Design

Interface and experience design for web and mobile products, from user flows through to production-ready screens.

Most products do not have a design problem, they have a clarity problem. I work out what the person in front of the screen is actually trying to do, then design the shortest honest path to it.

Typical timeline
2–6 weeks, depending on scope
Starting from
From ₹40,000

How it works

  1. Understand

    What is the product for, who uses it, and what are they trying to finish? I read whatever exists — analytics, support tickets, an old design file — before opening Figma.

  2. Map the flows

    The screens come out of the flows, not the other way round. This is where most of the thinking happens, and where changes are cheapest.

  3. Explore in low fidelity

    Several directions, deliberately rough. Polishing too early makes it hard to throw anything away.

  4. Design the real screens

    High fidelity, on a real type scale and spacing system, with the empty and error states designed rather than assumed.

  5. Hand over

    A documented Figma file with components and tokens, plus a walkthrough call so nothing is guessed at in implementation.

What you get

  • User flows for the core journeys
  • High-fidelity screens for every state, including empty and error
  • A component library with design tokens
  • Responsive layouts for mobile, tablet and desktop
  • A documented Figma file and a handover call

Common questions

How much does UI/UX design cost?
UI/UX design projects start at ₹40,000 and are quoted per project rather than per hour, so the price does not change if the work takes longer than expected. The figure depends on the number of screens and how much research is needed.
How long does a UI/UX project take?
Most projects run 2–6 weeks. A focused landing page can be done in two; a product with a dozen screens and real research behind it takes closer to six.
Do you work in Figma?
Yes. Every project is delivered as a documented Figma file with components and design tokens, so a developer can build from it without guessing at spacing or colour.
Can you build what you design?
Often, yes. Design and development can be quoted together, which usually produces a better result — it is harder to hand over something impractical when you are the one implementing it.