UI/UX and product design, tested before it is built
We research how your users actually work, then design the flows, interface system and prototypes your engineers can build from directly. Accessibility to WCAG 2.2 is part of the design review, not a separate audit after launch.
What we deliver
Scoped in the 48-hour proposal, priced as a fixed quote or a monthly team.
User research
Interviews, usability tests and analytics review, to find where people struggle before design decisions are made.
Journey and flow mapping
Task flows and service blueprints that show each step, decision and handoff for your users and your staff.
UI design system
Components, tokens and states in Figma that developers can map directly to code.
Interactive prototypes
Clickable prototypes of the key flows, tested with real users before development starts.
Accessibility review
Colour contrast, keyboard navigation, focus order and screen reader checks against WCAG 2.2.
Usability testing
Moderated sessions with your target users, recorded and summarised into a prioritised list of fixes.
Design handoff
Specifications, redlines and asset exports, plus a review of the built screens against the approved design.
How we run product design projects
- 01
Reply in 4 hours
We reply within 4 hours during IST business hours and ask about your users, your current analytics and any existing product material.
- 02
Proposal in 48 hours
The proposal sets out research questions, design scope, the flows in scope and a fixed quote for discovery and design.
- 03
Prototype in 7 days
A clickable prototype of the main flows, so you can test the idea with users before committing to build.
- 04
Two-week sprints
Design work runs in two-week sprints, each ending with reviewed screens and a summary of usability findings.
- 05
Weekly handoffs
Developers receive updated components and specifications each week, so design and build move together rather than in phases.
Stack
Chosen per project. See the full stack.
- Figma
- FigJam
- Maze
- Hotjar
- Miro
- Storybook
- Tokens Studio
- Adobe Illustrator
- Framer
- Lottie
- axe DevTools
- Stark
What you can expect
- Decisions based on observed user behaviour rather than opinion in the room.
- A component library that keeps screens consistent as the product grows.
- Accessibility issues found during design, where they are cheaper to fix than after development.
- A prototype that has already been tested before engineering time is spent on it.
Questions buyers ask us
Something else? Ask us directly. First reply within 4 hours.
Do we need research before we design?
Not always, but it usually saves rework. For a new product we start with short interviews and a review of any existing analytics. For an established product we focus on the flows that are causing drop-off. We agree the scope in the proposal.
Can you redesign an existing app or website?
Yes. We start with an audit of the current experience, then redesign the flows in priority order, so improvements can be released in smaller steps. Existing brand guidelines are followed where they exist.
Do you design for Indian users and multiple languages?
Yes. We design mobile-first for the networks and devices common in India, and we plan for text expansion and right-to-left layouts where a product needs them. Indian scripts such as Malayalam and Hindi can be checked for line height and font rendering with real content.
Will the design be accessible?
We check colour contrast, keyboard use, focus states and screen reader labels against WCAG 2.2 during design, and again on the built product. Accessibility sign-off is a stated deliverable, not an optional extra.
Who owns the design files?
You do. Figma files, component libraries and research notes are handed over at the end of the engagement, and we set up the file structure so your team can carry on without us.
Tell us what you need shipped.
Send a short brief. You get a written proposal with scope, stack, timeline and a fixed price within 48 hours.