Audience research
Interviews, behaviour analysis and a read of the data you already have. Before designing, we understand who buys and what blocks the purchase.
Service
UX Research and UI Design
Every interface decision starts from data, not guesswork. We research audience and competitors, prototype, and validate with real users before a line of code is written.
Most of the rework on a new store starts with a screen designed in the dark: someone decided by taste, the team built it, and three months later the data shows the path was another. We flip the order. Getting it right in Figma costs less than fixing it in production.
Book a 30-min conversationWhat this service covers
Deliverables that work together or separately, depending on where your brand stands.
Competitor analysis
A map of what reference brands do well and where they leave a gap, reading features and journey, not just aesthetics.
Information architecture
Taxonomy, navigation and content hierarchy defined before the screen. Findability is what separates a catalogue from a store.
Clickable prototype
Critical flows prototyped and clickable, so the journey is tested with real people before any development.
Responsive interface
Design built for conversion on desktop and mobile, with attention to contrast, legibility and accessibility.
Documented handoff
An organised delivery for the development team, with components, states and rules described. Nobody has to guess.
How we work
A clear method. A partner who stays when execution starts.
Data before screen
No interface decision goes in without a reason that can be explained. Personal taste is not an argument.
Testing with real users
We validate with people who buy, not with people who work on the project. Five right people reveal more than a meeting of twenty.
Prototype before code
Adjusting in Figma costs hours. Adjusting in production costs sprints and the team's patience.
Accessibility from the start
Contrast, visible focus and semantic hierarchy go into the design, not as a fix after go-live.
Documentation that survives
The handoff is written for whoever maintains the store a year from now, not only for whoever builds it today.
Frequently asked questions
How long does the research take?
Two to four weeks, depending on catalogue size and how many customer profiles there are. You get the findings and the prioritisation at the end of that period.
Do I need data ready to start?
No. If you have analytics, heatmaps or support history, we use them. If you do not, we start with instrumentation and interviews.
How many users do you test with?
Usually five to eight per profile. That is the point where the serious problems have already shown up and extra sessions return less.
Does the design work on any platform?
Yes. The design accounts for the limits of the platform you use, whether VTEX, Shopify, Nuvemshop or Olist.
Do you also develop?
Yes. If it makes sense, the same squad continues into development, which removes the classic noise between design and code.
How do I know it worked?
We define the metric first: conversion rate, drop-off at a specific step, or task completion in testing. We compare against the baseline.
Want to understand how this applies to your brand?
Tell us about your operation. We will say honestly what can be delivered and how long it takes.
Get in touch