Service
We start by watching what people actually reach for, then build the shortest honest path to it.
Design that steps aside so people can do what they came to do.
Good UI depends on good UX, and good UX depends on actually knowing what your users are trying to get done. So we do the boring research first: usability testing, flow mapping, card sorts. That way the visual decisions rest on something real.
We work in Figma and put clickable prototypes in front of real users before anyone writes production code. It's the cheapest place in the whole process to catch a bad idea.
Moderated sessions and a look at your analytics to find where people actually get stuck.
Sitemaps and flows that make the shortest path the obvious one.
Clickable Figma prototypes, tested with real users before we lock the visual design.
Reusable components and their states, so design and engineering stay in sync once we hand off.
Contrast, focus order, and screen-reader checks. A real audit, not a checkbox.
We talk to real users and dig through analytics to find where the friction really is.
Flows and sitemaps that hold up before anyone styles a pixel.
Clickable prototypes in front of real users. Twice, if the first round surprises us.
A UI system engineering can build from without guessing.
Related work
Basin & Co. — Fintech Dashboard
A full UX overhaul that took a dense, spreadsheet-like dashboard and made it something a first-time user could read correctly in ten seconds.
Both, and we'd argue against pulling them apart. We can run a research-only engagement, but most projects go better when research and design run as one loop.
Figma, for design and prototyping. You get organized files at handoff, not a shared link and good luck.
Yes. A lot of our UX work is auditing or extending a system you already have rather than starting over.
Thirty minutes, no deck, no pressure. Just a straight conversation about what's working and what isn't.