A good UI UX design process has seven steps before any code is written: research, user flows, wireframes, a clickable prototype, usability testing, a design system, and a clean handoff to developers. Each step produces something you can see and approve. If your agency jumps from a phone call straight to “here is the homepage design”, most of the process has been skipped, and you will pay for it later in rework.
Below, each step in plain terms: what happens, what you receive, how long it takes and what it costs in India, plus a checklist for judging an agency.
Why the UI UX design process matters more than the visuals
Most business owners judge design by the final screens: colors, fonts, photos. That is the UI part. The expensive mistakes happen earlier, in the UX part: structure, the order of steps, what the user sees first.
Take a diagnostic lab in Salt Lake building a booking app. If nobody asks how patients actually book tests, the app may demand a login before showing prices, and many visitors leave. A proper process catches that on paper, when a change costs an hour, not after development, when it costs a week.
We wrote more about the business side of this in how UI/UX design affects conversions. This post is about the how.
The 7 steps of a proper UI UX design process
Each step below ends with something you can review and sign off. Do not move to the next step until the current one is approved.
Step 1: Research and discovery
Research is where the designer learns your business, your users and your competitors. It does not need to be a three-month study. For most small and mid-size projects, one to two weeks is enough.
What usually happens:
- A kickoff workshop with you and anyone who talks to customers (sales, front desk, support).
- A review of your current site or app, analytics and any customer complaints.
- A look at three to five competitors, noting what they do well and badly.
- Short interviews with 4 to 6 real users or customers, where possible.
What you should receive: a short research summary, one or two user personas based on real people (not made-up “Priya, 28, loves coffee” profiles), and a list of goals for the product, ranked.
What you must provide: access to analytics, a list of common customer questions, and a few hours of your own time. Skip this and the same information comes out later, in the middle of design reviews.
Step 2: Information architecture and user flows
Next, the designer decides what goes where. Information architecture is the sitemap or app structure: which pages or screens exist and how they are grouped. User flows show the exact path a user takes to finish one task, for example “book a home sample collection” or “reorder last month’s groceries”.
For a coaching institute website, the key flows might be: find a course, check batch timings and fees, submit an enquiry. Drawn as boxes and arrows, problems show up fast, like a fee page four clicks deep or a twelve-field enquiry form.
What you should receive: a sitemap or screen map, and a flow diagram for each important task. These are cheap to change, so argue here, not later.
Step 3: Wireframes
Wireframes are grey-box layouts of each screen, with no colors or final images. The point is to agree on layout and content priority without getting distracted by visual taste.
A common mistake is to treat wireframes as a formality. They are the most useful review you will do. Ask questions like:
- Is the main action obvious within three seconds?
- What does this screen look like on a ₹10,000 Android phone with a small display?
- What happens when there is no data yet (empty states), or an error?
- Is the copy real, or is it lorem ipsum? Real headings change layouts.
What you should receive: low or mid-fidelity wireframes for every key screen, mobile first if most of your traffic is mobile, as it is for many Indian consumer businesses.
Step 4: Clickable prototype
Once wireframes are approved, the designer creates the visual design and links the screens into a clickable prototype, usually in Figma. You can tap through it on your phone as if it were a real app or website. Nothing is built yet.
This is where UI decisions get made: brand colors, typography, spacing, buttons, icons, imagery. A good designer checks color contrast and tap target sizes at this stage, so the design is readable in bright sunlight and usable with a thumb.
What you should receive: high-fidelity designs for all key screens, both mobile and desktop where relevant, connected as a prototype you can share with your team.
Step 5: Usability testing
Usability testing means watching real people try to complete tasks on the prototype, without help. You do not need a lab or a big budget. Jakob Nielsen’s well-known research at Nielsen Norman Group found that testing with about five users uncovers most usability problems, and that several small rounds beat one large one.
In practice, for a Kolkata restaurant ordering app, that could mean five regular customers, each asked to “order a biryani and two rolls for delivery to your office”. The designer watches where they hesitate, what they tap by mistake, and what they say out loud. Then the design is fixed and, ideally, tested again.
What you should receive: a short test report listing the problems found, how serious each one is, and what changed in the design because of it. If an agency says “we test internally”, ask what that means. Testing with your own designers is not usability testing.
Step 6: Design system and component library
Before handoff, the designer turns repeated elements into a small design system: buttons, form fields, cards, colors, type scale, spacing rules and icons, each with its states (normal, hover, disabled, error, loading).
Small projects often skip this. Then developers guess, and six months later your site has four slightly different blue buttons. With a system, new pages are faster to design and build.
What you should receive: a Figma component library with named styles and components. For larger products, short usage notes for each component.
Step 7: Developer handoff
Handoff is where design becomes a build plan. A proper handoff includes final Figma files with clear naming, exported assets, spacing and font specs, responsive behavior notes (what changes on tablet and mobile), interaction notes (animations, validation messages), and edge cases.
The designer should stay involved during development and review built screens against the design. Ask for at least one design QA round before launch, because small gaps like missing error states are common.
UX design process steps: timeline and deliverables at a glance
Timelines below assume one experienced designer working with quick client feedback. Slow approvals are the main reason design phases run late.
| Step | Main deliverable | Typical time (website) | Typical time (app MVP) |
|---|---|---|---|
| Research and discovery | Research summary, personas, goals | 3–7 days | 1–2 weeks |
| Information architecture and flows | Sitemap, user flow diagrams | 2–4 days | 1 week |
| Wireframes | Grey-box layouts for key screens | 4–7 days | 1–2 weeks |
| Visual design and prototype | High-fidelity clickable prototype | 1–2 weeks | 2–3 weeks |
| Usability testing | Test report and design fixes | 3–5 days | 1 week |
| Design system | Figma component library | 2–4 days | 1 week |
| Developer handoff and design QA | Specs, assets, QA notes | 2–3 days | 1 week, plus QA during build |
So a typical business website takes about four to six weeks of design. A mobile app MVP with 25 to 40 screens usually takes eight to twelve weeks. If you want to see how design fits into the full build, our guide to the mobile app development process covers what happens after handoff.
What UI/UX design costs in India
Prices vary a lot with scope, number of screens and how much research is included. As a rough guide, these are typical Indian market ranges, not fixed quotes:
| Project type | Typical scope | Typical range in India |
|---|---|---|
| Small business website | 8–15 pages, mobile and desktop | ₹40,000 to ₹1.5 lakh |
| E-commerce store | Home, category, product, cart, checkout, account | ₹80,000 to ₹2.5 lakh |
| Mobile app MVP | 25–40 screens, one platform style | ₹1 lakh to ₹4 lakh |
| SaaS dashboard or portal | 40+ screens, roles, data tables | ₹2.5 lakh to ₹8 lakh or more |
Freelancers often quote lower, which can work for a simple site. Cheaper quotes usually leave out research, testing and the design system. For full build costs, see our guide on website development cost in India.
How to judge a UI UX design company in Kolkata or anywhere in India
Portfolios all look good, and Dribbble shots say little about process. When you speak to a UI UX design company in Kolkata or elsewhere, ask:
- Can you show me wireframes and user flows from a past project, not only final screens?
- How do you do research, and who do you talk to?
- Will you test the prototype with real users? How many, and how is it reported?
- Do I get a component library in Figma, and do I own the files?
- Who answers developer questions during the build, and is design QA included?
- How many revision rounds are included at each step?
Red flags: a fixed price before anyone asks about your users, “unlimited revisions” (which usually means no clear process), and designs shown only as static images with no prototype.
Good UI/UX design services in India will happily walk you through their UI UX design process. If an agency is vague about it, there probably is not one.
Frequently asked questions
What are the main stages of the UI UX design process?
The main stages are research, information architecture and user flows, wireframes, visual design with a clickable prototype, usability testing, a design system, and developer handoff. Some agencies merge steps on small projects, but each one should still happen in some form.
How long does UI UX design take for a website?
For a typical business website of 8 to 15 pages, expect four to six weeks, including research and one round of testing. The biggest factor is how quickly you review and approve each step.
What is the difference between UI and UX design?
UX design is about structure and behavior: what the user needs, the order of steps, and how easy a task is to finish. UI design is the visual layer: colors, type, buttons and imagery. You need both, and the UX work should come first.
Can I skip usability testing to save money?
You can, but it is usually a false saving. Testing a prototype with five people takes a few days and finds problems that would cost far more to fix after development. If budget is tight, cut visual polish before you cut testing.
Do I own the Figma design files?
You should. Make sure your contract says the final design files and component library are handed over to you. This lets you change agencies or developers later without starting from scratch.
Start with the process, not the pixels
If you are planning a new website or app, ask for the process first and the visuals second. Our UI/UX design services follow the steps above, and our wider web design team can take it through to build. If you want to talk through your project and timeline, get in touch here.