UI/UX design

A UI UX design agency that tests with your users before developers build

We interview and test with the people who use your site or product, then hand your developers designs that have already been tried on them.

Get your design review
Trusted by the world's fastest-growing brands

Portfolio · selected work

The work, not the deck.

Every site below is live, client-owned, and shipping revenue. Each cleared our Core Web Vitals gate.

Categories we work across
HospitalityFinancial servicesManufacturing and exportConsulting and researchRecruitmentD2C
urjalifes.inUrjalife's Pravaah resort website: rooms, activities and dining across a photographic homepage.
UrjalifeHospitality
adventswealth.comAdvents Wealth website: a financial planning homepage covering wealth building, tax and retirement.
Advents WealthFinancial services
syounaa.inSyounaa website: a wellness apparel storefront built around smart-textile product ranges.
SyounaaWellness apparel
infokool.comInfokool website: a precision cooling manufacturer, with an outdoor cabinet product grid and capability sections.
InfokoolManufacturing
howardjohnsonhinton.caHoward Johnson Hinton website: a mountain-lodge hero over a room-booking bar, followed by renovated room types.
Howard Johnson HintonHotel
sycamoreconsultant.comSycamore Consultancy website: a recruitment agency, with separate paths for employers and candidates.
Sycamore ConsultancyRecruitment
stutiexports.comStuti Exports website: a technical fibers and specialty yarns exporter, with core markets and capability sections.
Stuti ExportsTechnical textiles
duhomespg.inDuhomes website: student housing, with walking distances to nearby colleges and a room rate table.
DuhomesStudent housing
vaspro-global.comVasPro Global website: a technical advisory and project consulting firm, with expertise and mission sections.
VasPro GlobalConsulting
pretor.aePretor website: a marketing research and promotion consultancy, opening on research, strategy and growth planning.
PretorMarketing research

What UX design covers

Three questions that decide the design

A UI UX design agency answers three questions before it draws a screen: who is using this, what are they trying to do, and where do they get stuck. The answers come from your users, and the designs follow from them.

Journey map · Book a first visitWhoNPNew patientWeighs insurance and cost4 testedTask1234567Stuckat step 3FixTwo plain buttons replace the toggle

Who is using it

We talk to the people who book, buy or log in, in short interviews. What they say about how they decide and what worries them shapes the pages before any layout is drawn.

What they’re trying to do

We list the few tasks that matter, such as booking a first visit, and map the steps each one takes. Fewer steps and clearer labels come from that map.

Where they get stuck

We watch people use the current site or a prototype, and record where they hesitate or fail. A fix is drawn, then tested again on new people.

How design starts

Design that starts from your users

Two ways to begin a design. Both end in screens; they differ in what the first screen is based on.

Brief firstStarts from a briefResearch firstStarts from your users
The starting pointA written brief and the team’s own knowledge of the usersInterviews with your customers and a test of the current flow
StructureMenu set from the team’s own knowledgeMenu labels and groupings tested on people before they are designed
Review of the designStatic screens that stakeholders reviewA clickable prototype that a handful of users try, with the failures recorded
HandoffStatic exports with a written specA Figma file with components, variables and notes developers can inspect
After launchCompared against the project goalsTask success and analytics events compared with a baseline
Why we start with users

A few users tested early can show which assumptions are wrong before screens are built.

The standards

Six facts behind our research and design choices

Testing research and the WCAG 2.2 rules a design is held to, with the source under each.

  1. Test sizeNN/g

    Five test users find most of the usability problems in a round.

    Jakob Nielsen reports that one user uncovers about 31% of the problems and five uncover about 85%. He advises several small tests, such as three rounds of five, with a redesign between them, over one large test.

  2. Different usersNN/g

    Distinct groups of users need their own testers.

    The same article makes an exception for sites with several highly distinct groups of users. For two groups it suggests 3 or 4 testers from each, and 3 from each when there are three or more groups. A patient site has new and returning patients.

  3. SuccessNN/g

    Success rate is the share of users who complete a task.

    NN/g calls it easy to collect and very telling. It suggests recording levels of success, such as complete, with minor issues, with major issues and failed, labeled in words, and warns against averaging numbers assigned to those levels.

  4. StructureNN/g

    Card sorting finds groupings; tree testing checks them.

    NN/g describes card sorting as generative, because it shows how users group topics, and tree testing as evaluative, because it checks whether users can find items in a proposed hierarchy. A small qualitative round gives insight; a larger quantitative round gives statistics.

  5. Tap targetsW3C

    WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels.

    Success criterion 2.5.8, at level AA, says the size of a pointer target is at least 24 by 24 CSS pixels, with exceptions that include undersized targets spaced apart so their 24-pixel circles do not overlap, inline links and controls the browser sizes.

  6. ContrastW3C

    WCAG 2.2 AA asks for 4.5:1 contrast on text and 3:1 on controls.

    Criterion 1.4.3 sets a contrast ratio of at least 4.5:1 for text, or 3:1 for large text, with exceptions. Criterion 1.4.11 asks for 3:1 for user interface components and graphical objects against their neighbors. Both sit at level AA.

The scope

What the six parts of the design work hand you

Six parts. Each ends in something your team can open and use.

Research with your usersRound 14 of 8Current-flow testbooked a first visit unaidedNew patientsP1BookedP2StalledP3BookedP4StalledReturning patientsP5StalledP6BookedP7BookedP8Stalled

Research with your users

Short interviews with customers or patients, and a test of the current flow with people who match your audience. We recruit from your own customer list where we can. You receive: a findings report that ranks the problems by how many people hit them.

InterviewsUsability tests
Information architectureTree testTaskFind insurance informationProposed menuHomeServicesPatientsBook a visitInsuranceSteps to find itToday5Proposed2

Information architecture

The menu, the page groupings and the labels, checked with a card sort or a tree test before any page is designed. You receive: a sitemap with the label for each page, and the task flows for the actions that matter.

Card sortTree test
Wireframes and prototypeReady to testWireframePrototypeOn tapBook a visitNew to our office?New patientReturning patient

Wireframes and prototype

Low-detail wireframes to agree the layout and the order of each screen, then a clickable prototype in Figma that people can use on a phone. You receive: the wireframes and the prototype link, to approve before visual design.

WireframesFigma
Design system handoffReady for devButtonBook a visitBook a visitBook a visitDev ModeButton / PrimaryVariablescolor/action/bgspace/inset/md16radius/control8

Design system and handoff

Components built once in Figma, with variables for color and spacing, then marked ready for developers to inspect in Dev Mode. You receive: the Figma file in your account and a handoff guide naming each component and its states.

ComponentsVariables
Design accessibility checkWCAG 2.2 AAChoose a timeTue, Oct 138:30 a.m.10:00 a.m.11:30 a.m.Continue1234511.4.3≥ 4.5:1Text contrast22.4.7Focus visible32.5.824 × 24Target size41.4.11≥ 3:1Non-text contrast52.4.11Focus not obscured

Accessibility in the design

Contrast, focus states and tap-target size set in the design, against WCAG 2.2 AA criteria 1.4.3, 1.4.11, 2.4.7, 2.4.11 and 2.5.8. You receive: a design accessibility check listing each criterion and its result.

WCAG 2.2 AAContrastFocus
Measuring the changeBaseline set41%Completion ratebooking_complete ÷ booking_startGA4 · last 30 daysbooking_start1,240booking_complete512After releaseNot read yet

Measuring the change

A baseline taken before the change: task success from testing, and analytics events for the steps of the key flow. The same measures are read after release. You receive: a measurement plan listing each event and how it is counted.

Task successGA4 events

How it runs

Research, structure, prototype, hand over and measure

Research, structure and prototype each end with your approval and a document you keep.

research-plan.csv

Research plan

Sample · Sample Dental Center
MethodWhoHow manyAnswers
InterviewsPeople who booked a first visit lately5How they chose, and what worried them
Usability test, current flowNew patients4Where first-time booking stalls
Usability test, current flowReturning patients4Where rescheduling stalls
Review of booking eventsSite analyticsThe past 30 daysWhere visitors leave the flow
Two groups of 4 follows Nielsen Norman Group’s advice of 3 or 4 testers per distinct group. Total testers: 8. In the current-flow test, 4 of 8 booked a first visit unaided.

Our stack

The tools for research and handoff

Named, so you know what the work is made in and where it ends up. Each is listed with the part of the design process it serves.

Figma
Why Figma

Figma is a design tool where screens, components and prototypes are built and shared in the browser.

How we use it

We build the wireframes, prototype and components in Figma, in a file that moves to your account, and mark components ready for developers in Dev Mode.

Real-timeDev handoffTokens
FigmaYes
SketchSome
Static mockupsNo

Questions

UI/UX design, answered

Start here

Get a review of how people use your design

Send us your site or product, and tell us what you want people to do there. We’ll walk the key task as a first-time user, note where it stalls, and tell you what we’d test first.