1
Website redesign
A clearer structure and visual system for an existing site, so visitors can see what you offer and take the next step.
UI and UX Design
Interfaces designed so the next step is obvious
Guvantic designs websites, app screens and product dashboards. Each project includes the user flow, a clickable Figma prototype, and notes a developer can build from.
Designed in Figma, for phone screens first, then tablet and desktop.
Last updated
What does a UI and UX design project include?
A UI and UX design project plans how a product looks and how a person moves through it. That covers the flow, the layout, the components and a prototype your team can click through. Guvantic designs website pages, app screens and dashboards, then hands over a Figma file a developer can build from.
A clear screen does three jobs. It shows what this step is for, it makes the main action easy to find, and it still makes sense when something is empty, loading or wrong. We plan every screen around those three jobs.
What we build
Six types of design work we take on most often.
2
App screen design
Phone screens for the main job of the app, designed for one-handed use and the states a screen can be in.
3
Product dashboard
An internal or customer view of the numbers and actions people use every day, with less hunting through menus.
4
Design systems
Colours, type, buttons, forms and other components collected so later screens stay consistent.
5
Clickable prototypes
A Figma prototype of the agreed flow, so your team can try the path before development starts.
6
Handoff for a build
Specs, components and notes a developer can build from. We can also hand the design to our web development.
What every design from Guvantic includes
These are part of the standard build, not paid extras.
User flow
The path from the first screen to the action you care about, including empty, error and success states.
Phone layouts first
Screens are designed for the phone first when that is where people will use the product, then adapted for larger screens.
Figma prototype
A clickable version of the agreed flow, so reviews happen on a real path rather than on static pictures alone.
Design system
Shared components when the product has enough screens to need them, so new work reuses what already exists.
Conversion notes
The primary action on each screen is named, and competing actions are reduced so the next step is obvious.
Accessibility checks
Contrast, focus order, form labels and text size, with WCAG 2.1 AA as the target.
Developer handoff
Spacing, type and component notes in the Figma file, plus the assets the build needs.
Review rounds
A set number of review rounds, agreed in the scope, with comments kept in the file.
How a design project works
The timeline is agreed in writing after the discovery call.
1. Discovery call
Thirty to forty-five minutes. We ask who uses the product, what they are trying to do, and which screens matter first.
2. Flow and scope
We list the screens and the path between them, and agree what is in this round of design.
3. Wireframes
Simple layouts come first, so the structure can be approved before visual details are added.
4. Visual design
We apply type, colour and components, then turn the agreed flow into a clickable Figma prototype.
5. Review
Your team clicks through the prototype. We revise the items that are inside the agreed review rounds.
6. Handoff
You receive the Figma file, the component notes and the exported assets. A build can start from that file.
A redesign, a design system or a prototype
Each option suits a different starting point. We recommend the one that fits, even when it is the smaller piece of work.
| Option | Best for | Deliverable | Handoff | Main limit |
|---|---|---|---|---|
| Screen redesign | An existing site or app that is hard to use or looks dated | New layouts for the agreed screens | Figma file and notes | Does not include new features that were not in the flow |
| Design system | A product that will keep adding screens | Shared components plus example screens | Component library in Figma | Takes longer than designing one page on its own |
| Prototype before a build | A new flow you want to try before writing code | Clickable Figma prototype | Prototype and a screen list | It shows the path, not the finished software |
How to choose the right approach
A short guide to deciding when a design project is the right first step.
Design is the right first step when
- People get lost, drop off, or ask support how to finish a task
- The site or app will be rebuilt and needs a screen plan first
- More than one designer or developer will touch the product
- You want to approve the flow before development starts
A full design project is unnecessary when
- You only need a small text or colour change on a live page
- The layout is already approved and only code is left
- There is no user and no task to design for yet
- You need a logo or a brand name, which is a separate piece of work
Tools and platforms we work with
We design in Figma. A project can include FigJam for the early flow, wireframes, visual design, a clickable prototype, website layouts, app screens, dashboards and accessibility checks against WCAG 2.1 AA.
- Figma
- FigJam
- Design systems
- Wireframes
- Clickable prototypes
- Website layouts
- App screens
- Dashboards
- WCAG 2.1 AA
What a design project costs
Fixed scope and fixed price for the design. Ongoing screen work is billed monthly.
Website or app screens
The agreed screens, a clickable prototype and developer notes. Quoted in writing after the discovery call.
Design system
Scoped after we see how many products and screens must share the same components.
Design support
Monthly time for new screens and small changes after the first handoff.
Paid fonts, stock photos and prototype-tool seats are billed at cost and listed as separate lines in every quote.
What the handoff includes
The file should be enough for a developer to start without a second round of guessing.
- Every agreed screen has a desktop or phone layout, plus the states that screen can be in
- Colours and type are named so a developer does not have to guess
- Buttons, forms and repeated blocks come from components where a system is in scope
- The prototype covers the path you approved, including success and error states
- Open questions are listed in the file instead of being left in a chat thread
You own the design files
When the project ends, the Figma file and the agreed assets are in your hands.
- The Figma file is moved to your account
- You receive the component notes and exported assets in the scope
- Your team gets a walkthrough of the file
- Edit access is transferred to you
- Ownership terms are stated in the project agreement
UI and UX design at Guvantic: key facts
| Service | Website, app and product interface design |
|---|---|
| Provider | Guvantic (guvantic.in), India |
| Serves | Small and mid-size businesses in India, with remote delivery |
| Tools | Figma for wireframes, visual design and clickable prototypes |
| Included as standard | User flow, phone and desktop layouts, prototype, accessibility checks, developer handoff |
| Pricing model | Fixed price design quoted after discovery, monthly design support |
| Ownership | Figma file and agreed assets handed over to the client |
| How to start | Book a call at guvantic.in |
| Last updated | 23 September 2026 |
Guvantic is a technology company in India. We design and build websites, web apps, mobile apps, AI agents and automation for businesses. This page describes our UI and UX design service.
Frequently asked questions
Straight answers to what clients ask us before a project starts.
What is included in a UI and UX design project?
A typical project includes the user flow, the key screens, a clickable Figma prototype, and the notes a developer needs to build it. A design system is included when the product has more than a few screens. We agree the list of screens in writing before design starts.
Do you only design, or do you also build the product?
We can do either. Some clients want the Figma files and hand them to their own team. Others want Guvantic to design and then build the website or the app. The build is quoted separately when you want both.
How much does UI and UX design cost in India?
The cost depends on the number of screens, whether you need a design system, and how many rounds of review are included. Website redesigns, app screens and dashboards are quoted after a discovery call. Paid fonts, stock photos and prototype tools are listed separately.
How long does a design project take?
The timeline is set in writing after the discovery call. It depends on the number of screens and how quickly your team reviews them. We set review dates at the start so the work does not sit waiting for feedback.
Will I be able to click through the design before development?
Yes. We deliver a clickable Figma prototype of the agreed flows, so you can try the path a customer would take before any code is written. Comments stay in the Figma file so the notes are next to the screen they refer to.
Do you design for both websites and mobile apps?
Yes. We design website pages, app screens and product dashboards. Phone screens are designed first when most of your visitors or users are on a phone. Desktop and tablet layouts follow from the same components.
What is a design system?
A design system is the shared set of colours, type, buttons, forms and other components used across the product. It keeps new screens consistent and gives developers pieces they can reuse. We add one when the product will keep growing after the first release.
Can you redesign a site without losing what already works?
Yes. We start from the pages and flows people already use, then change the parts that cause confusion or drop-off. If the site also needs new code, that build is scoped with our web development service, including redirects for any URLs that change.
Do you design for accessibility?
Yes. We check contrast, focus order, labels on forms and text size so more people can use the product. WCAG 2.1 AA is the target. The checks are noted in the handoff so the build can keep them.
Who owns the design files?
You do. The Figma file is transferred to your account, along with the component notes and any exported assets agreed in the scope. Ownership terms are written into the project agreement before work begins.
What do you need from me to start?
We need the job the screen should do, who will use it, and any brand colours or logo you already have. Examples of products you like are useful, but not required. A short discovery call is enough to start, and we send a written scope afterward.
Tell us which screens to start with
Book a 30 minute call. We will ask who uses the product and what they need to finish, and tell you honestly which design scope makes sense.
Book a callOr write to us at info@guvantic.in or call +91 90278 65224.