.svg){kind=icon}
.svg)
Take a Tour
From raw documentation to a clickable prototype using a structured, AI-assisted
workflow at every key step.
UXRS is a UX/UI design team that companies bring in to own the design side of a product. We take responsibility for how it's structured, how the flows connect and how the interface stays consistent while it keeps changing. The work we hand over is ready for development and made to grow with the product.
We work with SaaS platforms, mobile apps, dashboards, internal tools, marketplaces and enterprise systems, often products that got harder to manage as they grew. Some teams reach us with an early-stage MVP. Others run large products with hundreds of screens, several user roles and years of accumulated decisions. The job changes very little between the two: make the product clearer, make it consistent and get it ready for what comes next.
.svg)
What UXRS Actually Is?
.png){kind=avatar}
A focused team of 7 to 9 of UX researchers, UX/UI and brand designers, UX strategists, systems and design-system designers, and CX designers. Certified by the Nielsen Norman Group and the UX Design Institute. Our work builds on research from NN/g and the Baymard Institute. Based in Barcelona, working across Europe.
What we help with
- UX Audits & Reviews
- Product Redesign
- Web, Mobile & Desktop UX/UI
- Dashboards and Admin Panels
- Design Systems & Components
- AI Prototyping
- Branding & Visual
- Developer-ready handoff
- Claude and Figma to Code
Products we work on
- SaaS platforms
- Mobile apps
- Dashboards and analytics interfaces
- Internal tools and admin panels
- AI-powered products
- Marketplaces
- Healthcare and other regulated products
- Workflow-heavy and legacy systems
- Product and marketing websites
We work with teams at very different stages, from a founder shaping a first product to an enterprise untangling years of growth. What they have in common is simple: the product matters enough to get the design right and they'd rather hand that part to a team that will own it properly.
Founders building a first product
You have an idea, an MVP, or a half-built product, and you need it to feel like a real, considered experience before it reaches...
Show More
You have an idea, an MVP, or a half-built product, and you need it to feel like a real, considered experience before it reaches users or investors. Many of the founders we work with don't come from a design or tech background, so they hand the UX/UI to us and stay focused on the business.
Show Less
Product and SaaS teams
Platforms, dashboards, and workflow-heavy tools need design that keeps up as features pile on. We bring the UX/UI stru...
Show More
Platforms, dashboards, and workflow-heavy tools need design that keeps up as features pile on. We bring the UX/UI structure and the system underneath it, so the product stays usable and consistent as it grows.
Show Less
Engineering teams without a designer
Your product was built by developers and works well underneath, but the interface shows it. We step in as the design side y...
Show More
Your product was built by developers and works well underneath, but the interface shows it. We step in as the design side your team doesn't have in-house and prepare everything so it's straightforward to build.
Show Less
Enterprise and complex systems
Large products collect complexity over time: fragmented workflows, inconsistent screens, and interfaces built before the...
Show More
Large products collect complexity over time: fragmented workflows, inconsistent screens, and interfaces built before there was a design system to hold them together. We restructure the experience and put a proper system in place.
Show Less
Mobile app teams
You need a mobile product designed around how people actually use it, across devices, regions, and user types...
Show More
You need a mobile product designed around how people actually use it, across devices, regions, and user types. We design mobile UX built for real usage and ready to scale.
Show Less
AI product teams
AI products often pair powerful capability with an interface that struggles to explain it. We design the workflows, onboarding,...
Show More
AI products often pair powerful capability with an interface that struggles to explain it. We design the workflows, onboarding, and interface logic that make an AI product understandable and worth returning to.
Show Less
Teams in the middle of a redesign
A product that works can still feel dated, with an experience that no longer matches where it's heading. We handle t...
Show More
A product that works can still feel dated, with an experience that no longer matches where it's heading. We handle the refresh: restructuring flows, modernizing the UI, and bringing back consistency.
Show Less
Teams preparing to scale
The product is solid, but the design wasn't built to stretch. Before you grow further, we put reusable components, a...
Show More
The product is solid, but the design wasn't built to stretch. Before you grow further, we put reusable components, a design system, and a more maintainable UX foundation in place.
Show Less
Agencies and studios
You take on product work and need a design team behind you. We handle UX/UI, design systems, or full product desig...
Show More
You take on product work and need a design team behind you. We handle UX/UI, design systems, or full product design for your clients, under your name when that's what's needed.
Show Less
Marketing teams and product websites
A business website has to keep pace with the company behind it: clearer structure, stronger UX, and messaging that lands...
Show More
A business website has to keep pace with the company behind it: clearer structure, stronger UX, and messaging that lands. We treat the site as part of the product experience rather than a separate exercise.
Show Less
Most teams worry about the same things when they bring in an outside design team: chaos, endless revisions, and a handoff developers can't actually use. Our process is built to remove all three. Every project is different, but the shape stays familiar understand the product, structure the UX, design the interface, validate it, and prepare it for development. At any point you know what stage we're at and what comes next.
Product Review & Research
We start by understanding what already exists: the current screens, the workflows, the business goals, and where users get stuck. For existing products that usually means a UX audit; for new ones, product discovery and competitor research. We use heatmaps and AI-assisted analysis to surface friction quickly, then talk to the people who know the product best.
UX & User Flows
Before any visual work, we get the structure right navigation, user flows, screen hierarchy, and how the product should behave. The aim is a product that's predictable and easy to follow, mapped out in flows, wireframes, and low-fidelity prototypes you can click through.
UI Concepts & Visual Direction
With the structure settled, we move to the interface. Depending on the product, that's a full redesign, a visual refresh, or a more scalable UI direction, with branding when it's part of the work. We build a visual system that stays clear and consistent as the product expands.
AI Prototypes
For most projects we build clickable prototypes to test flows and present ideas before anything gets built. Stakeholders can review them, users can try them, and the team can make product decisions early, while changes are still cheap.
Design System
As a product grows, consistency is what keeps it manageable. We build reusable components, design tokens, and structured Figma libraries, so the product stays easier to maintain, extend, and develop instead of drifting out of sync screen by screen.
QA
Nothing reaches a client or a developer without passing three checks: a self-review against the brief, a second pair of eyes from the team, and an AI pass for accessibility, contrast, consistency, and UX logic. Clients increasingly run designs through AI themselves, so we do it first and fix what it finds before anyone else sees it.
Ready for Development
We design with development in mind from the start: organized Figma files, documented states, responsive behavior, and clear UI logic the team can build from. Where it helps, we stay involved through implementation, review the final screens, and support the team as the product goes live.
Throughout, we work in short cycles with clear checkpoints, so feedback lands at the right moments instead of all at once at the end. Some projects run from idea to UI in a few weeks; others involve deeper restructuring or a long-term partnership across releases. The process adapts to the product and the stage you're at, without losing its structure.
For a lot of teams, how a design team communicates matters as much as the design itself. A project can stall even when the work itself is fine, simply because no one can tell what's happening, what's decided, or what comes next. We put real effort into making sure that never becomes the problem. The work stays visible, documented, and easy to follow, whether you check in every day or once a week.
A workspace you can actually read
Everything lives in one organized place. Figma files are structured into clear pages and flows, components are named and reusable, states are documented, and the reasoning behind decisions is written down where the work happens. You should be able to open the project on any given day and understand what's ready, what's in progress, and why things were done the way they were.
Async by default
Most communication happens asynchronously, through Figma comments, Loom walkthroughs, and Slack. We record short walkthroughs to explain decisions and leave context directly on the designs, so the conversation stays next to the work rather than buried in a thread. That keeps the project moving across time zones and keeps your calendar mostly free of meetings.
Working across time zones
We're based in Europe, so European teams work in full overlap with us. For clients in the US and Australia, we keep a set window each day for live calls, and async covers the rest. You send feedback when it suits you, and there's usually progress waiting by the time you're back online.
Updates before you ask
We share work as it develops rather than going quiet until a deadline. You get intermediate results, short explanations of what changed, and a clear sense of where things stand. If something's unclear on our side, we ask early.
Honest about risk
A calm tone doesn't mean we just agree. If a decision adds risk to the timeline, the quality, or the product, we say so plainly, explain why, and lay out the options. We'd rather have the uncomfortable conversation early than let a problem reach production.
None of this is complicated, but it's often what decides whether a project feels calm or stressful. We treat it as part of the work.
These are real projects, chosen to show the kind of work we take on rather than a wall of screens. Across industries and product stages, the pattern repeats: a product that grew complicated or inconsistent, and a team that needed it restructured, modernized, and made ready to build on. If your situation looks like one of these, chances are we've solved something close before.
Banking software
UX/UI redesign and Design system
A company in banking software came to us with a developer-built product: solid underneath, but inconsistent across screens and missing any shared UI system. We restructured the experience, brought the interface into one consistent language, and built a design system the development teams could work from.
Enterprise email platform
Product UX and launch site
An enterprise client needed a desktop email platform for teams, in the territory of tools like Outlook. We handled the UX structure, a scalable Material Design–based UI system, and a landing page to present the product before development scaled further.
Crypto analytics platform
Enterprise dashboards
A crypto analytics platform was handling dense financial and operational data with no UX structure to support it. We rebuilt the experience around customizable data views and a UI system that could carry that level of complexity.
AI interview platform
SaaS, design system, SEO site
A startup building an AI-powered interview platform needed a large SEO-focused website, a scalable design system, and development-ready layouts to support long-term organic growth. We delivered the system and the site as one coherent product surface.
AI-generated MVP
Cleanup and product direction
A solo founder had generated their first screens and documentation with AI tools, but the product lost consistency and quality the moment it reached implementation. We restructured the flows, lifted the UI, and gave the product a clearer direction before it scaled.
Global nutrition app
Mobile UX at scale
Used across more than 90 countries, a nutrition app needed mobile UX that could adapt to different user types and keep working as the product grew. We designed it around real, everyday usage and long-term scale.
Premium healthcare website
Design language
A Swiss healthcare company wanted a premium web experience with strong visual consistency and a clearly defined design language across the whole presentation. We built that visual DNA and applied it end to end.
Social platform SaaS
Full redesign through development
A founder came to us with a working product that needed almost everything: UX restructuring, new features, a UI redesign, branding, and a scalable component system. Later stages moved into AI-assisted workflows and direct collaboration with development through GitHub.
Real estate platform
Desktop to mobile
A real estate platform wanted to move its users from desktop workflows into a mobile-first experience. We built clickable prototypes so stakeholders could validate the flows and product direction before committing to full UI and development.
Start a conversation
FAQ
It starts with a short look at your product and the problem you want to solve. From there we agree on scope, a first set of priorities, and how we'll work together. Most projects begin with either a UX audit of what exists or product discovery if you're starting fresh.
It depends on the scope and the state of the product. A focused MVP can take a few weeks; a full redesign usually runs over a few months; large enterprise products with many stakeholders take longer. We give you a realistic estimate once we've seen what we're working with, and we keep it updated as the project moves.
Pricing is based on scope. After a first conversation and a look at the product, we scope the work and propose either a project price or an ongoing arrangement, whichever fits better. You'll know what you're paying for before anything starts.
Both. Some teams bring us in for a single redesign, audit or MVP; others keep us involved across releases as the product grows. We'll suggest whichever model fits your stage and you can move between them as things change.
Feedback is built into the process at clear checkpoints, so we adjust as we go rather than saving everything for the end. Within the agreed scope, we iterate until the work is right. If a change expands the scope significantly, we'll flag it and talk it through before moving ahead.
Less than you might think. A link to the product, a Figma file, a Loom, or a short description of the problem is enough to start. Anything else, like docs, existing research or access to your team, helps but isn't required up front.
Yes and we usually do. We prepare organized, development-ready Figma files with documented states and clear UI logic, and we can plug into your workflow through Slack, your task tracker, and reviews during implementation. The aim is to make building straightforward, not to hand over files and disappear.
During active work you'll have regular contact and quick turnaround, mostly through Figma comments, Loom, and Slack. We share progress as it develops rather than going quiet between milestones, so you always know where things stand.
Often, yes. Many teams keep us involved after the first release to add features, evolve the design system, and support the product as it grows. If you only need a single piece of work delivered cleanly, that's fine too.
That's normal at this stage. You can start small, share the product and see how we think before committing to anything larger. We'll be honest about whether we're the right team for what you need, and if we're not, we'll say so.
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}